[cisco-voip] AD2008 w/ Unity v5

[Pat Hayes]

I haven't done it as a migration, but I've set it up as a new install.
There isn't too much to worry about. From Unity's perspective, nothing
fundamental had to change to support 2008, it still uses ldap, etc.
The only real difference is that AD 2008 introduced the concept of the
read-only DC, so the ES adds some logic to make sure Unity isn't
trying to write to one of those.

Depending on how you're doing the migration, Unity will probably be
bouncing from DC to DC during the work. It is likely to drop into UMR
mode for some/all of it, as it needs a GC to authenticate things off
of. While it should be able to handle most changes on the fly, a good
reboot or two, particularly once all of the work is done, is probably
a decent idea.

Finally, take a look at the chapter on changing the DC that Unity
points to in the Unity Reconfiguration and Upgrade Guide. It covers
all of the places to check to see what Unity is currently pointing to
(yep, more than one). Be sure to do this at the end, to make sure it
didn't end up picking some random DC across a wan link.

On Thu, Jun 4, 2009 at 9:44 AM, Ed Leatherman <ealeatherman at gmail.com> wrote:
> Good morning,
>
> Has anyone done a migration to active directory 2008 from 2003 that
> involved a Unity system? Curious if there are any gotcha's I need to
> be concerned about other than running the required ES on Unity and
> probably rebooting it half a dozen times while GC and DC's get
> replaced.
>
> --
> Ed Leatherman
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>