Re: Allow log on locally in Default Domain Controller Policy.
- From: "zenner" <zenner@xxxxxxxxxxx>
- Date: Thu, 09 Jun 2005 17:26:24 GMT
There is no reason that a normal user needs to logon to a Domain Controller.
Anything he needs should be accessed through an API. Files are access
through shares, printers through spooler, applications through whatever API
that the app provides. Only members of one of the Admin groups, by default,
are allowed Logon rights to a DC. Member servers are an entirely different
issue.
Are we talking about the same thing?
"zenner" <zenner@xxxxxxxxxxx> wrote in message
news:fnIpe.1581$Z44.602@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Is your DC also serving double duty as possibly a File or Printer server?
>
> Your System Administrator may have an explanation, if you are not the
> sysAdmin...then ask him or her (respectfully, if possible.) if they knew
> about it and/or intended to include domain users in the "logon locally"
> permission list, and if so...why?
>
> Asked in the right way you may get an explanation that is reasonable,
> given the circumstances of your companies environment.
>
> Even the best guidelines have exceptions...that's why the are called
> Guideline, instead of rules.
> "Rebsu" <Rebsu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:BD38617E-5A13-4A21-A5D1-A7EB4A732294@xxxxxxxxxxxxxxxx
>>I was looking over our group policy settings while studying for 70-292 and
>> noticed that the group Domain Users is included in the Allow log on
>> locally
>> setting in the Default Domain Controller Policy. Is this ok or
>> dangerous?
>> Is it necessary? DCs are 2003 standard.
>
>
.
- Follow-Ups:
- References:
- Prev by Date: Re: MCSE to be scrapped
- Next by Date: Re: And so it goes...
- Previous by thread: Re: Allow log on locally in Default Domain Controller Policy.
- Next by thread: Re: Allow log on locally in Default Domain Controller Policy.
- Index(es):
Relevant Pages
|