XenMobile Server 10.7 Rolling Patch 2

Patches Xenmobile

Citrix has released XenMobile Server 10.7 Rolling Patch 2

More information here after:


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.7 on the Citrix Product Documentation site.


Known Issue(s) in this Release
  1. When you switch to Microsoft Java Database Connectivity (JDBC) driver with Windows authentication, the XenMobile Server database connectivity check fails.
  2. If XenMobile Server is installed in Federal Information Processing Standards (FIPS) mode, you can switch to Microsoft Java Database Connectivity (JDBC) driver with SQL Authentication. Switching to JDBC driver with Windows Authentication fails. 

    New Fixes in This Update
  1. You can use the Restrictions Policy to disable the camera on Android devices. 
  2. XenMobile Server now supports the Microsoft Java Database Connectivity (JDBC) driver for SQL connectivity. The jTDS driver remains the default driver when you install XenMobile Server on-premises or upgrade from a XenMobile Server that’s configured to use the jTDS driver.To switch from the jTDS driver to the Microsoft JDBC driver, perform the following steps:
    1. In the XenMobile CLI main menu, type 2 to select the System Menu.
    2. Type 12 to select Advanced Settings.
    3. Type 7 to select Switch JDBC driver, and then type m for Microsoft JDBC driver or j for jTDS.
    4. When prompted, type y to choose SQL authentication, or n to choose Windows authentication, and then type the SQL Server username and password.
    5. Repeat the steps for each XenMobile Server node.
    6. Restart each XenMobile Server node.

     

  3. When you configure Mobile Service Provider (MSP) on XenMobile Server over a secure connection such as https:// /services/zdmservice, the connection fails and the following error appears:”An error occurred when verifying security for the message.”

     

  4. In XenMobile Server, the following error message that appears consistently for various XenMobile Server authentication failures:”Authentication failed. Please try again.”

     

  5. When you upgrade from XenMobile Server 10.6 to XenMobile Server 10.7, devices registered in MAM-only mode might fail to download MDX apps. 
  6. Network Access Control (NAC) actions written to console log files result in large files. 
  7. The .EWDEPLOY_HISTO database table is not cleaned up periodically, resulting in a large table size. 
  8. iOS users can’t update Citrix Receiver to version 7.2.3. When you click Check for Update, the message “The app is up to date with the latest version” appears even when you have an older version. 
  9. When you left-click Secure Mail or Citrix Secure Web for Android in the Configure > Apps list and then click Show more, the following error might appear: “A configuration error occurred. Please try again.” In the App rating section, the Android tab is blank. 
  10. When you upload an SSL listener certificate in XenMobile Server, the error “Could not import the certificate” appears. 
  11. When you enrol iOS devices on XenMobile Server, enrolment fails intermittently, and the error “Could Not Connect” appears. 
  12. Uploading some APK files to the XenMobile console might fail with a “500 Internal Server Error.” 
  13. On Android devices, managed apps do not appear during XenMobile Server API calls. 
  14. The report that you can export from Manage > Devices has two columns labeled “ASM DEP device Type.” 
  15. Security actions don’t perform on a node that is already initialized for a given push if the notification is sent from another node.

Fixes From Replaced Releases
  1. On iOS 11 devices, issuing an MDM security action command once causes this command to be issued to the device repeatedly. 
  2. After upgrading to XenMobile Server version 10.5 or later, device enrollment fails and the “Could not sign CSR” error message appears in the debug log of setups using Generic PKI (GPKI). This issue occurs because the GPKI protocol fails to retrieve a signed user certificate.

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.

The Rolling Patch 2 for XenMobile 10.7 can be downloaded here