IT Core Blog

Never stop questioning. Curiosity has its own reason for existing…

Virtual Machine Manager Rollup Package Issues…

leave a comment »

Today we decided to apply the System Center Virtual Machine Manager 2008 R2 Rollup Package .

Since that our VMM R2 doesn’t have internet access, we downloaded the update package from the Microsoft Update Catalog. The process went okay for VMM server, after that it’s was time to update the agents, and FUN began!!! 🙂

After starting the update in the first host the process fails with the error 403:
Error (403)
VMM01 is not a valid network computer name. 
Recommended Action
Only fully qualified domain names and NETBIOS computer names are valid. An IP address is valid only for hosts on a perimeter network, ESX hosts, and hosts joined to the domain by using an IPv6 address. Check the computer name, and try the operation again.

What!!! VMM01 is our SCVMM R2 computer name??!!! From the error description appears to be a problem with name resolution process!!!

Note that in the previous screen the “Update agent” operation was performed by a user with local Administration permissions on both Server and VMM. After that the VMM server “tries” to refresh the physical host but the process fails with error (2910) using the VMM service account??!!!

Error (2910)
VMM does not have appropriate permissions to access the resource  on the srvhv01.domain.tld server.
(Access is denied (0x80070005))

Recommended Action
Ensure that Virtual Machine Manager has the appropriate rights to perform this action.

Great!!! Nice!!! 😦 – Note, before agent update we can see that no errors occur in refresh process, either using the domain account that we used to update the agent nor using the VMM service account!!!

Weird 😦 – Let’s try to remove the Physical host and re-add it again!!!

Hum… Same 403 error, this is not working… 😦

Okay, in our scenario, and after a couple of more tests, we verify that something went really wrong with this update. Let me describe some of them:

Error (2910)
VMM does not have appropriate permissions to access the resource C:\Windows\system32\qmgr.dll on the srvhv01.domain.tld server.
(Access is denied (0x80070005))

Recommended Action
Ensure that Virtual Machine Manager has the appropriate rights to perform this action.

Error (2910)
VMM does not have appropriate permissions to access the resource D:\VMs\SRVVM015\Hdd01.vhd on the srvhv02.domain.tld server.
(Access is denied (0x80070005))
Recommended Action
Ensure that Virtual Machine Manager has the appropriate rights to perform this action.

Note the previous screen that is saying “VMM  does not have permissions for the VHD file for SRVVM015 in srvhv02“?!! WHAT!!! The SRVVM015 IS NOT hosted in SRVHV02!! This VM is hosted on SRVHV10, what #!#”#@#@#@#@#&#*#kc!!!!

Permissions, Permissions, Permissions!!! 🙂 Self explanatory 🙂

Error (2910)
VMM does not have appropriate permissions to access the resource \\vmm01.domain.tld\MSSCVMMLibrary2 on the srvhv01.domain.tld server.
(Access is denied (0x80070005))

Recommended Action
Ensure that Virtual Machine Manager has the appropriate rights to perform this action.

  

Solution:

In our scenario we need to fix several things before make this all work again.

1 – We had to add the Physical hosts (Name and IP) to the local hosts file in VMM (This process was done only for a few hosts, there’s a possibility that in fact we do have a name resolution problem with specific hosts).

2 – We need to fix the security permissions in the Physical hosts. We need to add the service account of VMM to the  “Virtual Machine Manager Servers” and to local administrators security group.

3 – We need to fix the permissions in the VMM shares, yep, those were all missing as well 😦 – We notice this problem when we uninstall the agent on the Physical hosts and from VMM server. When we tried to add the host to VMM server again we got an error telling us that the permissions for the VMM share were missing.

4 – In some hosts (For hosts in DMZ this is mandatory) we had to remove the physical host from the VMM server, uninstall the VMM agent, and then re-add them again after we did all previous steps mentioned before.

Note: In most scenarios, Step 2 will be enough, but you may need to perform all steps when dealing with several problems at once. 🙂

Let me know if this worked for you – 🙂

Advertisements

Written by IT Core

February 17, 2010 at 3:26 PM

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: