Cannot replace VMware mouse with Hyper-V mouse

We restored a Windows XP Pro SP3 machine from a ShadowProtect backup. The source VM is running on ESXi (unlicensed), and we restored it to a Hyper-V environment running Server 2012 R2 Datacenter.

Everything works except the mouse. Device Manager shows a  "VMware Pointing Device," which I can remove, but Hyper-V never takes over and installs the mouse driver. It just keeps coming back as "VMware Pointing Device."

I've tried reboots, hardware uninstall/reinstall, reinstalling Integration Services. I even tried unpacking the drivers from the Integration Services cabinet file and trying to update the drivers manually. All to no avail.

Anyone know of a way to get the mouse working in XP on a Server 2012 R2 server?
highdellAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
Does the VMware Mouse driver not work?  It does for me (VMware Workstation). No issues.  

Sorry, I see you move the machine to Hyper-V.  Did you change the hardware?  Again, a concept from VMware, but necessary for a machine change.
highdellAuthor Commented:
The VMware mouse driver does not work. Whenever I click the mouse, it just toggles the Start Menu.... the same as if you typed the keyboard shortcut: Ctrl + Esc.

The hardware has changed along with the hypervisor platform. The VM moved from a PowerEdge 2950 to a PowerEdge R720, but does that matter?

This VM was created on the VMware hypervisor, and I just moved it over to Hyper-V. Everything works except the mouse.

For what it's worth, I cannot uninstall VMware Tools because it can no longer talk to the VMware host.
JohnBusiness Consultant (Owner)Commented:
I am not sure how you can proceed.

You need to uninstall the VMware Tools (and should have before moving the machine).

See if this VMware Knowledgebase Article will help you force uninstall the Tools.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2010137

Here is a more dangerous (registry) way to force uninstall the Tools.

http://techhead.co/how-to-manually-remove-vmware-tools/

I think you need to uninstall the tools to change the mouse.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

highdellAuthor Commented:
Yeah, we were not permitted to remove the VMware Tools before the move.

The manual uninstall was successful, but Windows XP still identifies the mouse as a VMware mouse, even when forcibly removing the drivers in the %%\system32\drivers folder.

Thank you for your help, though!

I'll try anything if anyone has any ideas.
JohnBusiness Consultant (Owner)Commented:
This Microsoft Hyper-V article suggests you cannot change the machine hardware after creating the machine.

https://technet.microsoft.com/en-ca/library/dn282285.aspx

You may have to make a new XP virtual machine in the Hyper-V environment.
noxchoGlobal Support CoordinatorCommented:
The Shadow Protect has a Hardware Independent Restore. Apply this feature to restored machine.
highdellAuthor Commented:
I tried it again, this time disabling the VMware Tools before restoring the VM with HIR from StorageCraft... all to no avail.

Now it sees it as just a PS/2 Mouse and no drivers are ever detected, not even after the HIR.

I guess Windows XP just doesn't work well on a 2012 R2 server, maybe?
noxchoGlobal Support CoordinatorCommented:
Well, XP support was stopped at the time when HyperV Generation 2 was out. So it can be that MS knowingly did not include the XP drivers in it.
noxchoGlobal Support CoordinatorCommented:
A question: have you installed Integration Services on this VM? If yes then is them mouse working if you use Remote Desktop Protocol to connect this VM remotely?
highdellAuthor Commented:
Integration Services are installed, yes, and we're able to use the mouse in an RDP and LogMeIn connection, which is good enough to do what we need.

Just do NOT like not having the mouse driver installed..

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JohnBusiness Consultant (Owner)Commented:
You can always try building a new machine (30 minutes) to see if the XP mouse works when built as a Hyper-V machine.
highdellAuthor Commented:
Looks like it's not possible.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hyper-V

From novice to tech pro — start learning today.