Agreed. 2008 R2 is the plan actually, but from my org's perspective going to 2008 or 2008 R2 is the same level of change.
Dave From: Tim Vander Kooi [mailto:[email protected]] Sent: Thursday, January 07, 2010 9:10 AM To: NT System Admin Issues Subject: RE: Adding 2008 DC's... I am curious why you would only go to Server 2008 and not 2008 R2? If you are going to begin your migration of AD to a newer version why not go to the latest one available instead of remaining a couple of years behind? Having at least one DC at 2008 R2 will also make more of the "better together" features of Windows 7 available to you when you make that move (Direct Access for instance will make a big difference to admins going forward when it comes to patching and management). Tim From: David Lum [mailto:[email protected]] Sent: Thursday, January 07, 2010 11:00 AM To: NT System Admin Issues Subject: Adding 2008 DC's... We have an environment with five 2003 Server DC's. I need to roll out two new DC's and would like to make them 2008 Server. Do you guys consider this a major or minor infrastructure change? I'm on the fence - existing DC's are untouched save for running ADPREP on the schema master, otherwise the existing DC's are untouched. Lots of new features though and to me just as importantly 2008 will be supported for years to come. My fellow SE's are telling me to just roll out 2003 and call it good, but to me it seems silly since our DC's typically hang around a long time (6+ years currently), and in 5 years security patches go away for 2003 (extended support ends 7/2015, and mainstream support ends 7/2010). Comments? David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
