design I described. In a simpler environment (e.g. "we have a
departmental share with each department having a subfolder" on the extreme
side), you don't necessarily need the ABS layer.
Dan
From: [EMAIL PROTECT
having a subfolder" on the extreme side), you don't
necessarily need the ABS layer.
Dan
From:
[EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED]] On
Behalf Of Wyatt, David
Sent: Wednesday, July 26, 2006 8:28 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Domain Loca
extreme side), you don’t
necessarily need the ABS layer.
Dan
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Wyatt, David
Sent: Wednesday, July 26, 2006 8:28 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Domain Local Groups vs Global Groups
I&#
his group often enough,
so feel free to write me directly.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Wyatt, David
Sent: Wednesday, July 26, 2006 8:28 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Domain Local Groups vs Global Groups
I'd
b
Somehow I avoided answring your question the first time...Going global role-based group and local task-based group is pretty standard in larger environments.You create the global group to hold users and the local group to hold users. The purpose for this is so that you can nest multiple role-based
Having went through this quite a bit recently, I'll see if I can give you some help on this. Every security group on a user's token adds about 45 bytes to the token and sometime around 80 security groups, you can expect a token to break 4k and bump up to 8k. This will have the most impact to Excha
Title: Message
I'd be interested to
hear peoples strategy for permissioning windows based file servers when the
server is in a Windows 2003 domain. I have read the best practices about
putting users into global groups then put the global groups into local groups
then permission the resource
