XenMobile Server 10.9.0 Rolling Patch 3

Package name: xms_10.9.0.10303.bin

For: XenMobile Server 10.9.0

Deployment type: On-premises only

Replaces: xms_10.9.0.10204.bin, xms_10.9.0.10105.bin

Date: April, 2019

Languages supported: English (US)

Readme version: 1.00

Readme Revision History

Version Date Change Description
1.00 April, 2019 Initial release

Important Notes about This Update

As a best practice, Citrix recommends that you install this and other updates only if you are affected by the specific issues they resolve.

Where to Find Documentation

This document describes the issue(s) resolved by this release and includes installation instructions. For additional product information, see XenMobile Server 10.9 on the Citrix Product Documentation site.

What’s new

  • Public REST API change. The XenMobile Server Public API for REST Services now includes an API to edit platform details inside the container for MDX apps. For more information about updating platform details, see “Section 3.15.2.4 Update platform details inside the container for MDX apps” in the PDF, [Public API for REST Services](/en-us/xenmobile/server/downloads/public-rest-api-xenmobile-10-9.pdf).

    [From xms_10.9.0.10303.bin][CXM-62899]

  • Upgrade from GCM to FCM. As of April 10, 2018, Google deprecated Google Cloud Messaging (GCM). Google will remove the GCM server and client APIs as soon as May 29, 2019.

    Important requirements:

    • To avoid disruptions, upgrade to upgrade to XenMobile Server 10.9 Rolling Patch 3 before May 29.
    • Upgrade to Secure Hub 19.3.5 or later.

    For more information about configuring FCM, see Upgrade from GCM to FCM

    [From xms_10.9.0.10303.bin][CXM-64728]

  • Citrix recommends using Firebase Cloud Messaging (FCM) instead of this connection scheduling policy. FCM allows for a near real-time communication to devices. To configure FCM, click the gear icon at the top of this page and the click on Firebase Cloud Messaging.

  • [From xms_10.9.0.10303.bin][CXM-64729]

For information about XenMobile Server 10.9.0 Rolling Patch 2 release, see XenMobile Server 10.9.0 Rolling Patch 2.

For information about XenMobile Server 10.9.0 Rolling Patch 1 release, see XenMobile Server 10.9.0 Rolling Patch 1.

Known Issue(s) in this Release

There are no known issues in this release.

New Fixes in This Update

  1. When you approve a new Android Enterprise app and assign it to a delivery group in the XenMobile Server console, the app does not appear in the Play Store app on the device.

    [From xms_10.9.0.10303.bin][CXM-62612]

  2. You are unable to enroll Android devices and the following error appears:

    “Security policy does not allow you to connect”.

    [From xms_10.9.0.10303.bin][CXM-63412]

  3. The default DEP components are not auto-populated in the XenMobile Server console when Require credentials for device enrollment setting is set to ON.

    [From xms_10.9.0.10303.bin][CXM-64452]

  4. When you edit Category on devices running Android Enterprise, the category does not appear in Google Play Store. This issue occurs when you navigate to Configure > Apps, select an app that you have added and then click Edit > App Category.

    [From xms_10.9.0.10303.bin][CXM-64695]

  5. In XenMobile Server console, the license count shown is not in sync with the number of enrolled devices.

    To correct the license count shown:

    • Set the server property license.clean.task.activate to true.
    • Then, a nightly clean task can be activated.

    [From xms_10.9.0.10303.bin][CXM-64730]

  6. Performing the full or partial wipe security action on devices running Android 7.0 or later does not remove the device from the XenMobile Server console. This device does not undergo a factory reset and remains listed in the console.

    [From xms_10.9.0.10303.bin][CXM-64731]

  7. If you deployed a Store device policy for iOS/Android/Windows 10 Desktop and Tablet devices before upgrading to 10.9 Rolling Patch 3: When a user clicks the iOS/Android/Windows store link in the Start menu, the message “500 Internal Server Error” or “HTTP Status 401 – Either you have reached a old URL or this device is not registered” appears. To resolve this issue, you must recreate and deploy your Store device policy.

    [From xms_10.9.0.10303.bin][CXM-64834]

  8. When you upload a Google Play app in the XenMobile Server console without adding an app icon image, and try to edit and upload a .WebP image later, the image does not appear in the apps list.

    [From xms_10.9.0.10303.bin][CXM-64849]

  9. When you enroll a device in the Profile Owner mode, the Android Enterprise apps are not available.

    [From xms_10.9.0.10303.bin][CXM-64850]

  10. You are unable to deploy VPP apps and media to new VPP users on devices running iOS.

    [From xms_10.9.0.10303.bin][CXM-65038]

Fixes From Replaced Releases

  1. When you have set a non-default value to pki.xml file and then import it, the pki.xml file resets to the default value.

    [From xms_10.9.0.10204.bin][CXM-38390]

  2. When you create a Web&SaaS app through the XenMobile server console and have modified the User Account option, and try to edit the User Account option, the default value appears.

    [From xms_10.9.0.10105.bin][CXM-53722]

  3. For Android devices, when a certificate renewal does not succeed or is cancelled, checking the Delivery Group logs shows that the enrollment certificate renewal completed successfully.

    [From xms_10.9.0.10105.bin][CXM-55352]

  4. For Android devices, the Device administrator disabled property is missing when you navigate to Device management > Device > Properties.

    [From xms_10.9.0.10105.bin][CXM-56098]

  5. When you enroll a device in the Profile Owner mode, the Android Enterprise apps are not available.

    [From xms_10.9.0.10105.bin][CXM-56629]

  6. While editing an app in the app store that contains a special character in the description, the 500 Internal Server Error appears.

    [From xms_10.9.0.10105.bin][CXM-56638]

  7. When StoreFront is integrated with XenMobile Server, non-primary domains cannot enroll.

    [From xms_10.9.0.10105.bin][CXM-56640]

  8. MDX-wrapped Android apps might download slowly from the Citrix Secure Hub app store.

    [From xms_10.9.0.10105.bin][CXM-57697]

  9. When you upload a new version of MDX file through the XenMobile Server console to replace an older MDX version using a REST API call to update platform details, the new MDX version does not appear in the console.

    [From xms_10.9.0.10105.bin][CXM-57787]

  10. The ability to configure the server property max.renew_device_cert_requests.allowed is removed. By default, the number of devices on which you can request certificate renewal simultaneously is 100.

    [From xms_10.9.0.10105.bin][CXM-57830]

  11. When you create an iOS public store app and assign it to a Delivery Group and enroll the iOS device, the app fails to install.

    [From xms_10.9.0.10105.bin][CXM-58583]

  12. The following error is displayed while adding a registry key to a Windows Embedded Compact policy if the length of the registry value is more than 2048 characters:

    “Console error: could not execute statement; SQL [n/a]; nested exception is org.hibernate.exception.DataException: could not execute statement.”

    [From xms_10.9.0.10105.bin][CXM-58834]

  13. You are unable to upload Google Play services APK versions later than 11.5.09 in the XenMobile Server console.

    [From xms_10.9.0.10105.bin][CXM-58952]

  14. When you upload Google Play services APK versions later than 11.5.09 in the XenMobile Server console, multiple “500 Internal Server Error” messages appear. The error message persists even after closing the error window.

    [From xms_10.9.0.10204.bin][CXM-59022]

  15. When you upgrade from XenMobile Server version 10.9 to 10.9 RP1, a fatal error message appears in the debug log file.

    [From xms_10.9.0.10204.bin] [CXM-59040]

  16. In the Shared devices mode for Android, you receive a prompt to install required apps even when all the required apps are installed on the device.

    [From xms_10.9.0.10204.bin] [CXM-59182]

  17. You are unable to import and install B2B apps delivered through Volume Purchase Program (VPP) after you migrate DEP accounts to Apple Business Manager.

    [From xms_10.9.0.10105.bin][CXM-59300]

  18. For devices enrolled with the XenMobile Server set to the MAM mode, the license count appears incorrectly and keeps increasing, resulting in a license overconsumption notification.

    [From xms_10.9.0.10204.bin] [CXM-59539]

  19. When you deploy the following policies on devices running iOS 12 or later, the Create Event calendar option does not appear:

    • Documents from managed apps in unmanaged apps [OFF]
    • Documents from unmanaged apps in managed apps [ON]

    [From xms_10.9.0.10204.bin][CXM-59603]

    Note: This is an Apple limitation and is tracked in [CXM-60708].

  20. When you enroll devices and modify the Delivery Groups, the changes do not reflect after a server refresh cycle. This occurs when public IP addresses are configured as XenMobile node IP addresses in a cluster.

    [From xms_10.9.0.10204.bin][CXM-60290]

  21. You are unable to push Provisioning profiles on to XenMobile Server version 10.8, and the device states appear as “Pending” along with the java.lang.NullPointerException error.

    [From xms_10.9.0.10204.bin][CXM-60370]

Installing This Update

Note: If your system is configured in cluster mode, follow the steps below to update each node, one after the other.

Important: Before installing this update, take a snapshot of the current settings and create a backup of the database.

  1. Log on to your account on the Citrix website and download the XenMobile Server update (.bin) file to an appropriate location.
  2. In the XenMobile Server Console of a node click Settings > Release Management. The Release Management page appears, which displays the currently installed software version, as well as a list of any updates, patches, and upgrades you have already uploaded.
  3. Under Release Management, click Update. The Update dialog box appears.
  4. Click Browse to upload the update (.bin) file you have downloaded from support.citrix.com.
  5. Click Update and then if prompted, restart the XenMobile Server node using command line.

To verify the patch deployment

After installing this patch, log on to the XenMobile Server Console as an administrator, then navigate to Settings > Release Management > Updates. Information about the most recent successful patch installation appears in this section.

Related:

  • No Related Posts

Leave a Reply