All Delegated OU’s will be named after the Departmental Code in PeopleSoft, or a Pre-determined code established by the OU Admins. This code will be used as the prefix for AD objects within the SUB OU’s of those delegated OU’s. This is will make it easier for OU admins to search for their objects, and to ensure that OIT-EI will be able to identify the team that support the objects.
OIT would like to ensure naming convention for OUs and groups stay consistent with guidelines below. PC, Printers, and Servers can adhere to internal naming conventions that suit the needs of the department, but request that documentation of that naming convention be provided to OIT.
OU Name
Departmental Code assigned from an authoritative source or pre-determined by Admin (i.e OIT, ORA, SAS).
- Sub OU names
- Based on sub departments. (i.e Dean, EI, ESO)
- Can also be named based on Purpose (Lab, Clinics, Classroom)
Group Names
Groups used for application, data, or printer access.
- Prefixed with OU name.
- Should have the name of app, or data that it will access.
- Example = OIT group used to provide access to Splunk
- Example = Group Used to provide access to the ORA print queue we previously named.
- Print queue name can be used for access group name.
Suggested PC and Printer Names
- Prefixed with OU name
- Should have building and\or room #
- Should have Identifier to determine type of device. (D= Desktop, L=Laptop, M=Mac Device, P= Printer)
- Number digit to identify how many of these devices reside in the same location.
- Example =RAD managed PC for the OIT department that resides in the ASB room 100A.
- Example = RAD Managed print queue for ORA that sits in Knight’s Bridge Room D206
Suggested Server Names – Non enterprise servers
- Prefixed with OU name
- Should have building or data center name present.
- Should have name of app supported or Role within the name.
- Example= OIT server for Splunk Access Located in ASB Datacenter