You can configure the UMS server so that all devices on the server's network are automatically registered at startup. To do this, the devices must be given the address of the UMS server via DHCP or DNS.

We recommend automatic registration when registering new devices for the first time during the rollout. Disable automatic registration as soon as all devices have been registered, so that no unknown devices can obtain sensitive settings.

To configure UMS servers and devices for automatic registration, proceed as follows:

  1. Under UMS Administration > Global Configuration > Device Network Settings, select the Enable automatic registration (without MAC address import) checkbox.

    If this option is enabled, each device without a UMS certificate (is distributed to the clients during registration) in the network will be added to the UMS database. If you reset a device to the factory settings and reboot it, it will immediately be registered on the server again. 
  2. Configuration of the network environment for an automatic UMS registration:
    • Via DNS:
      Create a DNS entry igelrmserver (entry type A) on your DNS server which points to the UMS server.
    • Via DHCP:
      Change the DHCP server configuration depending on the IGEL OS version of your endpoints as follows:
      • IGEL OS 11.03.500 or lower: Set igelrmserver as DHCP option 224. Set the DHCP option 224 as a string - not as a DWORD - to the IP address of the server. For the default Linux DHCP server, add the following in the dhcpd.conf file in the appropriate section, e.g. in the global section: option igelrmserver code 224 = text option igelrmserver ""
      • IGEL OS 11.04.100 or higher: Alternatively you can use DHCP option 43 (vendor-specific options) to send DHCP option 224 (name: igelrmserver) to the correct endpoints. An end device with IGEL OS 11.04.100 or higher sends the option 60 (vendor class identifier) with igel-dhcp-1 as value.

        An IGEL specific DHCP option that is sent in DHCP option 43 overrides a corresponding DHCP option that is sent in the global namespace. The DHCP options 1, 224, and 226 can be embedded in option 43.

        You can prevent a DHCP option 224 that has been sent in the global namespace from being interpreted. To achieve this, you must add option 1 (called "exclusive", type Byte, value 1) to DHCP option 43.