The WOLFTECH domain is designed to be usable by any organization within NC State University. Consequently, special naming considerations are necessary to promote organization, prevent conflicts, and ease delegation.
Most objects within Active Directory are required to have unique names. In addition, it is important that an objects name indicate its purpose, as well as the organization it belongs to. The following naming standards were developed to help achieve these goals. Please be sure to follow these standards, as any unidentifiable or conflicting objects may be removed.
- Users – Active Directory requires that all users have unique names. This is achieved by using users UnityID (guaranteed to be unique), and in some cases, special suffixes. https://activedirectory.ncsu.edu/ou-admins/naming-conventions/user-accounts-naming-conventions/
- Groups – Active Directory requires that all groups have unique names. This is achieved by including the acronym of the department, college, or university that the group belongs to. The table below outlines the naming conventions that should be used for different types of groups on the WOLFTECH domain. https://activedirectory.ncsu.edu/ou-admins/naming-conventions/groups/
- Machines – Active Directory requires that all machines have unique names. In addition, it is good network etiquette to not duplicate any other machine’s name on the NCSU network. Please check IPAM to ensure that the name you wish to use is not already in use on the NCSU network.
- Group Policies – Active Directory requires that all group policies have unique names. This is achieved by including the acronym of the department, college, or university that the group policy belongs to. The table below outlines the naming conventions that should be used for different types of group policies on the WOLFTECH domain. https://activedirectory.ncsu.edu/ou-admins/naming-conventions/group-policy/
- Organizational Units – Active Directory does NOT require organizational units to have unique names. The only naming requirement for OUs is that they clearly indicate their purpose. There is, however, a default OU organization structure that is created for each new departmental OU. OU Admins are free to change, or even scrap, the default setup within their departmental OU if it does not meet their needs. Above the departmental OUs, the WOLFTECH domain has a rigid OU architecture. To learn more, see OU Architecture Overview and Detailed Architecture.
- Infrastructure Servers – Infrastructure Servers or servers that support campus or domain wide services should use the following naming convention when naming servers. Exceptions may be made for servers that cannot follow the naming convention and must be approved by the AD Technical Committee/Working Group.
- WT-<service><role>-XYY, where X is datacenter & YY are succession numbers