Vista - Hyper-V Integration Services problem on Windows 2000 Server...

I have an old Windows 2000 Server which I'm trying to virtualize under
Hyper-V. It's not joined to the domain because it's a web server, so I
don't think I can use VMM to do a P2V conversion.

What I've done so far is this: clean install of Windows 2000 Server
under Hyper-V, backed up source server using NT Backup, restored
backup to clean 2000 target virtual server. Most things are working
okay in the new virtual server, but I am having a few problems.

I can't seem to fully install Hyper-V Integration Services. If I try
to install it, I am told "A previous installation of Hyper-V
integration services has been detected. Click OK to upgrade or repair
this installation." It's not listed in Add/Remove Programs, so I'm not
sure where it's hiding. Anyway, I hit OK, the installation starts,
then I get "An error has occurred: Fatal error during installation."

Service-wise, it appears that the Plug and Play service is hanging
while trying to startup, and I do have some entries in the event logs
to that effect. It simply reads "Starting". I'm unable to stop it or
restart it. It looks like some other services aren't starting up
either because of dependencies on the Plug and Play Service.

Is there any way for me to remove whatever pieces of Integration
Services exist now and reinstall it? Any other ideas how I can correct
these errors?

Thanks,

Mike

I am having the same problem with P2V of Windows 2000 server SP4, did you ever find a solution?

Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com

I have finally found a workaround solution to a Windows 2000 VM in hyper-V with the Integration tools installed not starting up properly and some of the services not starting.

Disable the net stop "Windows Management Instrumentation Driver Extensions" service, with this disabled the server will start up fine with all services started.

This service is required for Windows update to work but it can be started manually once the server is running if required, always change it back to disabled as if it is set to manual it will still attempt to start on startup and cause the problems.

This has been frustrating for somtime so it's nice to finally have something that will work.