Cached Profiles Mysteriously Appearing

[enjay]

Got a really weird one here. Our PCs are set to use server-based profiles which are downloaded as you log on, uploaded at logoff and then deleted. This works fine (although obviously won't help us with laptops, but that's another story). We have one PC which recreates a load of user profiles each time it reboots - the profiles are always time-stamped 6am, regardless of what time you restart the PC, and re-appear even if you manually delete them. The profiles are not listed in the ProfileList section of the registry. This only affects one computer, and I have re-imaged it several times without success.

 

6am is the time that a scheduled task on all our computers restarts them, FWIW.

 

This is really annoying, as at least one of the profiles it recreates is corrupt preventing the affected user from working, so at present I am manually deleting the profile off the computer each morning before the teacher logs in - obviously not an ongoing solution!

 

Does anyone have any ideas?!

[crutchfieldj]

We have this issue too and haven't found a solution yet either.

[enjay]

We have this issue too and haven't found a solution yet either.

 

Is it affecting all your PCs or just specific ones? If specific ones, what is different about them compared to your other computers?

 

Our affected computer is attached to a Smartboard and for some reason thinks it is a tablet/touch-enabled computer; we have other Smartboard-connected computers, however they are on slightly different models of board.

 

Solution-pending, have you found a viable workaround? At present, I am manually deleting the corrupt profiles from the PC each morning, which is far from ideal.

[enjay]

Solved! The PC had the Tablet PC feature enabled for the handwriting recognition within Smart Notebook. This meant that it was keeping a .dat file in each user's profile and recreating these should they be deleted.

 

For us, this meant that each user had a cached profile so the PC didn't go get a new one from the server, but that profile only had one file in it so the rest of the users' settings weren't available.