Dell Wyse Management Suite Version 2.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction................................................................................................................................. 5 Migrating from Wyse Device Manager to Wyse Management Suite............................................................................. 5 2 Prerequisites for migration........................................................................................................... 7 Wyse Management Suite license requirements.....................................
6 Postmigration............................................................................................................................ 24 7 Uninstall Wyse Management Suite Import Tool............................................................................. 25 8 Troubleshooting......................................................................................................................... 26 Data import failure..................................................................................
1 Introduction This guide contains instructions to migrate from Wyse Device Manager (WDM) to Wyse Management Suite. The target audience for this guide is enterprise customers with administrator privileges. You must have knowledge about various thin client operating systems, Wyse Device Manager, cloud infrastructure, network technologies, file system permissions, and user authentication technologies. It is recommended that you migrate from WDM version 5.7.2 to Wyse Management Suite version 2.x.
8. Switch devices from WDM based on your thin client infrastructure—see Switching devices from Wyse Device Manager to Wyse Management Suite. • • • • • Switch Windows-based devices—see Deploy RSP package to Windows-based devices. Switch ThinLinux-based devices—see Deploy RSP package to ThinLinux devices. Switch SUSE Linux Enterprise-based devices—see Deploy RSP package to SUSE Linux devices. Switch ThinOS-based devices—see Deploy INI parameter to ThinOS devices.
2 Prerequisites for migration Ensure that you meet the following migration requirements from Wyse Device Manager (WDM) and Wyse Management Suite (WMS): • Wyse Device Manager (WDM) • • Migration to Wyse Management Suite is supported from WDM version 5.7.2. If you are using an earlier version of WDM, then upgrade WDM to version 5.7.2. • WDM enterprise edition must be installed on your network. • Scheduled jobs or tasks in WDM must not be in progress state.
Supported environment for migration Table 1. Wyse Device Manager Operating system Database Wyse Device Manager • • • • Wyse Device Manager version 5.7.
Data available on thin client Wyse Device Manager (WDM) Wyse Management Suite Additional information Resources that are associated with profiles on Windows Embedded Standard 7, Windows Embedded Standard 7P, Windows Embedded 8 Standard, and Windows 10 IoT Enterprise. Wallpaper and Windows wireless profile. Resources are moved to the data folder in the local repository. EULA and logo are not applicable for Windows-based operating systems. Teradici configurations on ThreadX 5.x devices. ThreadX 5.
3 Using Wyse Management Suite Import Tool Wyse Management Suite Import Tool allows you to import the data from WDM to Wyse Management Suite.
Install Wyse Management Suite Import tool To install the Wyse Management Suite Import tool: 1. Sign into Dell Digital Locker, and download the Wyse Management Suite Import Tool installer on your server operating system. 2. Extract the contents of the installer. 3. Run the WMS_Import_Tool.exe file.
Wyse Device Manager database guidelines • • • If the WDM database is created on Microsoft SQL Server, enter only the server name. If the WDM database is created on Microsoft SQL Server Express, enter the server name and the database instance name. For example, VM\RapportDB. If the WDM database is created on Microsoft SQL Server, and configured with a custom port, enter the server name followed by the custom port. Use a comma or a colon to separate the custom port from the server name. For example, 10.0.0.
4 Importing data inventory Data import is the process of importing data inventories from Wyse Device Manager (WDM) to Wyse Management Suite. In the WDM Import Task screen, you can perform each task independently. However, you must import Windows-based WCM resources from WDM before importing view and Windows profiles. To import view and Teradici configurations, you must first import Teradici-based WCM resources from WDM.
Dell recommends that you click the Validate Repository Access link to validate whether the Wyse Management Suite local repository is accessible. If the Wyse Management Suite local repository is configured, then you can enter the Wyse Management Suite local repository. If the Wyse Management Suite local repository is not accessible, then enter the network credentials.
• Failed import Packages—Displays the total number of resources that failed during import. To import a failed resource, click the link and start the import activity again. NOTE: • After the import activity of the resources is complete, the VIEW STATUS option is displayed during next login or after you click Back to Task. • The date of the last import activity is displayed in the WCM resources task section.
Create groups and profiles using WDM default group types Use the Build option to create groups and profiles using WDM default group types. You can create a group hierarchy in Wyse Management Suite provided that grouping is not assigned as a view in WDM. 1. On the View and WES Profiles/ThreadX_5X Configurations screen, click the Build radio button. A drop-down list with all the default group types in WDM is displayed. The order determines the group hierarchy structure.
NOTE: • After the import activity of the view and Windows-based profiles is complete, the VIEW STATUS and Rollback options are displayed. These option are displayed during next login or after you click Back to Task. For more information about rollback capability—see Rollback capability. • The date of the last import activity is displayed in the View and WES Profile/ThreadX_5X Configurations task section.
• • Create groups and configurations using one of the existing WDM views. See Create groups and configurations using existing WDM views. Create groups and configurations using WDM default group types, or create a group hierarchy that is not assigned as a view in WDM. See Create groups and configurations using default WDM group types. 4. Click Import. The import status is displayed as In Progress.
NOTE: You cannot assign more than one WDM Configuration Package to a group. If you do not have ThreadX 5.x configurations assigned to views, and you use an individual JSON Configuration Package in WDM, then assign the Configuration Packages to groups. 2. From the drop-down list, select a group type. If you want to create a group hierarchy, click the plus sign (+) next to the drop-down list, and start adding the group types.
To perform a rollback: 1. Go to the WDM Import Task screen. 2. Click Rollback in the View and WES Profiles/ThreadX_5X Configurations section. If you have any device that is registered to Wyse Management Suite, you are prompted to reconfirm whether you want to continue the rollback process. 3. Click Rollback. The time that is taken to complete the rollback process depends on the size of the data inventory that is imported to the Wyse Management Suite.
5 Switching devices from Wyse Device Manager to Wyse Management Suite After you import devices from WDM to Wyse Management Suite, the device registration status in Wyse Management Suite is displayed as Pre-registered. Deploy an RSP package to switch the Windows Embedded Standard, Windows 10 IoT Enterprise, ThinLinux, and SUSE Linux devices from WDM to Wyse Management Suite.
The Package Script screen is displayed. 4. Click Edit, and replace the server URL with the Wyse Management Suite server URL in the RSP package script. For example: "/bin/sh/tmp/deviceSwitchOver.sh https://wmserver.wms.com:443". 5. Click Save. 6. Deploy the RSP package to the ThinLinux devices by using WDM. For information about installing an RSP package using WDM, see the Wyse Device Manager version 5.7.2 Administrator's Guide at www.dell.com/manuals.
Table 5. INI parameters ThinOS v8.5-based devices ThinOS v8.4-based devices AutoLoad=1 AutoLoad=1 SignOn=1 SignOn=1 WDAService=yes\ WDAService=yes\ Priority=WMS Priority=CCM WMSEnable=yes\ CCMEnable=yes\ Server=\ CCMServer=\ CAValidation=no\ GroupPrefix=\ Override=yes GroupKey=\ MQTTServer=\ CAValidation=no\ Override=yes NOTE: For ThinOS Lite devices, you must create a xen.ini file with the same INI parameters that are listed in the table.
6 Postmigration Verify the data that is imported from Wyse Device Manager (WDM) to Wyse Management Suite. You can use the event logs to compare the total file count and capacity. To verify that the data is successfully migrated: 1. Log in to the Wyse Management Suite. 2. On the Dashboard page, verify the device count for total devices that are imported from WDM. 3. On the Dashboard page, verify the summary of events for WDM import activity. 4.
7 Uninstall Wyse Management Suite Import Tool To uninstall Wyse Management Suite Import Tool: 1. Go to Control Panel, and click Programs > Programs and Features. 2. Select Wyse Management Suite Import Tool. 3. Click Uninstall. The Wyse Management Suite Import Tool Uninstaller screen is displayed. By default, the Remove radio button is selected. 4. Click Next. 5. Click Finish after the uninstallation is complete.
8 Troubleshooting This section describes some basic troubleshooting that you can implement when you experience any problem. NOTE: If the details of the previous import session are not required, delete the %programdata%WMS-Import \WMSMigrationInfo.json file.
Switching SUSE Linux device from WDM to Wyse Management Suite is unsuccessful Problem—Switching the SUSE Linux Enterprise device from WDM to Wyse Management Suite is unsuccessful. Solution—Ensure that the server URL, MQTT URL, and group token that is entered in the RSP package script are valid. Switch the devices to Wyse Management Suite using the RSP package.
