I just finished my first attempt at using the rehost tool. Went pretty good. The first time I got it to start, it ran successfully all the way through. (It won't start if you have spaces in the path name, ex. "Rehost Tool 2.0").
Technically this might not be a totally fair test just because of the number of manual steps I took before actually running the rehost tool.
Here are the steps that I took:
- Setup two new Windows 2012 R2 servers (R2 is technically not supported, I know, but it works fine.)
- Installed all available Windows updates
- Installed SQL 2012 on one of them.
- Installed all available SQL updates (SP2)
- Created a backup up the Windchill database from the production SQL server
- Imported the Windchill database on the development SQL server
- Used robocopy to mirror the filevault from production to development
- Used robocopy to mirror the entire PTC folder structure from production to development
- Copied the Windchill shortcuts from production to development
- Deleted \PTC\Windchill_10.2\Java
- Installed the latest Java 7 SDK to \PTC\Windchill_10.2\Java
- Configured WindchillDS to start as a service (DS control panel)
- Configured Apache to start as a service (built-in ant scripts)
- Configured Windchill to start as a service (built-in ant scripts)
- Ran the rehost utility in 'Clone' mode. Used the following modules:
- InfoEngine
- Database
- Apache
- IEAdapter
- WVSAgent
At this point I started up the server. I knew there would be an issue with the remote file server (I didn't want to clone that). After everything started up I manually deleted the remote file server from the site and restarted again. Everything came up clean with no errors in any of the logs. Nowhere can I find any references to the old system, so it seems like the rehost utility did it's job.