As I understand it, the GPOs with user configuration settings have been linked to OU with user objects making them to affect the users when they log on to their local machines. When enabling the lopoback processing mode on the TS computer, user configuration settings will be applied when linking the user-GPOs to the OU with computer object. Combine it with security filtering on the GPO to only affect a group of users instead of all users logging on to the machine.
Main Topics
Browse All Topics





by: tigermattPosted on 2009-07-18 at 04:58:16ID: 24885696
Can you please explain what you mean by not wanting it to apply to the local machine? Do you mean you don't want it to apply to users' XP workstations, or to users who logon locally at the console of the 2008 Terminal Server?
Making it only apply to users on the TS is easy - and you had the correct idea with the loopback policy. Move the Terminal Server to its own OU, then create and link a new policy in that OU. Set the User policies and then enable Loopback Processing, probably in Merge mode.
However, the other option, which I believe you are referring to, cannot be done. You cannot specify a Group Policy which only applies to remote Terminal Server sessions and not to local console sessions. Policies apply to the computer and its users, and that is that.
However, since only the Domain Administrators should be logging into the Terminal Server's console, you could use Security Filtering to indirectly stop the policy applying to Domain Admins - http://www.windowsnetworki
-Matt