The relocation procedure is initiated by the source server (device-releasing server) and, by default, completed by the target server (device-receiving server). The actual relocation procedure, however, is performed by the devices. They check the conditions and transfer the license information.
Relocation is triggered by the notification Initiate client relocation for the relevant devices in the Scout Console of the source server. The notification includes all required details. On the next device restart, the devices receive the new configuration data of the source server and evaluate the relocation notification.
The devices then check whether the transmitted target server's address is available via the network. Provided, the target server's Scout version is valid,1 the relocation process is started and the devices are deleted from the source server.
By default, the devices bring their management and application licenses as well as their proportional Subscription validity with them to the target server. The license and Subscription information is then deleted on the source server and added to the target server.
The new devices are assigned to the specified OU on the target server. If no destination OU has been specified, the default OU or the OU defined by OU filter rules is used (configured in Advanced options > Devices > New devices).
The relocation procedure is completed by an automatic device restart which activates the configuration of the target server. If configured, locally defined configuration is pertained. If the OU filter is used, an additional device restart is provoked by the system after assignment.
In contrast to the default procedure, the administrator can configure the following options in the notification:
The devices are removed from the source server without checking whether the target server is available. They move to the target server only when they can connect to it.
Relocation without transfer of licenses
License and Subscription information is left on the source server so it can be used by other devices. This includes management licenses, application licenses assigned to the devices (if any), and the subscription portion of the relevant devices.
Retain local configuration on new Scout Server2
If on the source server is configured that users' local configurations in unlocked fields should not be overwritten by server-side configurations (Advanced options > Devices), then the local configurations are carried along. The relocated devices receive the target server's device configuration only where there are no local configurations.
Do not reserve device profiles by entering MAC addresses of the new devices on the target server before client relocation. If the devices are already registered on the target server, licenses and Subscription will not be updated.