Windows AD Domain Name Change

[joshuamarsh]

Hello, Netpros.

I have a customer who is changing their AD domain name.  They are running Unity 5.0(1), Unified Messaging, and off-box Exchange 2003 as the message store.  From looking at the docs, I am assuming that this will be considered changing both the DC and the message store.  I think I'll have to do a complete rebuild and restore using DiRT (http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcuruge060.html).  After that, I'm assuming that I'll need to do a message store change (http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcuruge050.html). 

However, we are not really changing to a different DC or an Exchange, it will be the same one just renamed, but it appears to me that we have to consider it as all new.  Is this correct?  If so, are there any steps I'm missing?  What do I have to do to subscriber properties, if anything? Do I need to decommission the server from the domain before removing?  Is there any concern as to the order of operations?  E.G. Do I need to decommission, kill subscriber properties, have them change the domain name, then rebuild and re-add?

Is there anyway to not have to go this route, say using DNS to translate the old domain?  We'll be migrating to Connection in several months, so I'd like to avoid a rebuild now if possible, as both time and budget are short.

Thanks for your thoughts on this,

Joshua

[David Hailey · Accepted solution]

This would be considered the same as moving Unity to another domain.  So, it is a DiRT backup, rebuild, DiRT restore operation.  Here is the applicable link from the configuration guide:

http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcuruge080.html#wp1097725

I do not know of any way to get around this.  Unfortunately, it would be much easier for you if you could have timed the migration to Unity Connection in conjunction with this change.

Hailey

Please rate helpful posts!

[joshuamarsh]

Thanks!