HyperV "clone" -- Windows Server 2012R2

I just have Windows Server 2012R2 STANDARD,
no System Center 2012 Virtual Machine Manager yet.

What is the cheapest way to CLONE an existing machine
so I can install a Windows PATCH on the machine
and see how good it works ?
 1. power down Windows Server 2012R2
     STANDARD VM #1 on PHYSICAL machine
 2. somehow make a copy of it, running
     SYSPREP/etc to remove the static IP
 3. somehow bring this copy up as a Windows Server 2012R2
     STANDARD VM #2 on the same PHYSICAL machine
     and change to a static IP
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

Patrick BogersConnect With a Mentor Datacenter platform engineer LindowsCommented:

As the machine is running (no need to power down ni 2012r2) right click it and select export. Export needs to be done locally.
Once exported add the virtual hard disk (only the VHD) to a new VM with no NICS attached and boot up. If the machine is domain joined login as local admin and disjoin the machine, rename it as desired and shutdown.

Powered down, add a NIC and boot up, login as local admin-> configure ip address and download/install your patch.
Cliff GaliherConnect With a Mentor Commented:
Even with SCVMM, I never recommend running test machines (or VMs) on a production network. A bad patch can not just impact the machine, but the entire network. Especially in AD environments where secure communications occur constantly, you can *really* jeopardize your network and security. Running a completely separate test network is easy with hyper-V. Just have an isolated v-switch and import the machines you want, attaching them only to the private switch.
Philip ElderConnect With a Mentor Technical Architect - HA/Compute/StorageCommented:
Simple way:
Make sure to create a Private Network in Hyper-V Network Management.

Copy the VHDX files into a separate folder.

Create a new VM called "TestVM" or the like and attach the vNIC to the Private Network. Attach the VHDX files. Boot the vM and run your test.

A separate VHDX file could be created in Disk Management with the patch file(s) copied into that. Detach the VHDX file and attach it to your test VM. Go.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Neil RussellConnect With a Mentor Technical Development LeadCommented:
Obviously as you have only Server 2012 Standard license, you need to ensure that you have a license for each two machine you have running ( per 2 processors )

1 license covers your Hyper-V server install and two VM's running on a max of 2 physical CPU's. 3 or 4 CPU's, 2 licenses etc.
finance_teacherAuthor Commented:
Does anyone do "Sysprep /generalize /oobe /mode:vm" found on
http://technet.microsoft.com/en-us/library/hh824938.aspx to

Can the DELL VM easily be put on an HP PHYSICAL server
or does the 2nd PHYSICAL server need to be the same
make/model as the 1st PHYSICAL server ?
Nagendra Pratap SinghConnect With a Mentor Commented:
Using a VM frees you up from a model etc to a large extent. Each VM has a virtual motherboard specified in it with few virtual parts like NIC/Video/HDD .

To run this, you need a matching player(Hypervisor).

In short.

Original Server was a Dell dx5000 model.
One of the VM conversion steps is removing the physical hardware drivers and utilities.

Converted to VM, it starts using a Hyper-v Model motherboard. Now it can be played by any hyper-v version which is same or 1-2 version higher than this VM.

If you plan to go VMware way, then the destination VM will have a VMware model motherboard and can be played inside few versions of VMware products.

In case your physical hardware is being retired etc then all you need to do it is to find another server with a matching player software (Hypervisor). Your VM will run on the new device with maybe zero modifications.
Cliff GaliherConnect With a Mentor Commented:
Sysprepping is great for cloning a VM that you plan on running in production. But that serves an entirely different purpose. Sysprep is destructive enough that, for your purpose of patch testing, you wouldn't get a reliable result anyways. The test ,machine is no longer similar enough to the live machine due to the sysprep.
Patrick BogersConnect With a Mentor Datacenter platform engineer LindowsCommented:
Sysprep makers the VM system independant so you can convert to physical. For patch testing you would not want to do this.
All Courses

From novice to tech pro — start learning today.