Changing Domains and Exchange

%3CLINGO-SUB%20id%3D%22lingo-sub-1213703%22%20slang%3D%22en-US%22%3EChanging%20Domains%20and%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1213703%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EWe%20have%20a%20client%20with%20%3CSPAN%3Emultiple%20servers%3C%2FSPAN%3E%20in%20an%20old%20%22business.local%22%20domain.%20Their%20SVR1%20is%20a%20domain%20controller%20and%20SVR2%20is%20BDC%20and%20email%20server.%20I%20have%20created%20a%20new%20SVR01%20under%20the%20new%20domain%20and%20moved%20the%20desktops%20into%20it.%20Now%20I%20want%20to%20remove%20Exchange%202013%20on%20SVR2%2C%20then%20demote%20the%20server.%20After%20that%20I%20plan%20to%20join%20SVR2%20to%20the%20new%20domain%20%22business.net%22%20and%20reinstall%20Exchange.%20Essentially%20moving%20the%20server%20into%20a%20new%20domain%20and%20recreating%20the%20Exchange%20Server%20under%20the%20new%20domain%20name.%20Leaving%20mailboxes%20and%20File%20Storage%20intact.%20Then%20reattach%2Freapply%20Users%2C%20Mailboxes%2C%20and%20File%20Permissions.%3C%2FP%3E%3CP%3EAll%20of%20the%20Servers%20get%20Nightly%20Backups.%3C%2FP%3E%3CP%3EI've%20tried%20other%20methods%20of%20renaming%2C%20etc.%20and%20seen%20bad%20results.%20I'm%20hoping%20this%20is%20a%20way%20to%20move%20them%20forward%20and%20remove%20the%20certificate%20and%20security%20issues%20of%20the%20.local%20domain%20carried%20forward%20from%20SBS.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1213703%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1213724%22%20slang%3D%22en-US%22%3ERe%3A%20Changing%20Domains%20and%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1213724%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20sure%20what's%20the%20point%20of%20reusing%20the%20old%20windows%20that%20exchange%20was%20installed%20on%3F%20Better%20option%20would%20be%20to%20just%20stand%20up%20a%20new%20one%2C%20patch%20fully%20(assumes%20virtual%20environment)%20or%20clean%20install%2C%20etc.%20it%20if%20physical%20box.%3C%2FP%3E%0A%3CP%3EAs%20to%20the%20exchange%20migration%20task%20I'd%20suggest%20asking%20subject%20matter%20experts%20in%20dedicated%20forums%20over%20here.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Foffice%2Fen-US%2Fhome%3Fcategory%3Dexchangeserver%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Foffice%2Fen-US%2Fhome%3Fcategory%3Dexchangeserver%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1213758%22%20slang%3D%22en-US%22%3ERE%3A%20Changing%20Domains%20and%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1213758%22%20slang%3D%22en-US%22%3EI%20understand%20that%20thinking.%20Our%20main%20reason%20is%20downtime.%20SVR2%20is%20newer%20and%20excellent%20hardware%20that%20we%20plan%20to%20keep%20a%20couple%20more%20years.%20But%2C%20clients%20can't%20deal%20with%20any%20downtime%20these%20days.%20We're%20trying%20to%20limit%20the%20downtime%20using%20the%20method%20I%20described.%20The%20SVR1%20hardware%20is%20the%20one%20we%20are%20replacing%20this%20round.%20The%20SVR1%20server%20runs%20all%20of%20the%20virtual%20systems%20currently%20and%20needs%20more%20power%20and%20resources.%20In%20order%20to%20properly%20move%20this%20client%20forward%2C%20we%20have%20to%20change%20that%20old%20%22overdue%22%20%22business%2Clocal%22%20domain%20name.%20You%20make%20a%20valid%20point%20and%20I%20was%20looking%20at%20that%20Server%20software.%20Perhaps%20we%20could%20virtualize%20the%20current%20Exchange%20Server%20on%20other%20hardware%20and%20then%20reload%20the%20exiting%20hardware%20as%20you%20suggested%20thus%20keeping%20downtime%20to%20minimum.%20Thank%20you%20for%20pointing%20me%20toward%20the%20Exchange%20group.%20I'm%20new%20to%20this%20site%20and%20could%20not%20find%20a%20location%20to%20post%20Exchange%20questions.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello,

We have a client with multiple servers in an old "business.local" domain. Their SVR1 is a domain controller and SVR2 is BDC and email server. I have created a new SVR01 under the new domain and moved the desktops into it. Now I want to remove Exchange 2013 on SVR2, then demote the server. After that I plan to join SVR2 to the new domain "business.net" and reinstall Exchange. Essentially moving the server into a new domain and recreating the Exchange Server under the new domain name. Leaving mailboxes and File Storage intact. Then reattach/reapply Users, Mailboxes, and File Permissions.

All of the Servers get Nightly Backups.

I've tried other methods of renaming, etc. and seen bad results. I'm hoping this is a way to move them forward and remove the certificate and security issues of the .local domain carried forward from SBS. 

3 Replies
Highlighted

Not sure what's the point of reusing the old windows that exchange was installed on? Better option would be to just stand up a new one, patch fully (assumes virtual environment) or clean install, etc. it if physical box.

As to the exchange migration task I'd suggest asking subject matter experts in dedicated forums over here.

https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver

 

 

 

Highlighted
I understand that thinking. Our main reason is downtime. SVR2 is newer and excellent hardware that we plan to keep a couple more years. But, clients can't deal with any downtime these days. We're trying to limit the downtime using the method I described. The SVR1 hardware is the one we are replacing this round. The SVR1 server runs all of the virtual systems currently and needs more power and resources. In order to properly move this client forward, we have to change that old "overdue" "business,local" domain name. You make a valid point and I was looking at that Server software. Perhaps we could virtualize the current Exchange Server on other hardware and then reload the exiting hardware as you suggested thus keeping downtime to minimum. Thank you for pointing me toward the Exchange group. I'm new to this site and could not find a location to post Exchange questions.
Highlighted

Sounds good, you're welcome. Clean installing the operating system and patching should not take all that much time to do (assumes you're not talking 2012 or older) and in the end you'll know the install is clean and free of corruption (less overall downtime). If you have the option to virtualize then this may make the task even easier.

 

(please don't forget to mark helpful replies)