How to move member servers to a different domain
I have to move our member servers and computers from our existing domain to a new domain in the cloud.
I have moved computers from one domain to another before, simply by removing them from the domain to a workgroup and then joining them to the new domain.
We are waiting for a connection to our new cloud-based domain to be installed. When that is done I will install a separate switch and keep the two networks physically separated at first. The two networks will use different IP subnets (192.168.0.XXX and 10.119.0.XXX). I plan plug a PC in to the new switch and join the new domain and make sure I can access the cloud stuff correctly .
Our existing domain uses Hyper-V VMs for all our servers and I have a couple of 'spare' member servers. I am planning to remove one of these member servers from our domain, connect it to the new switch and then join it to the new cloud-based domain.
If this works then I should be able to see the local member server and the cloud-based stuff from the local connected computer. So then I can confidently move the remaining member servers and all our PCs across to the new domain. I am not planning to move the existing Domain Controller or Exchange server across as we already have AD setup for all users on the new domain.
But I have a couple of questions:
1. Is it possible to just remove the member server from one domain and then join it to a new domain?
2. How will this work when the member server is part of Hyper-V running from the same physical server as the existing Domain Controller?
Cheers,
Greg
I have moved computers from one domain to another before, simply by removing them from the domain to a workgroup and then joining them to the new domain.
We are waiting for a connection to our new cloud-based domain to be installed. When that is done I will install a separate switch and keep the two networks physically separated at first. The two networks will use different IP subnets (192.168.0.XXX and 10.119.0.XXX). I plan plug a PC in to the new switch and join the new domain and make sure I can access the cloud stuff correctly .
Our existing domain uses Hyper-V VMs for all our servers and I have a couple of 'spare' member servers. I am planning to remove one of these member servers from our domain, connect it to the new switch and then join it to the new cloud-based domain.
If this works then I should be able to see the local member server and the cloud-based stuff from the local connected computer. So then I can confidently move the remaining member servers and all our PCs across to the new domain. I am not planning to move the existing Domain Controller or Exchange server across as we already have AD setup for all users on the new domain.
But I have a couple of questions:
1. Is it possible to just remove the member server from one domain and then join it to a new domain?
2. How will this work when the member server is part of Hyper-V running from the same physical server as the existing Domain Controller?
Cheers,
Greg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks guys. Our schedule has been pushed back a couple of months and now I am going to take some holidays, so I won't be able to do much more with this for a few weeks.
ASKER
The Hype-V concern is still real for me though.
The server I will move initially for testing, is currently off and serves no real purpose in the existing network. But it does provide me with a server to play with as I connect it to the new network and see what happens.
Having said that, the existing network will still be live and active for a few weeks, so I can't take the DC off-line yet. I guess I could for a short period but I certainly can't leave it off permanently at this stage.
The physical server (Hyper-V host computer) has 4x NICs, so there is the potential to configure the test server to a different NIC than the others.
I won't get back to it now for a few days, but I will report back with how it went next week.