Dell Wyse Management Suite Version 1.
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. © 2019 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.............................................................................................................................................. 26 7 Uninstall Wyse Management Suite Import Tool............................................................................................ 27 8 Troubleshooting........................................................................................................................................... 28 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. Dell recommends that you migrate from WDM version 5.7.2 to Wyse Management Suite version 1.4.
8 • View import status of Teradici-based WCM resources—see View import status of Teradici-based WCM resources. • View import status of View and Windows-based profiles—see View import status of View and Windows-based profiles. • View import status of View and Teradici-based configurations—see View import status of View and Teradici-based configurations. Switch devices from WDM based on your thin client infrastructure—see Switching devices from Wyse Device Manager to Wyse Management Suite.
2 Prerequisites for migration Ensure that you meet the following migration requirements from Wyse Device Manager (WDM) and Wyse Management Suite: • 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.
Prerequisites for Teradici-based device migration Before you migrate ThreadX.5.x devices from WDM to Wyse Management Suite using the Import Tool, ensure that you complete the following task: 1 Stop the WDM server—Jetty Apache service. 2 Stop all running EM SDK services. 3 Upgrade the EM SDK package to the latest version by using the Wyse Management Suite 1.4 installer. 4 Proceed with the Wyse Management Suite installation without selecting the EM SDK component.
Data available on thin client Wyse Device Manager (WDM) Wyse Management Suite Additional information Standard, Windows 10 IoT Enterprise, and ThinLinux. Configuration packages on Windows Embedded Standard 7, Windows Embedded Standard 7P, Windows Embedded 8 Standard, and Windows 10 IoT Enterprise. Packages present in the Device Configuration category. Configuration packages are moved to Wyse Management Suite as profiles wherein you must assign configuration packages to groups.
Device operating system Supported in Wyse Device Manager (WDM) • Windows CE • • Yes Windows Embedded Standard 7—32-bit Windows Embedded Standard 7 Professional— 64-bit Windows Embedded 8 Standard—64-bit Windows 10 IoT Enterprise—64-bit • • Supported in Wyse Management Suite Migrated from WDM to Wyse Management Suite Yes Yes Windows Embedded 8 Standard (32-bit) Yes No No SUSE Linux Enterprise 11 SP1 Yes No No SUSE Linux Enterprise 11 SP2 Yes No Yes.
3 Using Wyse Management Suite Import Tool Wyse Management Suite Import Tool allows you to import the data from WDM to Wyse Management Suite.
• Only Windows-based wireless profiles in .xml format from WCM can be imported. • Scheduled jobs from Wyse Device Manager (WDM) cannot be imported. • When verifying the licenses, the import tool does not filter the unsupported devices in the Wyse Management Suite. The tool checks the license based on total license subscriptions in Wyse Management Suite and devices imported from WDM. • Only the first package is imported when you import Teradici 5.
7 Click Connect. The Wyse Device Manager Import task screen is displayed. NOTE: If you have entered the wrong credentials, or if you do not meet the license requirements, an error message is displayed. NOTE: • If the import tool is unable to connect to the WDM server, database, or repository, an error message is displayed. • If the import tool is unable to connect to the Wyse Management Suite server, an error message is displayed.
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.
The import status of a package is displayed as In-Progress. The time that is taken to import the RSP packages varies from minutes to hours depending on the size of the RSP package. The import status of a package is changed to Imported after the package is imported to the Wyse Management Suite repository. If the package import is unsuccessful, the import status of a package is changed to Failed. For more information about the import status screen—see Viewing import status of RSP packages.
The import status of a resource is displayed as In-Progress. The import status of a resource is changed to Imported after the resource is imported to the Wyse Management Suite repository. If the resource import is unsuccessful, the import status of a resource is changed to Failed. For more information about the import status screen—see View import status of Windows-based WCM resources.
You can only select a view with nine or less levels of the group hierarchy. If there are group levels with empty values, then the group levels are renamed to NotSet. However, if the group levels are missing in WDM, then they are assigned to the available parent. NOTE: If there are resources for wallpaper and wireless in profile/configuration, the resource filenames are prefixed with the configuration package name in WDM. For example, packagename_resourcename.
2 From the Profile drop-down list, select a profile. 3 From the Group drop-down list, select a group. To add more profiles and groups, click the plus sign (+) next to the drop-down list, and start adding profiles and groups. When you are creating the group hierarchy, select only up to nine group levels. This is because the maximum number of groups does not exceed the supported levels of Wyse Management Suite.
View import status of Teradici-based WCM resources After you import Teradici-based Wyse Configuration Manager (WCM) resources using the WDM Import task screen, the task status screen is displayed automatically. The status screen lists the following attributes: • Imported Packages—Displays the total number of resources that are successfully imported. • Pending Packages—Displays the total number of resources that are pending to be imported.
3 Select any of the following options: • Groups—By default, the Groups check box is selected. • Devices—To import devices that are already associated to the selected view in WDM, select the Devices check box, and click Next. • ThreadX_5X Configurations—To import a ThreadX 5.x device configuration that is already assigned to the selected view in WDM, select the ThreadX_5X Configurations check box, and click Next.
To add more profiles and groups, click the plus sign (+) next to the drop-down list, and start adding configurations and groups. When you are creating the group hierarchy, select only up to nine group levels. This is because the maximum number of groups does not exceed the supported levels of Wyse Management Suite. You can select both Devices and ThreadX_5X Configurations check boxes if you want to assign both devices and Teradici-based configurations to the created view.
2 Log in to WDM and go to Devices page. 3 Select all devices and click Refresh.
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.
Deploy RSP package to ThinLinux devices To deploy an RSP package to the ThinLinux-based devices: 1 Download the RSP package from Dell Digital Locker. 2 Register the downloaded RSP package to Wyse Device Manager (WDM) version 5.7.2. 3 Navigate to Other Packages, select the registered RSP package, and click Package Script. 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.
NOTE: The system reboots three times during the package deployment process. Deploy INI parameter to ThinOS devices Ensure that your devices are running ThinOS version 8.4 or later. To deploy an INI parameter to the ThinOS-based devices: 1 Create a wnos.ini file with the following INI parameters: 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
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.
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.
Import process stops when importing view and profiles Problem—While importing view and Windows-based profiles, if you close and reopen the import tool, then the import process stops. The import status screen displays a zero value. Solution—Perform the Rollback operation on the View and WES Profiles task screen, and start the import activity again—see Importing view and Windows-based profiles.
