S
Simon Begin
I know Best practice tells to use Global groups & Local domain groups,
associate users with the global group, associate the resource with the Local
domain group, then associate the 2 groups together.
I'm from a Novell environment, and "best practices" doesn't exist. We used
to understand how it works, then choose what's best for us.
Back to my 2003 AD groups, nobody could tell me WHY to use BOTH groups,
instead of using only Local domain groups (even a teacher of 2003 AD
course). We have 1 tree and 1 domain, <1000 users. We will have someday
other foreign 2003 AD trees, and will need to link with them for some
applications.
Do we really need to make 2 groups, when it works very well with 1 ?
associate users with the global group, associate the resource with the Local
domain group, then associate the 2 groups together.
I'm from a Novell environment, and "best practices" doesn't exist. We used
to understand how it works, then choose what's best for us.
Back to my 2003 AD groups, nobody could tell me WHY to use BOTH groups,
instead of using only Local domain groups (even a teacher of 2003 AD
course). We have 1 tree and 1 domain, <1000 users. We will have someday
other foreign 2003 AD trees, and will need to link with them for some
applications.
Do we really need to make 2 groups, when it works very well with 1 ?