[THIN] Re: Cannot delete local profile

  • From: "Baldwin, Tony" <Tony.Baldwin@xxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Wed, 18 Jan 2006 15:34:56 -0500

Doug,
 
I was thinking that they could open filemon and set a filter for
c:\documents and settings\username and see what processes were opening what
files there (maybe do a search for ntuser.dat from there).
 
Now that I think about it Process Explorer
(http://www.sysinternals.com/Utilities/ProcessExplorer.html) might be the
better tool (search handles for c:\documents and settings\username).
 
Tony

  _____  

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Stratton, Doug ISMC:EX
Sent: Wednesday, January 18, 2006 3:15 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Cannot delete local profile


Hey can you expand on how to figure out what is locking the reg file with
filemon?
 
We have had problems in the past.  Something is locking the reg file for the
users (they are already logged off).
 
I know running filemon shows all the files that are accessed.  Just don't
see the process for when it is already locked.
 
Thanks

  _____  

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Baldwin, Tony
Sent: January 18, 2006 10:13 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Cannot delete local profile


Evan,
 
Can you use filemon (http://www.sysinternals.com/Utilities/Filemon.html) to
see what's got a hold of the profile?
 
Tony

  _____  

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Evan Mann
Sent: Wednesday, January 18, 2006 11:05 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Cannot delete local profile



I have a profile that I cannot delete from a Citrix server.  The "delete"
option is greyed out doing it through user accounts and I cannot directly
delete the users directory under documents and settings.


This user is not logged into any of the Citrix servers.  My guess is their
registry hive is still loaded?  UPHClean is running on the server.  How do I
correct this without a reboot?


Other related posts: