Moving a 5.2 MAS with Exchange 2010 backend to an new AD domain?

[ksphoneman]

Searching for a procedure and second opinions for moving an existing 5.2 MAS with Exchange 2010 (working) to a new Active Directory Domain.
The new domain has a new Peer directory server and a new Exchange 2010 CAS.
It seems as though I'll need to treat this as a new installation.
I haven't found any documentation to serve as a guide for the process.
My thoughts are:
Before removing the MAS from the current domain, I'll need to remove all of the MM subscribers, and remove the existing Voicemail domain to disassemble the existing MAS from the old AD domain.
Prepare the new AD - DC with the MM schema updates, join the MAS to the new domain, update the DNS, wipe the MMPREP.xml files, adjust the DCT file, run the MSICM, re-build the subscriber mailboxes.
Knowing the nature of Modular Messaging and changes to its environment, should I plan to completely rebuild the MAS server to the point of re-installing the OS, or can this change be made by making the necessary adjustments to the provisioning settings?

MM 5.2 SP9 patch 3 (may update to SP 11)

Mike O'Neil

 

[texeric]

My suggestion would be to treat this as a new install. Definitely a good idea to permanently disable MM from accounts (removing all MM related data from them) prior to uninstalling/removing MM from the existing domain.

I would rebuild from the OS on up because you will probably be using a new account in the new domain and you wouldn't want files from the old system to get in the way of the new system.

Is the new domain in the same AD forest?

http://www.theviagroup.com

 

[ksphoneman]

Thanks for the reply Texeric,
No, the new AD will be completely separate. (New company after a merger) Nothing from the old domain will be present. New AD DC and new Exchange server.

Thanks,
Mike O'Neil

 

[texeric]

Based on your answer this will definitely be a new installation.

Since the new domain is in a different AD forest I'm glad you noticed you will have to update the AD schema as well as everything else for a new install (new accounts, permissions, etc).

http://www.theviagroup.com