Microsoft VMM Issues

Microsoft VMM Issues

Blue stop 0000007B on a Virtual Machine - Resolution with screenshots
Can't convert windows 2000 P2V with 80040154
Error 406 access denied while trying to Add Windows 2008 HV
Error (12700): VMM cannot complete the Hyper-V operation on the server
Failed to create a new virtual machine. (Unknown error (0x8001)
Microsoft VMM Agent installation failed copying: The network path was not found
One of hosts in Microsoft Virtual Machine Manager is pending
P2v using VMM 2008 R2 gets this warning: 13210 and 13222
Receiving error 2902 while trying to add a virtual hard disk
Setup cannot connect to the specified SQL server instance (ID: 339)
Unable to connect to the Virtual Machine Manager server
VMM 2008 R2 error 2921
VMM Error 3148: \\?\Volume is not accessible - Resolution with screenshots
VMM Error (2921)
VMM error 2916 when doing P2V
VMM error: ID 3128 Details (Unknown error 0x80041001)
VMM: Failed to log on with the provided credentials
VMM P2V error: Agent installation failed
VMM shows Unsupported Cluster Configuration
Virtual Machine Manager Issue

Microsoft VMM Agent installation failed copying: The network path was not found

When trying to convert P2V on Windows VMM, you may receive this message: Agent installation failed copying. ID: 415. Details: The network path was not found

Case 1: The physical computer was blocked by a firewall.

Case 2: The physical computer is running Symantec Endpoint. We need to disable the Network Protection or add the VMM server IP to the Endpoint to convert it.

Case 3: The File and Printer sharing was disabled on the physical computer.

Case 4: There is not sufficient free space on the system volume.

Case 5: Use net share command to verify that the ADMIN$ share on physical computer exists. If the ADMIN$ share does not exist, reboot physical computer and then try the operation again.

Post your questions, comments, feedbacks and suggestions

Contact a consultant