How to Virtualize a Windows 2003 AD Server using Ghost

I need to virtualize a development Windows 2003 AD Server to run on MS Virtual Server 2005. What files should I delete to ensure that the Mass Storage Controller drivers are built on first boot?
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.

I think there is a Physical to Virtual utility that takes your physical server and makes it virtual.

This one is right from Microsoft:

If don't want or can not use P2V then try this:
Boot into a new virtual machine with the ghost recovery CD
Recover the ghost image into the virtual machine.

The (virtual) hardware is very different, so we want to resolve this. Issues are mainly: partitions (boot.ini), controllers, single to dual cpu but also SID's.
OK, follow this:
- Use the first 2003 server CD and boot the new server from it. - On the Install/Repair screen: choose R. This will bring you to the recovery console.
- Type 'bootcfg /rebuild'. This will adjust the boot.ini.
- Then type 'exit' and reboot from 2003 server CD again.
- Now choose install, then F8 (agree), then R(epair) and execute the install. This will fix any hardware compatibility issues between source and destination hardware, while retaining your settings.
- Unplug the virtual machine from the network and boot it.
- Now you have to make sure that you don't conflict with the original DC which you ghosted. Run newsid from Sysinterals ( ) to change to SID. If you want the DC to be part of the existing domain, then you can use newsid to copy one from an existing DC.
- Finish of the configuration (assign IP addresses to network cards, install missing drivers, …)

Still, for a development machine, why do you want to start from a clone? I think it is better to just start installing from scratch. Especially if the development machine will be in a separate domain (which it should be for testing purposes).
Or do you already have that dev. machine running and just want to virtualize it and retiring the old physical machine? Then you don't need the newsid thing.


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
eohmanAuthor Commented:
The reason we want to virtualize is that we are taking a development server that has the most recent version of our vertical that is in development, and virtualizing into a 'sandboxed' environment for documentation purposes.

Otherwise, your suggesting would be the best alternative.


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
Storage Software

From novice to tech pro — start learning today.