|
Posted by Roger Abell [MVP] on July 3, 2006, 5:04 pm
Please log in for more thread options >
>> If you want only the users from domain X to have access then
>> the user right would be granted to X\Domain Users only.
>> Network Service would not be used unless you wanted the machine
>> itself to access its own shares via a network connection.
>> Domain Computers would only be used if you wanted to allow
>> processes running as Local System or Network Service on any
>> machine in the domain whose Domain Computers group is use.
>> Use of a grant of this right to Domain Computers is highly unusual,
>> but is used for such as access to startup scripts or to where info
>> is written during startup.
>
> What about for replicating machine group policy from the domain controller
> to the member server? Isn't that replication being done by some service
> that runs as Local System or Network Service
>
Will, that is the grants on the DC that are involved, and in general,
unless you know pretty well the architecture of AD you would be
well off not fooling with the settings on a DC.
>
>> > Does the client computer on a network that
>> > needs to access a share on a file server need to include all of the
>> > same
>> > elements in "Access this computer from network" that the file server
> does?
>>
>> I believe the answer should be clear by now. No.
>
> So on the typical member server, what should be in the list of users in
> the
> "Access this computer from the network" user right? It should be empty?
>
It all depends on what roles are filled by the member.
For example, an SQL server might have need for no grants of this,
whereas an organizations' fileservers or printservers certainly would.
>
>> > If the answer is no, Microsoft really needs to rewrite this entire
>> > document
>> > and supply a different list of recommended entries based on the role of
>> > the
>> > computer on the network.
>>
>> Try rereading with the above added clarifications, keeping in mind that
>> when a account is authorized at each different machine by establishing
>> a connection the basic user token is adjusted to represent authorization
>> on that specific machine.
>
> I still think the Microsoft KB article, as written, does a poor job of
> explaining that the client side settings will different from the server
> side, and it should be written to supply an explicit recommendation about
> what users or groups to add to this privilege on client computers.
>
Perhaps, but generally, in an enterprise, clients do not share and so
have no need for any account to be granted this right, given that there
is distinct preference for server-based storage and print queueing.
|