Before you upgrade to XenMobile 10.9:
- Update your Citrix License Server to 11.15 or later before updating to the latest version of XenMobile Server 10.9. The latest version of XenMobile requires Citrix License Server 11.15 (minimum version). Note: Be aware that the Subscription Advantage (SA) date in XenMobile 10.9 is September 14, 2018. The Subscription Advantage (SA) date on your Citrix license must be later than this date. You can view your SA date next to the license in the License Server. If you connect the latest version of XenMobile to an older license server environment, the connectivity check fails and you can’t configure the license server. To renew the SA date on your license, download the latest license file from the Citrix Portal and upload the file to the Licensing Server. For more information, see http://support.citrix.com/article/CTX209580.
- For a clustered environment: iOS policy and app deployments to devices running iOS 11 and later have the following requirement. If NetScaler Gateway is configured for SSL persistence, you must open port 80 on all XenMobile Server nodes.
- If the virtual machine running the XenMobile Server to be upgraded has less than 4 GB of RAM, increase the RAM to at least 4 GB. Keep in mind that the recommended minimum RAM is 8 GB for production environments.
- Recommendation: Before you install a XenMobile update, use the functionality in your VM to take a snapshot of your system. Also, back up your system configuration database. If you experience issues during an upgrade, complete backups enable you to recover.
After you upgrade to XenMobile 10.9:
If functionality involving outgoing connections stop working, and you haven’t changed your connections configuration, check the XenMobile Server log for errors such as the following: “Unable to connect to the VPP Server: Host name ‘192.0.2.0’ does not match the certificate subject provided by the peer”
The certificate validation error indicates that you need to disable hostname verification on XenMobile Server. By default, hostname verification is enabled on outgoing connections except for the Microsoft PKI server. If hostname verification breaks your deployment, change the server property disable.hostname.verification to true. The default value of this property is false.
Citrix publishes new versions or important updates of XenMobile to Citrix.com. At the same time, a notice is sent to the contact on record for each customer.
You can directly upgrade to XenMobile 10.9 from XenMobile 10.8.x or 10.7.x. To perform the upgrade, you use the latest 10.9 binary available on the Citrix Download page. In the XenMobile console, click the gear icon in the upper-right corner of the console and then click Release Management.
To upgrade from XenMobile 10.6 to 10.9, first upgrade from XenMobile 10.6 to 10.7 or 10.8, then upgrade to 10.9.
To upgrade from older releases of XenMobile, see the Upgrade article in the XenMobile Server 10.8 PDF.
This article describes how to use the Release Management page, upgrade clustered XenMobile deployments, and upgrade from MDM to Enterprise Edition.
To upgrade using the Release Management page
Use the Release Management page to upgrade from XenMobile 10.7.x or 10.6.x to the latest version of XenMobile Server.
- Review the System Requirements.
If you have a clustered deployment, see the instructions at the end of this article.
Log on to your account on the Citrix website and go to the Download page. Download the XenMobile Upgrade (.bin) file to an appropriate location.
In the XenMobile console, click the gear icon in the upper-right corner of the console. The Settings page appears.
Click Release Management. The Release Management page appears.
Under Updates, click Update. The Update dialog box appears.
Select the XenMobile upgrade file you downloaded from Citrix.com by clicking Browse and navigating to the file location.
Click Update and then if prompted, restart XenMobile.
If for some reason the update cannot be completed successfully, an error message appears indicating the problem. The system is reverted to its state previous to the update attempt.
After an upgrade, XenMobile requires a restart. Use the XenMobile CLI to restart XenMobile Server. It’s important that you clear your browser cache after the system restarts.
To upgrade clustered XenMobile deployments
Before you install a XenMobile update, use the functionality in your virtual machine (VM) to take a snapshot of your system. Also, back up your system configuration database. If you experience issues during an upgrade, complete backups enable you to recover.
If your system is configured in cluster mode, follow these steps to update each node from a XenMobile 10 release:
Upload the .bin file on all nodes from Settings > Release Management.
Shut down all the nodes from the System Menu in the CLI.
Bring up one node, from the System Menu in the CLI, and check that the service is running.
Bring up other nodes one after the other.
If XenMobile can’t complete the update successfully, an error message appears indicating the problem. XenMobile then reverts the system to its state previous to the update attempt.
Upgrade from XenMobile 10.8 MDM Edition to Enterprise Edition
You can upgrade XenMobile 10.8 MDM Edition to XenMobile 10.8 Enterprise Edition for iOS and Android devices.
- The correct Enterprise license.
- NetScaler Gateway is configured.
- Go to Settings > Licensing and verify that the correct Enterprise Edition license type is uploaded.
- Go to Settings > Server Properties and change the Server Mode property from MDM to ENT.
- Go to Settings > NetScaler Gateway and configure the NetScaler Gateway details. Set the authentication mode to the same as the MDM Edition, that is, domain (Active Directory) authentication. XenMobile doesn’t support changing the authentication mode after user enrollment.
- Optional: Go to Settings > Client Properties and enable Citrix PIN authentication.
After you complete those steps, users must perform the following steps to switch a device into Enterprise mode.
- Close Secure Hub: Tap the device home button twice (quickly) and slide up the Secure Hub app.
- Open Secure Hub.
- Open Secure Hub.
- Go to Preferences > Device Information.
- Click Refresh Policy.
If you enabled Citrix PIN authentication, Secure Hub prompts users to create a PIN. After a user creates a PIN, XenMobile configures the device in Enterprise mode. In the XenMobile console, the Manage > Devices page then shows both MDM and MAM as active for the device.