Remote Desktop Services Manager Hangs / Crashes

Hi,
I have windows server 2008 R2 based remote desktop environment. When i access remote desktop services manager to manage domain users session, it hangs / crashes. I am not unable to add any other computer to manage as well. Same was working fine in Windows
server 2003.
Any valuable suggestion????
Regards
Rox_Star

Hi,
As a test, please create a new domain admin user account, log on to the server with it, and then open RDS Manager.  Do you see the same issue with the new account?
Thanks.
-TP

Similar Messages

  • Remote Desktop Service Manager - configure permissions for Remote Desktop Users to Send Message, Disconnect, Logoff

    Hello, dear colleagues.
    We are using Windows Server 2012 R2 as Remote Desktop Server. Also use Windows Server 2008 R2 with Remote Desktop Service Manager to control RDS user sessions (Send Message, Disconnect, Logoff, Query Info). 
    Send Message, Disconnect, Logoff options works only for users in Administrators group.
    I can't to configure permissions for Remote Desktop Users, specific user or AD group. 
    To set permissions I'm running RDS Host Configuration on Windows Server 2008 R2 and connect to Windows Server 2012 R2. Then double-click
    RDP-Tcp, Security tab, add specific user account , AD group or configure
    advanced permissions
    for Remote Desktop Users.  
    But, as I sad above, these options works only for users in Administrators group. How to make it work for Remote Desktop Users or specific user, AD group?
    Thanks.
    P.S. If move specific user from Remote Desktop Users group to Administrators group on
    Windows Server 2012 R2 - it works. 

    Hi,
    You can prevent administrators from changing the permissions for a connection by applying the
    Do not allow local administrators to customize permissions Group Policy setting. 
    This Group Policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security
    Apart there is one command with which you can set the permission for that check the related
    article. Additionally checkthis
    thread for more detail.
    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]

  • Users not showing in Terminal Server Under Remote desktop services manager and Task Manager

    Hi All,
    I have a problem here in Terminal Server. I can not see the users logged in to Server but i know users are accessing the files and currently working.
    1. From the Task Manager-- Show processes from all users displayed all the processes accessing by users.
    2. From the Task Manager-- From Users Tab--No users list at all
    3. From the Command Prompt- Query users-- No information
    4. From the Remote desktop services Manager-- used with IP/Host name-- Still can not see the users list and processes. So i can not kill the session if needed.
    Enviroment:
    TS CALS 20 currently accessing 15 users
    VM-WARE GUEST: 2008 RS Terminal Services/Remote Desktop services installed
    Windows up to date-- Just updated last month
    Problem is here for long time. Just couldn't find the time to trouble shoot.
    UMESH DEUJA MCP,MCTS,MCSA,CCNA

    Hi,
    Thank you for posting in Windows Server Forum.
    As you have tried many steps, I suggest you to try below command line and power shell command if successful in your case. Please try below command with Admin access:
    qwinsta /server:<servername>
    To kill a session use rwinsta to delete the session specifying the ID number:
    rwinsta /server:computer01 3
    Here's the list of command line tools for Remote Desktop Or, you can use PowerShell:
    Get-RDUserSession and Disconnect-RDUser
    Please check the list of Power Shell command from
    this link.
    Hope it helps!
    Thanks,
    Dharmesh

  • Remote Desktop Connection Manager hang

    I work at a win8.1 client. I use Remote Desktop Managr to access my servers and clients.
    It was working fine till it goes in hanging state and the the screen freez when i am tring to remote login to any PC.
    The version of RDM is 2.2 build 2.426 by Julian Burger.
    I uninstall it and install again, but still the same problem.
    can anybody help me to fix this problem?

    Hi,
    Is this the RDCman you downloaded?
    Remote Desktop Connection Manager
    The system requirements told that it's supported OS is Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, so there might be some compatiblity issues when using in Windows 8.1.
    Here is another thread talking about the RDCMan version:
    Where to download Windows Remote Desktop Manager
    V2.5
    Best regards
    Michael Shao
    TechNet Community Support

  • Taking control with Remote Desktop Services Manager from workstation console

    When I run Remote Desktop from the console of my computer Windows 7 I get a message saying that if I run this tool from the console some options are disabled as Remote Control and Connect.
    Is there any way to enable these possibilities from the console?
    Thanks, VOR

    Hi,
    No, there is no way to enable them for use from the console.  These features
    require that you be within a Remote Desktop session in order to use them.  For RDP 8.0/8.1 sessions the situation is different in that you can now perform a shadow (Remote Control) by launching mstsc.exe with
    command line switches even from the console.
    -TP

  • Install Remote Desktop Services Failed on Windows 2012 Server

    I understand RDS is not recommended on DC due to security consideration.  However since I want to play it at home, it is not much a concern.  Such scenario works fine on Windows 2008 R2.  But on Windows 2012, the RDS (session-based, have not
    tried VDI, but expect same result) installation always fails and is incomplete on DC. 
    In \Administrative Tools\Terminal Services, I only have RD Licensing Diagnoser and RD licensing manager.  The remote desktop service management service cannot be started (Error code: 0x88250001).  Is there any extra configuration needed for RDS
    working on Server 2012 DC or before the installation?  Thanks.
    Update: this issue has been solved in Windows 2012 R2 Server.  According to
    http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
    "Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller.  In addition, we published
    guidelines for how RD Session Host could be used without the RD Connection Broker."
    The guidelines (http://support.microsoft.com/kb/2833839/en-us) primarily apply to Windows 2012 Server.

    Asinine.  Simply Asinine.  Microsoft took it out because of $GREED$.  
    RemoteDesktop has become so popular, they had to break it to make more money.  Thats why they discontinued SmallBusinessServer.   If this practice is so tabooo... Why did MS go the opposite direction with SBS 2011 Premium Cal's?  SBS2011
    had DC, Exchange, RDS and Sharepoint,SQL, RemoteWebWorkplace, OWA all working in perfect harmony.  It is an untrue statement then, that it was "allowed but not recommended"
    Now you by Server2012 (core + two virtual) and its not enough for all this. 
    You need at least another $700 for another sever licence to have it all
    and who knows if SQL will run on a DC, or Exchange, or R-DERP server.  Another reacherous bridge to cross.
    By far, the absloute worse release since Millennium.  The product is not ready for production, we broke our rule of waiting until the first SP1 upgrade for this and Exchange 2013.  Problems with USB drivers and networking running extreamly slow. 
    Our 2003 SBS server was at least three times as fast, and this server has SAS and SSD drives running.  It can't get out of its own way, and IE10 is the most unstable piece of crap to come out of Redmond.  Open wide and swallow - Mother Microsoft
    knows whats best for you.  YOU WILL EAT OUR SLOP AND LEARN TO LIKE IT.   Server2012 AKA  "METRO-SERVER"
    Now here I sit after 50 Hours back to back setting up a new R-DERP server 2012, AD, Have my RDP licences in my hand at $100 each, and WTH does Microsoft care if I install it on my DC.  ITS MY DC.  And the cost savings versus the "risk" was
    previously MY decision. 
    Sure, I can install a couple of Virtual HyperV sessions but they are so tempremental to a power-outage in a small business its not worth it.  I have to double up my server hard drive resources, buy a $800 battery backup unit and make sure to attach
    the cable, and even then, if that Bi**H does not shut down properly, one bit goes awry in a VHD or VHDX file and you are screwed.  Restore from lastnights backup and forget about todays work.  Not to mention it will probably take a half day to try
    to fix it, then recover it then tell the 30 users they lost a days worth of work. 
    HYPER-V is for test servers and has no place in a small (micro) business environment. 5-30 users. 
    Microsoft's solution, buy another server.  Need Exchange?  Buy another server or take the risky cheapskate route and spin up some VHD's.  Might as well put a gun to your head and play russian roulette, at least you know you have a one in six
    chance of failure.  With MS, its a 100% failure for a dirty shutdown power loss, motherboard blows, memory goes corrupt in a few years, your conventional method of recovery is gone, and you have some upchucked VHD file to try to recover some of TODAYS
    data from. 
    Screw server 2012 forever. 
    I will sell 2008 and SBS2011 Premium unitl it rots in hell like XP (of which there is NOTHING wrong with for the average, WORD, EXCEL, OUTLOOK and QUICKBOOKS that all SMB's use.  Its MS $GREED$  Grab the world by the B**ls and squeeze with all
    your might to squeeze every dime you can out of *SMB* because big business is going to run thier 2003 Exchange and 2008 servers into ground before they switch to this garbage. 
    YOU CANNOT INSTALL EXCHANGE 2013 on DC , OR on R-DERP server. 
    Go buy another server license and server or MOVE TO THE CLOUD and get fleeced every month. 
    I have 30 DC/R-DERP/Exchange and SBS2011 Premium servers all running for years in perfect harmony, locked down with security so the users can't even WIGGLE with something they are not supposed to work with.  They get their apps, cannot install anything
    and all these servers are running just fine behind the firewall and perfectly save.  The track record of this combination is 100% stable and is up 24/7/365 with no problems.  Do yourself a favor and throw this 2012 into the river, you don't need
    any weights because it is LEAD and will sink to the bottom by itself.
    Why, you ask?  Official is "Its for your protection"  The real reason?  To sell you more $700 server licences.
    Maybe for SMB, we start selling Linux NAS Servers, host the Exchange in the cloud and be hearded like cattle to the Microsoft slaughterhouse.  One way or another, you are going to bleed.    A little each month to move to the cloud, or
    a small fortune if you want to have it in house.  Microsoft wants it to be more expensive to have in house.  No more buying a server and running it for six years before you upgrade.  They can't have in house servers competing with their cloud,
    and small businesses are the low hanging fruit  ripe for the pickin'. 

  • Remote Desktop Services Error when trying to send a message to a user in the collections

    We are implementing RD for thin clients and when I try to send a message to a user I get an error that states,: Unable to send a message to session X on (SERVER NAME.COM). WTS API Failed
    Is there a service that needs to be turned on?
    Thanks EPK

    Hi,
    Thank you for posting in Windows Server Forum.
    Before sending message please check following considerations.
    - You must have Message special access permission to send a message to a user.
    - You can send messages only to users whose sessions are in the active or connected state.
    - You can send a message to a user session in Remote Desktop Services Manager by using the Send Message action.
    Send a Message to a User
    http://technet.microsoft.com/en-us/library/cc754124.aspx
    Else you can also try below script and check the result.
    Send-NetMessage - Net Send / Msg.exe
    http://gallery.technet.microsoft.com/scriptcenter/Send-NetMessage-Net-Send-0459d235
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Audio service hangs on Windows Server 2008R2 with Remote Desktop Services

    Hello! 
    I have some terminal servers on Windows Server 2008R2. Users have the ability to use web browsers (IE, Firefox) with the included Flash Player, IM clients / Internet
    telephony (Skype, ICQ), Windows Media Player, Office, and a specific internal software (works with MS SQL). I have the following problem: the Windows audio service hangs up that leads to hangup of all programs which use it, such as: any sites in Internet with
    a flash content (in all browsers), ICQ, Skype.Even logging out the session hung when tried to lose a sound. It's impossible to stop or restart service from the services.msc the service just hang with status "restarting". To stop service I terminate svchost
    process. As soon as the audio service is stopped - all programs start to work correctly (certainly without a sound). This problem appeared not suddenly - periodic hangups of programs on servers were marked long ago (more than half a year), but not directly
    were connected to audio service, especially there were they rather rare (on the average once a week - two) and were corrected by server reset. The error message: 
    Error container , type 0 
    Event name: AppHangXProcB1 
    Reply: No data 
    Ident CAB: 0 
    Problem signature: 
    P1: iexplore.exe 
    P2: 9.0.8112.16446 
    P3: 4fb57c8f 
    P4: 77c1 
    P5: 131200 
    P6: svchost.exe:AudioClientRpc 
    P7: 0.0.0.0 
    P8: 
    P9: 
    P10: 
    shall suggest an idea about a sound service, but in Event Viewer has no Windows Audio events. 
    Recently I updated Skype to the last version 6.0.66.120. Before was 4.2.35.155 because versions 5хх on Windows2008R2 with the Remote Desctop Services actually don't
    work, if users at the server more than one or two. We checked the sixth version by the test machine with the terminal environment and very were delighted to its normal working capacity. However after installation of this client on production servers it appeared
    that hangups of programs on servers began to occur on the average time at an o'clock in case of an average daily load (about 20 users on one server). If you have worked one or two users, problems weren't watched. Internet search led me to the support page
    Skype, where the Windows 7 x64 user faced a similar problem in the fifth version of the program. But the solutions proposed by the support team does not help me. In addition, I found the advice to disable enhancements in the properties of the playback device,
    but it is impossible for the "Remote Audio" device. 
    At the moment, on servers where I updated the Skype, I disabled the audio service. If within a reasonable time, I do not find a solution, I will have to revert
    to an older version of Skype, but I would like to solve the problem completely. 

    Enable the Allow audio and video playback redirection Group Policy setting
    To allow audio and video playback when connecting to a computer running Windows Server 2008 R2, you must enable the Allow audio and video playback redirection Group Policy setting. The Allow audio and video playback redirection Group Policy setting is located
    in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection and can be configured by using either Local Group Policy Editor or the Group Policy Management
    Console (GPMC).
    For more information about Group Policy settings for Remote Desktop Services, see the Remote Desktop Services Technical Reference (http://go.microsoft.com/fwlink/?LinkId=138134).
    Is this policy applied? Refer:
    http://technet.microsoft.com/en-us/library/dd759165.aspx
    Also, have you tried update the audio device driver for this terminal server?

  • Remote Desktop Connection Manager can only open 6 sessions at a time on Server 2012

    I am only able to open, and view thumbnails, for a maximum of 6 RDP sessions on my Server 2012 box at a time in Remote Desktop Connection Manager (RDCM). If I add more sessions I just get a variety of connection errors for the additional sessions. If I activate
    a 7th session one of the existing 6 sessions goes off-line with a connection error message. Sometimes the error says 3334, sometimes the error says 0x8345000E, and sometimes it just says there is a connection error.
    I have checked Group Policy on the server to ensure I don't have any settings restricting the number of RDP sessions.
    In fact, I will often have 30 or 40 RDP simultaneous sessions opened, I am just not able to view them all in RDCM. I have seen reviews of RDCM with screenshots showing dozens of thumbnails so it seems to be something that's possible to do.
    Are there any settings I should make on the server to allow RDCM to connect to more than 6 simultaneous RDP sessions?
    Just to be clear, all these RDP sessions are running on the same server. Also, I am just using the trial license for Server 2012 and Remote Desktop Services right now. I don't think that should have an impact, but I wanted to be thorough.

    Thanks Jakub for "corflags" info.
    Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll [mstscax.dll]?
    Error message when making RDP connection:
    Could not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
    I was able to create new AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll assemblies from 64bit dll version and now it works with "AnyCPU":-)
    http://www.filedropper.com/axinteropmstsclib-mremoteng
    Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"
    so final .dll wasn't working.
    Adding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file.
    Hope it helps
    P.S. Sorry for possible technical misinterpretation, I am not programmer so creating new assemblies was trial-error process...

  • To install Remote Desktop Services User CAL on Windows Server 2008 R2 Enterprise Edition with SP1

    Dear Sir,
    Presently we have installed Windows Server 2008 R2 Enterprise Edition with SP 1. And now i would like to install Remote Desktop Services User CAL on this server. I have 25 digit product key of Windows Server
    2008 R2 Remote Desktop Services User CAL (20). Downloaded this product key from our MSDN Subscriptions.
    Kindly suggest me how to install (CAL server with product key that i have) and configure remote desktop services on my above existing server also how to point other server with my CAL server.
    Thanks

    Hi,
    1. Install Remote Desktop Session Host and Remote Desktop Licensing Role Services using Server Manager.
    2. Open RD Licensing Manager (licmgr.exe), Activate your server, then install your license
    3. In RD Session Host Configuration (tsconfig.msc), set the Licensing mode to Per User and Specify your RD Licensing server name (itself).  If you want you may configure these two settings via group policy setting instead.  The path of the
    group policy settings is Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing
    4. You may point other RDSH servers to your RD Licensing server using RD Session Host Configuration or via group policy as mentioned above.
    5. Optionally you may consider installing other Remote Desktop Role Services such as RD Gateway, RD Web Access, RD Connection Broker, etc.
    -TP

  • Remote Desktop Services Role on a Virtual Machine (VM) Requirements

    Does MS recommend installing RDS Role on Hardware or Virtual Machine? I have a use case where I have about 35 people that will be using the Internet Explorer and possibly run additional piece of software. I'm having trouble determining if the RDS Role on
    Virtual Machine will be able to sustain the load of so many users. Should the same performance metric used in hardware selection be appropriate to apply for Virtual Machines. We are using VMware on pretty powerful DELL hardware, which is also hosting
    120 existing VMs as of now. So my questions is would VM with 4 CPU's, 8GB of RAM, 80 GB Virtual Disk and 1 GBPs NIC would be handle the job?

    Hi,
    Thank you for posting in Windows Server Forum.
    There is no any particular requirement to run RDS on physical or virtual machine. But if you want to install RD Virtulization role then you need to see that Hyper- V role installed because “when the RD Virtualization Host role service is installed, Server
    Manager checks to see if Hyper-V is installed. If Hyper-V is not installed, Server Manager will install it”. And Hyper-V role cannot be installed on virtual machine so for that you need to install on Physical machine. Other all RDS role can be installed
    on virtual machine also.
    Install the Remote Desktop Virtualization Host Role Service
    In addition, please check below articles.
    1. Remote Desktop Services: Server and client requirements
    2. RDS Hardware Sizing and Capacity Planning Guidance.
    Hope it helps!
    Thanks,
    Dharmesh

  • Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer

     Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer, And when Installing network printers from the domain controller it reports it cannot connect to printer.  I can ping all
    network devices. I can connect to the internet.
    On boot I get a netlogon 5719 error followed by service control manager errors 7023,7001 and a group policy error 1129.
    Clients can connect to the remote application and RDP operates to connect to the server internally and externally.
    The domain controller is another server 2008r2 box. I have scoured the internet but have not found any solutions that work yet.

    Hi,
    After referring to your post, it can be identified that the issue which you are facing is mostly due to some network issue in your environment. Please recheck your network connection issue between computer and domain controller. 
    Can you able to ping with IP address and also with fully qualified name of a domain controller in the users' and computers' domain. If it fails states that name resolution issue with computer and domain controller. Are you using MS DHCP Relay agent then there’s
    available Hotfix for the particular Event ID. Please go through this KB 2459530 to fix the error event ID.
    As per the net logon error 5719 which you are facing states that the client component of Netlogon was unable to locate a DC for the domain it was trying to perform an operation against. Below is one of the reason. If this is being logged on a DC and the event
    refers to the DC's own domain, something might be preventing the client component of Netlogon from starting a network session (to itself or to another DC in the domain). The following event 7001 & 7023 states start & stop operation service. Please
    go through beneath article for more details.
    1.  Event ID 5719 is logged when you start a computer
    2.  Netlogon 5719 and the Disappearing Domain [Controller]
    3.  Event ID 1129 — Microsoft-Windows-GroupPolicy
    Hope it helps!
    Regards.

  • How do I remote control a user in remote desktop services in Windows Server 2012?

    Hello,
    we currently operate in a 2008 R2 environment with the majority of clients connecting to our terminal servers.  We use the remote control feature in terminal services manager to connect to a users session when a user phones our helpdesk with
    a question / issue.
    Just today I've installed 2012 server on a hyper-v virtual machine to have a play with it.  I've installed the Remote Desktop Services and noticed this remote control feature is gone.  I can still log off or send a message to a user, but I can
    no longer remote control their session.
    I've seen one or two other posts stating this feature has been removed completely.
    So, a couple of questions:
    1. How on earth do I "shadow" or connect to a users session now?
    2. If I have to go third party to get this functionality back, what's the best software on the market for this and does it support remote connecting of users who have their RDP session span multiple monitors? (2008 R2 doesn't)
    3. Will Microsoft ever bring this feature back? as at this stage I doubt we would move to 2012.  This is the one feature that is crucial to the day-to-day running of our helpdesk.
    Cheers.

    A large percentage of our IT support business is through remote management. Most of our large enterprise customers are Terminal Server environment (now called Remote Desktop - why does Microsoft have to change EVERYTHING - how would they feel if I changed
    the colour of the sky from blue to red just because I could?).
    Last week, after much expense to the customer (and realising that there WOULD be some cosmetic headaches to contend with Server Management) we installed a new "Remote Desktop Server" for them and shifting them from 2003 - a big leap so we discovered.
    During deployment it came as a HORRIFIC surprise that we could not remote control user's sessions!
    Yes, we ARE to blame for not fully realising the cock-up Microsoft has made for us. We should have fully researched every detail of what changes they made and what they have robbed us of.
    Firstly, the removal of the ability to fully manage user's sessions came as a HUGE blow!
    The remaining multiple issues that followed (including the hugely cumbersome and SLOW way of accessing user's sessions and the false information that the console was reporting users logged in when they had already logged out) suddenly resulted in us decommissioning
    the new 2012 installation in favour of a 2008 R2 installation.
    Some may ask; Why not use "Third Party" apps to counteract the issue? Firstly; why spend MORE and why use a third party app that "is as" cumbersome to use just because of a freaking feature that Microsoft deemed a "security risk" - for G.D sake!
    We have now been directed by management to convince customers that a move to 2012 is NOT recommended - good choice boss, I love you!
    The question is; will Microsoft re-implement this feature and fix Server Management performance/accessibility in a future release before 2008 R2 is no longer available? Probably not - it looks like their stubbornness to forge ahead with their craze mind-set
    of transforming their products into something that is now annoying millions (including their bloody push towards everything-cloud which NONE of our customers want anything to do with).
    Microsoft! Get us back on to your side and take a step back, take a deep breath and listen to consumers!

  • Server 2012: Remote desktop licence manager not issuing licences

    Hi,
    I am battling with an problem which i cannot seem to resolve and no other forums actually come to a conclusion on how to resolve this problem!
    I have a windows server 2012 server which is NOT part of a domain.
    I have installed Remote Desktop Services and also installed the Remote Desktop License manager and i just cannot get the license manager to issue cals when users connect remotely via RDP
    I have installed an extra two CAL's and tried using them as both a "Per User" and also "Per Device" but still does not work.
    I have now run out of my grace period and cannot connect to the server at all
    I have also tried changing some gpo's with no luck, 
    Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
    "Use the specified RD license servers" = myservername
    "Set the Remote Desktop licensing mode" = Per User
    How can i fix this?
    Thanks

    Hi,
    Thank you for posting in Windows Server Forum.
    Have you seen that you have activated RDS License server before installing CAL?
    Please check that the License Server should be part of ‘Terminal Server License’ group in Active Directory Domain Services. You can also configure RD License server manually by powershell commmand. Please check below article for 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, please install below Hotfix and verify the result.
    No RDS license when you connect to an RDS farm in Windows Server 2012
    http://support.microsoft.com/kb/2916846
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Can't log on with administrator user by finding the message "The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on.

    Hi,
    Now, my Windows 2008 R2 Enterprise server are running in the domain. It have problem about some one in my team have remote my server with the user administrator while I'm remote it now. It make my session loss. I tried to remote it again but I found
    the message at the log on screen about "The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on."
    Now, nobody can't remote with administrator user into this server. I have check the application log. I found the error message like this.
    ++++++++++++++++++++++++++++
    Source: Desktop Window Manager
    Event ID: 9003
    Detail: None The Desktop Window Manager was unable to start because a composited theme is not in use
    ++++++++++++++++++++++++++++
    Source: Microsoft-Windows-Winsrv
    Event ID:10002 
    Detail: The following application was terminated because it was hung: mmc.exe.
    ++++++++++++++++++++++++++++
    Source: Microsoft-Windows-Winsrv
    Event ID:10002 
    Detail: The following application was terminated because it was hung: javaw.exe.
    ++++++++++++++++++++++++++++
    Source: Microsoft-Windows-Winsrv
    Event ID:10002 
    Detail: The following application was terminated because it was hung: Explorer.exe.
    ++++++++++++++++++++++++++++
    Source:Desktop Window Manager
    Event ID:9009
    Detail:The Desktop Window Manager has exited with code (0x40010004)
     ++++++++++++++++++++++++++++
    Source:Microsoft-Windows-Winlogon
    Event ID:6005
    Detail:The winlogon notification subscriber <Sens> is taking long time to handle the notification event (Logoff).
    ++++++++++++++++++++++++++++
    In addition, I can log on this server with other user but I can't log off by it's showing the message "please wait for the system Event Notification service". Normally, the problem can solve by reboot the server. But how can be solve this problem
    by we do not reboot the server?

    Hi,
    The cause of unable to remote back to the server seems to be services hung, please try to reset session as the article below guides to see if it works:
    Windows Server: Remote Desktop Error: The task you are trying to do can't be completed because Remote Desktop Services is currently busy
    http://social.technet.microsoft.com/wiki/contents/articles/28636.windows-server-remote-desktop-error-the-task-you-are-trying-to-do-can-t-be-completed-because-remote-desktop-services-is-currently-busy.aspx
    If the issue can always be re-produced, then I would suggest you fully patch the system.
    More information for you:
    The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on
    https://social.technet.microsoft.com/Forums/windows/en-US/c58bfbd5-1d63-47e3-a489-6d8c8778b76b/the-task-you-are-trying-to-do-cant-be-completed-because-remote-desktop-services-is-currently-busy?forum=winserverTS
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Maybe you are looking for