Re: Deleting user's roaming-mandatory profile at logoff not reliab
- From: Kam <Kam@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 7 May 2008 07:01:01 -0700
Hi,
We have a typical Active Directory domain structure, and originally we had
the profiles on the DC. Our public computers have a 1-hour usage limit. Their
session is forcibly logged off on the hour, so we routinely have approx. 1500
computers logging off and auto-logging back on at the same time throughout
the day! Our bandwidth was being clobbered with the profiles downloading
approx. 9MB x 1500 computers each hour! So, we changed the roaming profile
path to point to a share on the local C: drive, and of course, had to deploy
a copy of the 'master' profiles to every workstation.
Why do we delete the profiles after each user's session? We were finding
that the mandatory settings remain unchanged, some temp internet files were
not being erased at logoff, even though that is the action specified in our
group policies. We have a strict privacy policy and have to safeguard the
public users from any temp files or historical data that might be used to
reveal their internet activity. We're a government organization who provides
free internet access to the public.
"Lanwench [MVP - Exchange]" wrote:
Kam <Kam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
Hi,
We have public-access computers that log on with a mandatory roaming
profile, which we have set to 'self-delete' upon logoff--we use Group
Policies to put the local Users group into the Guest group.
Microsoft's default mechanism is to delete any Guest's profile at
logoff. The 'master' copy of the profile actually sits on the
computer itself, C:\Profiles, so a copy of it is made to C:\Documents
and Settings\<username>. The profile is .MAN.
The problem is that invariably the system fails to delete the
profile, then the auto-login kicks in and the user is logged back in
with a duplicate profile as the previous one becomes
unusable/corrupted. Thus as the day goes on, each user session
invariably creates successive profiles, and some computers end up
with hundreds of 'dead' profiles that we need to manually delete.
Does anyone have any advice on how to ensure that the cached profile
is deleted consistenly and reliably each time the user logs off and
on? Thanks.
How are you using roaming profiles if the "server" copy is actually local to
that computer? I have never seen this work unless you're using a domain
model (and the profile lives on the server). You say you've got group
policy, which is also a domain thing....otherwise it's a local policy. So
I'm a bit confused as to what you've got.
That said, you might check rsop.msc and your event logs for errors/clues.
However, since a mandatory profile cannot be changed, why are you concerned
with deleting it anyway? What's the harm in leaving it be?
- Follow-Ups:
- Re: Deleting user's roaming-mandatory profile at logoff not reliab
- From: Lanwench [MVP - Exchange]
- Re: Deleting user's roaming-mandatory profile at logoff not reliab
- References:
- Deleting user's roaming-mandatory profile at logoff not reliable
- From: Kam
- Re: Deleting user's roaming-mandatory profile at logoff not reliable
- From: Lanwench [MVP - Exchange]
- Deleting user's roaming-mandatory profile at logoff not reliable
- Prev by Date: Re: Windows XP Password During Recovery Console
- Next by Date: Invisible Data
- Previous by thread: Re: Deleting user's roaming-mandatory profile at logoff not reliable
- Next by thread: Re: Deleting user's roaming-mandatory profile at logoff not reliab
- Index(es):
Relevant Pages
|
|
