Local Administrator and Temporary Profile

We have a fairly large Active Directory installation running on Server 2008 R2. A majority of our users are successfully using roaming profiles, and we have a number of Group Policies controlling folder re-direction and the cleanup of cached profiles from the various workstations the roaming profile users are allowed to use. Recently, after some Group Policy changes, we started to see that when a local administrator logged on to the workstations that the roaming profile users are allowed to use, the local administrator is receiving an error message about their roaming profile and is being logged in with a temporary profile. The Group Policy that deletes the cached profiles has a scope for Authenticated Users.

How do I fix this problem so that when I log into a workstation and/or server as the local administrator, I do not get a temporary profile but get the profile I had the last time I logged into that workstation and/or server?
mharris3Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Hypercat (Deb)Connect With a Mentor Commented:
Yes. On the specific policy that you use to control the deletion of the cached roaming profiles, on the Scope page under Security filtering, list only the group for the users who use roaming profiles.  This limits the ability to read (apply) the group policy settings to just that security group. Note that if this policy contains any other settings, those settings will only apply to that group as well - it's a global setting for the group policy. You could create a specific group for this if you don't already have one and add the roaming users to that group.
0
 
Hypercat (Deb)Commented:
The Authenticated Users group, being a system group, obviously includes the Administrator account. I'd scope it to the Users group instead, which doesn't include the local admin account or administrators group. The only potential problem here would be domain controllers, where logging on as a domain administrator, that account could possibly by default be a member of the domain Users group.  It's easily checked and removed from that group, though, if you need to do so. I'm not even 100% sure that the group policy would apply in that scenario, but I would test it before relying on it's not being applied.
0
 
mharris3Author Commented:
So Hypercat, even if the "set roaming profile path..." option is set in the GPO, limiting the scope to only those users who use roaming profiles should fix this problem?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.