Skip to main content

SCVMM Error (2912) when creating a VM from the Self-Service Portal workaround

By

While using the Self Service Portal on SCVMM, I received this error when creating a virtual machine.

 

Error (2941)
VMM is unable to complete the request. The connection to the agent on machine [SCVMMServer] has been lost.
(Unknown error (0x80072efe))

Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic.

 

In the job details, the error occurred at step 1.5 Install VM Components.  This issue was reported to Microsoft on October 12, 2008.  The suggested fix on June 26, 2011 does work, but with an issue.  If you were using quotas to help manage the resources your users were consuming, the record of this quota usage will be lost.  The users quota will have those points returned to it as if they are not being used.

 

To prevent the loss of data associated with the host, here is an easy alternative.

 

  • Go to the Hyper-V manager on the host that the deployed VM resides on.
  • Make sure the correct VHD files are attached and that correct virtual network is attached.
  • Start the VM and finish any installation activities from the deployment.
  • Install the integration services if necessary.
  • Properly shut down the VM.
  • Start the VM back up.
  • In the VMM manager console, right click the VM and select Repair.
  • The only option you should get is Retry.  Should Ignore be an option, us it.
  • Let the process finish.  If it errors again, attempt the Repair.  You want it to present to you the option of Ignore. Once you can ignore the errors, your VM will be functional in the VMM console.

 

This procedure is a bit awkward, but it preserves not only the quota points, but all settings and database information associated with the host.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more