I am hoping soemone can help me here. I am in the process of migrating users from Unity 4.0(5) to Unity 5.0(2). My proposed plan is as below:
1. Build new Unity 5 Servers on new hardware (new IP address & Hostname).
2. Run ADSchema Update on Customer AD & create new install accounts for Unity 5.
3. Install new server and integrate into Exchange 2003. This is the same Exchange Server as the older Unity 4 box.
This is pretty straight forward but what I was wanting to do then was allow users currently using the Unity 4 Server to be able to dial into the Unity 5 server to record Outgoing messages & change PINs. However, to do this I believe their accounts must exist on the Unity 5 Server ?
Is there a way I can do this as before we migrate all users off Unity 4 we want to carry out this recording activity without stopping them using Unity 4. Once they have recorded their messages and changed PINs we would them migrate the users onto Unity 5.
So to summarise, I suppose what I want to know is it possible to import User accounts to Unity 5 without disrupting the service on the Unity 4 Server ? Then migrate users off Unity 4 to Unity 5.
Any suggestions to how this can be done would be much appreciated.
Yes, COBRAS will call the DirSync service on Unity when creating new users - the dir synch service will either create a new AD account for that user or bind them to an existing AD account (i.e. "point" them at the Unity server) if it finds a match on the alias/UID in the directory.
In a situation like this some bigger sites use COBRAS to get a backup then GSM to move the users and then follow up with a COBRAS import on the new box to update those users with more data (COBRAS gets much more data than GSM does). The advantage of this is GSM takes care of deleting the user on the old box for you and forcing a sync of the directory on both boxes to update the global subscriber tables.
If you're going to go "COBRAS only" that's fine, but after you run the bulk delete you may need to wait a while for the directory to synch. Those users will still show up as "owned" by the old box on the new server (in the global subscriber table) and COBRAS will not allow you to import them (i.e. like the SA will not let you import them). This can take a little while and add a wrinkle to your process but depending on your topology it may not be a big deal.
You might just want to create a test user on your old box and walk through this process with one user - do a COBRAS backup, delete the old user, see how long it takes for the new box to see they are no longer tagged as a subscriber and then do a COBRAS import of just that one user on the new box.
Check out the video. It really gives you an idea how it works.
The GSM will automatically delete the old account and move them to the new server when you run the tool (select which ones you want) It will migrate all their settings, recordings, etc. Once they are moved, change their VM Profiles in CUCM and you are done!