The tool is supported for upgrades from XenMobile MDM edition deployments. Using the tool to upgrade from XenMobile App Edition or XenMobile Enterprise Edition is not supported. Likewise, you cannot use the tool to upgrade from XenMobile 8.6 or 8.7 to XenMobile 10. In addition, if the Multi-Tenant Console (MTC) is enabled on XenMobile 9.0, the MTC cannot be migrated to XenMobile 10.
The Upgrade Tool is built within the XenMobile 10 virtual machine. You enable the one-time only wizard through the command-line console during the initial installation of XenMobile 10.
What the Upgrade Tool does – The XenMobile 10 MDM Upgrade Tool migrates configuration and user data from the XenMobile 9.0 server to a new instance of XenMobile 10 with the same fully qualified domain name (FQDN).
You can choose to test drive the upgrade or to do a full production upgrade. When you choose Test Drive in the tool, only configuration data is migrated to XenMobile 10; no device or user data is migrated. This option lets you compare XenMobile 9.0 and XenMobile 10 without affecting your production environment.
When you choose Production Upgrade in the tool, all configuration, device, and user data is migrated. When you log on to the XenMobile 10 console after the upgrade, you see all the user and device data that was migrated from XenMobile 9.This is not an in-place migration; all data is copied during migration, not moved, to XenMobile 10. Everything in XenMobile 9.0 remains intact until you move the XenMobile 10 server into production. When users connect to XenMobile 10 in production, if for some reason you want to revert to XenMobile 9.0, those users must re-enroll in XenMobile 9.0.
After a successful production upgrade, to move XenMobile 10 to live production, you must do the following:
- Update the DNS entry to map the XenMobile 9.0 FQDN to the new XenMobile 10 server IP.
- If NetScaler is load balancing XenMobile Device Manager servers, you need to switch the XenMobile 9.0 service to the XenMobile 10 service.
What the Upgrade Tool Does Not Do – The following information is not migrated to XenMobile 10 when you use the Upgrade Tool:
- Licensing information.
- Reports data.
- Automated actions.
- Server group policies and associated deployments.
- MSP group.
- Policies and packages related to Windows CE and Windows 8.0.
- Deployment packages not in use; for example, when no users or groups are assigned to a deployment package.
- Any other configuration or user data as described in the migration.log file.
- CXM Web (replaced by Citrix WorxWeb).
- DLP policies (replaced by Citrix Sharefile).
- Custom Active Directory attributes.
- If you have configured multiple branding policies, the branding policy is not migrated. XenMobile 10 supports one branding policy; you have to leave one branding policy in XenMobile 9.0 to successfully migrate to XenMobile 10.
- Any settings in the auth.jsp file in XenMobile 9.0 that are used to restrict access to the console. Console access restrictions in XenMobile 10 are firewall settings that you can configure in the command line interface.
Several things has changed with XenMobile 10! XenMobile 10 does not support Active Directory users who are assigned to local groups, and the local groups hierarchy is flattened.