H
HelpPls
Hello -
I have a user with a roaming profile. In our environment, I've configured
GPO's that affect both the user and the machine that this user logs onto
every day. I also have a Terminal Server which I've defined strict GPO
settings for [w/loopback] that really locks the server down. The user
informs me that he does not typically log off his machine at night AND often
logs onto the Terminal Server from home. The result is that many of the
LOCKED DOWN settings from the Terminal Server GPO's "transfer" to his
profile/local machine. Is this simply a case of telling the user to log off
his workstation before logging onto the Terminal Server or is there
something else I need to do to prevent the Terminal Server settings from
affecting his workstation environment? Also, once this does occur - how do
I revert to the "correct profile/settings" Do I delete the Local Cached
Profile or do I need to restore the Profile on the remote server to a
previous working version?
Thanks -
Sean
I have a user with a roaming profile. In our environment, I've configured
GPO's that affect both the user and the machine that this user logs onto
every day. I also have a Terminal Server which I've defined strict GPO
settings for [w/loopback] that really locks the server down. The user
informs me that he does not typically log off his machine at night AND often
logs onto the Terminal Server from home. The result is that many of the
LOCKED DOWN settings from the Terminal Server GPO's "transfer" to his
profile/local machine. Is this simply a case of telling the user to log off
his workstation before logging onto the Terminal Server or is there
something else I need to do to prevent the Terminal Server settings from
affecting his workstation environment? Also, once this does occur - how do
I revert to the "correct profile/settings" Do I delete the Local Cached
Profile or do I need to restore the Profile on the remote server to a
previous working version?
Thanks -
Sean