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.

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.

"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

I need windows 7 screensaver to activate after terminating a remote desktop session

I need windows 7 screensaver to activate after terminating a remote desktop session
Ok, so this one is slightly complex.
I have a monitor at work which needs to display company info via a screensaver set to scroll through a series of images. This is a pretty standard thing, but where my problem occurs is that the screensaver must be updated remotely each
day via Remote Desktop, and not by a local user sitting at the PC itself. This works on XP with a bit of hacking and playing with settings. But it won't work on W7.
Ok, so the XP setup first:
When terminating the remote session, on the XP machine the system looks here:
C:\windows\system32\config\defaultprofile\administrator’s documents\administrator’s pictures
OR
C:\WINDOWS\system32\config\systemprofile\ administrator’s documents\administrator’s pictures
for the images to display during the screensaver, so I placed a shortcut to this folder (whichever one of the two it is on either of the two PCs i am doing this on; for some reason it isn't always the same path across all machines)
on the desktop and had the user place the images in there. I also do a small registry hack so that after a timeout of 60 seconds, the screensaver looked in this location, found the images, and displayed as you'd expect. It always looks here after a remote
session, and ignores the screensaver configured in the control panel UI, hance these stpes were necessary.
So, now the PCs are being upgraded to W7, but this isn't working. I think it's because on W7 the desktop isn't simply being locked when a remote session is started, the entire user is being logged off. Once the session is terminated,
the W7 PC sits at the login screen indefinitely and no screensaver ever displays.
Does anyone know a workaround here? Sorry for the overly complex explanation, and if it doesn't make sense I'd be happy to elaborate. Thanks.

Hi,
Please see if the Screen saver timeout setting helps:
Group Policy Settings for Personalization
http://technet.microsoft.com/en-us/library/ee617164(v=ws.10).aspx
Thanks.
Nicholas Li
TechNet Community Support

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

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

Windows Server 2012 The licensing mode for the Remote Desktop Session Host server is not configured

Hi
I have a standard Windows Server 2012 that is hosted in the cloud by a hosting provider -
This server has been up and running fir 6 months - recently we have been getting a warning
"The licensing mode for the Remote Desktop Session Host server is not configured" - The Remote Desktop Session Host server is within its grace period, but the RD Session Host server has not been configured with any license server.
Yet, we only use this with 2 connections as part of the standard licence agreement and this server is not used as a user's desktop only an ftp and web server- do therefore we do not need to purchase any cal licences (we have another server with the same
hosting company that does not have this issue and has been up for 18months)
Please can someone advise how I resolve this issue, the hosting company states that I must resolve it as they only host and resell the server licence
Thank-you
Richard Steele

Hi Richard,
You need to uninstall Remote desktop session host feature. After removing it, you will default two connections which does not need to purchase RD CALs'.
Thanks,
Umesh.S.K

Remote Desktop Session Host on Server 2012 not domain-joined

I have a server 2012 which is running Remote Desktop Session Host role without the Connection Broker like described here:
http://support.microsoft.com/en-us/kb/2833839
Now the client would like the Network Level Authentication (NLA) disabled. And since server 2012 does not have the Remote Desktop Session Host Configuration tool, I have to use the server manager console.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/630cc818-69b0-4e1c-8d65-1b895b20e203/where-is-the-remote-desktop-session-host-configuration-tool-in-server-2012-?forum=winserverTS
But when I go to the remote Desktop Services of Server manager, it says “You are currently logged on as local administrator on the computer. You must be logged on as a domain user to manage servers and collections.”
So I tried finding some Powershell cmdlet could help me with the problem. I guess
Get-RDServer
or Set-RDSessionCollectionConfiguration would be the ones but I can’t seem to make them work.
Any help, or a hint that I going in the right direction or not?

Hi,
Have you configure the certificate for your server?
Add the user under Remote Desktop user local group, configure FQDN name of server. Please see that if we are using RDS server in workgroup then most of the tools provided to make managing/configuring RDSH servers easier in 2012 will not work in a workgroup
configuration including some PowerShell command. You can check the below article for information.
Deploying a RDSH Server in a Workgroup – RDS 2012 R2
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]

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.

Windows 2012 Remote desktop session host server not detecting RD licensing server

Hi,
We have a customer server which is Windows 2012. We installed RDS session host server role and configured it to use RD licensing server as per the
https://support.microsoft.com/kb/2833839?wa=wsignin1.0
After configuring, when I open RD license diagonser tool, it says, RD license server is not available. Also shows, credential not available. When I enter the credential by clicking, provide credentials, it does not get applied. I see no event logs related
to RD service. However, I see the below event log which points to RD licensing server.
DCOM was unable to communicate with the computer <RD license server> using any of the configured protocols; requested by PID 273c (C:\Windows\system32\mmc.exe).
Please help in fixing the issue.
Thanks,
Umesh

Hi Umesh,
Thanks for your comment.
During your configuration, have you specified RD License server for RDSH to use?
You can also specify a license server for the RD Session Host server to use by applying the Group Policy under below path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
Use the specified Remote Desktop license servers – Provide the FQDN of the license servers to use
Also this setting can be specified by below method.
To configure the license server on RDSH/RDVH:
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj.SetSpecifiedLicenseServerList("License.contoso.com")
Note “License” is the name of the License Server in the environment
To verify the license server configuration on RDSH/RDVH:
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj.GetSpecifiedLicenseServerList()
More information.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
In addition you can refer this article for reference.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Windows 2012 R2 - Remote Desktop Sessions, RemoteFX, GPU, Blue Screen RemoteFX adaptor

Nvidia GPU GRID K1
Host Server - Dell Power edge R720 128 gig RAM 2 Xeon E5-2640v2 2.0GHz, 20M cache 8c
Windows 2012 R2 full installation – Bios and all hardware with latest updates.
Roles - Hyper V and Remote Desktop Virtualization Host
EPT, GPU, WDDM (latest drivers) compatible for RemoteFX and fully up to date.
I have disabled the video adaptor on the motherboard.
I cannot complete with administrative permissions;
dism /online /enable-feature /featurename:Microsoft-Windows-RemoteFX-EmbeddedVideoCap-Setup-Package
Error: 0x800f080c
Feature name Microsoft-Windows-RemoteFX-EmbeddedVidoCap-Setup-Package is unknown
Question 1 - because video card on motherboard disabled, do I still need to complete this command?
VM’s
**I’m not interested in VDI but more Remote Desktop Sessions and the option to ‘pinch and zoom with Windows 8.1 tablets**
VM1 - Windows 2012 R2 configured as generation 1 that is fully patched.
This VM is able to start up and run until I add the new hardware for the RemoteFX Video adaptor from within the Hyper V settings. When I start the VM the server blue screens. I have tried multiple VM’s with 2012 but same thing
If I created the VM as Generation 2 I am able to start the VM but the RemoteFX adaptor doesn’t appear in the device manager. I have read generation 2 isn’t compatible with RemoteFX.
VM2 – *Testing purposes* - Windows 8.1 Enterprise configured as generation 1 that is fully patched.
This VM I am able to start up and run the VDI after the RemoteFX video adaptor is installed, also the correct adaptor appears in the device manager. This seems to at least work correctly but I cannot pinch and zoom and the experience is poor.
GPU summary within the Hyper V settings state there are 4 physical GPU’s all of which can be used with RemoteFX and that 1 virtual machine are using the GPU (Windows 8.1 enterprise VM)
Firewalls off, latest RDP clients
I have read you should be able to use Windows 2012 R2 and we should be able to use the sessions with pinch and zoom but now and then you come across something that tells me different.
Question 2 – I need this to work with Windows 2012 R2 so we can use Remote Desktop Sessions
and the tablets can use pinch and zoom, anyone tell me what I may be doing wrong?

Hi,
Thank you for posting in Windows Server Forum.
As per my research, you need to run the command although video adapter is disabled on motherboard. If you install the RemoteFX cap driver, the integrated video adapter is disabled while the operating system is running.
For more information you can refer beneath article.
1. RemoteFX (with Hyper-V) is a serious business tool. For games.
2. Configure RemoteFX in Hyper-V running Windows Server 2012 with low end GPU
Hope it helps!
Thanks.
Dharmesh Solanki

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

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/

Can I use System Center 2012 Endpoint Protection in "Windows Server Remote Desktop Session Host" without buy the license ?

Can I use System Center 2012 Endpoint Protection in Azure Virtual Machine Gallary's "Windows Server Remote Desktop Session Host" without buy the System Center 2012 Endpoint Protection license ?
I want to protect my Azure RemoteApp against the malware.
System Center 2012 Endpoint Protection installed Azure Virtual Machine Gallary's "Windows Server Remote Desktop Session Host".
Now, I try to build Azure RemoteApp template by using the Azure Virtual Machine Gallary's "Windows Server Remote Desktop Session Host" .
Regards,
Yoshihiro Kawabata

Hi Yoshihiro,
Unless and until Microsoft modifies the license terms for System Center 2012 Endpoint Protection and/or modifies the Online Services Terms (OST) and/or other document explicitly saying that use is included with the Azure RemoteApp (ARA) monthly
fee I recommend you assume as that it is
not included and license it separately for ARA if that is even possible, which is a separate question.
For licensing it is best to be cautious and make decisions based on the official documents that are available that govern use of the software and services involved. At this moment I'm not able to find a Microsoft document that grants use of System
Center 2012 Endpoint Protection with Azure RemoteApp.
When I first used the gallery template and noticed that Endpoint Protection was installed within it I had the same question as you. I will update this thread if/when I obtain more information.
-TP

The remote desktop session host configuration & Remote session shadowing options missing in Windows server 2012.

Hi All,
I am using a Windows server 2012 Standard. When i leave my session idle for more than 20 min it disconnects and post more 20 minutes my session is logged off.
I know this setting can be changed from Remote desktop session host configuration in Windows server 2008 R2. But this option "Remote desktop session host configuration" is not there in Windows server 2012. Does any one have an idea where do i go
and edit these settings in the Server 2012 o/s ?
Also the Remote session shadowing option is also not available when i right click a user in the task manager. Any idea on an alternate method in Windows server 2012 ?
Gautam.75801

Exactly WHERE are the W2K12 R2 equivalent GPO settings to W2K8 R2 GPO settings of "Set time limit for disconnected sessions" and "set time limit for active but idle Remote Desktop Services
sessions"? Microsoft changed the remote desktop/terminal services around.
Appreciate it.
Matt
Policy Path
Scope
Policy Setting Name
Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
User
End session when time limits are reached
Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
Machine
End session when time limits are reached
Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
User
Set time limit for disconnected sessions
Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
Machine
Set time limit for disconnected sessions
Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
User
Set time limit for active but idle Remote Desktop Services sessions
Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
Machine
Set time limit for active but idle Remote Desktop Services sessions
Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
User
Set time limit for active Remote Desktop Services sessions
Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
Machine
Set time limit for active Remote Desktop Services sessions
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

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

Similar Messages

Maybe you are looking for