Known Issues

Known Issues

The following are known issues for the XenMobile 10 MDM Upgrade Tool:

• The XenMobile lockout limit value is not migrated. After migration, reset the value. [#545770]
• Options in role-based access control (RBAC) roles do not migrate cleanly. After migration, review RBAC roles and make any necessary adjustments. [#543183]
• Log settings do not migrate. After migration, re-configure log settings in the XenMobile console. [#541869] 
• When a configuration with multiple LDAP configurations in which only one LDAP configuration to support nested groups is migrated, after migration, nested groups support is enabled on all LDAPs you configured. In addition, groups synchronization happens on all LDAP servers during server start-up. [#540713]
• When a Web Content Filter device policy contains URLs without HTTP/HTTPS, the URL is deleted when users edit the URL and then cancel the operation. After migration, make sure all URLs contain HTTP or HTTPS to prevent deletion when canceling an edit operation. [#540025]
• When policies, apps, or actions are included in multiple packages with different rules, deployment rules do not migrate. This behavior is as designed. [#539517]
• The XenMobile 9.0 administrator cannot log on to the XenMobile 10 console after successful migration when the administrator user name contains an uppercase character. Before migration, create an administrator user account with all lowercase letters and with all permissions enabled so that after migration you can use that account to log on to the XenMobile 10 console. [#547422]
• If Multi-Tenant Console (MTC) is enabled on XenMobile 9, MTC cannot be migrated to XenMobile 10. [#549969]
• The Super Admin role created in XenMobile 9.0 does not migrate several setting and assignment permissions in XenMobile 10. After migration, in the XenMobile 10 console, go to Configure > Settings > Role Based Access Control and recreate the XenMobile 9.0 Super Admin role with permissions from the XenMobile 10 Admin role. [#553079]
• Deployment package names created in XenMobile 9.0 with special characters (:, !, $, (), #, % , +, *, ~, ?, |, {}, and []) cannot be edited after migration. In addition, local users and local groups created in XenMobile 9.0 that contain an open square bracket ([) cause problems in XenMobile 10 when creating enrollment invitations. Before migration, remove all special characters from Deployment Package names as well as open square brackets from local user and local group names. [#538639]

Prerequisites

Prerequisites

You need to complete the following prerequisites before you run the XenMobile 10 MDM Upgrade Tool.

Citrix License Server

Make sure that you install the 11.12.1 Citrix License Server (available on the page) and that you configure the server with the latest V6 MDM-only license. Ensure that the licensing server ports 27000 and 7279 are open to the server. This step is crucial to prevent unintentionally upgrading users' devices to XenMobile Enterprise mode, which may lead to a licensing violation and also force users to re-enroll their devices.

Database

Migration can only be done between databases of the same type. For example:

Supported

• PostgreSQL to PostgreSQL
• MSSQL to MSSQL

Not supported

• MSSQL to PostgreSQL
• PostgreSQL to MSSQL

During the data migration process, XenMobile needs the ability to access the database solution implemented on XenMobile 9.0 Device Manager. For example, the following ports must be open:

• For Microsoft SQL Server, the default port is 1433.
• For PostgreSQL, the default port is 5432.

To allow remote connections to PostgreSQL, you must complete the following steps:

1. Open the file pg_hba.conf and locate the following line: "host all all 127.0.0.1/32 md5"

2. Append a new line host all all [XMS address/external address]/32 md5 

3. Save the file.

4. Stop and start the service.

5. Locate and open the postgresql.conf file and change this line from:

"#listen_addresses = 'localhost'" to "listen_addresses = ‘*’"

Note: The line must be uncommented. This can be made restrictive by allowing only XenMobile 9.0 and XenMobile 10 server IPs to access the PostgreSQL database (listen_addresses = '10.x.x.1,10.x.x.2').

6. Stop and start the PostgreSQL service for changes take effect.

7. Ensure that XMS and the database are able to communicate with each other. (This also checks that the database is able to accept remote connections.)

If a custom port has been assigned to the database solution, you have to ensure that the port is allowed and open in the firewall protecting XenMobile 9.0 Device Manager. Doing so enables XenMobile 10 to connect to the database and to migrate the required information.

External SSL certificate

External SSL certificates must meet the conditions outlined in . Be sure to review your pki.xml before starting the migration to ensure that the SSL certificate meets those conditions.

Administrator account user name

The administrator account used to log on to the XenMobile 10 console can contain only lowercase letters; you will not be able to log on to the XenMobile 10 console after migration if the account contains uppercase letters. Create an administrator user account with all lowercase letters and with all permissions enabled so that after migration you can use that account to log on to the XenMobile 10 console.

Deployment Package names with special characters

Deployment package names in XenMobile 9.0 that contain special characters (!, $, (), #, % , +, *, ~, ?, |, {}, and []) migrate, but the Delivery Groups in XenMobile 10 cannot be edited after migration. In addition, local users and local groups created in XenMobile 9.0 that contain an open square bracket ([) cause problems in XenMobile 10 when creating enrollment invitations. Before migration, remove all special characters from Deployment Package names as well as open square brackets from local user and local group names.

Copy files from XenMobile 9.0 Device Manager

Assuming Device Manager is installed in the default location (C:\Program Files(x86)\Citrix\XenMobile Device Manager\tomcat), copy the following files into a temporary folder:

From C:\Program Files (x86)\Citrix\XenMobile Device Manager\tomcat\conf folder:

• server.xml
• https.p12
• cacerts.pem.jks
• pki-ca-root.p12
• pki-ca-devices.p12
• pki-ca-servers.p12

Note: If custom server SSL server certificates (.p12) were used on the server running Device Manager, make sure that you copy that certificate instead of https.p12 to the temporary folder.

From the C:\Program Files (x86)\Citrix\XenMobile Device Manager\tomcat\webapps\zdm\WEB-INF\classes\ folder, copy the following files into the same temporary folder:

• ew-config.properties
• pki.xml
• variables.xml

After you have copied all the preceding files, open the temporary folder and zip the files; do not zip the folder, only the files. The zipped files will be uploaded during the upgrade.

When you understand the known issues and meet all the prerequisites, start the upgrade. For details, see Running the XenMobile 10 MDM Upgrade Tool.

XenMobile 10 MDM Upgrade Tool

XenMobile 10 MDM Upgrade Tool

You use the XenMobile 10 MDM Upgrade Tool to upgrade from XenMobile 9.0 to XenMobile 10. The tool is supported for upgrades from XenMobile MDM edition deployments.

Important: Using the tool to upgrade from XenMobile App Edition or XenMobile Enterprise Edition is not supported. Likewise, you cannot use the tool to upgrade from XenMobile 8.6 or 8.7 to XenMobile 10. In addition, if the Multi-Tenant Console (MTC) is enabled on XenMobile 9.0, the MTC cannot be migrated to XenMobile 10.

If your XenMobile 9.0 setup is based on named SQL instances, you need to follow steps specific to this situation. For details see, .

The Upgrade Tool is built within the XenMobile 10 virtual machine. You enable the one-time only wizard through the command-line console during the initial installation of XenMobile 10.

What the Upgrade Tool does

The XenMobile 10 MDM Upgrade Tool migrates configuration and user data from the XenMobile 9.0 server to a new instance of XenMobile 10 with the same fully qualified domain name (FQDN).

You can choose to test drive the upgrade or to do a full production upgrade. When you choose Test Drive in the tool, only configuration data is migrated to XenMobile 10; no device or user data is migrated. This option lets you compare XenMobile 9.0 and XenMobile 10 without affecting your production environment.

When you choose Production Upgrade in the tool, all configuration, device, and user data is migrated. When you log on to the XenMobile 10 console after the upgrade, you see all the user and device data that was migrated from XenMobile 9.

Note: This is not an in-place migration; all data is copied during migration, not moved, to XenMobile 10. Everything in XenMobile 9.0 remains intact until you move the XenMobile 10 server into production. When users connect to XenMobile 10 in production, if for some reason you want to revert to XenMobile 9.0, those users must re-enroll in XenMobile 9.0. After a successful production upgrade, to move XenMobile 10 to live production, you must do the following:

1. Update the DNS entry to map the XenMobile 9.0 FQDN to the new XenMobile 10 server IP.

2. If NetScaler is load balancing XenMobile Device Manager servers, you need to switch the XenMobile 9.0 service to the XenMobile 10 service.

What the Upgrade Tool Does Not Do

The following information is not migrated to XenMobile 10 when you use the Upgrade Tool:

• Licensing information.
• Reports data.
• Automated actions.
• Server group policies and associated deployments.
• MSP group.
• Policies and packages related to Windows CE and Windows 8.0.
• Deployment packages not in use; for example, when no users or groups are assigned to a deployment package.
• Any other configuration or user data as described in the migration.log file.
• CXM Web (replaced by Citrix WorxWeb).
• DLP policies (replaced by Citrix Sharefile).
• Custom Active Directory attributes.
• If you have configured multiple branding policies, the branding policy is not migrated. XenMobile 10 supports one branding policy; you have to leave one branding policy in XenMobile 9.0 to successfully migrate to XenMobile 10.
• Any settings in the auth.jsp file in XenMobile 9.0 that are used to restrict access to the console. Console access restrictions in XenMobile 10 are firewall settings that you can configure in the command line interface.

Also note the following changes with XenMobile 10:

• XenMobile 10 does not support Active Directory users who are assigned to local groups.
• The local groups hierarchy is flattened.

Terminology Change with XenMobile 10

Note that after you upgrade, deployment packages in Device Manager are now referred to as delivery groups, as shown in the following figure. For more information, see.

Inside the delivery group, you can view the MDM policies, actions, and apps required for the group of users who require the resources.

Device Enrollment After Upgrade

Users do not need to re-enroll their devices after you upgrade to XenMobile 10. The devices should connect automatically to the XenMobile 10 server based on the heartbeat interval.

If you want to connect a device to XenMobile 10 immediately, on the device, use WorxHome > Device Info > Refresh Policy.

After the user devices connect, check to make sure you see the devices in the XenMobile console, as shown in the following figure.

Importing Certificates

Importing Certificates

The following procedure describes how to configure FIPS on XenMobile by importing the certificate, which is required when you use a VMware hypervisor.

SQL Prerequisites

1. The connection to the SQL instance from XenMobile needs to be secure and must be SQL Server version 2012 or SQL Server 2014. To secure the connection, see Microsoft Management Console.

2. If the service does not restart properly, check the following:Open Services.msc.

a. Copy the logon account information used for the SQL Server service.

b. Open MMC.exe on the SQL Server.

c. Go to File > Add/Remove Snap-in and then double-click the certificates item to add the certificates snap-in. Select the computer account and local computer in the two pages on the wizard.

d. Click OK.

e. Expand Certificates (Local Computer) > Personal > Certificates and find the imported SSL certificate.

f. Right-click the imported certificate (selected in the SQL Server Configuration Manager) and then click All Tasks > Manage Private Keys.

g. Under Group or User names, click Add.

h. Enter the SQL service account name you copied in the earlier step.

i. Clear the Allow Full Control option. By default the service account will be given both Full control and Read permissions, but it only needs to be able to read the private key.

j. Close MMC and start the SQL service.

3. Ensure the SQL service is started correctly.

Internet Information Services (IIS) Prerequisites

1. Download the rootcert (base 64).

2. Copy the rootcert to the default site on the IIS server, C:\inetpub\wwwroot.

3. Check the Authentication check box for the default site.

4. Set Anonymous to enabled.

5. Select the Failed Request Tracking rules check box.

6. Ensure that .cer is not blocked.

7. Browse to the location of the .cer in an Internt Explorer browser from the local server, http://localhost/certname.cer. The root cert text should appear in the browser.

8. If the root cert does not appear in the Internet Explorer browser, make sure that ASP is enabled on the IIS server as follows.

a. Open Server Manager.

b. Navigate to the wizard in Manage > Add Roles and Features.

c. In the server roles, expand Web Server (IIS), expand Web Server, expand Application Development and then select ASP.

d. Click Next until the install completes.

9. Open Internet Explorer and browse to http://localhost/cert.cer.

Note: You can use the use the IIS instance of the CA for this procedure.

Importing the Root Certificate During Initial FIPS Configuration

When you complete the steps to configure XenMobile for the first time in the command-line console, you must complete these settings to import the root certificate. For details on the installation steps,

Enable FIPS: Yes

Upload Root Certificate: Yes

Copy(c) or Import(i): i

Enter HTTP URL to import: http://FQDN of IIS server/cert.cer

Server: FQDN of SQL Server

Port: 1433

User name: Service account which has the ability to create the database (domain\username).

Password: The password for the service account.

Database Name: This is a name you choose.

Configuring XenMobile in a Web Browser

Configuring XenMobile in a Web Browser

After completing the initial portion of the XenMobile configuration in your hypervisor Command Prompt window, complete the process in your web browser.

1. In your web browser, navigate to the location provided at the conclusion of the Command Prompt window configuration.

2. Type the XenMobile console administrator account user name and password you created in the Command Prompt window.

3. On the Get Started page, click Start. The Licensing page appears.

4. Configure the license. XenMobile comes with an evaluation license valid for 30 days. For details on adding and configuring licenses and configuring expiration notifications, see . Important: If you intend to cluster nodes, or instances, of XenMobile, you need to use the Citrix Licensing on a remote

server.

5. On the Certificate page, click Import. The Import dialog box appears.

6. Import your APNs and SSL Listener certificate. For details on working with certificates, see. 

Note: The SSL Listener certificate requires restarting the server.

7. If appropriate to the environment, configure NetScaler Gateway. For details on configuring NetScaler Gateway, see.

Note: You can deploy NetScaler Gateway at the perimeter of your organization's internal network (or intranet) to provide a secure single point of access to the servers, applications, and other network resources that reside in the internal network. In this deployment, all remote users must connect to NetScaler Gateway before they can access any resources in the internal network.

Note: Although NetScaler Gateway is an optional setting, after you enter data on the page, you must clear or complete the required fields before you can leave the page.

8. Complete the LDAP configuration to access users and groups from Active Directory. For details on configuring the LDAP connection, see.

9. Configure the notification server to be able to send messages to users. For details on notification server configuration, see.

Configuring FIPS with XenMobile

Federal Information Processing Standards (FIPS) mode in XenMobile supports U.S. federal government customers by configuring the server to use only FIPS 140-2 certified libraries for all encryption operations. Installing your XenMobile server with FIPS mode ensures that all data at rest and data in transit for both the XenMobile client and server are fully compliant with FIPS 140-2.

Before installing a XenMobile Server in FIPS mode, you need to complete the following prerequisites.

->You must use an external SQL Server 2012 or SQL Server 2014 for the XenMobile database. The SQL Server also must be configured for secure SSL communication. For instructions on configuring secure SSL communication to SQL Server, see the SQL Server Books Online.

->Secure SSL communication requires that an SSL certificate be installed on your SQL Server. The SSL certificate can either be a public certificate from a commercial CA or a self-signed certificate from an internal CA. Note that SQL Server 2014 cannot accept a wildcard certificate. Citrix recommends, therefore, that you request an SSL certificate with the FQDN of the SQL Server.

->If you use a self-signed certificate for SQL Server, you will need a copy of the root CA certificate that issued your self-signed certificate. The root CA certificate must be imported to the XenMobile server during installation.

Configuring FIPS mode

You can enable FIPS mode only during the initial setup of XenMobile server. It is not possible to enable FIPS after installation is complete. Therefore, if you plan on using FIPS mode, you must install the XenMobile server with FIPS mode from the start. In addition, if you have a XenMobile cluster, all cluster nodes must have FIPS enabled; you cannot have a mix of FIPS and non-FIPS XenMobile servers in the same cluster.

There is a Toggle FIPS mode option in the XenMobile command-line interface that is not for production use. This option is intended for non-production, diagnostic use and is not supported on a production XenMobile server.

1. During initial setup, enable FIPS mode.

2. Upload the root CA certificate for your SQL Server. If you used a self-signed SSL certificate rather than a public certificate on your SQL Server, choose Yes for this option and then do one of the following:

a. Copy and paste the CA certificate.

b. Import the CA certificate. To import the CA certificate, you must post the certificate to a website that is accessible from the XenMobile server via an HTTP URL. For details, see the section later

in this article.

3. Specify the server name and port of your SQL Server, the credentials for logging into SQL Server, and the database name to create for XenMobile.

Note: You can use either a SQL logon or an Active Directory account to access SQL Server, but the logon you use must have the DBcreator role.

4. To use an Active Directory account, enter the credentials in the format domain\username.

5. Once these steps are complete, proceed with the XenMobile initial setup.

To confirm that the configuration of FIPS mode is successful, log on to the XenMobile command-line interface. The phrase In FIPS Compliant Mode appears in the logon banner.

XenMobile 10.x

XenMobile 10.x

Supported NetScaler Gateway versions:
11.0.64.x
10.5.x.e
10.5.x MR
10.1.x.e
10.1.x MR

XenMobile client components generally follow these compatibility requirements:
The latest versions of Worx Home and the MDX Toolkit are compatible with the latest version of XenMobile server and the two most recent versions before that.

The latest version of the MDX Tookit, and the two most recent versions before that, are compatible with the most recent versions of Worx Home and Worx Mobile Apps.

To take advantage of new features, fixes, and policy updates, Citrix recommends that you install the most recent version of the MDX Toolkit, Worx Home, and Worx Mobile apps for the best experience.

Note
Worx Home versions earlier than 10.0.3 are compatible but not supported.

1 Windows Phone 10 is not supported on XenMobile server 10.1.
2In earlier releases, the Worx version of QuickEdit was named WorxEdit and the Worx version of ShareConnect was named WorxDesktop. Both the MDX and non-MDX versions now have the same names: QuickEdit and ShareConnect.
3 The download page includes a separate version of ShareFile Worx for iOS that is required for use with restricted StorageZones.

Browser Support
XenMobile 10.x supports the following browsers:
Internet Explorer*
Chrome
Firefox
Safari on mobile devices for use with the Self Help Portal.

XenMobile 10.x is compatible with the most current version of the browser and one version prior to the current version.
*XenMobile 10.x does not support Internet Explorer version 9 and earlier.

XenMobile 9
XenMobile 9 includes Device Manager 9.0 and App Controller 9.0.
Supported NetScaler Gateway versions:
11.0.64
10.5.x.e
10.5.x MR
10.1.x.e
10.1.x MR

XenMobile client components generally follow these compatibility requirements:
The latest version of Worx Home and the MDX Toolkit are compatible with the last two versions of
XenMobile server.
The latest version of the MDX Toolkit is compatible with the latest Worx Mobile Apps.
Recent MDX Toolkit versions are compatible with the following versions of Worx Home:

1 Previously, the Worx version of QuickEdit was named WorxEdit and the Worx version of ShareConnect was named WorxDesktop. As of the latest releases, both the MDX and non-MDX versions have the same names: QuickEdit and ShareConnect.

2 The download page includes a separate version of ShareFile Worx for iOS that is required for use with restricted StorageZones.

Device Manager 8.7.1 and App Controller 2.10
Supported NetScaler Gateway versions: 10.1.126.1203.e and 10.1.124.1308.e

Supported client versions:
* MDX Toolkit 2.3 and 2.2.1 do not support WorxNotes.
** Not applicable

Device Manager 8.6.1 and App Controller 2.9
Supported NetScaler Gateway version: 10.1.124.1308.e
Supported client versions:
* MDX Toolkit 2.2.1 does not support WorxNotes.
** Not applicable

XenMobile support

XenMobile support

For details on how to access supported related information and tools in the XenMobile console, see XenMobile support and Maintenance.

Supporting Mobile Platforms in XenMobile Cloud

After you make a request for a XenMobile Cloud instance, you can, if you like, begin preparing to support Android, iOS, and Windows platforms. As you complete the steps that apply to your environment, keep the information handy so you can use it when configuring settings in the XenMobile console.

Note that these requirements are a subset of the overall communication and port requirements that make up the XenMobile Cloud onboarding process. For details, see XenMobile Cloud prerequisites and administation.

Android

- Create Google Play credentials. For details, see Google Play Getting Started with Publishing.

- Create an Android for Work administrator account. For details, see Managing Devices with Adroid for Work in Xenmobile.

- Verify your domain name with Google. For details, see Verify your domain for Google Apps.

- Enable APIs and create a service account for Android for Work. For details, see Google for Work Adroid.

iOS

- Create an Apple ID and developer account. For details, see the Apple Developer Program website.

- Create an Apple Push Notification service (APNs) certificate. For details, see the Apple Push Certificates Portal.

- Create a Volume Purchase Program (VPP) company token. For details, see Apple Volume Purchasing Program.

Windows

- Create a Microsoft Windows Store developer account. For details, see the Microsoft Windows Dav Center.

- Obtain a Microsoft Windows Store Publisher ID. For details, see the Microsoft Windows Dav Center.

- Acquire an enterprise certificate from Symantec. For details, see the Microsoft Windows Dav Center.

- Create an Application Enrollment Token (AET). For details, see the Microsoft Windows Dav Center.

System Requirements

To run XenMobile 10, you need the following minimum system requirements:

- One of the following:

XenServer (supported versions: 6.2.x, 6.1.x, or 6.0.x); for details, refer to XenServer

VMWare (supported versions: ESXi 4.1, ESXi 5.1, or ESXi 5.5); for details, refer to VMware

Hyper-V (supported versions: Windows Server 2008 R2, Windows Server 2012, or Windows Server

2012 R2); for details, refer to Hyper-V

- Dual core processor

- Two virtual CPUs

- 4 GB of RAM

- 50 GB disk space

The recommended configuration for 10,000 devices is the following:

- Quad core processor

- 8 GB of RAM

NetScaler Gateway System Requirements

To run NetScaler Gateway with XenMobile 10, you need the following minimum system requirements:

- XenServer, VMWare, or Hyper-V

- Two virtual CPUs

- 2 GB of RAM

- 20 GB disk space

You also need to be able to communicate with Active Directory, which requires a service account. You only need query and read access.

XenMobile 10 Database Requirements

The XenMobile repository requires a Microsoft SQL Server database running on one of the following supported versions:

- Microsoft SQL Server 2014

- Microsoft SQL Server 2012

- Microsoft SQL Server 2008 R2

- Microsoft SQL Server 2008

Citrix XenMobile supports SQL Always on availability group and SQL Clustering for database high availability. Citrix does not support database mirroring for XenMobile database high availability. We do support database high availability with Active/Active or Active Passive mode with MS SQL Cluster deployment..

Citrix recommends using Microsoft SQL remotely. PostgreSQL is included with XenMobile and should be used locally or remotely only in test environments.

XenMobile Compatibility

This article summarizes the versions of the supported XenMobile components that you can integrate, including NetScaler Gateway and the version of the MDX Toolkit needed to wrap, configure, and distribute Worx Mobile Apps.

Quick links to sections in this article:

- XenMobile 10.x

- XenMobile 9

- Device Manager 8.7.1 and App Controller 2.10

- Device Manager 8.6.1 and App Controller 2.9