Help debugging logon process
I am trying to locate some holdup points in a slow network logon process. There are a few areas in the log where I can see it being held up, but now that I have this I am not sure where to look and troubleshoot it.
Does anyone recognize the processes listed below and know where I can look to try and address this issues:
USERENV(17b4.a44) 03:40:41:644 LibMain: Process Name: \??\C:\WINDOWS\system32\wi
USERENV(17b4.a44) 03:40:47:535 LoadUserProfile: Yes, we can impersonate the user. Running as self
USERENV(1fc.228) 03:40:30:753 ReleaseClientContext_s: Releasing context
USERENV(1fc.228) 03:40:30:753 MIDL_user_free enter
USERENV(17b4.a44) 03:40:41:644 InitializePolicyProcessing
USERENV(17b4.a44) 03:40:41:644 InitializePolicyProcessing
USERENV(17b4.17fc) 03:40:48:316 ApplyGroupPolicy: Leaving successfully.
USERENV(12d8.145c) 03:40:48:394 LibMain: Process Name: C:\WINDOWS\system32\userin
USERENV(17b4.a44) 03:41:48:644 IsSyncForegroundPolicyRefr
USERENV(17b4.b58) 03:41:48:644 IsSyncForegroundPolicyRefr
The slow logon is happening for all users, both general domain user and admins. Logon is happening on a Citrix server and this is where I generated the log that identified these holdup areas. The slow logon also exists if you logon to the Citrix server console.
So where do I look now?
Does anyone recognize the processes listed below and know where I can look to try and address this issues:
USERENV(17b4.a44) 03:40:41:644 LibMain: Process Name: \??\C:\WINDOWS\system32\wi
USERENV(17b4.a44) 03:40:47:535 LoadUserProfile: Yes, we can impersonate the user. Running as self
USERENV(1fc.228) 03:40:30:753 ReleaseClientContext_s: Releasing context
USERENV(1fc.228) 03:40:30:753 MIDL_user_free enter
USERENV(17b4.a44) 03:40:41:644 InitializePolicyProcessing
USERENV(17b4.a44) 03:40:41:644 InitializePolicyProcessing
USERENV(17b4.17fc) 03:40:48:316 ApplyGroupPolicy: Leaving successfully.
USERENV(12d8.145c) 03:40:48:394 LibMain: Process Name: C:\WINDOWS\system32\userin
USERENV(17b4.a44) 03:41:48:644 IsSyncForegroundPolicyRefr
USERENV(17b4.b58) 03:41:48:644 IsSyncForegroundPolicyRefr
The slow logon is happening for all users, both general domain user and admins. Logon is happening on a Citrix server and this is where I generated the log that identified these holdup areas. The slow logon also exists if you logon to the Citrix server console.
So where do I look now?
Are you using roaming profiles? If you are this is your problem, as they can take some time to load.
eb
eb
ASKER
No roaming profiles
I don't know if it will do anything for you but defrag the drives, a fragmented local profile can take some time to load.
Also check the startup items, and scripts to make sure nothing you do not need is loading.
eb
Also check the startup items, and scripts to make sure nothing you do not need is loading.
eb
ASKER
negative on defrag. Startup items look basic, nothing unusual.
I can confirm that duing the process that hangs for 1 minute, what the user sees on the screen is "applying policymaker registry policy"
We do use policymaker, but again, I don't see anything unusual and not sure when to look and find what setting is causing this.
I can confirm that duing the process that hangs for 1 minute, what the user sees on the screen is "applying policymaker registry policy"
We do use policymaker, but again, I don't see anything unusual and not sure when to look and find what setting is causing this.
Is it posible someone installed pilicy maker? Ccheck add remove programs
ASKER
Yes. I said we use it. It is on all our systems.
Been using it for a couple years. The hang problem just started about 2 weeks ago.
Been using it for a couple years. The hang problem just started about 2 weeks ago.
Sorry missread, thought you said did not use it. I'm not familure with it so I don't know how much I can help but I think this is the source of the problem. Have you made any changes to it's settings latley? You may also want to see if the maker has a FAQ/ KB for help.
eb
eb
ASKER
No changes I am aware of other than installing the latest MS updates, which certainly could be the cause
I was hoping maybe someone using Policy Maker might have had some experience in dealing with this and what they are doing to resolve it.
I was hoping maybe someone using Policy Maker might have had some experience in dealing with this and what they are doing to resolve it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The solution here turned out to be MS Updates.
eb