new thread unable to virtualize physical machine

[DennisDeV]

Got the past first problem I posted about 2 days ago. Host is Win 10 home , running workstation pro 16.1.2 attempting to virtualize the Win 10 host. 

Turned off UAC and rebooted. Started standalone converter, entered host name, user name and password. Clicked next and received message "Permission to preform this operation was denied". Tried again using host IP address rather that host name and received same message. 

Any ideas what to try next?

Any suggestions would be very appreciated. This would be the final step in converting to a new machine. 

Dennis

[kasper]

Disable host network.   Disable host AV.   Run Clonezilla.   Restore image as a guest.

[DennisDeV]

Thank you for responding Kasper. I have never heard of Clonezilla but will certainly do some research as a possible option for my problem. 

[goldeneye_007]

I have used Clonezilla on difficult to port physical machines and can confirm it does work well.

You can also try many different versions of vmware-converter as they all behave slightly different.

Older machines seem to respond better to older versions of converter, it's like newer versions removed

support for older hardware, or perhaps have more 'security' features that ultimately block older hardware

from being read.

[CarltonR]

A tad more information might be useful:

• What version of 'vCenter Converter Standalone' are you using
• As you've mentioned a 'Host Name/IP', 'User name' and 'password', it would indicate that you are attempting to perform this remotely ?
• How many drives/volumes and you attempting to virtualize ?
• Is there a reason why this cannot be done locally [see below]

The reasons for receiving the "Permission to preform this operation was denied" are many and varied, such as; network; credentials; firewall, and everything else 'in-between'.  I would suggest that the first port of call is to check the relevant logs/Events/firewalls on both the machine with vCenter Converter Standalone installed and also the host you are trying to virtualize.

I would suggest that to overcome 'connectivity' issues is to install the vCenter Converter Standalone software onto the machine you wish to virtualize . . . plug in a drive with appropriate capacity; 'Select source' type as 'This local machine', press Next; Select destination type: as VMware Workstation or other VMware virtual machine, and Hardware compatibility, press the Browse... button and point to the drive you plug in, press Next . . . and continue from there.

As an aside would it be correct to assume that from this and your previous thread that you wish to virtualize your 'old machine' that was running VMware Workstation, and then run it as an embedded virialized instance on you 'new machine' ?

[CarltonR]

Should you wish to continue to perform the virtualization as you are attempting, i.e. remotely, then you should ensure that the appropriate ports are available and accessible:

   Ports Used When Converting a Powered On Machine Running Windows

   Required VMware vCenter Converter ports

Also, some additional useful reading . . .

   vCenter Converter Standalone

[DennisDeV]

• What version of 'vCenter Converter Standalone' are you using - Using version 5.5.3 build 2592263.
• As you've mentioned a 'Host Name/IP', 'User name' and 'password', it would indicate that you are attempting to perform this remotely ? - I am running the converter on the physical machine to be virtualized.
• How many drives/volumes and you attempting to virtualize ? - 1 drive, drive C which is the boot drive.
• Is there a reason why this cannot be done locally [see below] - I am attempting this locally sitting in front of the machine. 

I navigated to the folder containing the converter icon, right clicked and selected "run as administrator". I checked the event logs and did not see any relevant messages in the application or security or system event logs. There was an application event at the time I ran the converter, RemotePCService event id 0 (zero) referencing CppWwindowsService.  The description for event 0 could not be found. 

Does the file system for Converter have a log file, I did not find one. 

I never get far enough along to make any source or destination choices.

[CarltonR]

As it has been sometime since I've P2V a machine, I ran through this in a test environment encountering no issues.  All but with one difference, I used vCenter Converter Standalone v6.6.0, which I would suggest that you download and give a try . . . and yes, you need to run it as Admin:

Main Window

Source System

Destination System 

  note: e:\ is a local drive with appropriate capacity to store the P2V image.

Options

  note: your mileage may vary

Summary

[DennisDeV]

Thank you Carlton. I clicked on the converter link you were kind enough to provide but like a lot of others attempting to download anything since the Broadcom take over I can see the http link on the far right hand side of the screen but attempting to select it gets me a big red circle with a line through it. Guess I have to call them? Is there no other way to get it?

I really appreciate the time and effort you have invested assisting me. 

Dennis

[CarltonR]

Is this what you are getting . . . 

if so then 'spin' the arrow [right facing chevron] to point downwards.

[CarltonR]

P.S. Did you also agree to the terms and conditions ?

[DennisDeV]

Carlton:

I am ashamed to admit I did not initially check the terms and conditions box, a truly amateur mistake. I corrected that allowing me to download the current version of converter. I got it installed and am converting the win10 old machine to a VM now. 

I really do appreciate your help in resolving this and apologize for wasting your time on a really **** simple oversight. You are the best. Many years ago I did software support on main frame computers and end users can be very trying at times. 

Dennis