First off I think it would be a good time for you to get rid of the 2000 domain controller and bring your domain/forest to at least 2003 functional level, ideally 2008 r2 if you can have it, the DHCP role on a 2003 domain controller should be ok (I think it was windows 2000 DCs that had some issues in the past) but as you mentioned virtualization I recommend to have either a physical DC or have them on separate physical hosts (I prefer one physical DC and dhcp, and GC virtual) again that is if you have the extra hardware, terminal services or RDS should definitely be on its own.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Alberto Medina Sent: Monday, December 13, 2010 11:20 AM To: [email protected] Subject: Windows Server Roles Hi all, I'm planning in migrating some servers to VM's for separate some roles and for and replace some old servers. Currently we have 2 domain controllers, one on Windows 2000 and other in Windows 2003. Windows 2000 is the primary domain controller and W2K3 is Domain Controller, Terminal Services, and DHCP (and of course DNS for AD), and I want add VPN server for remote access. I have found that is not recommended to run DHCP or Terminal services in a Domain controller, so I want separate those roles to VM's but I want to know which of this roles can I run together in a VM without affecting security. Please let me know your opinions about this. Thank you and Best Regards, Alberto Medina
