This article provides information on frequently asked questions and answers for XenMobile 10 MDM migration tool.

Contents

Q: What XenMobile editions are supported with the migration tool?

Q: What versions of XenMobile are supported with the migration tool?

Q: Where is the XenMobile 10 migration tool located?

Q: What browsers are recommended to use for the migration procedure?

Q: What is the difference between “Test Drive” and “Production Upgrade”?

Q: During the initial of configuration of XenMobile Server 10, do I need to assign the same hostname set on XenMobile 9 Device Manager?

Q: I heard the migration tool will prompt to collect some files from XenMobile Device Manager and ZIP them. What files are required?

Q: What if XenMobile 9 Device Manager was configured with FIPS-enabled?

Q: What files/data are not migrated to XenMobile Server 10?

Q: Is there a log file that I can check after the migration is complete?

Q: What ports need to be opened between XenMobile 9 Device Manager and XenMobile Server 10?

Q: What happens if I missed a file in the ZIP folder?

Q: What happens if the migration process gets interrupted in the middle or fails?

Q: I noticed that the migration process stopped but it did not provide me the option to see or download the migration logs file as displayed below. What should I do?

Q: After migration is complete, are there any post-migration steps to follow?

Q: Where are the Deployment Packages now on XenMobile Server 10?

Q: What XenMobile editions are supported with the migration tool?

A: Currently, XenMobile MDM edition and Enterprise edition deployments are supported with the migration tool. XenMobile App is not supported at this point. Therefore, the following scenarios are supported:
XenMobile 9 MDM edition to XenMobile 10 MDM edition.
XenMobile 9 Enterprise edition to XenMobile 10 Enterprise edition.

Q: What versions of XenMobile are supported with the migration tool?

A: Only XenMobile 9 (MDM Edition). XenMobile 8.7.x is not supported.

Q: Where is the XenMobile 10 migration tool located?

A: The migration tool is built-in within the XenMobile Server 10 VM. There is no separate download for it.

To access the XenMobile Migration tool wizard, it needs to be enabled during the first-time installation wizard (through CLI console). 

If you select “Yes” to upgrade from previous release, then, XenMobile Server enables a one-time only upgrade wizard. The upgrade wizard can be accessible from https://<XenMobile-Server-IP-Address>/uw/.

However, Citrix will have available updates to the XenMobile Server 10 Migration tool under the XenMobile Enterprise download site.

Q: What browsers are recommended to use for the migration procedure?

A: It is recommended to use Google Chrome and Mozilla Firefox browsers. There are known issues with caching when using Internet Explorer browsers. 

Q: What is the difference between “Test Drive” and “Production Upgrade”?

Test Drive
By selecting this option, it will migrate only configuration data from the previous release of XenMobile 9 Device Manager and any data related to devices and users will NOT be migrated. This option will help customers/admins to experience XenMobile 10 but with their current XenMobile 9 Device Manager configuration.

Production Upgrade
By selecting this option, it will migrate all the configuration included in the previous release of XenMobile Device Manager – for example, server configuration, devices, users, and data. This option should be used after thorough validation of configuration using “Test Drive” to ensure all required/eligible configuration is migrated.

Note: The preceding options are one-time usable only. This means that once an option is chosen, it cannot be reverted. Overwriting or re-do of the migration is not supported.

Q: During the initial of configuration of XenMobile Server 10, do I need to assign the same hostname set on XenMobile 9 Device Manager?

A: Yes. It is mandatory to use the same hostname assigned on XenMobile 9 Device Manager to XenMobile Server 10 for a successful migration process.

Q: I heard the migration tool will prompt to collect some files from XenMobile Device Manager and ZIP them. What files are required?

A: Assuming the XenMobile Device Manager is installed in the default location (for example, C:\Program Files (x86)\Citrix\XenMobile Device Manager\tomcat), copy the following files into a 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 the zdm.geolitecity.datafile parameter is set on ew-config.properties file then, ensure to copy the file called – GeoLiteCity.dat (located under C:\Program Files (x86)\Citrix\XenMobile Device Manager\tomcat\webapps\zdm) to the ZIP folder.

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

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

Q: What if XenMobile 9 Device Manager was configured with FIPS-enabled?

A: If XenMobile 9 Device Manager server had FIPS enabled, there is no need to collect any files during the migration process.

If FIPS is enabled on XenMobile 9 Device Manager, then, select “Yes” when prompted on XenMobile Server 10 in the SFTU (Server First-Time User) console wizard.

Q: What files/data are not migrated to XenMobile Server 10?

A: The following information is not migrated to XenMobile 10:

• Licensing information.
• Reports data.
• Server group policies and associated deployments.
• MSP group.
• Policies and packages related to Windows CE 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, as described in the following section.
• CXM Web and DLP Policies.
• 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.
• Custom dashboard.
• Any other configuration or user data as described in the migration.log file (available post-migration).

Important changes to consider

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

Q: Is there a log file that I can check after the migration is complete?

A:  Yes. Post migration, the XenMobile Migration tool will provide a log file that can be downloaded and reviewed. 

It is highly recommended to review the migration.log file after migration to review what policies, settings, user data, and so on was migrated to XenMobile Server 10.

Q: What ports need to be opened between XenMobile 9 Device Manager and XenMobile Server 10?

A:  During the data migration process, XenMobile Server 10 needs to be able to access the database solution implemented on XenMobile 9 Device Manager. For example:

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

Note: To allow remote connections to PostgreSQL, there are additional steps that need to done.

1. Locate and edit the file pg_hba.conf to add the following line:
   host all all <XenMobile Server IP address>/32 md5
2. Save the file.
3. Locate and open postgresql.conf file and change the following line:
   listen_addresses = ‘localhost’
   To
   listen_addresses = ‘*’
4. Restart the PostgreSQL service for changes take effect.

For more information, refer blog.
If a custom port has been assigned to the database solution, you have to ensure to allow/open this port in the firewall protecting the XenMobile Device Manager. This way, the XenMobile Server 10 can connect to the database and migrate the required information.

Q: What happens if I missed a file in the ZIP folder?

A: If there is required file missing from the ZIP folder, then, the XenMobile Server Migration tool will guide you which file is missing. For example: 

When the file is added to the ZIP folder, you can continue the migration process.

Q: What happens if the migration process gets interrupted in the middle or fails?

A: An error message will appear on the screen. At this point, capture the error message (snapshot), gather the XenMobile Support Bundle and contact Citrix Technical Support for further investigation.

At this state, you need to import a new XenMobile Server 10 VM instance and restart the migration process.

Q: I noticed that the migration process stopped but it did not provide me the option to see or download the migration logs file as shown in the screen shot. What should I do?

A: At this stage, it is highly recommended to obtain the Support Bundle through the CLI console for further troubleshooting and analysis. Refer to this link to know the location of the Support Bundle option in the CLI.

Q: After migration is complete, are there any post-migration steps to follow?

A: Yes. Ensure to configure the following settings:

• XenMobile licensing - XenMobile Server 10 only supports Citrix V6 Licensing. Ensure to set the local or remote license configuration and download the license file from MyCitrix portal.

  

• End-user testing - End-users do NOT need to re-enroll to the new XenMobile Server 10. However, it is recommended to Sign Off and Sign On in Secure Hub. When this is complete, check that mobile devices are seen under the unified XenMobile 10 console.

  

Q: Where are the Deployment Packages now on XenMobile Server 10?

A: Deployment Packages that were in use (for example with users assigned, policies, etc) in XenMobile 9 Device Manager, XenMobile Server 10 would migrate and display them as Delivery Groups.

Inside the Delivery Group, you should find the MDM policies, actions and apps required for the group of users that need these resources.

Additional Information