App-V, Hyper-V, and P2V - Veritable Volumes of Vexation!

Could I add more V to this? I could, but I don't condone it.

Once more I have found that the permissions that App-V imposes on VSS get in the way on servers, this time when doing a P2V migration of several servers into our Hyper-V farm. As you may have seen in yesterday's post, I ran into problems with creating new VHDs on my Windows Storage Server 2008 R2 box while I was setting up the iSCSI SAN. Today I ran into an access-denied issue.

It stared innocently enough - I tried to move a physical server into the Hyper-V farm and it failed with this error message:

VMM does not have appropriate permissions to access the resource on the <REDACTED> server.

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

ID: 2910

Details: Access is denied (0x80070005

This vexed me. (ha! I knew I could get one more V word in there!) Thinking I had meatfingered the password, I re-entered it, and received the message again. Remembering the lesson from yesterday, I opened up the control panel and ripped out the App-V client. Lo and behold, the problem has vanished from my system and the P2V migration is underway. I rinsed-and-repeated this with a couple of virtual machines in my XenServer test farm and found that it was repeatable 100% of the time.

Microsoft, oh Microsoft, how I love thee, and how I love thy App-V goodness, but please... fix it!