hcste
asked on
Replacing 03 Server Domain Controller
So here's the skinny..
I have three servers running 03 server standard. The main server ( the domain controller ) needs to be replaced as it is just moving too slow. Besides it running the office of 25 or so computers, I have about 30 additional people who remote desktop into it daily so downtime is a big no-no. I have a new server ready to go with WIndows Server 2012 R2 on it and I want to make this transition as seamless as possible. The old domain controller works but is very bogged down and slow when it is being RDP'd into etc etc.
What do you guys propose as the best route to go here?
I have three servers running 03 server standard. The main server ( the domain controller ) needs to be replaced as it is just moving too slow. Besides it running the office of 25 or so computers, I have about 30 additional people who remote desktop into it daily so downtime is a big no-no. I have a new server ready to go with WIndows Server 2012 R2 on it and I want to make this transition as seamless as possible. The old domain controller works but is very bogged down and slow when it is being RDP'd into etc etc.
What do you guys propose as the best route to go here?
Last Comment
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Completely agree - you should not be running Remote Desktop Services/Terminal Services on a domain controller. From a security and managability standpoint this is a HUGE professional no-no.
As VB ITS suggests, you want to use the PHYSICAL install of Server 2012 R2 as a Hyper-V host ONLY - no DC, no file server, no RDS, then install TWO VMs - one for your DC and one for your RDS server. From a licensing standpoint, there is ZERO additional cost for this.
As VB ITS suggests, you want to use the PHYSICAL install of Server 2012 R2 as a Hyper-V host ONLY - no DC, no file server, no RDS, then install TWO VMs - one for your DC and one for your RDS server. From a licensing standpoint, there is ZERO additional cost for this.
If you aren't familiar with proper domain/server setup and separation of services and don't have the time (or inclination to learn) I STRONGLY recommend you look for an outside consultant who can do this for you. If you have the time to learn, then I recommend setting up a test network and starting to play - install the roles, setup VMs, and ask questions as they come up.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Okay, again, for the sake of my actual question, lets put the hyper-v recommendation aside. Either way I want a backup DC.
My question is once I promote the new server as a domain controller, would all the users/configuration duplicate if I were to physical shut down the original DC?
My question is once I promote the new server as a domain controller, would all the users/configuration duplicate if I were to physical shut down the original DC?
ASKER
VBS IT I understand where you are coming from and I already have a plan of action. But I also posed the questions to pick your brains and get some fresh input.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
And regarding the Hyper-V, Why wouldn't you recommend that I just make the Hyper-V server the host and DC and create a VM for just RDS?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
With that being said, if I follow that guide, it will make my new server a domain controller. At that point, will it duplicate the users/configuration if I were to shut down the original domain controller automatically?