Re: lockdown desktop without Group Policy
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 26 Oct 2007 12:42:54 -0700
First of all: a DC is *not* a standalone server!
A standalone server (i.e. a server in a workgroup) is only
subjected to it's local policy, nothing else. A DC is subject to
Group Policies in the domain.
Can you check who is the current owner of gpt.ini? Right-click
gpt.ini - properties - scecurity - advanced - owner.
And what exactly is listed in the security tab? Any accounts at all
there? With which permissions?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?VG9ua3k=?= <Tonky@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 26
okt 2007 in microsoft.public.windows.terminal_services:
Dear Vera.
I have a similar issue, but on a Server 2003 R2 SP1 box which is
a DC and so I followed the instructions for GP Editor as
suggested by TP. All seemed to go well until accessing the
desktop shortcut created in the last step. A Command prompt
appears requesting the gpedit password. When I attempt to type
it in, nothing appears but the Command Line disappears launching
Group Policy Editor saying access denied.
Something obviously went wrong, which could stem back to editing
the security settings for gpt.ini, which suggested changes
couldn't be made as it was read only, but it appeared to make
changes all the same as all existing security groups were
removed from the list.
I can now no longer edit group policy.
Any help?
Many thanks.
Tony
- Follow-Ups:
- Re: lockdown desktop without Group Policy
- From: Tonky
- Re: lockdown desktop without Group Policy
- References:
- Re: lockdown desktop without Group Policy
- From: Tonky
- Re: lockdown desktop without Group Policy
- Prev by Date: Re: lockdown desktop without Group Policy
- Next by Date: Re: Migrating the Terminal Licensing Server in
- Previous by thread: Re: lockdown desktop without Group Policy
- Next by thread: Re: lockdown desktop without Group Policy
- Index(es):
Relevant Pages
|