Server 2003 DC to 2008R2 Upgrade Question

I am working on upgrading my domain from two domain controller running server 2003 to 2008 R2.  Everything is in a VMWare environment so there are no real hardware considerations.  My current domain controllers are 32bit SP2 and run both DNS and DHCP services.  I was wondering if it might make sense to attempt an in place upgrade of the servers rather than doing a clean install and trying to migrate DNS and DHCP services over to a new server.  We have all static addressing on our LAN and changing the DNS on every device would be a huge task so I'm looking for ways to avoid that.

Is it possible to do an in place upgrade from the 32bit version of Server 2003 to 2008 R2 which is 64bit?  If so what is your opinion about potential problems I might encounter?  If the in place upgrade is unwise or not possible what would you recommend to deal with the DNS issue?  In a nutshell my thought was to integrate the new servers, promote them to DCs, move the roles over, demote the old servers, then have the new servers assume the IP addresses of the old servers.  I'm worried that this might cause some problems but I can't think of any specific issues myself.  I would greatly appreciate any assistance you could offer, thanks!
LVL 1
First LastAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ernie BeekExpertCommented:
Cross architecture in-place upgrades (for example, x86 –> x64 or x64 –> x86) are not supported.

Source: http://blogs.technet.com/b/askperf/archive/2009/10/01/windows-7-windows-server-2008-r2-upgrade-paths-registry-enhancements-crash-dumps-and-page-file-sizing.aspx

The thing is, when servers have been dcpromod you can't change the ip (!)
What you sould do is: first move all roles to one server (DNS, DHCP and don't forget the FSMO's!) and decomission it. After that, install the new server, give it the ip of the decommissioned server, add that to the domain, dcpromo it and move all roles from the old to the new server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ernie BeekExpertCommented:
For DNS, you can make the new server a DNS server as well and let the two sync. When that's finished you can remove the DNS role from the old server.
DHCP migration is also a lot easier nowadays: http://www.petri.co.il/dhcp-server-migration-made-easy-windows-server-2008.htm
0
First LastAuthor Commented:
Hi erniebeek!  Ok, let me rephrase to make sure I understand what you are saying.  Since I have 2 DCs (lets call them DC1 and DC2) now I would basically move all the FSMO roles and DHCP over from DC1 to DC2 (DC2 is also the secondary DNS server).  I'd then demote DC1 from the domain and remove it entirely.  Then I'd bring in the new server using the same IP of the recently removed DC1, promote it to a DC and add the DNS and DHCP roles.  It would then be a simple matter to repeat this to replace the 2nd DC.  Does that sound about right?  Thank you very much for the tips, very much appreciated!
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Ernie BeekExpertCommented:
That sound completely right :)
That's the way I did it a few weeks ago.

Wait, there was something with the certificate authoroty. You have to back it up (better safe than sorry) and perhaps migrate it: http://smtpport25.wordpress.com/2010/01/16/migrating-windows-certificate-authority-server-from-windows-2003-standard-to-windows-2008-enterprise-server/
0
First LastAuthor Commented:
Fantastic, thanks for everything!
0
Ernie BeekExpertCommented:
You're welcome :)

Thx for the points.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.