windows server 2012 remote desktop freezes

Normally you should have 0 packet loss, a couple of of packet loss occasionally is not. Packet loss is easily detected, just ping the server for minutes, an hour or more and check the results. I don’t know If it had something to do with the frozen up. It sounds like it could either be network problems (packet loss) or the server (s) that serves your vritual machines is (are) over utilized. On HYPER-V server, this Kernel-EventTracing error have been happening for a long time. 9:18 Service Control Manager A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service. 9:17 Application Error Faulting application name: WINWORD.EXEĥ. 9:04 9:11 9:14 9:15 9:16 Winlogon The Windows logon process has unexpectedly terminated.Ĥ. From 8:45 to 9:50(ongoing more than 30 this kind of warnings during this time) RemoteConnectionManager Remote Desktop Services has taken too long to load the user configuration from server \DOMAIN.local for user usernameģ. The TLS protocol defined fatal alert code is 20.Ģ. 8:39:55 Schannel A fatal alert was received from the remote endpoint. I looked in to event viewer but still have no idea what caused it.ġ. This morning at 9:05, user reported server was frozen again, I tried to login but the session was totally black screen.

We found Internet Explorer was the culprit 2 weeks ago, when some users close IE every time it left 2 Rundll.exe processes with each one consume 5% CPU, after launching and closing several times server froze, so we disabled IE and enabled CPU Fair Share Scheduling.

So we have got a virtual terminal server (Windows Server 2012 R2) sits in a Hyper-v server, the other 2 virtual servers are running fine, but the terminal server freezes every now and then, there are around 30 users logged in the server in peak hours. We have experiencing some random server freezing issue lately, but not sure what caused it.

Windows server 2012 remote desktop freezes