<div>
Thanx. &nbsp;<br />
<br />
What is sysprepped? (never did this)<br />
<br />
Also what do you mean by &quot;<i>only used as a master</i>&quot;?<br />
<br />
<b><u>Note:</u></b><br />
When we said we copied the data &nbsp;we just went into the folder of the VPC to copy and copied the &quot;Virtual Machines&quot; folder and the &quot;.vhdx&quot; file&quot; (see pix)<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/01_w06/1078897/vpccopy.jpg" target="_blank" title="vpc copy from-to (69 KB)"><img alt="vpc copy from-to" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2016/01_w06/800_1078897/vpccopy.jpg" /></a>(we left the copy running last night)
</div>


vpccopy.jpg

<div>
Question: <br />
When finish setting up the copy, will it request an activation keys for windows os?
</div>


<div>
If you are going like to like version wise in Hyper-V probably not.<br />
<br />
slmgr -rearm <br />
reboot.<br />
<br />
You should be okay for at least a 3 day minimum period.
</div>


<div>
Don't understand your entry. &nbsp;What do you mean?
</div>


<div>
I meant that the VM should be okay if transferring between two Hyper-V servers/desktops of the same version and patch level.<br />
<br />
The slmgr step is done from an elevated command prompt to reset the activation timer in the OS.
</div>


<div>
Ok Thanx!<br />
<br />
Will proceed to close.
</div>


<div>
You can close the ticket on your own without mod intervention. :)
</div>


<div>
It's ok. &nbsp;Even though we did not actually use the recommendations, we were going, and they make sense. &nbsp; We 'll leave like this.<br />
<br />
Note:<br />
Based comments here made us search more for the solution.<br />
<br />
So again, thanx!
</div>


<div>
We include our entry within the comments and &quot;Best Solution&quot; since it's what has been working these days.<br />
<br />
Tahxn all!
</div>


<div>
<div class="content wysiwyg-content">
We have a Hyper-V VPC windows 7 pro running in it. &nbsp;We would like to copy of that VPC so we can run other installs and test on the copy. &nbsp;We previously just copy the vhdx file and in the Hyper-V manager created a new VPC pointing to the copied file. &nbsp;<br />
<br />
We would to make sure we are doing this correctly. &nbsp;What are the proper steps to make a copy of a working VPC and have it up and running.<br />
<br />
Please advice.
</div>
</div>


We have a Hyper-V VPC windows 7 pro running in it.  We would like to copy of that VPC so we can run other installs and test on the copy.  We previously just copy the vhdx file and in the Hyper-V manager created a new VPC pointing to the copied file.  

We would to make sure we are doing this correctly.  What are the proper steps to make a copy of a working VPC and have it up and running.

Please advice.

Steps to make a working copy of a virtual drive Hyper-V

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.