Re: terminal Services Policies not working

You can filter your GPOs with user groups.
You should also use "loopback processing" of the GPO, with the
Replace option.

Details here:

816100 - How To Prevent Domain Group Policies from Applying to
Administrator Accounts and Selected Users in Windows Server 2003
http://support.microsoft.com/?kbid=816100

231287 - Loopback Processing of Group Policy
http://support.microsoft.com/?kbid=231287

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

"tshad" <tfs@xxxxxxxxxxxxxx> wrote on 17 nov 2005:

> I am running on Windows 2003 Server Standard Edition.
>
> I find that some of the policies for Terminal Server don't work
> (or at least I can't seem to make them work).
>
> For example, if you set the program "to start in" in the Group
> Policy Object Editor, it doesn't work. But if you set it in
> the Environment tab of the User, it works fine. Same thing with
> Always Show Desktop. This should show the Desktop, even when
> you have users start in a particular program. It doesn't!!.
>
> Am I missing something?
>
> Also, there doesn't seem to be a place for you to set policies
> for different user groups.
>
> We have certain users we want to start in particular programs
> and not have a desktop, but in another group we have set up we
> want them to have more control with the desktop.
>
> Where is this set - or can you.
>
> The Group Policy Object Editor has settings (that don't seem to
> work - as I mentioned), but they seem to apply to everyone using
> Terminal Server. An obvious problem would be for Administrators
> - I want to apply policies, such as no desktop displaying, but
> not for Administrators or there would be no way to set policies
> remotely.
>
> Thanks,
>
> Tom
.

Relevant Pages

  • Re: How to ... 2nd request
    ... > I appreciate your clarification and views on my answer Glenn. ... >> OUs and GPOs, ... >> There are two policies you can set to acheive the desired results. ... >> the workstations will not revert back to their default state. ...
    (microsoft.public.windows.server.general)
  • Re: How to ... 2nd request
    ... > I appreciate your clarification and views on my answer Glenn. ... >> OUs and GPOs, ... >> There are two policies you can set to acheive the desired results. ... >> the workstations will not revert back to their default state. ...
    (microsoft.public.windows.server.active_directory)
  • Re: terminal Services Policies not working
    ... I have a server that is only being used as a for Terminal Server. ... Administrators would need full desktops. ... We then are trying to set up the Policies from the Group Policy Object ... Group Policy Editor for Domains also have some policies for the Terminal ...
    (microsoft.public.windows.terminal_services)
  • Re: Configuring profiles
    ... You can avoid creating multiple user accounts, ... Loopback processing is especially created for this situation. ... 260370 - How to Apply Group Policy Objects to Terminal Services ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Block GPO across trusted domains
    ... On Domain A. users are subjected to several policies ... On Domain B is a Terminal Server with a loopback policy (in ... > accounts as well, so if you have any computer-specific policy in that GPO, ...
    (microsoft.public.windows.group_policy)