Re: Nesting domain groups under local groups
- From: "fpbear" <dontsendhere@xxxxxxxxxx>
- Date: Sun, 18 Mar 2007 14:23:49 -0700
The users will need to be able to logon to another domain in order to access
the other domain's file sharing resources, to collaborate across the network
with other users in this application. Using cached domain credentials would
get the user on the machine, but without access to the other domain's
network resources (if I understand correctly).
Further, the user's data files are protected with NTFS file DACLs that allow
only the user's group access. If the user disconnects from the home domain
and logs onto another domain without the group nesting scheme described
previously, the user would be locked out of their own files.
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
I'm still confused, I guess. Why can't they belong to domainX, and
*always* log into domainX no matter where they are - whether they can
reach a domainX DC or not?
.
- Follow-Ups:
- Re: Nesting domain groups under local groups
- From: Lanwench [MVP - Exchange]
- Re: Nesting domain groups under local groups
- References:
- Nesting domain groups under local groups
- From: fpbear
- Re: Nesting domain groups under local groups
- From: Lanwench [MVP - Exchange]
- Re: Nesting domain groups under local groups
- From: fpbear
- Re: Nesting domain groups under local groups
- From: Lanwench [MVP - Exchange]
- Nesting domain groups under local groups
- Prev by Date: Re: Block Windows Remote Shutdown on a Domain
- Next by Date: IBM thinkpad locked
- Previous by thread: Re: Nesting domain groups under local groups
- Next by thread: Re: Nesting domain groups under local groups
- Index(es):
Relevant Pages
|
