Reason for (local) profile corruption?

[robert.waters]

I administer a 2003 TS with about 10 active users having user profiles
local to the server every so often, a user's profile will become
corrupted. Why might this happen? Could logging in from machine A
(laptop), disconnecting (no logoff), then logging in with machine B
(desktop) cause this (users have exhibited this behavior)? (Note - I
have the UPHClean service installed)

Actually, I am not even 100% sure that the root problem profile
corruption however, deleting and recreating the user profile fixes
the problem (which is: a blank blue screen after connecting, with a
2nd userinit.exe process consuming a huge amount of cpu resources -
*sometimes*, after a 5 or 10 minute wait, the user's desktop will
appear. A user can get around this and log in by killing the userinit
process and manually starting explorer)

Thank you very much for your help.

 

[Vera Noest [MVP]]

Generally, it shouldn't cause problems to connect to a disconnected
session from another client.
Are there any errors or warnings in the EventLog on the terminal
Server when this happens?
You might also want to enable verbose userenv logging:

221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833

Interpreting Userenv log files
http://technet2.microsoft.com/WindowsServer/en/Library/ccd7b430-
99a5-40fd-b68a-6c1979e565a21033.mspx
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"robert.waters" <robert.waters@gmail.com> wrote on 25 jul 2007 in
microsoft.public.windows.terminal_services:

> I administer a 2003 TS with about 10 active users having user
> profiles local to the server every so often, a user's profile
> will become corrupted. Why might this happen? Could logging in
> from machine A (laptop), disconnecting (no logoff), then logging
> in with machine B (desktop) cause this (users have exhibited
> this behavior)? (Note - I have the UPHClean service installed)
>
> Actually, I am not even 100% sure that the root problem profile
> corruption however, deleting and recreating the user profile
> fixes the problem (which is: a blank blue screen after
> connecting, with a 2nd userinit.exe process consuming a huge
> amount of cpu resources - *sometimes*, after a 5 or 10 minute
> wait, the user's desktop will appear. A user can get around
> this and log in by killing the userinit process and manually
> starting explorer)
>
> Thank you very much for your help.