• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 47
  • Last Modified:

Take server off domain A and join domain B

Background:  We have stumbled into the .local vs .co.uk domain issues now that we're moving to off-premise exchange server.  As our site is small <40 users I'm considering starting afresh rather than rename the domain.

Question: As we are using vmware and all of my servers (currently 7, will be 4) (bar one) are virtual, could I create a new AD server with DNS/DHCP/etc with the .co.uk domain name and then migrate the old .local servers onto it by taking them out of the .local domain and adding them to the new .co.uk domain?

I appreciate I'd have to do the same with the desktops as well, but these should be much easier.

I should also say that we're currently using Exchange 2010 so I can't use the domain rename option (according to research)  I'm also not sure about adding a .co.uk UPN and whether that will do what I'm after without having to change everything..

Thanks, I'm struggling a bit with the logistics of moving to Office 365 / Off-premise exchange.
1 Solution
Dan McFaddenSystems EngineerCommented:
You could use the ADMT (http://technet.microsoft.com/en-us/library/cc974332(v=ws.10).aspx) to perform the bulk of the migration.  Here are recommendations from MS about the process you want to go thru:  http://technet.microsoft.com/en-us/library/cc974342(v=ws.10).aspx.

The only servers that will not be migrated are all the old DCs.  After everything has been migrated and functionality is verified AND the users are happy/content... then I would backup the old DCs and then permanently shut them down.

Hope this helps,

You can do cross forest migration with ADMT if wanted to

However if you are moving your exchange to O365, I don't understand why you wanted a new domain
You can just add UPN suffix in active directory for exchange domain (.co.uk) as O365 does not understand .local
Users should logon seamlessly as long as ADFS \ DirSync in place

Still if you wanted to migrate, you should setup new active directory forest,
then extend schema for exchange 2013
Then upload your new ad accounts to O365 with DirSync, create new mailboxes in O365, then point your existing on premise MX to O365 domain,
setup co-existence between O365 and on-premise Exchange
migrate mailbox data to cloud or add it as pst and so on.
Also For user profile migration and computer domain affiliation change you need Profwiz tool which can help you to migrate desktops with old user profile and assign it to users in new domain
Also you do require new ADFS and DirSync Server in new domain

No matter you create new domain or not, You need to do all configurations related to moving your on-premise exchange to O365, however new domain is not required as per my understanding
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now