Second Opinion Required for virtualisation process

I am about to virtualise my single domain system and wanted to check over the process with you guys, in case I have missed something vital in the order! Thanks in advance!

Current set up:
Single server running 2003 R2 SP2, Exchange 2003, File and Print, DC
 - I am aiming to have this server as a 2008 R2 hyperv host running two application guests, and one guest which will be 2008 R2 running Exchange 2010, AD, file and print.

My plan is as follows:
1. Create a vm on a separate (Temporary) host server running 2008 R2 HyperV. The vm will be 2008 R2 SP1.
2. Add vm to domain, add print server, file server, dhcp and dns
3. Add Active Directory and sync with current DC
4. Install Exchange 2010 SP1 (prerequisites first!)
5. Move all fsmo roles to new guest DC server
6. Move mailboxes from Exchange 2003 to 2010
7. Uninstall Exchange 2003 from original server
8. Demote (dcpromo) original server
9. Remove DNS and DHCP from original server
10. Raise functional level to R2
11. Stop file shares on original server
12. Full Backup Exec backup of data.
13. Restore data to vhd and attach to guest server
14. Format original server, install 2008 R2 with hyperv
15. Create virtual machines and mount vhds created earlier
Who is Participating?

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

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.

Mike KlineCommented:
In step 2 you say add DNS,  since you are running AD Integrated DNS just check the box during dcpromo (new box) to make it a DNS server (also a global catalog server)

Does this network have users on it or is it just your own lab.  The reason I ask is because I'd always have at least two DCs on any production network.



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
itadminukAuthor Commented:
quite right, will move the DNS part to dcpromo thanks..
Yes it does have users, but not many - and I currently don't have enough hardware for a second dc - but aware that its not ideal.
thanks for the quick response!
Mike KlineCommented:
ok in that case make sure to have backups and regular images of the DC.  In this case with only one DC you can't really run into USN rollback issues.

....when you get the money get a second DC up...but budgets are tight right now.  That is understandable.


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
Windows Server 2008

From novice to tech pro — start learning today.