| Object Type | Naming Convention |
| Forest Name | See Domain Namespace section |
| Windows 2003 Domain Name | See Domain Namespace section |
| NetBIOS Domain Name | Default based on the DNS label |
| Organizational Unit (OU) | See Organizational Units Design section |
| Active Directory Site name | < ISO 3166 country code >< location common name > Use Uppercase to differentiate the first letter of each word composing the site name. No space between words. Examples ShenZhen Regional Office in China: cnShenZhen Hong Kong Head Office: hkHeadOffice Cheangwattana store in Thailand: thCheangwattana <location common name> has to be unique in the Forest. Add an incremental number to the second site if two sites share the same common name. Example : cnSitename and cnSitename2 |
| Site Code | In order to support name technical restrictions, each location must be identifiable with a short site code based on the location name. The site code length is 4 letters max. By default, the first 4 letters are used. In the case of composed name, first 4 letters of the second word may be used. For head Office, use “ho”. For Regional Office, use ro and incremental identifier on two digits, alphanumeric base. Examples Phuk store in Thailand: phuk ShenZhen Regional Office in China: ro01 Head Office in Malaysia: ho |
| Site Link | Site links are named after the site names separated with a hyphen “-“. < siteNameA >-< siteNameB > The site acting as the hub for network traffic is placed first. Examples Site link between Head Office and Subang Jaya store in Singapore SubangJaya sgHeadOffice-sgSubangJaya |
| Site Links bridge | If there is necessity to create site link bridges, the Site Links bridge prefix is “sb”. The prefix is followed by the different site links bridged separated by hyphen characters “-”. sb< Site Name A >-< Site Name B > |
| Connection object | A manually created Connection Object is indicated with the prefix “co” followed by the connected Domain Controllers. Domain Controllers names are separated by the hyphen character “-”. co< Domain Controller A >-< Domain Controller B > |
| Domain Controller | Windows NetBIOS computer name is limited to 15 characters Domain Controller naming convention is: < Country code >< site code >dc< incremental identifier, alphanumeric base, two digits > All characters are lowercase. Examples ShenZhen Regional Office in China: cnshendc01 Hong Kong Head Office, second Domain Controller: hkhodc02 Hong Kong Head Office, tenth Domain Controller: hkhodc0a Cheangwattana store in Thailand: thcheadc01 |
| Group Name | Group naming convention is based on the group type, the scope of application and a description. < group type >< scope >< description > Group Type is represented by two letters in lowercase: Local Group and Domain Local Group “lg” Global Group “gg” Universal Group “ug” Scope indicates if the group object is used to apply permissions on transverse resources (domain level) or, on the other hand, on remote site resources only. Transverse or Domain application: Country code in uppercase or ZDC ofr the Zone Datacenter Local application: Country code in uppercase+ Name of the parent Organizational Unit Description up to the limit of 64 characters. Description may freely use lowercase, uppercase, underscore ”_” and hyphen “-” characters. Examples Domain Local Group used to provide Read & Write access to a shared directory in Honk Kong Head Office lgHK_CommonFileRepository-RW Global group containing all the Store Managers in Taiwan ggTW_Store-Managers Domain Local Group used to provide Read access to the local server shared folder “Communication” in Penang Prai store lgMLPenangPrai_CommunicationShare-Read |
| GPO Name | Group Policy Object naming convention is based on the scope of application and a description. < scope >< description > Scope indicates if the Group Policy is applied to the Domain, an Organizational Unit or an Active Directory site. Domain “dm” Organizational Unit “ou” Active Directory site “st” Description may freely use lowercase, uppercase, underscore ”_” and hyphen “-” characters. Examples Domain wide security settings dmSecuritySettings Remote Control configuration GPO linked to an OU ouRemoteControlDekstopConfiguration Note Default Domain Policy and Default Domain Controllers Policy GPOs are not renamed. |
| User logon name | User name is composed of a prefix representing the Country, the first letter of the last name, the first two letters of the surname or usual name and an incremental identifier on two digits. < Country Code > < first letter last name >< identifier > Example Christophe Bonnel, based in Hong Kong. hkbcg00 |
| Contractor logon name | Contractor account are prefixed by “c-“ in order to clearly identify them. |
| Service Account | Service accounts are prefixed by “svc-“ in order to avoid confusion with user accounts. |
| Admin Account | User logon name prefixed by “a-“. |
| Computer name | Computer name is composed of a prefix representing the Country, the type of the workstation and an incremental identifier. < Country Code > < Workstation Type >< identifier > The identifier is alphanumeric and displayed on 5 digits from 00001 to FFFFF (1048575). Desktop Workstation Type prefix : “D” Laptop Workstation Type prefix : “L” Example Taïwan Desktop number 123 TWD0007B Indonesia Laptop number 26 IDL0001A |
| Printer | Printer name is composed of a prefix representing the Country, the site name, the “PRT” keyword and an incremental identifier. < Country Code > < Site Name >PRT< identifier > The identifier is alphanumeric and displayed on 2 digits from 01 to FF (255). Example Second printer in Putra Jaya store, Malaysia mlPutraJayaPRT02 Tenth printer in Head Office, China chHeadOfficePRT1A Note Printer type (vendor, model) should be entered in the server printer properties in order to be published in Active Directory. |
| File share | File share name is composed of a prefix representing the Country, the site name, and the description < Country Code > < Site Name > < description > A hyphen may be used to separate the location from the description. Example mlPenangPrai-StoreMainShare |