Quantcast
Channel: Remote Desktop Services (Terminal Services) forum
Viewing all articles
Browse latest Browse all 5613

Windows Server 2012 R2 RDS Error 20499 Remote Desktop Services has taken too long to load the user configuration from server

$
0
0

Hello

We recently did a migration of our RDS Server to a brand new Windows 2012 R2 server.

All was working fine but we started to have this messages in the RemoteConnectionManager event log:

Log Name:      Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin
Source:        Microsoft-Windows-TerminalServices-RemoteConnectionManager
Date:          9/14/2016 8:42:53 AM
Event ID:      20499
Task Category: None
Level:         Warning
Keywords:     
User:          NETWORK SERVICE
Computer:      XXXXX.com
Description:
Remote Desktop Services has taken too long to load the user configuration from server\\xxxxx for user xxxx
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-TerminalServices-RemoteConnectionManager" Guid="{C76BAA63-AE81-421C-B425-340B4B24157F}" />
    <EventID>20499</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2016-09-14T15:42:53.300353800Z" />
    <EventRecordID>388</EventRecordID>
    <Correlation />
    <Execution ProcessID="28452" ThreadID="50892" />
    <Channel>Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin</Channel>
    <Computer>XXXX.com</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <UserData>
    <EventXML xmlns="Event_NS">
      <ServerName>\\XXXXX</ServerName>
      <UserName>agranados</UserName>
    </EventXML>
  </UserData>
</Event>

Everytime this error message is logged the user gets disconnected from their RDS session.

So far we tried the following:

- Validate AD health (sites,subnet,replication, sysvol)

- We changed the DisableTaskOffload option as suggested in other posts

- We verified the group policy settings applied

Unfortunately we still haven't found what the root cause of this issue is.

Any suggestion of similar previous experience is welcome.

Thanks in advance!

Cristian


Regards. Cristian V.



Viewing all articles
Browse latest Browse all 5613

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>