 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows Server 2003 / Group Policy / July 2008Preventing group policy when using remoteapp
We are going to start using terminal server on Windows 2008. The terminal server should pull down the group policies like any other server. However, when a user logs onto the terminal server from a remote session, i.e, remoteapp, group policies should not be processed. Right now, if I launch a remoteapp from my PC, I see that my group policies are running again. How do I prevent this?  SignatureThanks! Howdie! > We are going to start using terminal server on Windows 2008. The terminal > server should pull down the group policies like any other server. However, > when a user logs onto the terminal server from a remote session, i.e, > remoteapp, group policies should not be processed. Right now, if I launch a > remoteapp from my PC, I see that my group policies are running again. How > do I prevent this? you can try activating group Policy's loopback processing mode. It's there for Terminal Servers. It's got two modes: Replace and Merge. When choosing "Replace" mode, Group Policy applies all policies that are linked to the Terminal Server's OU to the user logging in there. It overwrites the user's "user configuration" portion so to speak. Check: http://support.microsoft.com/kb/231287/en-us http://support.microsoft.com/kb/260370/en-us http://technet2.microsoft.com/windowsserver/en/library/abe2b1a9-975f-4b2f-b771-9 e6a903e97db1033.mspx?mfr=true cheers, Florian SignatureMicrosoft MVP - Group Policy eMail: prename [at] frickelsoft [dot] net. blog: http://www.frickelsoft.net/blog. Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste > Howdie! > you can try activating group Policy's loopback processing mode. It's there [quoted text clipped - 11 lines] > > Florian I thought about this but the policies that are associated with the user account that logs onto the terminal server are still run. The loopback only replaces the Computer Configuration. Howdie! > I thought about this but the policies that are associated with the user > account that logs onto the terminal server are still run. The loopback only > replaces the Computer Configuration. Make sure you run Loopback in "Replace" mode. That replaces the "User Configuration" settings that apply to the user with the "User Configuration" settings that apply to the Terminal Servers. cheers, Florian SignatureMicrosoft MVP - Group Policy eMail: prename [at] frickelsoft [dot] net. blog: http://www.frickelsoft.net/blog. Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste Ahhh...I see. I will give this a shot. Thanks. > Howdie! > [quoted text clipped - 9 lines] > > Florian Well I tried creating a policy with Loopback Replace Mode but the users policy is still running. I can tell because the users policy is running a script and I can see this script error when I try to logon to a RemoteAPP. I linked this policy to the OU where the terminal server resides. > Howdie! > [quoted text clipped - 9 lines] > > Florian OK. It's working now. I think it needed time. Thanks. > Well I tried creating a policy with Loopback Replace Mode but the users > policy is still running. I can tell because the users policy is running a [quoted text clipped - 14 lines] >> >> Florian Thanks >> Howdie! >> you can try activating group Policy's loopback processing mode. It's [quoted text clipped - 15 lines] > account that logs onto the terminal server are still run. The loopback > only replaces the Computer Configuration. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.