Product Documentation

What’s new

A goal of Citrix is to deliver new features and product updates to XenMobile Service customers when they are available. New releases provide more value, so there’s no reason to delay updates. Rolling updates to the XenMobile Service release approximately every two weeks.

To you, the customer, this process is transparent. Initial updates are applied to Citrix internal sites only, and are then applied to customer environments gradually. Delivering updates incrementally in waves helps to ensure product quality and to maximize availability.

If you are a XenMobile Service customer, you also receive XenMobile Service updates and communications directly from the XenMobile Cloud Ops Team. Those updates keep you current with new features, known issues, fixed issues, and so on.

For details about the service level goal for the XenMobile Service for cloud scale and service availability, see Service Level Goal. To monitor service interruptions and scheduled maintenance, see the Service Health Dashboard.

Note about the Citrix unified product portfolio:

If you’ve been a Citrix customer or partner for a while, you’ll notice new names in our products and in this product documentation. The new product and component names stem from the expanding Citrix portfolio and cloud strategy. For more detail about the Citrix unified portfolio, see the Citrix product guide.

Articles in this product documentation use the following names.

  • Citrix Workspace app: The Citrix Workspace app incorporates existing Citrix Receiver technology as well as the other Citrix Workspace client technologies. It has been enhanced to deliver additional capabilities to provide end users with a unified, contextual experience where they can interact with all the work apps, files, and devices they need to do their best work. For more information, see this blog post.

  • You will begin to see the name Citrix XenMobile change to Citrix Endpoint Management, and XenMobile Apps will change to mobile productivity apps. These changes will initially occur within the Citrix Cloud console, but there will be no disruption to your or your employees’ experience.

Implementing this transition in our products and their documentation is an ongoing process.

  • In-product content might still contain former names. For example, you might see instances of earlier names in console text, messages, and directory/file names.
  • It is possible that some items (such as commands and MSIs) might continue to retain their former names to prevent breaking existing customer scripts.
  • Related product documentation and other resources (such as videos and blog posts) that are linked from this product’s documentation might still contain former names.

Your patience during this transition is appreciated.

XenMobile Service 10.18.12

The latest version of XenMobile has these new features and improvements:

  • Deploy CA Certificates for Citrix Ready workspace hub devices. Using the credentials policy, you can now deploy CA certificates for Citrix Ready workspace hub devices. For more information about the policy, see Credentials Policy

  • Support for Alexa for Business. You can now configure and manage you Alexa for Business devices in the XenMobile console. See Alexa for Business.

  • Prevent users from saving or deleting history on Chrome OS devices. By default, users of Google Chrome devices can save browsing history or delete browsing and download history. Additions to the Restrictions device policy for Chrome OS let you:
    • Prevent users from saving browsing history.
    • Prevent users from deleting their browsing and download history.

    Both of those settings require G Suite Chrome configuration. For more information, see Chrome OS settings.

  • Control Google Safe Browsing behavior on Chrome OS devices. By default, Google Safe Browsing warns users when they navigate to sites that are potentially dangerous. Additions to the Restrictions device policy for Chrome OS let you:
    • Enable users to proceed from the Safe Browsing warning page.
    • Ensure that Safe Browsing is always active and prevent users from changing or overriding the “Protect you and your device from dangerous sites” setting in Chrome.

    Both of those settings require G Suite Chrome configuration. For more information, see Chrome OS settings.

  • Deploy device policies to selected Chrome OS devices. The Manage > Devices page now includes a Deploy button for Chrome OS devices. The button works only if G Suite is configured and pushes only Chrome Device Management policies and not extension policies.

Note:

When an upgrade includes new Restrictions device policy settings, you must edit and save the policy. XenMobile won’t deploy the upgraded Restrictions device policy until you save it.

Starting the second quarter of 2018, support for Symbian and Windows Mobile/CE devices is no longer available to new customers. For information about the Microsoft product lifecycle, see https://support.microsoft.com/en-us/lifecycle/search/1143.

Fixed issues in XenMobile Service 10.18.12

Some cloud instances are unable to perform NetScaler Gateway connectivity checks. [CXM-53113]

User names that contain umlauts can now authenticate on the XenMobile server without errors. [CXM-53238]

When using XenMobile MDM and Intune MAM, users can not change or edit the PIN type from the EMS console. [CXM-53805]

XenMobile Service 10.18.11

The latest version of XenMobile has these new features and improvements:

  • Specify the iOS version to use to update supervised iOS devices. The Control OS Updates policy now lets you specify which version number to use to update supervised iOS devices. You can choose the latest update or specify an OS version number. For more information, see iOS settings.

  • Search capability and more columns in VPP ID assignment table. You can search the columns in the VPP ID assignment table in the XenMobile console. The table now includes columns for the serial number of the device and the phone number of the device. Because there is a column for the serial number of the device, the serial number no longer appears in the Associate Device column.

  • Disable the camera on Android devices. By default, camera use is enabled on Android devices. To disable camera use, change the Camera setting to Off.

Fixed issues in XenMobile Service 10.18.11

XenMobile Console may operate slowly. [CXM-48059]

After a XenMobile node goes offline and a redeploy or reboot occurs: Some background jobs might not recover. [CXM-50802]

Some apps cannot be wrapped using the MDX Service. [CXM-51045]

After a user enrolls into Android for Work on a Samsung device by using a QR code, apps and policies aren’t deployed to the device. [CXM-52237]

Current known issues

Known issues in XenMobile Service 10.18.5

When a Chrome app is configured as a required app for Chrome OS devices: Users may need to log off and log back on to install the app. This third-party issue is Google bug ID #76022819. [CXM-48060]

Known issues in XenMobile Service 10.18.3

After you delete a Citrix Cloud administrator who has a device enrolled: XenMobile doesn’t update the User Role in the XenMobile console until after the administrator logs in again from Secure Hub or the Self Help Portal. [CXM-45730]

Known issues in XenMobile Service 10.7.6

For a Restrictions device policy for Samsung SAFE: The Browser, YouTube, and Google Play/Marketplace options have been removed. Use the Disable Applications option to enable or disable those features. [CXM-43043]

Known issues in XenMobile Service 10.7.4

If you configure XenMobile Service for single sign-in using Citrix Identity Platform with Azure Active Directory: When a XenMobile administrator or user gets redirected to the Azure Active Directory sign-in screen, the screen includes the message “Sign-in page for Citrix Secure Hub.” That message should be “Sign-in page for Citrix XenMobile console.” [CXM-42309]

Known issues in XenMobile Service 10.7.3

For devices running Windows 10 RS3 Version 1709 build 16299.19: XenMobile App Configuration device policies created by importing a Citrix Receiver ADMX file might fail when pushed to those devices. This third-party issue is Microsoft bug ID #14280113. [CXM-40521]

What’s new