|
|
 FAQ
 Search
 Memberlist
 Usergroups
 Register
 Profile
 Private messages
 Log in
|
|
| Author |
Message |
SPiderman
Guest
|
 Posted: Mon Jul 09, 2007 2:17 am Post subject: Naming Scheme HELLP :) |
 |
|
Hi,
Can people who have been around quite a bit toss out idea on naming security
groups and email lists? I once used # sign in front of all email lists and
that wasn't bad, but not great. |
|
| Back to top |
|
 |
|
|
SPiderman
Guest
|
| Posted: Tue Jul 10, 2007 2:44 am Post subject: Re: Naming Scheme HELLP :) |
|
|
Hi,
That sounds good, can you give me an idea of email lists names you might use
or security group names? When do you use global and when do you use local?
Do you ever do universals?
"Herb Martin" wrote:
| Quote: |
"SPiderman" <SPiderman@discussions.microsoft.com> wrote in message
news:AA9CEFA5-CDDC-419F-B353-977F0869CE6F@microsoft.com...
Hi,
Can people who have been around quite a bit toss out idea on naming
security
groups and email lists? I once used # sign in front of all email lists
and
that wasn't bad, but not great.
I would never do that. I try to keep all names simple, alpha first
character
and alphanumeric for subsequent characters, especially if they must be
used outside the organization (or for NetBIOS names.)
If you must do something "unique to distribution groups" then perhaps
using a prefix or suffix like "DL" or ML (for mail list.)
Security Groups should be named after the FUNCTION of the People
involved for Global Groups and the PURPOSE of the resources for
Local Groups.
* I break this rule for Template User accounts, which are usually of
the form:
_Engineer _SalesPerson _DeptAdmin
OUs named for Departments or Job function:
Sales HumanResources Secretarial Development
Groups (Global) for similarly but with a person or some similar
adjustment to avoid collisions:
SalesPeople HumanResourcesPersonnel Secretaries Deverlopers
Not perfect examples but quick ideas.
|
|
|
| Back to top |
|
|
|
|
