Product Documentation


Jan 18, 2017

The following issues are fixed in XenMobile 10.4. Fixed Upgrade Tool issues appear under the heading "XenMobile Upgrade Tool 10.4" at the end of this article.

Note: As of the release of version 10.4, Worx Mobile Apps are renamed to XenMobile Apps. Most of the individual XenMobile Apps are renamed as well. For details, see About XenMobile Apps.

When you try to add a public app store app for Windows Phone, when you enter a URL from the Microsoft store, the upload fails. [CXM-13468]

For some configurations, after upgrading from XenMobile 9 to 10.3.6, devices that were previously enrolled in XenMobile 9 cannot open installed apps or download new apps from the WorxStore. Apps also disappear from Worx Home and users can't access the WorxStore. [CXM-13708]

When you create a WiFi device policy with a defined WiFi password that includes special characters, such as a less than symbol (<), greater than symbol (>) or an ampersand (&), users are prompted to enter their WiFi password. [CXM-13717]

When you try to upload an iOS enterprise app, an "icon not found" error appears when the icon size exceeds 1,000 KB. [CXM-13729]

If clustering is enabled and a device wipe is sent to a disconnected device, the device is wiped when it reconnects, as expected. However, if the device re-enrolls or connects to a different cluster node, XenMobile wipes the device again. [CXM-13793]

The shared devices enroller permission is enabled by default for the Admin RBAC role in XenMobile Service (cloud) deployments. As a result, all devices belonging to users with the Admin role enroll as shared devices. [CXM-15203]

When you configure client certificate authentication and the Require Server Name Indication option is enabled on the CA server, enrollment fails. [CXM-15312]

When searching for Google Play Store apps from the XenMobile console, the search does not return apps based on the Android operating system on the registered device. For examples, apps that require a minimum operating system of 4.4 do not appear in the results. [CXM-15653]

When you create a local user assigned to a local group and when the local user tries to enroll using a Windows 10 device, enrollment fails. [CXM-16895]

When you create a Citrix Launcher policy, users can enroll an Android device, but if you change a policy setting, they cannot exit Citrix with the password you set in the policy. As a workaround, you need to reinsert the password in the policy settings and update the policy. [CXM-17157]

When you disable the Enable ShareFile option in XenMobile, in Secure Mail for Android, users cannot access any attachment type. [CXM-17887]

When you update from XenMobile 10.3.6 with Rolling Patch 1 to XenMobile 10.4, license types of permanent expire with an error message. [CXM-17900]

When you update from XenMobile 10.3.6 to XenMobile 10.4, even though the license of permanent type is still valid, an expired license error message appears. [CXM-17987]

If you manually enter a URL for a Windows public store app and the URL is not from a U.S. store, the XenMobile console displays an error. When you use the U.S. store app URL, the upload is successful. [CXM-18013]

When users receive one-time password invitations for IMEI binding (username and password) and SMTP and SMS notifications, the first profile installs successfully and the second profile installation fails with the error message "Profile Installation Fails. A connection to the server could not be established." On iPhone 6 and iPhone 6 Plus devices, there is an IMEI number and MEID number and the one-time password binds to the MEID number instead of the IMEI number. You can replace the IMEI number with the iPhone's Unique Device Identifier (UDID) or use a regular phone number. [#606162]

Attempts to download a Certificate Signing Request (CSR) from Internet Explorer and Firefox web browsers fail with the error "The Webpage cannot be displayed." Downloading the CSR from the Chrome web browser works. [#609552]

If you log on to the XenMobile console, navigate to Analyze > Reporting and then click Inactive Devices, a blank page appears instead of downloading the file. [#609649]

The XenMobile NetScaler Connector doesn't obtain the Samsung 5.x devices from a sync with ActiveSync. [#613522]

When you create a WiFi device policy for Android with an authentication type of 802.1x EAP, the Password field is no longer mandatory.  [#614932]

This fix addresses a security vulnerability. For more information, see security bulletin
Note: For this security fix to work, a second reboot of the XenMobile server is required for the fix to take effect. [#624347]

You cannot currently locate your Android ID by entering *#*#8255#*#* on your phone, as instructed on the XenMobile Settings > Google Play Credentials page. Use a device ID app from the Google Play store to look up your device ID. [#633854]

Windows Phone enrollment sometimes fails to start Worx Home. [#633884]

Disabled HDX apps do not enumerate in the Worx Store. [#634110]

The XenMobile server shows incorrect user data in the log file. [#636754]

After updating from XenMobile 10.3.1 to 10.3.6, the file type and destination folder in the Files policy properties doesn't display correctly in the XenMobile console. [#640334]

VPP token max length text box is 256 characters. [#640692]

Windows Phone users can't enroll a device with a sAMAccount. [#640847]

After removing enrolled users from the ShareFile control subsystem, the enrolled users might appear in the user audit log file of the XenMobile console. [#641342]

After upgrading from XenMobile Server 10.1 to 10.3.x, clicking https://<enroll.FQDN>/zdm/enrollmdm.html, the iOS platform is not listed as a platform selection. [#641771]

When you enroll a Worx Home for iOS device, the MDM enrollment might be successful but MAM registration fails. [#644892]

Deletion of nested groups is never reflected. [#647557]

If Manage > Enrollment has more than 2,000 entries, after you click Export the page goes blank and the report isn't generated. [#647855]

XenMobile administrators attempting to access the XenMobile console might be directed to the XenMobile Self-Help portal instead. This can happen when XenMobile administrator groups are created with role-based control access and a group is moved from one Active Directory OU to another. [#647987]

Uploading iOS app fails with error - Uploaded mobile app is invalid. Application icon was not found.[#649574]

XenMobile server might become unresponsive with an Out of Memory error. [#650490]

Device wipe issues because of clustered messaging. [#650555]

When configuring a VPN device policy, you can't specify a port number. [#650972]

After upgrading XenMobile server with clustering enabled, several deadlocks might occur. The server might become unresponsive. [#651122]

The XenMobile console doesn't include Serial Number details while prompting you to confirm device deletion. [#651185]

SSO Account Policy on XenMobile server 10.3.6 does not work as expected. Users keep getting prompted for password.  [#651860]

Cannot disable iPad app association on XenMobile 10.3.6 for VPP applications.[#652280]

If you delete a delivery group from a device policy, XenMobile doesn't save the change and the delivery group remains assigned to the policy.  [#652321]

SSO account unable to save short FQDN. [#652704]

When a user removes Device Admin rights from their Android device, XenMobile changes the state of both MDX and MAM enrolled devices to "Orange/unmanaged" and the user doesn't have access to any MDX apps. The MAM state should remain as "Green/managed". [#655180]

XenMobile 升级工具 10.4

If the device setting in XenMobile 9.0 for maximum or minimum operating system is set to 10 or above and for excluded devices for MDX and enterprise apps, after upgrading, the rule does not migrate properly. Apps that should appear do not and apps that should not appear do. [#603412]

If Microsoft SQL server is configured as case-sensitive, an upgrade fails if the table "Id_Generator" is specified as "id_generator". [#623300]

After upgrading from XenMobile 9 to XenMobile 10, the Personal Hotspot policy value type is Boolean instead of string. [#633337]

If an Active Directory group name contains the "@" character, an upgrade fails. [#633718]

If your Device Manager 9.0 server is set up using Local PostgreSQL and you use localhost as a reference for the database server, an upgrade will fail. To work around this, edit on the Device Manager 9.0 server and replace all localhost references with the IP address of the Device Manager database server, then continue with the Upgrade pre-requisites. [#635023]

In XenMobile 9.0, when you define the Users organizational unit (OU) in the LDAP connection parameters, after you upgrade to XenMobile 10, the full root context is not appended to users organizational unit. For example, OU=MDMUsers, OU=SALES should be OU=MDMUsers, OU=SALES, DC=citrite, DC=com. As a result, you need to make the update manually in XenMobile 10. [#635981]

During an upgrade, when uploading the support bundle, the error "MAM set up failed, see the logs for details" appears and the Upgrade Tool retains corrupted MAM data. [#638062]

If an Active Directory group name contains the "." character, a role migrated as a delivery group loses its group association. [#647590]

If the web proxy setting in App Controller includes the "\" character, XenMobile 10.1 server can't start and the message "Starting main app…" appears as the server continues to reboot. [#647919]

After an upgrade from XenMobile 9 to XenMobile 10, paid VPP apps do not install from the XenMobile (Worx) Store unless the app configuration requires installation. [#668102]

In a cross-domain authentication configuration, after an upgrade to XenMobile 10.3.6, devices that were previously enrolled in XenMobile 9 can't open installed apps or download new apps from the Worx (XenMobile) Store or access the Store. [CXM-13708]

After an upgrade from XenMobile 9 to XenMobile 10, installed public store apps appear as unsubscribed in the XenMobile (Worx) Store. [CXM-17936]

If the database connection URL is localhost, you no longer must modify 

If you have RBAC roles configured with access restricted to LDAP and Active Directory or any child, after upgrading, when you log on to the XenMobile console as an administrator, the same settings are not selected.