That impersonate error comes up usually when some part of GP processing needs to impersonate the user but can't access the user's account in the domain. It could be caused by a bad trust relationship between the workstation and the domain or by the DC not being available when it occurs. I would check the workstation's system event log for netlogon errors, which may point to the trust problems. Otherwise, make sure that DNS is properly configured on the client. Does the same error show up when you do a gpupdate while the user is logged on? Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Conger, Justin Sent: Monday, December 04, 2006 11:58 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: ImpersonateUser: Failed to impersonate user with 5 Failed with 5 is an Access Denied error. Sounds like you have a script using the impersonate command that may have incorrect credentials. Have you gone through a password change recently? Justin _____ From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Difarnecio, Gino (Citco) Sent: Monday, December 04, 2006 1:37 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] ImpersonateUser: Failed to impersonate user with 5 Need some help trying to figure out why this message keeps showing up in my userenv.log file. I have attached the log file. User experiences slow log in times. Thank you Windows Security Architect Citco Technology Mgt. (Tel) 954-267-7855 (Cel) 954-579-7597 (E-mail) <mailto:GDifarnecio@xxxxxxxxx> GDifarnecio@xxxxxxxxx