This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Relocation procedure
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 for the relevant devices is triggered by a notification named Initiate device relocation 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. Then, the relocation process will be started and the devices will be 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.
Options
In contrast to the default procedure, the administrator can configure the following options in the notification:
- Offline relocation
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 Server1[from Scout 15 2110]
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.
Important:
Do
notreserve device profiles by entering MAC addresses of the new devices on the target server before device relocation. If the devices are already registered on the target server, licenses and Subscription willnotbe updated.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.