If I have a Windows server, and say some drives in the server are displaying as faulty and as a precaution I want to virtualize the OS and move it to a Windows 7 machine for example, how would I go about this. The virtualization part I gather is pretty simple using a virtualization  tool, but how could I get it running in say a Windows 7 machine ?
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.

Lee W, MVPTechnology and Business Process AdvisorCommented:
You really need to provide more information.

For example, What server OS is it?  Are you running Windows 7 home or Pro?  Why not replace the failing drives?!?!?  What virtualization solution did you want to use?  Virtual PC, Virtual Box?  Hyper-V? VMWare?  Xen? etc.?
discoveranotherAuthor Commented:
OS is 2012, replacing the drives will be done and on order, but my thoughts were what if the server went down whilst awaiting the drives. Hyperv would be the virtualization. Is it just a question of installing HyperV on another well specked machine and importing the .vhd file ?
Lee W, MVPTechnology and Business Process AdvisorCommented:
how could I get it running in say a Windows 7 machine ?
Hyper-V is a Type 1 hypervisor - you cannot run it on Windows 7

Short Term, Make a FULL BACKUP of the server.  Then use Disk2VHD to copy all hard drives to an external disk (Disk2VHD is NOT a supported P2V tool - BUT it often works fine.  I'm NOT advocating it be used in this manner as your first choice, but as a "backup" method, it can help ensure your network survives.

Setup Hyper-V on a DIFFERENT system and perform a MIGRATION to that system (ASSUMING you are not using an OEM license of SBS - Which CANNOT be moved).  Once the Migration to a VM is complete, GET RID of your old server - wipe the drives.  (I assume you know the proper steps in a migration?)  Once you have your new drives in place, rebuild the server as a hyper-V host and move the SBS VM onto the hardware.  Done.

NOTE: If you are forced to bring up the SBS Disk2VHD copy as a VM, MAKE SURE - ABSOLUTELY CERTAIN - the PHYSICAL SERVER is OFFLINE and NEVER comes up again.

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
discoveranotherAuthor Commented:
Yes they are the steps I expected. I have used Disk2VHD before and imported into hyperv, but not set it up as in the above scenario. Will give that ago.
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
Microsoft Virtual Server

From novice to tech pro — start learning today.