I know this may not be 100% related, but it occurs as a direct result of my P2V Process. I am trying to P2V a 2000 system, and after it reboots into the offline mode, it suddenly loses connectivity to the PC. I noticed on the VMM2008R2 server's Event Log the following:

Event ID 10009: unable to communicate with the computer p2v-poov using any of the configured protocols.

The computer's name is really "BOB", but VMM thinks the name is now p2v-poov, and although when it reboots into PE mode it still retains the same IP as "BOB", VMM is looking for and only recognizing the DNS name. It will not continue to the next step of Deploying the hard disk... 

So, what in the mean time I have had to do was create a CNAME/A record in DNS for that IP address and then suddenly DNS resolution for "p2v-poov" works, and the P2V process continues. I have checked my DNS security settings and it allows Dynamic DHCP updates for secure and unsecure hosts. Even if the job fails and I retry the P2V job VMM just renames the host again to "p2v-[something]" and I have to again go into DNS, delete the older entry, and retry with a new entry. 

Have a look at this thread fro the past, maybe it will be helpful: http://social.technet.microsoft.com/Forums/en/virtualmachinemanager/thread/54072d39-60de-4537-92b8-56e5874c52d1

---
Paul Svirin
StarWind Software developer ( http://www.starwindsoftware.com )

Thanks, but I (think I) saw that one already. Unfortunately, that post also talks about the prior version. I am using the "new & improved" version. :-)

try to update your target server NIC drivers..

I did - didn't help.

Hiya,

Just out of curiosity.
Did you try to start the P2V process on IP?
"Select target 10.0.1.230(rather than BOB)"

No - I did not - but I don't think it really matters what the name of the PC is - since at the end of the day - at least from what I saw - it is always looking for the record in DNS corresponding to the p2v-xxxx name the VMM process creates, regardless of what the computer name is.

Hiya,

For my case it was what made it work for me :)
Exactly as you say, it changes the name and looks for it, but no record exist, hence it will fail.

Still not being a true solution, more a workaround....

Worth a shot - next time I need to try I will give it a whirl.

P2V Troubleshooting - http://blogs.technet.com/jonjor/archive/tags/P2V/default.aspx

Additionally, you can run VMMCA tool to validate the configuration for various components - http://technet.microsoft.com/en-us/library/cc764328.aspx (highly recommended)
Some addiotional Technet resources - http://technet.microsoft.com/en-us/library/cc764339.aspx

Use this video to fix: https://www.youtube.com/watch?v=reb4eMcpl20