Migration Windows NT Server - Failed to take snapshot

[startrader]

I wanted to convert Windows NT Server to vmware ESX 3.0 server.

After 2% completion

Error message in the converter GUI:

ERROR: Failed to take snapshot of a source volume.

Possible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems,

and not having enough free disk space.

Error message in log file:

stcbasic.sys not installed or snapshot creation failed. err=2

CloneTask::task step "clone volumes" destroyed object explicitly disposed: computer= Cleaning up computer's child objects Unregistring volume id=virtVol={computer=,0} Unregistring volume id=virtVol={computer={565d40faa5c498387cabc75e6da84bfdb147e0d},1} Unregistring volume id=virtVol={computer={565d40faa5c498387cabc75e6da84bfdb147e0d},2} Unregistring disk id=disk= Unregistring disk id=disk= Cloning failed! CloneTask::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.SnapshotError

CloneTask::task: SetState to error Got an update from CloneTask::task

Remote task CloneTask::task completed Cleaning up remote task CloneTask::task

Disposing task wrapper for task CloneTask::task object explicitly disposed: CloneTask::task

CloneTask::task being destroyed VmiImportTask::task step "clone to VM" failed Reporting image processing task failure for task CloneTask::task

ImageProcessingTask FAILED. Fault name: sysimage.fault.SnapshotError

VmiImportTask::task step "clone to VM" destroyed Cloning failed: sysimage.fault.SnapshotError Removing destination VM Successfully connected to UfaManagedVMCreator Connecting to host 192.168.100.158 on port 443 using protocol https SSLVerifyCertAgainstSystemStore: Subject mismatch: vs 192.168.100.158 SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems: * The host name used for the connection does not match the subject name on the host certificate * A certificate in the host's chain is based on an untrusted root. SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error Authenticating user root Logged in! Waiting for VM destruction to complete... Waiting for a task to complete... VmiImportTask::task step "create and clone to VM" destroyed

VmiImportTask::task step "Clone VM" destroyed

Thanks for your help !

[theanykey]

If you have not already done so, install converter as the local administrator directly onto your NT machine. After installing, reboot.

If you error out again, please attach the log package:

To do so, simply open up your VMware Converter 3.x application and choose

File --> Export Logs

[startrader]

I cannot logon with local admin, because it is a domain controller. I can only choose logon as domainname.

[theanykey]

It is generally not a good idea to migrate a domain controller using Converter. There are several posts here that warn against that.

http://www.vmware.com/community/thread.jspa?messageID=531753&#531753

http://www.vmware.com/community/thread.jspa?messageID=582094&#582094

There is an issue when P2V'ing a DC (Windows 2000 and Windows 2003). It affects the AD's Update Sequence number and can halt DFS replication.

For more information, see the following Microsoft articles:

Windows 2000: http://support.microsoft.com/kb/885875/

Windows 2003: http://support.microsoft.com/kb/875495/

It is possible but not confirmed that HP recognizes the potential problems with migrating a domain controller to another server and built that safety feature into their product.

-

---

The following procedure has been said to work:

Run DCpromo to remove the machine as a domain controller.

In order to do so, please reference the following:

repadmin /options DC_Name -disable_inbound_repl -disable_outbound_repl

--> re-run dcpromo

If you need a backup, you may want to use an imaging software such as Ghost, Symmantec or Acronis.

[twinspop]

I had the same error with a WinXP P2V conversion. Dunno if it applies in your case, but I added a USB drive formatted as NTFS to the system. Apparently converter needs some scratch space to play in, and it must be NTFS. Conversion proceeding as normal now.

hth,

jon