This post was edited by haierccc at 22:22 on May 10, 2021
Physical machine to virtual machine is a very useful function. Imagine that you have an old PC that is approaching its service life, and the applications running on it are still in use. However, because of the age, you can‘t find the original operation and maintenance personnel, so you can‘t move the old applications to the new PC (whether the applications under XP can run in win10 is still unknown). At this time, you can convert the physical machine into a virtual machine (P2V), The operating system on this PC (including all the application software under it) enters the virtual machine and continues to play its role on the new PC. Both vmware workstation and VMware vCenter converter standalone client can be converted, but the former needs to install the latter to convert, and the former can directly store the converted virtual machine in the local directory, while the latter needs to be stored in the shared directory, which is more troublesome. In addition, vmware workstation can only convert a Windows host into a virtual machine, and vCenter converter standalone can also convert a Linux host. You can install VMware converter on host a and convert it to host a, or you can install VMware converter on host a to convert remote host B on the network (host B can be a physical machine or a virtual machine). Generally, the conversion to local host is very smooth and there is no problem, but the conversion to remote host often has various error messages and can not be successfully completed at one time. This paper describes the preparation work before the conversion, and lists the solutions to various error messages. This article takes the installation of vmware workstation on host a to convert remote host B as an exampleFor VMware converter conversion, the error message is the same. The path is VMware Workstation pro file virtualization physical machine (VMware converter needs to be installed in advance). The problem of conversion comes from two aspects: the network between a and B, and the host to be converted (host B). Preparation before conversion: ① During the conversion process, you need to visit the 80135445 port of host B to ensure that the router / firewall between AB and the windows firewall of host B do not block these ports,② You have administrative rights to host a and host B, that is, you need to know the administrator account and password of host a and host B; Yes, host a also needs to log in with an account and password. If you log in directly without a password before, you can temporarily add the login password and remove it after conversion. ③ The conversion process needs to write the agent to the hidden shared admin $of host B. to ensure that the network between the AB hosts is unblocked, the admin $of host B can be accessed by A. First of allHost BSee if the share exists because some systems shut it down for security reasons. Right click "my computer - manage - share folder": 
If it does not exist, find a way to restore admin$, which will not be repeated in this article, and then turn off the firewall of host B.
Operate on host A: run \\192.168.255.129/admin$ (fill in the IP according to your actual situation) to access host B, enter the user name and password if you are prompted to deny access:
Just save the following code as a .reg file and import it into the registry of Host B, or modify the registry manually: [HKEY_ LOCAL_ MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem]
" LocalAccountTokenFilterPolicy"= dword:1</ font>Copy code[/I]
Try again. If you enter the directory, you can access admin $.
④ Run: net use * / del / y to delete the previous connection. When admin $is accessible, run VMware Workstation pro file virtual physical machine to start P2V conversion. Error messages and solutions during the conversion process:
Unable to contact the specified host 192.1683.1.109'.Thehost might not be available on the network, there might bea network configuration problem, or the management services on this host are not responding。
Solution: Make sure that you can ping between A and B, the IP address of B host must be filled in correctly (in this example, 168 is wrongly written as 1683), remove the network security policy, and turn off the firewall of B host。
The operation could not be completed for '192.168.255.129\ADMIN$' due to incorrect usercredentials。
Solution: Host B must set a password, the entered password must be correct, there is a hidden share \\192.168.255.129/admin$ and it can be connected (see the preparations for hidden sharing above), and "simple file sharing" cannot be set , Do not enable "User Account Control (UAC)".
Insufficient permissions to connect to'192.168.255.1291ADMIN$'。
Solution: Whether the network hardware firewall has blocked ports such as 445, machine B needs to close the software firewall, admin$ can be accessed (see the preparations for hidden sharing above), "simple file sharing" cannot be set, and "user accounts" should not be enabled Control (UAC)".
Multiple connections to '192.168.1.109' by thesame user, using more than one user name,are noRallowed. Disconnect all previous connections to thehost and try again。
Solution: Run net use * /del /y on host A to delete the previous connection.
Unable to complete Converter agent installation on'192.168.1.109'.Error code: 1,603。
Solution: Save the following text as a .reg file and import it into the registry of host B, or manually modify the registry:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NetBT\Parameters]
"SMBDeviceEnabled"=dword:00000001</font>
permission to perform this operation was denied。
Solution: First run VMware Workstation or VMware-converter as an administrator on host A to convert. If the error is still reported, run secpol.msc on host B (or enter the control panel-management tools-local security policy), and enter the local policy- Security option-user account control-run all administrators in the mode of administrator approval-disable-restart, switch again, when you see the following figure, it shows that you are connected to host B normally, and the agent program has been written into ADMIN$, and the next step is to switch The process is:
Don't forget to turn on the firewall and user access control in the virtual machine after the conversion.
| 
English
Post time 10-5-2021 14:57:12
