L
Lasse
Guest
Hi
We have a Server 2003 R2 SP2 with Terminal Services that's causing some
problems. We have around 80 users using the server and each have a RDP
connection that automatically starts a program on the server.
Suddenly today the server more or less stopped responding and the only thing
I
could find was Winlogon.exe using 100% CPU time but I can't figure out WHY?
I logged off all the users and then the problem disappeared.
I suspect it might be our GPO logon script, but the only thing it does is
check if you logon to the Terminal Server and then it runs the following line:
rundll32 printui.dll,PrintUIEntry /Xs /y /n"Printername"
We have a Server 2003 R2 SP2 with Terminal Services that's causing some
problems. We have around 80 users using the server and each have a RDP
connection that automatically starts a program on the server.
Suddenly today the server more or less stopped responding and the only thing
I
could find was Winlogon.exe using 100% CPU time but I can't figure out WHY?
I logged off all the users and then the problem disappeared.
I suspect it might be our GPO logon script, but the only thing it does is
check if you logon to the Terminal Server and then it runs the following line:
rundll32 printui.dll,PrintUIEntry /Xs /y /n"Printername"