Convert Windows 10 1607 Russian to vmware


We have problems with converting the machine (Powered ON, Remote windows machine) to a virtual environment vmware.

Source machine (Powered ON, Remote windows machine): Windows 10 1607 Enterprise Russian

Converter: Vmware vCenter Converter Standalone 6.1.1 build-3533064 (OS Windows Server 2008 R2 Standard SP1 English)

Vcenter: VMware vCenter Server Version 6.0.0 Build 3634793

ESXi host: VMware ESXi 6.0.0 build 3620759

The process of cloning and copying disks is normal.

But when start customization we have error:

Error: Unable to create the customization deployment file.

And task FAILED:

  FAILED: Unable to proceed since the Sysprep parameters provided are not correct.

In converter-agent logs we see:

   2017-03-28T10:10:24.262+09:00 info vmware-converter-agent[03688] [Originator@6876 sub=task-17] sysprepDeployRoot:

   2017-03-28T10:10:24.262+09:00 info vmware-converter-agent[03688] [Originator@6876 sub=task-17] sysprepOptions:

   2017-03-28T10:10:24.262+09:00 warning vmware-converter-agent[03688] [Originator@6876 sub=Default] Unable to get GetShortPathName for 'C:\WINDOWS\TEMP\vmware-temp\vmware-РЎР˜РЎРўР•РњРђ\deploypkgwwphoojetoutvinq\deployPkg.cab', error 'Системе не удается найти указанный путь. --> '[3]

   2017-03-28T10:10:24.262+09:00 error vmware-converter-agent[03688] [Originator@6876 sub=task-17] Error while creating Customization deploy File: ERR: FileIO=0

   2017-03-28T10:10:34.737+09:00 info vmware-converter-agent[05576] [Originator@6876 sub=ThreadPool] Thread delisted

Apparently the problem is the presence of Russian characters (encoding) in the path, for GetShortPathName.

Can we work around this problem?

0 Kudos
2 Replies
Hot Shot
Hot Shot

Yes, its most likely UTF support related issue. Contact vmware support to handle this.

0 Kudos

If create new local administrator user with english characters.

And run convert agent service as this user, customization finaly normal and convert succesfully.

With russian characters trubles.

0 Kudos