Package name: xms_10.8.0.10702.bin
For: XenMobile Server 10.8.0
Deployment type: On-premises only
Replaces: xms_10.8.0.10602.bin, xms_10.8.0.10506.bin, xms_10.8.0.10402.bin, xms_10.8.0.10309.bin, xms_10.8.0.10212.bin, xms_10.8.0.10104.bin
Date: June, 2019
Languages supported: English (US)
Readme version: 1.00
Readme Revision History
|1.00||June, 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.8 on the Citrix Product Documentation site.
For information about XenMobile Server 10.8.0 Rolling Patch 6 release, see XenMobile Server 10.8.0 Rolling Patch 6.
Known Issue(s) in this Release
The following error message displays when you attempt to configure a Public App by using the new app URL from the Apple Store: “Could not find the app you entered. Check the URL and try again.”
Refer to the workaround in https://support.citrix.com/article/CTX256704.
New Fixes in This Update
Apple Volume Purchase Program (VPP) apps don’t import into XenMobile Server. This issue occurred after Apple changed the URL for apps from itunes.apple.com to apps.apple.com.
The Secure Hub Apple Push Notification Service (APNs) certificate for XenMobile Server 10.10 will expire on August 2, 2019. As a result, the Agent Notification fails and the application push might be delayed on iOS devices.
With this update, the Secure Hub APNs certificate will be renewed and will expire on July 12, 2020.
Fixes From Replaced Releases
If you deployed a Store device policy for iOS/Android/Windows 10 Desktop and Tablet devices before upgrading to 10.8 Rolling Patch 6: 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 an old URL or this device is not registered” appears. To resolve this issue, you must recreate and deploy your Store device policy.
Added support in XenMobile Server CLI to validate public key infrastructure (PKI) and SQL passwords before you begin a migration.
You are unable to deploy VPP apps and media to new VPP users on devices running iOS.
Configure valid VPP token on XenMobile Server and purchase new VPP books from Apple VPP portal. The newly added media books are not synced and do not appear on the console.
With no https proxy configured, admins cannot send SMS messages through the Nexmo SMS gateway.
You can’t use the public REST API to deploy delivery groups.
Third-party B2B VPP Secure apps don’t show as installed in Secure Hub.
After updating from XenMobile 10.6 to 10.8 RP1, the web console sometimes becomes unresponsive after an admin logs in. An error message displays “TypeError: this.featureFlags is undefined”.
For Android devices, when the server property “device.properties.userDefined1” is not set, adding a value to the User Defined#1 device details property does not display properly.
Enterprise apps don’t silently upgrade on supervised devices running iOS 11.4 or later.
After adding a custom property with a special character, admins cannot access the Devices page on the XenMobile console.
Admins can’t change the DEP setting “Require credentials for device enrollment” in XenMobile 10.7 if the DEP account is an edu organization. The option is always enabled and can’t be turned off.
For Android devices, the Device administrator disabled property is missing when you navigate to Device management > Device > Properties .
When StoreFront is integrated with XenMobile Server, non-primary domains cannot enroll.
When you enroll a device in the Profile Owner mode, the Android Enterprise apps are not available.
While editing an app in the app store that contains a special character in the description, the 500 Internal Server Error appears.
To prepare for device upgrades to iOS 12: The Citrix VPN connection type in the VPN device policy for iOS doesn’t support iOS 12. Delete your VPN device policy and create a new VPN device policy with the Citrix SSO connection type.
The Citrix VPN connection continues to operate in previously deployed devices after you delete the VPN device policy. Your new VPN device policy configuration takes effect in XenMobile Server 10.8 RP5, during user enrollment.
The Secure Hub Apple Push Notification Service (APNs) certificate for XenMobile Server 10.8 will expire on September 8, 2018. As a result, the Agent Notification fails and the application push might be delayed on iOS devices.
With this update, the Secure Hub APNs certificate will be renewed and will expire on August 2, 2019.
On the Analyze > Dashboard page, the Installed Apps graph and report show incorrect BluPrint app version numbers.
As a workaround provided by a third-party component, it is a prerequisite to have a license file with the sort keyword in the file.
After upgrading to XenMobile Server 10.7 or later and enrolling a device, the license count shown in the XenMobile console is much greater than the actual number of enrolled devices.
When trying to configure the Salesforce SAML app with provisioning enabled from the XenMobile Server 10.8.0 console, the XenMobile console displays the “Invalid Application details, please try again” error message.
Create a credentials provider ( Settings > Credential Providers), with the default notification template selected on the Renewal tab. When you return to Settings > Credential Providers and go directly to the Renewal tab, the Notification template shows None instead of the template previously specified. As a workaround, when you return to Settings > Credential Providers, click Next to navigate to the Renewal tab.
When you change the Store name in XenMobile Server, a warning message asking the iOS users to log off and log on to the Secure Hub might not appear. As a result, when the user accesses the Secure Hub Store, the MDM-pushed apps are uninstalled from the device.
After you restart XenMobile Server, your settings in the Log Settings page revert to the defaults.
Syslog messages now include the XenMobile Server/Node IP address.
When you attempt to add a URL that begins with “http” or “https” but does not contain the “.com” or file name extension to Web Content Filter policy, the following error message appears: “Please enter a valid FQDN or an http:// or https:// URL.”
In XenMobile Server, certain iOS apps’ version numbers are reported incorrectly.
The German expiration notification message for a VPP account is incorrect.
When users who are enrolled in XenMobile Server through “email enrolment” attempt to change the User Principal Name (UPN) in Active Directory, the device goes to an unmanaged state causing an App Wipe/Lockout.
However, when the user attempts to re-enroll with the new UPN, the users are directed back to the First Time Use (FTU) screen.
To enable the fix, set the custom server property “refresh.user.using.objectguid” to “true”.
The devices running on Microsoft Windows operating system such as Windows phone and desktop/tablet might fail to search the public store apps and the following error message appears: “Application search Failed”.
On devices running iOS 11.3, when multiple apps are installed and marked as required apps on non-supervised devices, you may receive repeated “Update Available” notifications.
The XenMobile console doesn’t accept valid Google play credentials for Android. The following error message appears: “The Google Play logon request used a user name or password that is not recognized.”
When you change users to a different Active Directory security group: For enrolled iOS devices, XenMobile Service does not detect the change, update the delivery group membership, or push new policies to the devices.
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.
- Log on to your account on the Citrix website and download the XenMobile Server update (.bin) file to an appropriate location.
- 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.
- Under Release Management, click Update. The Update dialog box appears.
- Click Browse to upload the update (.bin) file you have downloaded from support.citrix.com.
- 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.