
------------------------------------------------------------------
NDS-NAME.DOC -- 19960524 -- Info on NDS Suggested Naming Standards
------------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




Date:	Thu, 23 May 1996 20:56:51 -0600
From:	"Mark E. Schoonover -- KA6WKE" <schoon@cts.com>
Subject: NDS Suggested Naming Standards

		Netware Directory Service
		Suggested Naming Standards

This document will provide some guidelines for naming Netware Directory
Service (NDS) containers and resource objects. It will identify standard
properties and value formats, eliminate redundant planning and provide a
consistent NDS environment for users and system administrators. If you
have any questions or comments, please feel free to contact the author,
Mark Schoonover at schoon@cts.com.

The goal for this document is to develop an NDS environment that is
flexible, easy to use and meet your business needs, while ensuring a
consistent naming structure within NDS.

There are six objectives in creating this NDS naming guideline:

1. Make browsing and NDS navigation easy. Objects should be named with
   purpose and consistency.

2. Make administration and maintenance easy. Installing file servers,
   creating users and printers, making changes, modifications and moving
   NDS objects. Will facilitate easier workstation configuration.

3. Make merging separate trees easier. Improper naming of NDS objects is
   one of the leading causes of errors in merging trees.

4. Keep object names unique.

5. Avoid special characters reserved by other WAN operating systems.

6. Provide greater compatibility with software that requires Bindery
   Services.


NDS Object Naming Guidelines

This section provides syntax and examples for naming NDS objects.
Note that some properties are required by NDS ( Required: ) and
some are optional properties that I feel are important ( Optional: ).


The NDS Objects
---------------

AFP Server Object
-----------------
Required: Server Name
Syntax:   <SERVERNAME>_AFP ( Note Capitalization )
Example:  HR_FS1_AFP
Optional: Description, Location, Department, Version, Serial
	  Number, Network Address

Alias Object
------------
Required: Alias Name
Syntax:   <aliasedobject>_ALIAS
Example:  schoonom_ALIAS
Optional: N/A
Note:     Capitalization of aliasedobject should follow the capitalization
	  of object to be Aliased.

Communication Server Object
---------------------------
Required: Communication Server Name
Syntax:   <SERVERNAME>_COMM ( Note Capitalization. )
Example:  HR_FS1_COMM
Optional: Description, Location, Department, Version, Serial
	  Number, Network Address

Computer Object
--------------
Required: Computer Name
Syntax:   <user|O|OU>_COMP ( Note Capitalization )
Example:  schoonom_COMP or HR_COMP
Optional: Description [Manufacturer], Location, Department, Owner,
	  Serial Number, Network Address
Note:     Capitalization of the user, O or OU portion of the computer
	  object should follow the capitalization rules for those NDS
	  objects.

Directory Map Object
--------------------
Required: Directory Map Name and Volume/Path
Syntax: <NETWAREVOLUMENAME*>_COM ( Note Capitalization )
Example: SYS_DM
Optional: Description, Location, Department, Organization
Note:    *This is the Netware Volume, not to be confused with the NDS
	  Volume Object.

Distribution List Object
------------------------
Required: Distribution List Name
Syntax:   <Group|O|OU>_DL ( Note Capitalization )
Example:  Everyone_DL
Optional: Full Name, Owner, Description

External Entity Object
----------------------
Required: External Entity Name
Syntax:   <O|OU>_EXT ( Note Capitalization )
Example:  HR_EXT
Optional: External Name, Description

Group Object
------------
Required: Group Name
Syntax:   First letter capitalized, less than 48 characters and do not use
	  spaces, \, +,=, -, / in the Group Name
Example:  Everyone
Optional: Owner, Description, Location, Department, Organization

Server Object
-------------
Required: NW Server Name
Syntax:   XXX(XXXX)_FS# ( Note Capitalization )
Example:  HR_FS1
Optional: Owner, Description, Location, Department, Organization
Note:     X=Division/Department/Company

Organizational Role Object
--------------------------
Required: Organizational Role Name
Syntax:   Do not use spaces, \, +, =, -, / in the Organizational Role Name
Example:  Assistant
Optional: Occupant(s), Description, Location, Department,
	  Organization, Telephone, FAX Number

Organizational Unit (OU) Object
-------------------------------
Required: Organizational Unit Name
Syntax:   Do not use spaces, \, +, =, -, / in the OU Name
Example:  Accounting
Optional: Description, Location, Telephone*, FAX Number*
Note:    *These numbers can be the phone/fax numbers
	  to the OU System Administrator.

Organization (O) Object
-----------------------
Required: Organization Name
Syntax:   Do not use spaces, \, +, =, -, / in the O Name
Example:  Accounting
Optional  Required: Description, Location, Telephone*, FAX Number*
Note:    *These numbers can be the phone/fax numbers
	  to the O System Administrator.

Print Queue Object
------------------
Required: Print Queue Name
Syntax:   <PRINTERMODEL>_PQ#
Example:  HPLJ3_PQ1 ( Note Capitalization )
Optional: Description, Location, All of the Assignments Section

Print Server Object
-------------------
Required: Print Server Name
Syntax:   XX(XXXX)_YY(YYY)_PS
Example:  HR_ADMIN_PS
Optional: Description, Location, Department, Organization
Note 1:   X = Division/Department/Organization
	  Y (Optional) = Workgroup or Location
Note 2:   Advertising Name will ALWAYS be the same as Print Server Name.

Printer Object
--------------
Required: Printer Name
Syntax: <PRINTERMODEL>_P#
Example: HPLJ4MV_P1
Optional: Description, Location, Network Address, Department, Location

Profile Object
--------------
Required: Profile Name
Syntax: <OU>_PROFILE
Example: Accounting_PROFILE ( Note Capitalization )
Optional: Description, Location, Department, Organization

User Object
-----------
Required: Login Name, Last Name
Syntax:   lllllllf
	  llllllff
Example: schoonom, schoonma ( Note Capitalization )
Optional: Given Name, Full Name, Description, Title, Location,
	  Department, Telephone, FAX Number
Note:     Use the first seven letters of the user's last name, and the
	  first letter of their first name. If this produces a duplicate
	  user name, then use the first seven letters of the user's last
	  name and the first two letters of their first name

Volume Object
-------------
Required: Volume Name, Host Server, Physical Volume
Syntax:   <SERVERNAME>_<volumename> ( NDS Default )
Example:  HR_FS1_SYS ( Note Capitalization )
Optional  Required: Description, Location
Note:     These are the reserved words that a Netware Volume can not be
	  named:  AFP, ALIAS, COMM, FS(#), PS(#), DM, COMP, EXT, OU, O,
	  PROFILE, and any object properties of NDS.

------------------------------

