• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Hyper-V 2012 and XP guest

KillerFry

Limp Gawd
Joined
Apr 1, 2008
Messages
373
Hey there;

I'm almost done with the virtualization of my site infrastructure at work. All we're missing is a Windows 2000 SP4 and Windows XP computer.

The Win2K gives me a blue screen, but I'll deal with it later.

It's the XP that's giving me a headache. When I setup the VM, it doesn't capture keystrokes nor the mouse. No even if I click on the Ctrl+Alt+Del button on the top left.

Looking around the Interwebs, it seems it is a problem with the USB drivers. I've found solutions to this problem for VMware, but not with Hyper-V.

I have already tried plugging in a USB keyboard and mouse before creating the VHD with Disk2VHD but still, no go.

This describes my issue too: http://forum.sysinternals.com/xp-vhd-login-not-possible-no-keyboard-and-no-mouse_topic26118.html

But since it's joined to a domain, even if I try Safe Mode with Command Prompt I get asked for credentials.

Any ideas?
 
Does the XP VM have network connectivity? You could RDC into it and try installing the drivers, if RDC is disabled you can do the remote registry hack to enable it.
 
I had one issue a while back when I converted a customers XP instance to HV2008R2

They had some mouseware apps installed, I had to remove all the drivers first, then convert, then once it booted up, I had to wait a while for it to redetect all the devices.
 
Regarding network connectivity, I do have the virtual switch configured to it and unplug the network cable from the original computer. It is setup to get an IP from DHCP; yet, it won't allow me to use a RDC to log and install the drivers.

I don't know for sure if creating the VM disables RDC, but in the original computer it is activated.
 
do you get to the logon screen with RDP?
Your using a local logon, not a domain logon and your going by the IP not the name?

(IP of the VM might be different than the physical PC)
 
Have you installed Integrated Component Services on the VM's?

I've installed Windows 2000 AS4 on Hyper-V (via PXE with a standard ISO), on Server 2008 R2. I see no reason why it wouldn't install on 2012.
 
Back
Top