B
BFH
2003 server, running terminal services for XP Pro and Wyse thin clients.
Terminal server clients are taking about five minutes to get past the
"applying your personal settings" message, then behaving normally. I've
checked DNS and found nothing wrong performance monitoring on server show
CPU, disk, and LAN interface acting normally. I enabled "verbose logon
messages" per a KB article, and the culprit seems to be something called the
"ProcessLogonConfigurations" policy- the five minute hangup in the login
process is spent entirely on a screen saying "Applying
ProcessLogonConfigurations policy."
Searched KB for that, and googled the term, and got nothing- not a single
hit. It's not a name of any group policy in our AD domain, so this has to be
a Microsoft thing. Does anyone have any idea what it is?
Terminal server clients are taking about five minutes to get past the
"applying your personal settings" message, then behaving normally. I've
checked DNS and found nothing wrong performance monitoring on server show
CPU, disk, and LAN interface acting normally. I enabled "verbose logon
messages" per a KB article, and the culprit seems to be something called the
"ProcessLogonConfigurations" policy- the five minute hangup in the login
process is spent entirely on a screen saying "Applying
ProcessLogonConfigurations policy."
Searched KB for that, and googled the term, and got nothing- not a single
hit. It's not a name of any group policy in our AD domain, so this has to be
a Microsoft thing. Does anyone have any idea what it is?