We’ve posted a new Expert Spotlight! Joe Anderson (DatabaseMX) has been on Experts Exchange since 2006. Learn more about this database architect, guitar aficionado, and Microsoft MVP.
Moving from a 2000 domain
We have a server 2000 acting as a DC for our 20 user network. We purchased a 2016 server.
How should we go about eliminating the 2000 server? I know we cannot migrate...
How should we go about eliminating the 2000 server? I know we cannot migrate...
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
2000?? Ouch! migrating from OSes out of extended support is indeed painful. 2000 particularly so.
If you've invested time in tailoring permissions on files and resources, migrate. You'll need to introduce an "interim" server to move to. Effectively migrating twice.
If not, with only 20 users, it is one of the rare times I'd recommend just building a new domain. Recreate user accounts, manually copy data, create new permissions, and join machines to the new domain. You'll lose a weekend, with significant interruption and downtime, but might be easier than tracking down legal OS Medicaid licensing to do the interim gig.
And don't let it go so long next time. You'll save yourself, or your successor, a huge headache.
If you've invested time in tailoring permissions on files and resources, migrate. You'll need to introduce an "interim" server to move to. Effectively migrating twice.
If not, with only 20 users, it is one of the rare times I'd recommend just building a new domain. Recreate user accounts, manually copy data, create new permissions, and join machines to the new domain. You'll lose a weekend, with significant interruption and downtime, but might be easier than tracking down legal OS Medicaid licensing to do the interim gig.
And don't let it go so long next time. You'll save yourself, or your successor, a huge headache.
Hi,
Since it's just 20 users, the easiest method would be
1)install the new 2016 server with DC role. If possible give new domain name unless you would like to keep the same old name. Don't connect the new server onto the existing network now
2) copy the users work folder, profile etc from the old server and keep it in a safer place or if you have backup then fine
3) Disconnect the old server from network and connect the new server
4) join the machines to the new domain /server
5)copy the users data across
6) once you noticed all working fine then format the old server.
You can install fresh OS on the d server and join to this domain as member and use if required.
Since it's just 20 users, the easiest method would be
1)install the new 2016 server with DC role. If possible give new domain name unless you would like to keep the same old name. Don't connect the new server onto the existing network now
2) copy the users work folder, profile etc from the old server and keep it in a safer place or if you have backup then fine
3) Disconnect the old server from network and connect the new server
4) join the machines to the new domain /server
5)copy the users data across
6) once you noticed all working fine then format the old server.
You can install fresh OS on the d server and join to this domain as member and use if required.
Cliff... how would I go about this? Can 2 domains exist on the same network?
We currently have oldDomain running just fine. We make 2016 a newDomain AD server. Each workstation then moves from oldDomain and joins newDomain?
We currently have oldDomain running just fine. We make 2016 a newDomain AD server. Each workstation then moves from oldDomain and joins newDomain?
RK... to copy the users data, the old server would then have to be connected back to the network... this will work?
Premium Content
You need an Expert Office subscription to comment.Start Free Trial