Changing Unity's Domain and Partner Server

[mmcgille]

I am trying to plan a Unity move that will keep all my subscriber data and messages intact.

I currently have:

- Unity 3.14

- Unified messaging tied to DomainA (win2000)

- Exchange 2000 as the backend

I want to end up with

- Unity 4.03

- Unified messaging tied to DomainB (win2003)

- Exchange 2003 as the backend (different server than existing ex2k server)

Right now I am thinking that the only way to do this is to use DiRT (after 1st upgrading to 4.03), but I am hoping there is a better way.

Could I use the Migrate Subscriber data even with 2 different domains?

Any suggestions would be helpful.

Thanks!

[Markus Schneider]

Nope. DiRT is the only way when changing domains. The backend could be changed, but the domain change requires a reboot.

[kechambe]

I think Markus wanted to say rebuild -- not reboot. :-)

[ROB THORNTON]

To move Unity to a new domain requires a rebuild? (uninstall / reinstall)? Customer w/ 4.0.3 and Exch 5.5 off box in NT domain. Migrating to AD, Exch 2k3. I need to repartner Unity w/ Exch2k3 and was wondering about the following:

* Run DIRT backup

* Set Unity services to manual

* Move Unity to new domain

* Verify SQL, etc starts in new domain w/ Windows accounts properly

* Change any DCOM linked w/ old domain to new domain accounts

* Extend schema in AD, create AD accounts, run perm wizard, install Exch 2k3 Mgr, etc.

* Re-run Unity services wizard pointing to new AD accounts.

* Re-run Unity message store wizard and point to new Exch2k3 server.

* Verify subscribers work in Exch5.5 site and after moving to 2k3.

Seems like a lot of work but uninstalling, reinstall, restoring really add up in hrs of work. Can someone clarify what options for moving there are? Or is it simply a rebuild.

Thanks,

Rob

[mmcgille]

Thanks, that's what I needed to know.

Regards,

Matt