<div>
I was able to use that tool to migrate a client environment in a few hours; it is surprisingly zippy.
</div>


I was able to use that tool to migrate a client environment in a few hours; it is surprisingly zippy.

<div>
Thanks Cliff. &nbsp;The parition sizes are 147GB and 1892GB, so that might explain the lag. &nbsp;I assumed it would ignore unused space during the conversion.<br />
<br />
Since the second, larger drive is predominately profiles and user data a better approach might be just to convert the C: drive, then manually copy the data over. &nbsp;I was probably being a bit ambitious trying to squeeze it into one task.
</div>


Thanks Cliff.  The parition sizes are 147GB and 1892GB, so that might explain the lag.  I assumed it would ignore unused space during the conversion.

Since the second, larger drive is predominately profiles and user data a better approach might be just to convert the C: drive, then manually copy the data over.  I was probably being a bit ambitious trying to squeeze it into one task.

<div>
<div class="content wysiwyg-content">
Hi<br />
<br />
We are trying to P2V a Windows 2012 server for the first time. &nbsp;The source server is a domain controller/file server for a school. &nbsp;When we run disk2vhd it seems to take an age to convert the disks. &nbsp;It's currently estimating just under 2 days to complete the conversion.<br />
<br />
<u>Source server details</u><br />
Dell Poweredge 840 - 12GB memory<br />
C: - 134GB in use<br />
E: - 124GB in use<br />
<br />
<u>Target server for VHDX file</u><br />
New HP DL380e - 20 GB memory<br />
Target drive mapped to source server<br />
Both systems on same gigabit network switch<br />
General network activity is low <br />
<br />
Is this a typical timescale for P2V conversions using disk2vhd or is something amiss?<br />
<br />
Thanks
</div>
</div>


Hi

We are trying to P2V a Windows 2012 server for the first time.  The source server is a domain controller/file server for a school.  When we run disk2vhd it seems to take an age to convert the disks.  It's currently estimating just under 2 days to complete the conversion.

Source server details
Dell Poweredge 840 - 12GB memory
C: - 134GB in use
E: - 124GB in use

Target server for VHDX file
New HP DL380e - 20 GB memory
Target drive mapped to source server
Both systems on same gigabit network switch
General network activity is low 

Is this a typical timescale for P2V conversions using disk2vhd or is something amiss?

Thanks

How long should it take Disk2vhd to convert Windows 2012 server?

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Since 1984, Dell has been delivering technology to fit your life.
Dell is in Enterprise, Home Office and Consumer sectors of the market, supplying a broad range of customizable desktops, laptops, notebooks, servers, storage, and network devices.