Migration from elux RL

Transcription

1 Migration from elux RL to elux RP Short Guide Date: Preparing for migration Requirements Providing the required packages Limited migration Automated migration 6 2. Performing migration Migration flow chart Installing the migration package on the client Updating to elux RP4 (without automation) Details about the automated migration process Troubleshooting Unicon Software Entwicklungs- und Vertriebsgesellschaft mbh The information provided in this document is protected by copyright. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, without the express consent of Unicon Software GmbH. Information in this document is subject to change without notice. Unicon Software GmbH disclaims all liability regarding correctness, completeness and topicality of the information contained herein and regarding any errors or damage resulting from the information provided. elux and Scout Enterprise Management Suite are registered trademarks of Unicon Software Entwicklungsund Vertriebsgesellschaft mbh in the European Community and the United States. elux and Scout Enterprise Management Suite are registered trademarks of Unicon Software Entwicklungsund Vertriebsgesellschaft mbh in Japan. All other trade names we refer to are service marks or trademarks of the respective manufacturers.

2 1. Preparing for migration The procedure described in this document helps you migrate from elux RL to elux RP using the Scout Enterprise Firmware update feature. Hence, even for a great number of devices, you can keep the migration scalable and comprehensible. Note If you want to migrate your elux RL clients to elux RP5, note that you first have to migrate to elux RP4, before, in the next step, you can migrate from elux RP4 to RP Requirements Valid Subscription for the relevant devices FTP or HTTP server providing UC_RL and UC_RP containers Scout Enterprise server 13.1 or later version Installed software on the relevant devices: elux RL2 baseosrl or later version or elux RL3 baseosrl or later version elux RL migration package migrp or later version elux RP4 software packages in the new UC_RP container Latest AllPackages bundle (eluxrp-4.11.x_allpackages or later version) For further information, see Providing the required packages Providing the required packages Providing the migration package 1. On click Download > elux Software Packages > elux RL Container. In the Hotfix Packages column, open the container V ( ). 2. From the Misc section, download the latest migration package migrp and, if required, the relevant BaseOS package (baseosrl ). 3. In ELIAS, import the downloaded packages as ZIP files into your existing UC_RL container. For further information, see Importing packages to a container in the ELIAS manual. The migration package is provided in the UC_RL container and is ready to be integrated into an IDF. 2

3 1. Preparing for migration Installing the elux RP container 1. On click Download > elux Software Packages > elux RP4.x Container. In the Released Packages column, open the latest RP4 container. 2. From the Bundles section, download and unpack the file eluxrp-4.11.x_allpackages. 3. From the unzipped AllPackages directory, run the setup. For further information, see Installing a container in the ELIAS manual. The application eluxcontainerrp is installed. On the web server or FTP server, the UC_RP container is provided including software packages. 3

4 1.3. Limited migration If you want to limit the migration to particular device types you can provide a positive list containing the relevant device types. The positive list is transferred to the clients and saved locally in: /setup/whitelist4migrp.ini During installation, on the client, the migration package Migration RL-->RP checks if a positive list is available. a. If there is no positive list, the system is prepared for migration: The value to be resolved by the CONTAINER macro is changed from UC_RP to UC_RP5. b. If there is a positive list, only those devices whose type is listed in the /setup/whitelist4migrp.ini file are prepared for migration. Note As the existence of a positive list is only verified when the migration package Migration RL-->RP is installed, any modifications to the positive list are only read after uninstalling and re-installing the RP4 migration package Creating a whitelist 1. Create a text file named whitelist4migrp.ini. Then, enter the section name [AllowMigRP]. 2. Begin the following line with the string Product=. Then, enter all device types you want to migrate in one line. Separate the device types by blanks. If a device type name contains a blank, enter the device type name without the blank. You can retrieve the product type name of a client device from the Scout Enterprise Properties window. It is displayed in Asset > Hardware information > Type. 4

5 1. Preparing for migration 3. Transfer the whitelist4migrp.ini file to the local client directories /setup using the Scout Enterprise feature Files. For further information, see Files in the Scout Enterprise manual. 5

6 1.4. Automated migration Migrating elux RL clients to elux RP4 includes two basic steps: Step 1: The devices are updated to an elux RL image containing the migration package. Step 2: A second update sets the devices to an elux RP4 image. By default, the administrator initiates both steps by performing a separate update. To schedule the actual migration as required, send an explicit update command after the first step has been completed and the devices have been prepared. To trigger the second step automatically, you can enable automation. With automation, after the migration package has been installed (Step 1), a second update is requested automatically. With the second update, the devices are migrated to the IDF in the new container (Step 2). For further information, see Details about the automated migration process Activating automation Use the Advanced file entries feature of the Scout Enterprise console to modify the file setup/terminal.ini of the clients: File Section Entry Value /setup/terminal.ini UpdateInfo CheckUpdateOnMigRP true The new entries are written to the terminal.ini file on the next restart of the client. For further information, see Advanced file entries in the Scout Enterprise manual. This entry causes the update command for migration to be performed automatically after the RP migration package has been installed. 6

7 2. Performing migration 2. Performing migration Migrating elux RL clients to elux RP includes two basic steps: Step 1: The devices are updated to an elux RL image containing the migration package. When you install the migration package, the update path of the devices is forwarded to the UC_RP container. Step 2: A second update sets the devices to an elux RP image. By default, step 2 is only performed after an explicit Update command sent by the administrator once the RP migration package has been installed. So, without automation, you need to initiate the second step, which is the actual migration (see Updating to elux RP4). This way, you can schedule the migration process as required. If you enable automation, after the migration package has been installed, the second step is triggered automatically, and an update is requested by the system migrating the devices to the IDF of the new UC_RP container (Automated migration process). In addition to automation, there is another option you can choose: Limited migration. You can restrict the migration to specific device types. Both options must be determined before you start the migration process. For further information, see Preparing for migration. Starting the migration process 1. Follow the instructions given in Installing the migration package on the client. 2. If you migrate without automation, follow the instructions given in Updating to elux RP4 to perform the second step. Note You cannot perform a firmware update from elux RP back to RL. The only way to set your system back to elux RL is a recovery. 7

8 Migration flow chart

9 2. Performing migration 2.2. Installing the migration package on the client Requires The UC_RL container of your web server or FTP server must contain the migration package migrp RL-->RP and the BaseOS RL /RL package or later versions. The UC_RP container must contain the latest elux RP4 software packages. In Setup > Firmware > Path of the relevant devices, the container macro parameter CONTAINER must be set. For further information, see Different elux versions in the Scout Enterprise manual. 1. If you want to migrate with automation, activate automatic migration. For further information, see Activating automation. 2. If you want to limit the migration to particular device types, create a positive list. For further information, see Creating a whitelist. 3. In ELIAS, in your UC_RL container, define an elux RP image (IDF) containing the migration package Migration RL-->RP and a BaseOS version that meets the requirements. Or: Open the existing IDF and add the migration package Migration RL-->RP. 4. In ELIAS, save the image file. Example: myimage.idf 5. In ELIAS, in your UC_RP container, define and save an elux RP image (IDF) under exactly the same name as the IDF in the UC_RL container. This is the destination IDF for migration step 2. Example: myimage.idf 6. In the Scout Enterprise console, for the relevant devices, perform a firmware update to the previously saved myimage.idf file in the UC_RL container. The migration package Migration RL-->RP is installed and executed on the relevant devices. If the clients have a whitelist, the whitelist is analyzed and the listed devices are prepared for migration. If the clients do not have a whitelist, all devices are prepared for migration. The prepared devices, from now on, resolve the CONTAINER macro parameter of Setup > Firmware to UC_RP. The devices still remain in the UC_RL container. If automation is enabled, a second update command is provoked automatically updating the relevant devices to the IDF of the UC_RP container. Before elux RP4 is installed, the storage medium is formatted and partitioned. If automation is disabled, you can initiate migration now by performing an update command at any time. For further information, see Updating to elux RP4. 9

10 Note Without automation: If, after having installed the migration package and before updating to elux RP, you still want to update to an IDF of the UC_RL container, in Setup > Firmware > Path, specify the absolute path UC_RL instead of the CONTAINER parameter Updating to elux RP4 (without automation) This step is only required if you have deactivated automation. Requires The migration package has been installed on the relevant clients. For further information, see Installing the migration package on the client. The UC_RP directory of your web server must contain an image file (*.idf) with exactly the same name as the image file which has been used for the previous firmware update and which has installed the migration package Migration RL-->RP. For the relevant clients, perform a Scout Enterprise firmware update. Before elux RP4 is installed, the storage medium is formatted and partitioned. This may take a few minutes depending on size and speed. The relevant devices receive the IDF from the UC_RP container and hence are migrated to elux RP4. The devices are now located in the UC_RP container: elux: Setup > General > Installed image shows the entry UC_RP. Scout Enterprise: Device > Properties > Container shows the entry UC_RP. 10

11 3.1. Details about the automated migration process The automated migration process triggers an update request by the client right after the migration package Migration RL-->RP has been installed. In doing so, the CONTAINER macro of the Update path in Setup > Firmware on the client is resolved to UC_RP instead of UC_RL. The UC_RP directory of the web server must contain an image file (*.idf) with exactly the same name as the image file you used for the previous update when installing the migration package. Example UC_RL container: myimage.idf (contains elux RL BaseOS /RL BaseOS or later versions and contains the migration package Migration RL-->RP. UC_RP container: myimage.idf (contains the latest RP4 BaseOS). Migration procedure in detail 1. Update of RL based clients to myimage.idf Container parameter is resolved to UC_RL myimage.idf of the /UC_RL directory is used Installation of the migration package Migration RL-->RP A second update is initiated. 2. Update and migration of RL based clients to myimage.idf Container parameter is resolved to UC_RP myimage.idf of the /UC_RP directory is used 11

12 4. Troubleshooting 4. Troubleshooting All error messages are shown in the Update log of the Scout Enterprise server. Source of error Error message Solution Target image file for RP4 cannot be found. Graphics issues on older PC systems and ThinClients (5 years or older) after migration. http request failed: rc=0, ec=404 (File not found) Check the entry in Setup > Firmware for misspelling, and check if the specified file is located in the UC_RP container (instead of the previously used UC_RL). For migration from elux RL to elux RP4 on PCs, we recommend first to evaluate if elux RP4 runs on your PC. Even if the CPU and RAM seem to be sufficient, you cannot definitely assume that elux RP runs on your system. 12