Hi, We do a lot of migration like this in Colombia, like:
- Solaris to Linux same master server name
- Solaris 8 to Solaris 10 Master server name changed
- Solaris 10 single master server to Solaris 10 in Cluster
- Master Server in Windows to master server in Linux same master server name
- Master server in Solaris to Master Server in Linux Same name and different Name,
- Catalog merge between two and three different NBU domains,
To be sure of the process I suggest to you:
- No change the Master Server name,
- Do an Image catalog conversion with a tool that change file from Linux to Windows,
- I prefer not have devices configured inside the master server as a good practice and before the migration process,
- If you have few policies recreate them, if not is you have a lot of them try to convert the content inside the class directory, and transfer to the new server,
- for simplicity it's better to create a new EMM in the new master server, and manage the historical volume data in a Excel file, try to have additional cartridge to support your operation,
- If you want to transfer the EMM you will have to create symbolic links to the EMM previous route from linux to windows, that's the most difficult (but no impossible to do); that's tricky but works,
- If you are able to replicate the environment in virtual machines you can practice de migration process.
I'm going to look inside my company if I'm able to share the procedure (It's in Spanish) that We use for that migrations, but I'm sure if I'm able to.
Best regards,
