Assigning directory server to a group

1. Select in the left window pane either:
   • Device Groups,
   • User Groups, or
   • Global Settings > Administrator Groups
2. Select the desired group in the left window pane.
3. Select the subnode Dynamic Population in the left window pane.
4. Select the subnode Directory Server in the left window pane.
5. Select Edit > Assign Server .
    The Select a Directory Server dialog box appears on the screen. The dialog box lists all available directory servers with their organizational units depending on the base object, that is, when under a device group it displays all available device groups, and when under a user or administrator group, it displays all available user groups.
6. If the directory server you want to synchronize with is not displayed in this list, that is, it has not yet been created in CM , you can directly create it from here as follows:
   1. Click the Create and connect to a new directory server button.
       The Properties dialog box appears on the screen.
   2. Enter the required information into the respective boxes (see topic Creating a Directory Server for more information).
   3. Click OK to confirm the new directory server.
       The window closes and the new directory server is added to the list of available servers in the Select a Directory Server dialog box.
7. Select an entry from the list.
   You can either select the directory server itself or one of its children. If you want to synchronize all elements of a directory server in a flat list check the Synchronize All Devices/Administrators/Users box above this list together with the directory server root in the following text box. To synchronize with the server root or an OU maintaining, that is, recreating the directory structure in CM do not check this box. This does not apply to administrator groups, because these cannot have subgroups and thus will always import all elements in a flat list.
8. Click OK to confirm.
    The Properties dialog box appears on the screen. Here you can specify if all devices are to be synchronized or only those with an CM agent installed.
9. Select the respective option from the list.
10. Click OK to confirm.
     A confirmation window appears.
11. Click either:
    • OK to synchronize, or
    • Cancel to define the directory server without synchronization.
       If you chose to synchronize, the connection with the directory server is established and all members of the selected entry are added to or removed from your current group. The Directory Server Synchronisation window appears as a confirmation listing all objects that were added or removed with their status which in this case will either be New Object or Error . In case of an administrator group synchronization this can also be Administrator maintained if administrators are not to be deleted during synchronization. If more than 3000 elements are synchronized this window will be replaced by a simple confirmation message.
12. Click OK to close this window.

If you did not synchronize, the Select a Directory Server window will be closed and the directory server will be added to the table in the Directory Server node but no objects will be added.

If the directory server is assigned to a device group, the device type of the group will automatically be modified to All Devices .

No matter if you chose to synchronize or not, the name of your group will be changed to the name of the directory server entry followed by the full name of the server in dotted notation. For example, if your group was initially called by the default name New Device Group and you synchronized it with an organizational unit called Relay Servers , the name of your group will now were changed from New Device Group to Relay Servers.Full.Directory.Name . If the selected group has subunits these will also be synchronized and added to the group as subunit.group.server name.

If all elements of a type were synchronized the name of the group will change and to the full name of the directory server. The elements will be added to this group in a flat list ignoring any hierarchy they might were located in on the directory server.