CACHED PROFILES AFTER IE 6 SP 1 !!! HELP!! 1

[bran2235]

Ok, folks just upgraded to IE6, SP1 and now my Roaming Profiles / Cached are not being deleted when user logs off.
-----------------------------------------------------------
Here's what we have:
W2k SP3
Citrix XPe SP2, FR2
Farm of 7

We were running IE5.5 sp2 w/out any issues w/ cached profiles....

Here's what I have done...
I disabled Windows Installer;
I do not MS03-026 installed;
I have my WTS Servers in their OU where I have a GPO to delete the roaming profiles when user logs off;
I have also set a local policy on the box to delete roaming profiles (did this after the upgrade as an attempt to fix the problem- did not fix it);
I have also checked HKlocalMachine\SW\MS Windows\WinNT\CurrentVers\WinLogon... and yes the DeleteRoamingCache value is there (Set to 1)...

What else can I do???????!!!!!! Please someone give me some advice!!!
Thanks!!
BRandon

 

[CitrixEngineer]

The trouble with cached profiles is that if the user has not logged off cleanly - ie a process associated with their session still holds a file open - then the cached copy will not delete. Even the Administrator cannot delete it. I've seen this in all versions of Windows server - I don't think it's specific to your upgrade.

There are 2 ways to clear these rogue profiles that I can think of;

1) Hunt down the process that is holding the file open. This is not too tricky, as you can simply attempt to delete the profile manually from Documents And Settings (assuming W2k/2k3 server), then, when the system returns the file lock error, hunt down the object using a tool like handle from

http://www.sysinternals.com.

2) Since 1) can be time-consuming, just run a batch file to delete all cached profiles (except the Default User and Administrator ;-)) following your reboot schedule, and all should be well.

There is, of course, 3) - which is the option I can't think of right now...


It is interesting that you should only start to see this following the upgrade - it could be useful to take note of exactly which files regularly get held open, and which processes do the locking - if my theory is correct, of course!


I hope this helps you