NTUSER.DAT file gets modified everyday

Hello,

I have this weird problem. I have 10 accounts setup on my computer, one of
them is my own personal account. Everyday, I log ona and use my account. As
expected, the modified date of my NTUSER.DAT file gets updated to reflect the
fact that I have logged on. But, for some reason, the last modified date on
every other NTUSER.DAT file gets updated as well. This is an issue as I will
not be able to succesfully use the GPO setting that allows profiles to be
deleted if they have not been used for x umber of days.

We, but not I, have been in contact with our main tech support rep @
Microsoft, and they did not give us any meaningful answers. FYI, this same
behaviour will occur if you have Symantec Antivirus Corporate Edition
installed. Only way you can stop Symantec from interefering is if you
configure the clients to not scan all *.dat files, or create a logon script
to configure Symantec to ignore the NTUSER.DAT file for the currently logged
on user.

Any info or help will be greatly appreciated.

"fg" <> wrote in message
news:F3E9877C-D872-48CD-A2B5-...
> Hello,
>
> I have this weird problem. I have 10 accounts setup on my computer, one
> of
> them is my own personal account. Everyday, I log ona and use my account.
> As
> expected, the modified date of my NTUSER.DAT file gets updated to reflect
> the
> fact that I have logged on. But, for some reason, the last modified date
> on
> every other NTUSER.DAT file gets updated as well. This is an issue as I
> will
> not be able to succesfully use the GPO setting that allows profiles to be
> deleted if they have not been used for x umber of days.
>
> We, but not I, have been in contact with our main tech support rep @
> Microsoft, and they did not give us any meaningful answers. FYI, this
> same
> behaviour will occur if you have Symantec Antivirus Corporate Edition
> installed. Only way you can stop Symantec from interefering is if you
> configure the clients to not scan all *.dat files, or create a logon
> script
> to configure Symantec to ignore the NTUSER.DAT file for the currently
> logged
> on user.
>
> Any info or help will be greatly appreciated.

Isn't there another GPO that works in a more sophisticated way? I am
surprised that it would work by checking the modified file date.

When you NET USER <username>, is it the same incorrect date?

ss.

> Isn't there another GPO that works in a more sophisticated way?
I do not know and cannot find a better GPO that will fix this issue.

> I am surprised that it would work by checking the modified file date.
Well, it does, and this information came from Microsoft.

> When you NET USER <username>, is it the same incorrect date?
Funnily enough, no, the date you get when you NET USE <username> is the
correct date, but the GPO does not use that date to determine which profiles
to delete.