Remote Desktop Session has Ended

Hi,
I have a group of machines running Windows XP and this has enabled RDP feature. I enter the hostname/ip which (console remote desktop connection), I enter my user and password, the desktop is loaded but quickly (think less than 2s) the connection drops with
the message "The service session desktop remote has ended. Another user connected to the remote computer, hence his connection was lost ". The problem is that there is another user who has logged in and it occurs in other XP machines, but it
does not happen in Windows 7, Windows 2003 and 2008 servers.
My attempts:
- Windows Firewall off
- The problema also happens with user local administrator
- Put these station on a OU without GPO applied.
- There is no other user using the computer, because she is dedicated to testing.
The message that is displayed.
In the event viewer there are no errors related to this problem. Any suggestion?
**Sorry, my english is terrible. My native language is portuguese**
Denis Leal

This behavior is by design. Windows XP remote desktop is intended to give users the possibility to log in remotely to their own computer, not to run multiple sessions at once.
http://support.microsoft.com/kb/280828
MCP/MCSA/MCTS/MCITP

Similar Messages

Your Remote Desktop session has ended

Hi,
I have installed an RDS 2012r2 server and am using session hosting to publish a remote app or desktop to run this app.
In both cases I can run one instance but when a second client connects I receive the message in the title.
I'm thinking this is a configuration item I've overlooked?
Thanks for any help
Rich

Hi,
Thank you for posting in Windows Server Forum.
Please notice that every server will provide 2 remote session for administration purpose only. Whenever we try to login with more than 2 remote user then by default it will ask the other user to log off and connect new user. If you want more than 2 remote session
then we need to install RD License server and purchase RDS CAL (User or device) and configure it.
If the above one is not the case then kindly see whether you have not enabled any policy setting as to limit number of connections for server. You can check below GPO for this setting.
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections
Limit number of connections: Enable
In the RD Maximum Connections allowed box, type a number that is greater than or equal to the maximum number of simultaneous connections for the RD Session Host server, and then click OK
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
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]

The grace period for the Remote Desktop Session Host server has expired

<p>I'm running Windows Server 2012, we only have 1 server and it's a DC. I'm trying to RD to the server from my Windows 7 laptop. It was working fine on Friday but when I came in on Monday I got message saying that 'The remote session was disconnnected
because there are no Remote Desktop License Servers available to provide a license'
So after a bit of digging I found out my 'grace period' had expired, so ordered a new license which I got today, installed this all ok but still i cannot connect via RD I get the same message....went into the RD License Diagnoser and it said the problem
was as follows
'The grace period for the Remote Desktop Session Host server has expired, but the RD Session Host server has not been configured with any license servers. Connections to the RD Session Host server will be denied unless a license server is configured for
the RD Session Host server.'
Suggested Resolution as follows
Configure a license server for the Remote Desktop Session Host server. If you have an existing license server, specify that license server for the RD Session Host Server. Otherwise, install RD Licensing on a computer on your network and Configure RD Session
Host Server to use it.'
I cannot figure out how to do this as I cannot find the RD Session Host Server tool.
Can any of you lovely people help me please

Hello,
Best option would be to assign the license server by using AD GPO. Youl will need to configure the following:
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
and define the settings for:
Use the specified Remote Desktop License Server
Set the Remote Desktop Licensing mode
Then assign the policy tho your server.
regards Robert Maijen

How to properly end a Remote Desktop session?

I use Remote Desktop to access multiple PCs at work that run scheduled tasks on Task Scheduler. For these tasks to run correctly I need to be logged into the machine. We have Group Policy, that I cannot get changed, that limits a disconnected
remote session to 2 days. It appears to me, that because of this, my PCs are logging out on Sundays due to the fact that I last remoted into them on Friday. I am able to remote back into the PCs on Sunday evening and allow my processes to run correctly
on Monday morning, but I would like to not have to do this every week. Is there a way to end the remote session, stay logged into the PC, and not be in the disconnected state that is causing the log off with the group policy? I do not experience
any problems with PCs that I log into locally and then lock. Can I put my PCs in this same locked state, as if I were locking and ending a local session, when I end a remote session?

When you go into a remote desktop session. Simply click the "X" on the upper menu bar and it will keep you logged into the client computer but close it out of your screen. However, if someone logs into the client computer locally it wil disconnect your
session and there is no way around that.
Don't forget to mark the post that solved your issue as "Answered." By marking the Answer you are enabling users with similar issues to find what helped you. Lewis Renwick - IT Professional

Keyboard losing focus while in remote desktop session

Hi,
I have several Win7 computers that remote into a hosting company's server. Our users will log into the hosting company's servers via remote desktop. The issue that keeps coming back is that the keyboard will stop functioning after a user locks the computer
then returns after a short period of time to continue working. The remote desktop session will remain working while the pc is locked. After unlocking the computer the keyboard will not work in the remote session. The mouse isn't affected by this and minimizing
the session, the keyboard works fine on the local session. Sometimes you have to restore down then restore back or minimize the RDP session several times to get the keyboard to work inside the remote session. On a few occasions, ending the RDP session
will cause the keyboard to work again. Anyone experienced this and have a resolution for this issue? This issue appears to be occurring more frequently and we have already recreated user profiles on the remote server but to no avail. Thank you for your help.

Hi Nicholas,
I have this issue aswell, and it has traveled with me over a switch if computers. So I suspect there is something with my user account/profile or similar. My colleague does not have the issue.
I also tried the hotfix but I received a message that the hotfix doesn't apply to this computer. The
pc is a windows 7 Enterprise 64-bit. What can I do to resolve this?
Any way to reset my Remote-desktop-cache or settings for my user account perhaps, start from scratch.
Best regards
- Björn

Remote Desktop Session time limits

Hi, i have a Terminal Server Farm that hosts a Remoteapp.
I want to terminate sessions if the user has closed the remote app and log them off the server.
I have configured in Group Policy this settings:
Windows Components/Remote Desktop Services/Remote Desktop Session Host/Session Time Limits/
End a disconnected session - 30 minutes
RemoteApp session logoff delay: 30 minutes
Terminate session when time limits are reached - Enabled
However some users don't get disconnected, for example they close the Remoteapp window, the connect to the remoteapp again in a few hours and they still have the same session with the same window
opened.
Am i missing something in my GPO?
Thanks

Hi,
If you only would like to log off a disconnected RemoteApp session, I think this policy below is enough.
Set time limit for logoff of RemoteApp sessions
If you enable this policy setting, when a user closes the last running RemoteApp program associated with a session, the RemoteApp session will remain in a disconnected state until the time
limit that you specify is reached. When the time limit specified is reached, the RemoteApp session will be logged off from the RD Session Host server. If the user starts a RemoteApp program before the time limit is reached, the user will reconnect to the disconnected
session on the RD Session Host server.
However, please note that it requires at least Windows Server 2008.
Hope this helps.
Jeremy Wu
TechNet Community Support

"remote desktop connection has stopped working" When printing from remote desktop connection

I have been having a issue when using a windows 7 machine. I have Remote Desktop to a session on Windows2008 R2, I am using the local printer resources to redirect the printing. However everytime i try to print it crashes the remote desktop application.
Gives me "remote desktop connection has stopped working." I have 4 other computers connected and printing with no issues what so ever. This only happens when i print. It does print by the way just the application crashes.
-I have also updated the printer drivers to newest possible thru the manufactorer website. The printer is a Brother MFC-8890DW. Windows 2008 R2 is up to date for the RDS server. 3 other machines are able to Remote in and print. The user is able to print using
diffrent machines just not the Windows 7 machine.

Hi,
Happy to hear that you resolved your issue. For another issue which you are facing here trying to provide some suggestion.
As you have commented that you are facing issue with second screen resolution on wide screen. The setting which I am suggesting can only applies when you are using multi-monitor Remote Desktop connections. If you are making Connections using a single
monitor do not use this setting.
So for this you can try to apply “Limit maximum display resolution” setting in group policy, where you can mention the width & height for the screen to display. The setting can be applied on below mentioned
path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
Meanwhile sharing article with you for more information.
Remote Session Environment
http://technet.microsoft.com/en-us/library/ee791847(v=ws.10).aspx
Hope it helps!
Thanks.

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 Components/remote desktop services/remote desktop session host/profile doesn't appear to be working on 2008R2 boxes

I have two domains.   One is an account domain with a one way trust with the resource domain.   Resource domain trusts the account domain and has a number of 2008R2 servers running within. I am experiencing severe logon delays
due to these servers being unable to access the server that hosts the user home folder specified directly on the user account profile tab from the account domain.   When using my workstation in the actual account domain (corporate) I have no
problems.
Because of these network restrictions, I need to override the 2008R2's desire to access that user home folder location in the account domain.
So far the best thing I have found to try is Windows Components/remote desktop services/remote desktop session host/profile/Set Remote Desktop User Home Directory
The problem is that so far I have tried to configure this to point to both a local folder as well as a network path and it doesn't appear to be doing anything.   Not seeing any errors in the app or system log either.
It is still trying to map the path in the account domain.
Any ideas?
Is there a better way to accomplish my goal?   The servers in the resource domain will be Citrix servers and there will be a lot of users connecting from the account domain.
I tried this setting too, but it only seems to work on the 2012 machines in my Resource domain.
With the introduction of Windows 8 and Windows Server 2012 there is now a new group policy setting called “Set user home folder” and is found under Computer Configuration > Policies > Administrative Templates > System > User Profiles
Help!

Hi,
This might be due to permission problems. Please check whether the user accounts for whose home folder to be redirected have permissions in the shared folder specified in the server.
Checkout the below link on Best Practice for creating Roaming Profile and Folder Redirection
http://www.grouppolicy.biz/2010/08/best-practice-roaming-profiles-and-folder-redirection-a-k-a-user-virtualization/
Regards,
Gopi
JiJi
Technologies

NULL SID Security Log Event ID 4625 when attempting logon to 2008 R2 Remote Desktop Session Host

This is a new deployment of Server 2008 R2 in a newly created 08 R2 active directory on a newlyt installed 08 R2 RDSH server.
A new generic user is created in AD. That user can log on to the terminal server on the console just fine. But that user cannot logon via RDP. Furthermore, the domain admin credentials also cannot logon via RDP.
When either set of credentials is used, the logon attempt registered in the Windows Security Even Log as a denied attempt with Event ID 4625 reporting a NULL SID.
Troubleshooting: The RDSH has already been disjoined and rejoined to the domain. Also, curious note, there are three ways to save the user account on the RDSH server as a valid user account which has permissions to logon. The one Microsoft recommends is to open computer management and edit the remote desktop users group. When I the accounts here and click apply, they immediately dissapear. Secondly, I can open the computer properties and go to the remote tab. There I find the user accounts added using the previous method are enumerated but not displaying correctly. They show up with the RDSH server name and a question mark. The last way, is to open the Remote Desktop Session Configuration tool and edit the properties of the rdp connection and go to the security tab. This was the only place I could get a user to ‘stick’ but the logon attempts still show a NULL SID and access is denied.
I have scoured every bit of RDS documenation I can find with no luck.
Thanks,
Chris

I am also experiencing this issue.
2008 servers, 2007 exchange on server 2008.
These are fresh servers, fresh AD. Users can log onto domain normally, RDP not working for admin accounts, generating same errors as posted above.
The bigger issue, is that we have a cisco messaging service account that is generating this error on the DC's and the Exchange server as well. The service basically emails users voicemails to their inbox. The user we've created for the cisco service is unable
to authenticate to the exchange server, in turn generating the same errors posted above as well. We can log on to the domain with this account just fine.
Any ideas on this? We have not tried re-adding the servers to the domain.
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 5/5/2010 9:01:13 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: xx.corp
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
   Account Name: -
   Account Domain: -
   Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
   Security ID: NULL SID
   Account Name:
xxxx
   Account Domain:
xxxx
Failure Information:
   Failure Reason: Domain sid inconsistent.
   Status: 0xc000006d
   Sub Status: 0xc000019b
Process Information:
   Caller Process ID: 0x0
   Caller Process Name: -
Network Information:
   Workstation Name: laptop
   Source Network Address: -
   Source Port: -
Detailed Authentication Information:
   Logon Process: NtLmSsp
   Authentication Package: NTLM
   Transited Services: -
   Package Name (NTLM only): -
   Key Length: 0

Adobe Acrobat Reader Starts when opening a Remote Desktop Session

I recently upgraded to Acrobat Reader 8. Now I have a problem that Acrobat Reader loads when I open a Remote Desktop session. Has anyone else experienced this? Does anyone know what I should look at to get it to stop loading? Thank you.

After a third uninstall and re-install I've managed to crack it.
Thanks anyhow everyone.

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

Can't quit directly from remote desktop session on OS X

When I'm in a full-screen remote desktop session in Mavericks and I move the mouse to the top of the screen so the menu bar appears, selecting Quit from the File menu results in the session ending, but I have to select Quit a second time to actually exit
the application.

Hi,
It seems to be a Mac related issue, I would like to suggest you contact Apple support for help.
Thanks.
Jeremy Wu
TechNet Community Support

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.

PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007

Hi all,
we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html)
What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
Is what i'm trying actually possible?
Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!

It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
Jason | http://blog.configmgrftw.com | @jasonsandys

Remote Desktop Session has Ended

Similar Messages

Maybe you are looking for