Question : Userenv and LSASRV errors on XP Pro client

We have one XP Pro PC that is constantly coming up with Userenv 1030 errors and LSASRV 40961 warnings.  No other PC on our Windows 2003 domain has these errors.  We have reloaded the PC from scratch and changed the name of the machine.  But after about a week these errors start to re-appear.  

When the userenv errors appear we get the following messages in the Userenv debug log file.

USERENV(25c.824) 01:58:36:511 ProcessGPOs: GetGPOInfo failed.
USERENV(25c.824) 03:54:36:879 ProcessGPOs: GetGPOInfo failed.
USERENV(25c.824) 05:45:37:226 ProcessGPOs: GetGPOInfo failed.
USERENV(25c.824) 07:15:37:455 ProcessGPOs: GetGPOInfo failed.
USERENV(25c.824) 08:50:37:720 ProcessGPOs: GetGPOInfo failed.
USERENV(25c.824) 10:31:37:659 ProcessGPOs: GetGPOInfo failed.

The user profile has been deleted and setup from scratch, the only settings copied back were his Favorites

Thanks for any help in advance.

Cheers
Greg

Answer : Userenv and LSASRV errors on XP Pro client

chrismenear,
Here is my 'boilerplate' on LSASVR & 40961/9 problems:

From 'My Computer' Properties, drop the computer down into a Workgroup (DO NOT RE-BOOT).
Immediately go back in and re-add the computer to the Domain.

Reboot.

Stop and re-start the w32time service - and make sure it synchronizes time with the DC.

We have written a batch command at work with the steps below imbedded.
It seems to work for us.

To configure a client computer for automatic domain time synchronization

 1.  Open a Command Prompt.

2.  Type the following command and then press ENTER:

w32tm /config /syncfromflags:domhier /update

3.  Type the following command and then press ENTER:

net stop w32time

4.  Type the following command and then press ENTER:

net start w32time

Check the local workstation Event Viewer for Event ID 40961 or 9 - or anything else that relates to 'authentication errors'.
Make sure the boxes are not going into any kind of 'sleep' or hibernation mode.
Shutting down the monitor is fine, I never advise any automatic action with the CPU.

Any Terminal Services functions/connections?
When users logged into a terminal server and terminal sessions were disconnected (but not terminated).
Improperly terminating those connections will create the same symptoms.