When you load Unity, you have to connect to the AD directory, etc. The way mentioned above is implying that you are install the same Unity version on the NEW unity server with the NEW OS. For example, if you are running Unity 4.2 on the old server, you can install 4.2 on the new server THEN do an inplace upgrade to 5.x.
The way I prefer to install Unity servers now, if it permits, is to use Cobras Tool. You can install your new server, 2003, and Unity 5.x. Then use COBRAS to extract everyone and everything out (with exceptions) then import them into the new Unity server. You will need to rebuild a few things, but it's a great tool I think. Although not TAC support yet, Im assuming by late summer it will be because of the push of Unity 7.x.
The other way is using the Globals Subscriber Manager. You can network the old and new Unity servers, and move subscribers at your leisure. Use Cobras to migrate the Call Handlers and you are set to go.
DIRT of course is the safest and recommended way.
process in short:
- build your new Unity server with platform disc.
- Add to domain
- install Unity 4.2, same SQL version everything the same as the old server. (server names can change, thats ok and IP address if needed)
- DIRT backup old server
- DIRT restore into old server DIRT basically matches the Alias of the Subscriber and looks for a match. If it finds it, links everything up for you. (does not create new AD and Exchange accounts if there is a match)
- check your integrations, etc.
- inplace upgrade to 5.x
- Unity MS patches
Remember to bring over your old License from the 4.2 server. you will need to have licensing@cisco.com *rehost* your old 4.2 license to the new MAC address of your new server. On top of that, you will need to register the 5.x upgrade PAK key with the new server.
hope this helps
