Product Documentation

Upgrade Tool Post-Requisites

Sep 30, 2016

After you upgrade, make sure you complete the following post-requisites. When you click Finish & Restart, the server restarts.

Note: Log on to the XenMobile console using https://<XenMobile-Server-IPAddress>:4443 with your XenMobile 9.0 Device Manager administrator credentials. (If you are completing a MAM upgrade, you enter your XenMobile 9.0 App Controller administrator credentials.)

localized image
localized image

Licensing

XenMobile 10.1 only supports Citrix V6 licensing. Make sure to set the local or remote license configuration in the XeadnMobile console, as shown in the following figure, and download the license file from Citrix Licensing. For more details, see the topic, Licensing for XenMobile.

localized image

You must configure licenses on XenMobile 10.1 to enable user connections. To do so, go to Configure >Settings Licensing. In the case of a standalone server running XenMobile 10.1, you can upload the license in the XenMobile console.

NetScaler

注意

This post-requisite is required only when you upgrade a XenMobile Enterprise Edition production upgrade; it is not required for MAM or MDM upgrades.

The steps you follow in NetScaler result in the creation of a new load balancing virtual server for the XenMobile 9.0 App Controller FQDN. The main steps you follow are:

  1. Configure a migration load balancing virtual server.
  2. Create a host entry for the App Controller FQDN to point to the new load balancing virtual server.
  3. Change NetScaler Gateway to point to the new XenMobile server FQDN:8443.
  4. Change the Device Manager load balancing virtual server to point to the new XenMobile server IP address.
  5. Create a new MAM load balancing virtual server based on an SSL Bridge or an SSL Offload MDM configuration.
  6. Create a host entry for the XenMobile server FQDN to the new MAM load balancing virtual server.
  1. Log on to NetScaler and then click Traffic Management > Load Balancing > Virtual Servers.
localized image

2. Click Add.

3. On the Load Balancing Virtual Server page, configure the following settings and then click OK.

localized image
  • Name: Type a name for the new load balancer.
  • Protocol: Make sure it is set to SSL. The default is HTTP.
  • IP Address: Enter an IP address for the new load balancer, which follows RFC 1918; for example 192.168.1.10.
  • Port: Make sure the port number is 443.

4. Under Services and Service Groups, click No Load Balancing Virtual Server Service Group Binding.

localized image

5. Under Select Service Group Name, click Click to Select.

localized image

6. Click Add to create a new service group.

localized image

7. On the Load Balancing Service Group page, type a name for the new service group, make sure the protocol is set to SSL and then click OK.

localized image

8. Click Members.

localized image

9. Click the No Service Group Member entry that is highlighted.

localized image

10. On the Create Service Group Member page, configure the following settings:

  • IP Address/IP Address Range*: Enter the IP address for XenMobile 10.1 server.
  • Port: Set to 8443.
  • Server ID: If you are migrating from a clustered XenMobile 9.0 environment to a XenMobile 10.1 clustered environment, enter the Server Node ID for the current XenMobile server.

注意

You can obtain the server node ID by logging on to the XenMobile 10.1 server command-line interface (CLI) and typing 1 to go to the Clustering menu. The server node ID is called the Current Node ID.

localized image

11. Click Create and then click Done.

localized image
localized image

12. Click OK.

localized image

13. Click Bind and then on the next screen, click Done.

localized image
localized image

14. Under Certificates, click No Server Certificate.

localized image

15. Under Server Certificate Binding, click Click to Select.

localized image

16. Under Certificates, click the server certificate you exported in Prerequisites, click OK.

localized image

17. Click Bind and then on the next screen, click Done.

localized image
localized image

18. Click the refresh button to confirm that the server is up. 

localized image

Configure address record for AppController server FQDN pointing to the new Migration LB

Click Traffic Management > DNS > Records > Address Records and then click Add to create a new address record for the AppController FQDN pointing to the new Migration load balancer.

注意

If you have a Global Server Load Balancing configuration, adding an address record causes the Global Server Load Balancing system to respond authoritatively for that server with the local IP address.

localized image

Update the XenMobile 9.0 MDM Load Balancer to Point to the New XenMobile 10.1 Server IP

If you deployed the server running XenMobile 9.0 behind a load balancing NetScaler appliance, you need to configure the load balancing XenMobile 9.0 Device Manager instance in NetScaler with the new IP address for the XenMobile 10.1 server, as well as upload the XenMobile 9.0 server certificate to the XenMobile 10.1 server.

1.     Start the NetScaler XenMobile configuration utility.

localized image

2.     On the right side of the screen, under XenMobile Server Load Balancing, click Edit.

localized image

3.     Click the pen icon to edit the Device Manager Server IP Address.

localized image

4.      Select the XenMobile 9.0 Device Manager server IP address and then click Remove Server.

localized image

5.     Click Add Server and then add the new XenMobile 10.1 server IP address. Note: You cannot set the port numbers here. The server is created on port 80 and is given a Down status. You must create  services for ports 443 and 8443 and bind those services to the appropriate load balancing virtual server.

localized image
localized image

Change App Controller FQDN on the NetScaler Gateway

In XenMobile 10.1, the App Controller component listens on port 8443 instead of port 443. You need to change the App Controller FQDN based on the edition you are migrating.

XenMobile Enterprise Edition

Change the App Controller FQDN to point to the new XenMobile 10.1 FQDN, which is the XenMobile 9.0 Device Manager FQDN followed by port 8443. The following table shows an example. 

XenMobile 9.0 Component

Component FQDN

XenMobile 10.1 Enterprise Edition FQDN

Device Manager

enroll.example.com

enroll.example.com:8443

App Controller

appc.example.net

N/A

NetScaler Gateway

access.example.com

N/A

XenMobile App Edition

Change the App Controller FQDN to point to the new XenMobile 10.1 FQDN, which is the XenMobile 9.0 App Controller FQDN followed by port 8443. The following table shows an example.

XenMobile 9.0 Component

Component FQDN

XenMobile 10.1 Enterprise Edition FQDN

App Controller

appc.example.net

appc.example.net:8443

NetScaler Gateway

access.example.com

N/A

To Change the App Controller FQDN

1.     Under NetScaler Gateway, click Edit.

localized image

2.      Click the pen icon next to XenMobile Settings.

localized image

3.     Change the App Controller FQDN to: XenMobile Enterprise Edition: enroll.example.com:8443

localized image

XenMobile App Edition: appc.example.net:8443

localized image

4.      Click Continue and Finish. Next, you need to update your DNS to resolve the FQDN to the IP address of XenMobile Server 10.1.

Create a New MAM Load Balancing Virtual Server Based on an SSL Bridge MDM Configuration

You need to create a new MAM load balancing virtual server to load balance MAM traffic based on the configuration of the existing MDM load balancing virtual server. The following procedure describes how to do so if you have SSL bridge configured.  If your load balancing virtual server is configured with SSL offload, see the steps in this procedure

Create a MAM load balancing virtual server and bind Service Group services to the load balancing virtual server.

1.     Click Traffic Management > Load Balancer > Service Groups.

2.     Click Add and then configure the settings as shown in the following figure:

localized image

3.     Click OK and then click Members.

localized image

4.      Click No Service Group Member to add a new member.

localized image

5.     Enter the XenMobile server IP, port 8443, and Server ID and then click Create.

localized image

注意

  • You can get the Server ID from the XenMobile 10.1 CLI under the Show Cluster Status menu item.
  • If have multiple XenMobile nodes, repeat this step for each node, adding each node to the MAM_LB_SG_8443 Service Group.

6.     Click Done.

localized image

7.     Click Traffic Management > Load Balancer > Virtual Server and then click Add.

注意

You create this load balancer to route traffic from NetScaler Gateway to the XenMobile server nodes.

8.     Type a name for the MAM load balancer, port 8443, and any unused private IP addresses as shown in the following figure.

localized image

9.     Click No Load Balancing Virtual Server ServiceGroup Binding to bind the Service Group MAM_LB_SG_8443 as shown in the following figures.

localized image
localized image
localized image

10.      Bind the server certificate to the MAM_LB_8443 virtual server as shown in the following figures.

localized image
localized image
localized image
localized image
localized image

11.     Under Persistence, in the Persistence list, click CUSTOMSERVERID and then, in the Expression field, type HTTP.REQ.COOKIE.VALUE(“ACNODEID”) and then click OK.

localized image

12.     Click Traffic Management > DNS Records Address Records to create a new address record for the XenMobile 10.1 server FQDN pointing to the new MAM_LB_8443 virtual server.

注意

The XenMobile 10.1 server FQDN is enroll.example.com.

localized image

Create a New MAM Load Balancing Virtual Server Based on an SSL Offload MDM Configuration

1.     Click Traffic Management > Load Balancer > Virtual Server and then click Add.

2.     Type a name for the MAM load balancer, port 8443, and any unused private IP addresses as shown in the following figure.

localized image

3.     Click OK.

4.     Click No Load Balancing Virtual Server Service Binding to bind the Service Group MAM_LB_8443 virtual server as shown in the following figures.

localized image

注意

The service will be already present as it was configured using the MDM Load Balancing wizard.

localized image

5.     Bind the server certificate to the MAM _LB_8443 virtual server as shown in the following figures and then click Done.

localized image
localized image

6.      Under Persistence, in the Persistence list, click CUSTOMSERVERID and then, in the Expression field, type HTTP.REQ.COOKIE.VALUE(“ACNODEID”).

localized image

7.      Configure an address record for the XenMobile server FQDN pointing to the new MAM load balancing virtual server.

8.     Click Traffic Management > DNS Records Address Records and then click Add to create a new address record for the XenMobile 10.1 server FQDN pointing to the new MAM load balancing virtual server.

localized image

注意

The XenMobile 10.1 server FQDN is enroll.example.com.

9.     If you’re using SSL offload, in the command-line interface, enable port 80 for SSL offload.

localized image

Reconfigure STA on NetScaler Gateway

In NetScaler Gateway, you also need to add the IP address or FQDN of the server running the STA. To do so, follow these steps:

1.       Click Netscaler Gateway.

2.       Click Virtual Servers.

3.       Select the configured Netscaler Gateway Virtual Server and then click Edit.

4.       Under Published Applications, click STA server.

5.       Note the URL and then select the Secure Ticket Authority Server from the list.

6.       Click Unbind and then click Add Binding.

7.        In the Secure Ticket Authority Server field, type the URL that you noted in step 5.

8.       Click Bind, click Close and then click Done.

NTP Settings

Make sure to sync the time on NetScaler and on XenMobile server. If possible, point NetScaler and XenMobile server to the same public Network Time Protocol (NTP) server.

Clustering

If you deploy XenMobile 10.1 in a cluster, you must use the CLI to enable cluster support and then join the new XenMobile nodes. You can reuse the XenMobile 9.0 node IP addresses by configuring the new XenMobile 10.1 instance with the same IP address and join it to the oldest (administrator) node.

Updating Information That Did Not Migrate

Update the following as necessary:

  • Managed Service Provider (MSP) group
  • Custom Active Directory attributes
  • RBAC roles
  • Log settings
  • Any configuration or user data listed in the migration.log file
  • Any sys log server configuration
  • For an on-prem migration, RBAC roles are migrated but there are known issues. 

WorxStore custom store name post-requisite

Before you upgraded, one of the prerequisite steps was to work around this issue:

WorxStore known issue: Before upgrading from XenMobile 9 to XenMobile 10.1, if your WorxStore has a custom name, issues occur with enrollment, access to Worx Home, and access to the Worx Store. As a workaround, change the store to the default setting of Store before upgrading. [#619458]

If you did not complete that prerequisite, you must follow one of these post-requisite steps before using XenMobile Server 10.1:

  • If you have a large population of Windows devices, change the store name to the default value. After that, end users who are enrolled with iOS and Android devices must sign off from WorxHome and then sign in again.
  • If you have fewer Windows devices than iOS and Android devices, the recommendation is to have the Windows users re-enroll their devices.

For more information about this issue, see http://support.citrix.com/article/CTX214553