Hi,
With vCenter Converter 6.2.0 on my Windows 10 computer , I tried to convert Windows server 2016 from a physical box to a VM on EXSi 6.7 with the source machine's local administrator account.
I always got error message
and "GetTokenInformation failed: 1312" on converter log even after disable both UAC and firewall on the 2016.
Also, I am confused I chosen 3 HDs (C, E and F) and Windows restored partitions to concert.
and the source has 2 HDs:
But, on the Summary picture above I only can see Number of disks: 2
I am not sure that is no issue.
Once you can't create VM manually you can't expect Converter to create one... Check your storage, memory, etc. rules (and permissions) too!
Have no idea what could be wrong with your VC/ESX but rebooting could help :smileygrin: Just kidding.
The better way is to investigate why your user (even administrator) could not create VM however help for this you can find in appropriate forum for example vSphere or ESX, ..
HTH
The disks are 2 and others are volumes in disks. Looks that your problem is ESX/VC - check if they are in maintenance mode.
HTH
Hi Poceh,
Thank you for your help.
I checked my vSphere, both host and vCenter should be normal, even there are error and warning. Then, the same error "The operation is not allowed:
looks like my vSphere has issue, but I can't find it.
Could you please give me more help?
more to this,
I used vCenter administrator account on convert for the converting. I am confused that the right would be a issue.
thanks,
Once you can't create VM manually you can't expect Converter to create one... Check your storage, memory, etc. rules (and permissions) too!
Have no idea what could be wrong with your VC/ESX but rebooting could help :smileygrin: Just kidding.
The better way is to investigate why your user (even administrator) could not create VM however help for this you can find in appropriate forum for example vSphere or ESX, ..
HTH
Hi Poceh,
you are right!, I tried to create a new VM and failed with same error massage. I believe the source of problem is that the original vCenter could not boot couple weeks ago. I booted its a copy and use it for now. I will fix this.
Thank you so much!