"Mouse Not Captured In Remote Desktop Sesion" in Hyper-V

This is a silly little problem, but on my 2008 server I installed a Hyper-V virtual machine (a Win 2008-64 system), and I can't get it to capture the mouse.
Integration services are installed and the mouse is listed but I can't capture it. I've tried Ctrl Alt right arrow.....
I'm used to VmWare and this is my first time with Hyper-V.

Hi Mike,
Is the issue continues?
If you have a Windows Server 2008 with Hyper-V enabled, and the virtual machine is Windows Server 2008 X64, after you create the virtual machine, you
don’t need to install the Integration Services, and the virtual machine will capture the mouse even if you remote desktop into the remote Hyper-V computer and then manage the virtual machine there use Hyper-V Manager.
Please boot the Hyper-V computer to see whether you get the same issue. Please also check whether you get the same issue with other virtual machines.
Best Regards,
Vincent Hu

Similar Messages

Mouse not captured in remote desktop session

I have one (but only one) Hyper-V VM which has the "mouse not captured in remote desktop session" issue. I have researched this problem extensively and so far none of the suggested fixes I have found are working.
The VM is running Windows Server 2012. It is completely up-to-date.
The Hyper-V server its running on is running Windows Server 2012 R2. Also up-to-date.
All integration services are offered in the VM according to the Hyper-V management tool. I have tried removing all integration services from the VM and putting them back with the Hyper-V management tool. This had no effect.
I have also set the VM to "Detect HAL" using BCDEdit... this had no effect.
The only suggestion I could not try is the suggestion to use the "Insert Integration Services Setup Disk..." command from the "Action" menu. I can not do this because a message to "Tap to choose what happens with this device"
message pops up when I try it... and, guess what? I can't "tap" it because like everyone else we don't use touch screens in the server room. I can't click it either because my mouse doesn't work. Trying to click it just brings up the same "mouse
not captured in remote desktop session" message I am trying to get rid of.
Any suggestions?

Hi,
During your description, it seems you are using the touch screen to operate the server, personal experience is in general we don’t choose the touch screen to do this, please
try to use the general mouse try again, it seems your device not compatible with the Server 2012R2. You can search your device in Windows Server Catalog to identify the hardware compatibility.
The Windows Server Catalog.
http://www.windowsservercatalog.com/results.aspx?bCatId=1283&avc=10
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows 2012 + hyper-v + mouse not captured in remote desktop session + integrated services installed

windows 2012 + hyper-v + mouse not captured in remote desktop session + integrated services installed

Hi,
I am using Server 2012 R2 with Hyper-V and CentOS 6.5 that installed GNOME.
Same no mouse on remote desktop session or on the host's Hyper management interface.
From my knowledge, CentOS from 6.4 build in include the IS, how do I update the IS in CentOS 6.4-6.5 guest OS? Any detail docunment for reference?
Thank you.

Mouse Not Working in Remote Desktop Connection

Hello,
I am connecting from a work computer running Windows 7 Enterprise to my home computer running Windows 8.1 Pro. I am able to connect and the keyboard works just fine, but the mouse is not visible or usable in the
remote system. Any ideas?
Thank you in advance!
Josh

Hi Josh,
As the link provided by Arnav Sharma, please take a check to see if the mouse pointer shadow is truned on.
If yes, turn the mouse pointer shadow off on the remote side.
Check the article below fro the detailed steps to disable the mouse pointer shadow:
how do i turn off the shadow cursor which scatters typing on screen?
Best regards
Michael Shao
TechNet Community Support

HP Laserjet 1020 not working through remote desktop

I have a hp laserjet 1020 that I am vpn and remote desktop to a computer at work. I am suupose to be able to print from remote desktop to my local printer (the hp laserjet 1020) using the microsoft terminal Easy Print. The printer is showing up in the printer list, but when I try to print I get an error of Printer not ready. The printer is working fine on the local machine, just not through the remote desktop. I have install the printer drivers on the machine that I am remoting into , just to make sure. Is there anything else I can try. I am not finding any firewalls on either end blocking it?

After many months of frustration and 7 1/2 hours with Microsoft advanced prof support I've finally pinned down this printer and a slew of others. This problem as far as I have come across deals exclusively with HP printers. In simple terms: the drivers are flawed. This 1022 is a prime example. It prints locally and via TCP/IP just fine. I have about 7 other printers and dummy printers in my printer folder. Enter a remote desktop session and ALL of them populate except the 1022. This shows that the hooks and RDT finders are locating your printers and installing them properly as remote printers. All except the 1022.
Log out of your RDT session: goto the local 1022 setup and change the printer driver to a PCL driver. I used a 1200 PCL driver. Now log back into your RDT server and hockus pocus! there is your printer. Totally un-usable because the driver will not run this printer. Caveat: each time I did this XP crashed (I couldn't get to the properties TAB anymore -- I had to un-install the 1022 and then re-install it with at least 1 reboot in the process)
Moving on we go to the HP OfficeJet/LajerJet2840. Same thing. It won't pass through as remote printer in RDT. Go local. Set the printer driver to AppleLaserWriter8500 and boom. (same logout, change, back in steps) and your LJ2840 shows up and works.
While I will have to wait until tomorrow I am betting that this will fix the exact same problem with the HP Officejet 8500A all in one with the exact same problem.
Hey HP? Whats with the drivers??
Another work around if you have a static enough environment is to install your local printer that will not show up under RDT on the server, and then point the port to your fixed IP on your router, and passthru port 9100 to your locally installed printer that is failing. You can now be on RDT and chooses the network printer that is printing to the TCP address of your home (or office) router.

How to capture the remot desktop using RMI?

Hi friends..
I am doing a mini project to capture the remot desktop using RMI. I am very new with this subject. So 'm waiting for the help of experts...

You can't. RMI doesn't do that. After you have captured it, some other way, you can transmit it via RMI, or plain Sockets, or several other ways.

Windows 8 PC not able to remote desktop via Remote Web Access

Windows 8.1 PCs cannot initiate a Remote Desktop session to Windows 7 PCs via Remote Web Access running on Windows Server 2012 Essentials. The Windows 8.1 PC can Remote Desktop to the Windows 7 PC by IP using a VPN, and can connect using
the "Remote Desktop to the Computer" option under Devices in the WSE Dashboard.
All PCs and the server have all Windows updates applied. Specificallly, the Windows 7 PC has KB2574819 is installed and the RDP Policy 8.0 has been activated using local group policy. NLA is not active.
Given that direct Remote Desktop connections work OK but not RDP proxy session, it would appear that the problem has to do with the RD Proxy on Windows Server Essentials.
Is anyone else experiencing this problem? Does anyone have any troubleshooting tips on how to trace this problem down?

Hi,
Please check if there is any error in the remote desktop service log both on the Windows 8.1 client and server sides. You can find the log under Applications and Services logs – Microsoft
– Windows – TerminalServices.
Thanks.
Jeremy Wu
TechNet Community Support

Win svr 2008 r2 ent - user can not log into remote desktop after installing march's 2015 important updates

we installed march's 2015 important updates onto all of our servers. three of our servers are not allowing RDP.
these servers have windows server 2008 r2 enterprise sp1 installed.
we enter in the username and password in the rdp dialog box and click on ok. the rdp dialog box comes back for us to enter in the username and password.
we do have kb3046049 and kb3002657 installed.
is there a v2 of kb 3002657 for windows server 2008 r2 enterprise?
on one of the servers
1. I disabled rdp
2. stop and start the following services
remote desktop configuration
remote desktop services
remote desktop services usermode port redirector
remote procedure call
3. enabled rdp
4. added the users allowed to rdp into server
This allowed us to RDP into that box with the username and password.
But the other two servers the steps performed above did not work.
Any solutions for Win Svr 2008 R2 enter sp1?

Thursday, March 19, 2015
This is a summary of the new and changed content scheduled for release on Thursday, March 19, 2015.
New security content:
This has nothing to do with this issue in this thread, it just happens to have been published today and yet no kb is public.
Security Update for Windows Server 2003 (KB3048051)
Locale: All
Deployment: Windows Update, Microsoft Update, Automatic Updates, WSUS, and Catalog
Classification: Security Updates
Target platforms: Windows Server 2003 and Windows XP
Approximate file sizes:
Windows Server 2003 update: ~ 196KB
Description:
Install this update to resolve an issue which requires an update to the untrusted certificate store on Windows systems and to keep your systems up to date. After you install this update, you may have to restart your system.
http://support.microsoft.com/kb/3048051
It is related to the SSL cert revocation and Microsoft is very lame these days and gets the code on MU but can't sync up the KB.
See:
* Microsoft Security Advisory (3046310)
- Title: Improperly Issued Digital Certificates Could Allow Spoofing
- https://technet.microsoft.com/library/security/3046310
- Revision Note: V2.0 (March 19, 2015): Advisory rereleased to
announce that the update for supported editions of Windows
Server 2003 is now available. See Knowledge Base Article 3046310
for more information and download links.

Can not use any remote desktop like VNC after installing Oracle Linux 6.3

Hi
I just installed OL 6.3 on a HP Proliant ML380 g7. Now I want to connect to the server using any Remote Desktop tools but I can not!
I've activated system>pref>Remote Desktop
But I can not access any of servers from:
- a Mac using, Mac server sharing screen, VNC viewer or Microsoft Remote connection which is in a same subnet
- Other Server Using KRDC, Remote Desktop Viewer, terminal server client or tiger VNC viewer
Also I tried to connect to servers after activating krfb
but it always says no rout to server/ server not found/ connection closed
and remote desktop viewer can not find any host when I try to use option "find"
Please Advise
Thank you in advance

Make sure to enable "require a password..." in the Remote Desktop Preference on the Linux system. Some clients won't work unless this is set. Unfortunately the Remote Desktop Preferences panel on the Linux side does not show you the port it is listening on, but you can get it by clicking on the IP or name that it shows as a link. The first user or vnc server is usually listening on port 5900, then 5901, and so on.
Your problem is probably the firewall on your Linux system. You can disable the firewall on the Linux system:
service iptables stop
However, probably a better idea, simply tunnel the connection through SSH as following:
On the Mac, open the Terminal application from the Applications/Utilities folder. Then type the following:
<pre>
ssh -L local_port:localhost:remote_port -N -f -l username server_address
</pre>
local_port = port on your Mac that does not conflict with any of your own screen-sharing or other services, e.g. 5555
remote_port = vnc server port on your Linux system
username = user for which you have enabled remote desktop sharing
server_address = ip address or FQDN of your Linux system.
For instance:
<pre>
ssh -L 5555:localhost:5900 -N -f -l root 10.0.1.2
</pre>
The trick is now to connect to a local port on your Mac, instead using the address of your Linux server. The communication will be encrypted using ssh going over tcp port 22, which is normally enabled in the firewall.
The Mac screen sharing application is working fine. On your Mac, select "Go>Connect to Server" from the Finder menu and type:
vnc://localhost:5555

File associations not roamed using Remote Desktop Server 2012 R2 Standard

Hello everyone,
As the title mentions, some File Associations does not seems to roam on a RDS 2012 R2 server. We use the following configuration:
Windows Server 2012 R2 Remote Desktop Server(s)
Roaming Profiles to a user based network share
Delete cached copies of Roaming profiles [Computer GPO]
So there is no local stored profile after logoff.
Exclude directories in roaming profile [User GPO]
We only exclude "$Recycle.Bin" for testing. So all other profile settings (Local, LocalLow, Roaming) should be roamed.
With the above settings, some associations are, after logoff and logon not remembered. For example .pdf is always restored to MS Word even if Acrobat Reader is chosen as default program.
When we do not delete the cached copy of the Roaming profile [Computer GPO], the file associations are remembered after logoff and logon.
We did a little of research:
When changing the default application for PDF files to Acrorobat Reader, the setting for this user in the registry is:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pdf\UserChoice
Hash: BTWAFQFaLiw=
ProgId: AcroExch.Document.11
After logging off, the NTUSER.DAT for this users does contains the same settings. I guess the settings are successfully roamed to the shared roaming folder.
But after login, the settings are set back to:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pdf\UserChoice
Hash: mj3iGjB82bU=
ProgId: AppX86746z2101ayy2ygv3g96e4eqdf8r99j
My suggestion is these settings are not restored in the cached roaming profile.
Someone who recon this and knows if there is a solution for this issue?
Using a Association Configuration File (DISM) with the Computer GPO Setting "Set a default association configuration file", we can set the default program for the users. But this is a global Computer GPO setting and not all users must have the same
default programs.
Using this setting is no option for our environment.
Hope Someone can help us.

Hi,
For this you can make one separate group for all that users and applied the policy setting which you want to setup. But as per me, windows uses the Local and LocalLow folders for application data that does not roam with the user. Usually this data is either
machine specific or too large to roam. Maybe your thought would be a workaround.
More information.
Deploy Roaming User Profiles
https://technet.microsoft.com/en-us/library/jj649079.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Screen sharing not working after Remote Desktop 3.2 install

OK, I think I screwed it up.
I'm moving to a new iMac running Mountain Lion, and I need to use Remote Desktop. I own Remote Desktop 3.2 on DVD, so I installed from disk and launched the app. My plan was to download the latest update to 3.6.x, but I figured I would launch it to enter my license key and then quit and download the update.
I was given an error that newer components were already installed and clicked the Quit button. Ugh. Next I went to Apple's download site and downloaded the newest update but when I ran that installer it told me it could not install on my drive.
My grand plan has now left me with no Remote Desktop, and the built-in Screen Sharing core service beach balls when I try to connect to a remote client.
Is there a way to save me from myself?
Thanks in advance,
Bill

Hi Bill,
You could try removing all the installed components manually and then try again (install, don't open but update right away).
According to the installer the files are located in:
/Applications/Remote Desktop.app (that one was hard to find )
/Library/Application Support/Apple/Remote Desktop/
/Library/Preferences/com.Apple.ARDAgent.plist
/Library/Preferences/com.Apple.RemoteDesktop.plist
/Library/Receipts/
/Library/Widgets/RemoteDesktop.wdgt
(not sure if the following files tie into other parts of the OS so removing them may cause issues)
/System/Library/CoreServices/RemoteManagement
/usr/bin/share/man/man1
perhaps a permission repair after all parts have been deleted and a restart before trying again.

Novell login not available with remote desktop on windows 7

Installed Novell Client 2 SP3 for Windows Server 2012 on my terminal server. When I log in from Windows XP to that terminal server I am getting an option to login with Novell Client. On Windows 7 however I only can logon to the server. What am I missing here?

djaquays <[email protected]> wrote:
> Mostly, that MS RDP for Mac ignores the authentication level:i:0 option
> in an RDP file and there's no GUI equivalent to force legacy
> authentication.
Microsoft's Network Level Authentication (NLA) feature is supported in
Windows Server 2008 and later terminal servers, and supported by
Remote Desktop Connection (MSTSC) 6.x and later terminal clients.
Windows XP did not ship with a MSTSC 6.x terminal client, but it is
available optionally through Windows Update.
The NLA authentication is essentially requiring that valid Windows
user account credentials for the Windows Server machine must be
provided /before/ the RDP-level terminal session connection is even
attempted or permitted. If the Windows user credentials you're logged
in with on the client workstation do not already satisfy this
requirement, the NLA-aware MSTSC clients will prompt you for valid NLA
credentials before even attempting to open the terminal session.
In other words, NLA doesn't directly have anything to do with whom you
will become authenticated as within the terminal session, or whether
you'll reconnect to some other already-running terminal session; it's
a new default mechanism which requires Windows credentials for
authorizing you to create an RDP connection to the Windows Server
machine "at all."
Unfortunately Windows Server 2008 and later don't permit you to turn
NLA completely off. You can configure the Windows Server to always
require NLA, which means pre-MSTSC 6.x terminal clients will be unable
to connect. Or you can configure the Windows Server to "not require
NLA" ("Allow connections from computers running any version or Remote
Desktop"), but this still means Windows Server will use NLA if the
workstation's MSTSC client supports NLA.
The only option which has been available to "disable NLA" even when a
Windows Server 2008 or later terminal server and a MSTSC 6.x or later
terminal client are involved is to configure the
"enablecredsspsupport:i:0" setting in the MSTSC client's .RDP file
(e.g. default.rdp in the My Documents folder), in addition to
configuring the terminal server to "not require NLA."
Once you have "Allow connections from computers running any version or
Remote Desktop" set on the Windows Server, and
"enablecredsspsupport:i:0" set in the MSTSC client, now you're back to
the Windows XP & Windows Server 2003 behavior where an RDP terminal
connection can be established without first having to supply NLA
credentials, and the first thing the MSTSC client user will experience
is the full normal credential provider-based login experience just
like you see at the physical console of the terminal server.
Note that if you do leave NLA enabled and supply NLA credentials
during the MSTSC connection attempt, after successfully using those
credentials to authorize creation of the RDP connection, the MSTSC
client will /also/ default to using the NLA credentials as default
credentials to attempt logging on with within the terminal session
itself. In other words, if you successfully supply NLA credentials,
by default you also become logged in on the terminal session and go
straight to the desktop of the Windows user account specified in the
NLA credentials. So even though "NLA credentials" and "whom I will
logon as within the terminal session" are two separate things, by
default the MSTSC client tries to use the same credentials for both.
But it's not that the NLA credentials "must" be used for logging in on
the terminal session; that's simply the default behavior. If you
leave NLA enabled on the Server 2008 or later terminal server, after
NLA credentials are successfully used to authorize creation of an RDP
connection, if you wanted to instead be prompted within the terminal
session with the normal credential provider login experience, enable
the "Always prompt for password" on the Windows Server 2008 or later
terminal server.
(On the Server 2008 or later machine, under "Administrative Tools"
find the "Remote Desktop Services" group and launch the "Remote
Desktop Session Host Configuration" console. Highlight/select the
"RDP-Tcp" connection, right-click and select "Properties". On the "Log
On Settings" tab elect "Always prompt for password".)
That sounds like probably the scenario which fits best for the "I have
a Macintosh-based client which doesn't allow enablecredsspsupport:i:0
/ authentication level:i:0." You would leave NLA enabled on the
Server 2012 machine, but enable "Always prompt for password" in the
RPC-Tcp connection properties on the Server 2012 machine. Such that
after NLA authentication was performed and Windows allowed creation of
the terminal session, instead of immediately also attempting to login
within the terminal session as the Windows account specified in the
NLA credentials, Windows will instead present the normal interactive
credential provider login experience to allow the user to specify whom
they want to login as.
Finally, note that everything described above applies even to a
Windows Server and Windows client workstation that do /not/ have the
Novell Client for Windows installed. The same mechanisms remain in
effect even once the Novell Client is installed; the presence of the
Novell Client just changes what credential providers would be used or
presented within the terminal session once the terminal session was
allowed to be created. The fact that NLA is required by default and
requires valid Windows credentials in order to authorize an RDP
connection is still the same, regardless of whether the Novell Client
is present or not.
Alan Adams
Novell Client CPR Group
[email protected]
Novell
Making IT Work As One
www.novell.com
Upgrade to OES Community
http://www.novell.com/communities/co.../upgradetooes/

Ipad bluetooth keyboard not working with remote desktop

My clients ipad bluetooth keyboard works any other time, just not when connected to his servers via the remote desktop. PC Windows 7 Servers.
I'm trying to get the keyboard information, but any ideas?

Are you using an app like LogMeIn Ignition to access your servers? I believe that LogMeIn Ignition requires you to tap a little keyboard button near the bottom of the screen to activate use of the keyboard (that's how it works in Splashtop Remote, can't be much different in LogMeIn Ignition.)
Are you sure the app you have supports blue tooth keyboard support with remote desktop? (not sure if they have to, I just recall seeing this in Splashtop patch notes awhile ago.)
HuskieN.

Hardware accelerated views have been disabled because they are not compatible with remote desktop

Just started getting this error after updating to CC and latest NVIDIA drivers:
I don't run Remote Desktop. After this message appears, the checkbox in my preferences is disabled:
If I reboot my computer, the checkbox is again enabled, but then the error message about the remote Desktop appears, not right away, but after several minutes.
Details:
Windows 7 Pro
Intel i7 CPU X980 @ 3.3GHz
24GB RAM
GeForce GTX 680, Driver 320.49
AE CC 12.0.0.404
Thanks for any help.

Currently running apps:
Firefox
Chrome
TextPad
Adobe Prelude
So, as a test, I did the following:
Launched Adobe After Effects CC.
Looked at "Preferences" -> "Display" -> "Hardware Accelerate Composition......" ... it is enabled
Locked my workstation. [Windows key - L] I don't have a screensaver ... just plain black.
Typed my password to unlock. The dialog box shown at the top of this thread appears.
Closed AE.
Re-launched AE.
The option in Preferences is unchecked, but it is selectable.
So, that is MUCH more convenient thatn having to reboot the machine. Don't get me wrong here ... it's still annoying. It's especially annoying because I developed the (good) habit of locking my workstation whenever I walk away from it. During a typical work day, I may lock/unlock my workstation ten times ... or more.

USB Devices not working in Remote Desktop

Hi,
I have tried to use USB devices in Remote Desktop session. I did enable RemoteFX for USB devices and select Other supported RemoteFX USB devices before
establish connection; but, cannot find any device in Remote Desktop. Did I miss any configuration?
Regards,

Hi,
From your description, I understand you may experience 'USB device can’t be redirected on TS' issue. Please check the following aspects one by one and let know the result:
1)Please open Remote Desktop Connection, click Local Resource tab and More button, unfold device node. Please check if you choose all device letter.
2)Open Terminal Services Configuration, right-click RDP-tcp, choose properties. In Client settings, please check if disable device has been applied.
3)Please run Rsop.msc on Terminal server and see if Do not allow driver redirection has been configured under computer configurations\Administrative Template\Windows Component\Terminal server\Device and Resource redirection
For more information about how to use device in a remote desktop. Please refer to the following article.
How can I use my devices and resources in a Remote Desktop session?
http://windows.microsoft.com/en-us/windows7/how-can-i-use-my-devices-and-resources-in-a-remote-desktop-session
Configuring USB Device Redirection with Microsoft RemoteFX Step-by-Step Guide
http://technet.microsoft.com/en-us/library/ff817581(v=ws.10).aspx
Hope this helps,
Ada Liu

"Mouse Not Captured In Remote Desktop Sesion" in Hyper-V

Similar Messages

Maybe you are looking for