mouse unavailable inn remote desktop-session when integration services are installed inthe guest operating system. for more info search integration services help.
-
2012年5月1日 17:45
mouse unavailable inn remote desktop-session when integration services are installed in the guest operating system. for more info search integration services help.
This is a HP blade physical server which we did a P2V using VMM.
We cannot integrate services when in normal boot up.
In safe mode we can integrate services(you get a progress bar which you do not get with normal mode.)
However we cannot control the mouse so it is difficult to complete the rest of the NIC integration for this VM.
Normal windows keys do not work in the console.
I have been using tab key, arrow keys,... to no avail.
PLEASE SUGGEST SOMETHING THAT WILL WORK. WE NEED THE MOUSE TO WORK. OR COMMANDS THAT WILL WORK WITH CONSOLE.
dsk
- 編集済み kimdav111 2012年5月1日 17:45
すべての返信
-
2012年5月1日 18:19モデレータ
Can you please provide the OS that is in the VM?
The Integration Services require certain service pack levels for older operating systems such as Server 2003 and XP.
Have you tried using the Hyper-V Manager console, instead of the SCVMM VM console application?
Have you tried the RD session specific shortcut key combinations (this is not clear in your description)?
http://msdn.microsoft.com/en-us/library/windows/desktop/aa383500(v=vs.85).aspx
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
2012年5月1日 18:21
win 2008 R2 with no sp1.
dsk
We are using hyper-v console via server manager and not the VMM.- 編集済み kimdav111 2012年5月1日 18:22
-
2012年5月1日 18:31モデレータ
The Integation Services are built in to the OS, but they still need to be installed to match the release level of the hypervisor the VM is running on.
I am not clear what you mean by: "We cannot integrate services when in normal boot up."
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
2012年5月1日 20:59
never mind the comment: we cannot integrate services when in normal boot up.
We applied windows sp1 to the original physical server. Now we are going to do another P2V--2nd virtual machine.
Do we have to do any clean up in AD? Delete 1st virtual machine?
Or can we just turn off the 1st virtual machine? what about SID's?
dsk
-
2012年5月1日 21:05モデレータ
Just power off the first VM that you attempted so they don't conflict.
There could be a problem with AD if the first conversion attempt VM has updated the computer account password in AD, but htat can be fixed with an un-join and join.
I still do not what you mean by "we cannot integrate services" - I don't understand how you are using the phrase.
The biggest thing you have to worry about in doing a physical to virtual conversion is hardware monitoring or management agents that might have been installed on the server. These generally always cause problems after virtualizing. This includes HP and Dell managment agents - or systems that were installed using SmartStart for example.
I am still stabbing in the dark at what your real issue might be.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
2012年5月1日 21:11so when you say "unjoin" do you mean to remove from domain then readd to domain?
dsk
-
2012年5月1日 21:13モデレータ
yes, un-join the computer from the domain.
In extreme cases; unjoin, delete the computer account from AD, join the domain.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
2012年5月7日 6:11
-
This sounds like a HAL problem. What is the child OS? If it is Vista or 2008, do this:
1. start msconfig
2. go to the Boot tab
3. Click the Advanced options button.
4. Check the Detect HAL checkbox.
5. Click OK.
6. Click OK.
7. Reboot the vm.
8. Install Integration Services.
Regards,
Abhishek
-
-
2012年10月5日 19:15
Hi, I am having the same problem and I tried the steps above posted by ABhishekUK but I was not able to see the Detect HAL checkbox.
I am using a converted machine and before I converted the machine from one hyper-v to the other hyper-V. The machine works fine but I soon as I do the convertion my mouse does not work. Can you tell me what would be the best way or what can I change on the original hyper-V so I don't have this problem when I transfer the machine over?
I would really appreciate it.
Thanks
CC
-
2012年10月5日 19:28
I am also using a 2008R2 x64 server and I need to convert R2 Hyper-V to another Hyper-V on another server and as soon as the convertion is done I start the machine and I try to click with the mouse and I keep getting the message " the mouse is unavailable in a RemoteDesktop session when the virtual machine guest services are not installed" then I shut down the machine, right click the machine and selected the option to install the guest services and then when I start up the machine I keep having the same problem.
I would like to know wha would be the best setting before I transfer the machine or how can I fix it.
Please let me know
Thanks
CC
-
2012年10月5日 20:41モデレータ
The Detect HAL checkbox is specifc to certain versions not all releases (2003, 2008, 2008 R2, 2012) have this option.
Moving a VM from one Hyper-V Server to antoher dose not require a conversion. Simply an Export and Import.
Always move to a newer version of Hyper-V and after you do, you need to update the version of the Integration Components in the VM.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
2012年10月8日 15:16I don't have a Hyper-V server I just have the VMM and the only options I have are: Create a New Virtual machine, Convert a Physical server or Convert a Virtual Machine. How can I import? I don't have the option. That is why I am using Convert a physical machine. Any other sugestions?
.png)
