Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
RDP takes long time to load
Message
From
18/01/2017 16:14:33
 
 
To
18/01/2017 16:08:02
General information
Forum:
Windows
Category:
Remote access
Environment versions
OS:
Windows 8.1
Miscellaneous
Thread ID:
01646831
Message ID:
01646834
Views:
47
>How long is "a long time to load"?

A minute or two

>The fact that the VM is a DC should not, by itself, cause sessions on it to load slowly. I regularly connect to several DCs via RDP and performance is good, the same as connecting to non-DC servers or workstations.

I assumed so. Our secondary domain controller responds fast. So, I suspect something local to that specific one.

>Do you have any processes set to auto-start when your session loads?

No, nothing specific was configured on any of them.

>Assuming nothing above is out of the ordinary, go into Task Manager/Resource Monitor and check the following, in order:
>
>1. RAM usage. DCs tend to either have a lot of other stuff running on them (e.g. Small Business Server) or basically nothing else. In either case the VM can be RAM-starved; the first case with not enough allocated to support all the processes and services, the latter because the admin cuts its allocation down to the bare minimum (e.g. under 1GB) so there's nothing left for profiles when someone logs on remotely. If the VM gets starved for RAM it will page to disk, which is slow
>
>2. Full (more than 95% in use) or slow disk subsystem underlying the VM
>
>3. Check the Event Logs on the DC - primarily System and Application. Look for errors first. If nothing seems obviously wrong also look at non-error events. I've seen cases where improperly configured certificates or authentication causes dozens or hundreds of messages per second to be written to the Event logs, which bogs down the whole machine

When it happened, I would say this arrives at the same time I have three errors:

1. The Smart Card Device Enumeration Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
2. A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ScDeviceEnum service.
3. A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

We will check on that.

Thanks
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Previous
Reply
Map
View

Click here to load this message in the networking platform