Before installing Device Manager, ensure that the following prerequisites are in place.
To support enrollment of iOS devices, the restricted strength JCE components included in the JDK must be replaced with the unlimited strength files. To do this, copy the unlimited strength JCE files local_policy.jar and US_export_policy.jar to the \jre\lib\security\ directory of the JDK, overwriting the existing files. For more information see the readme file for the JDK, which is available at http://www.oracle.com/technetwork/java/javase/terms/readme/index.html.
If you are installing Device Manager on your computer for the first time, select Full install. When you select this option, the following components are installed:
Device Manager includes the PostgreSQL database server installation. If you installed a SQL database server on your computer or another server, clear the PostgreSQL check box in the list of components during the installation wizard. The install type switches automatically to Custom. When using Microsoft SQL Server, refer to the Microsoft installation instructions. If you do not clear the check box, the PostgreSQL installation wizard appears with configuration instructions.
If you install PostgreSQL, an installation wizard appears. The installation program automatically selects all of the default PostgreSQL options required to install an Device Manager server. However, you can check additional options you want to install. You can also change the installation location with the Browse button.
During installation of PostgreSQL, define the service account that runs the PostgreSQL server. The Service name, Account name, and Account domain fields are already completed. You need to enter a password for the service account.
If the user account does not exist, you receive a prompt to confirm creation of the account. In addition, if the password you choose is not a strong password, you are prompted to replace the password with a strong password. Click No in the message dialog box to keep the password you originally entered.
After you configure the PostgreSQL database, you can then install licenses. If you are using a different SQL database and did not install PostgreSQL, after choosing the initial components and installation location, you install the licenses.
Before you install Device Manager, make sure you do the following:
The setup wizard includes several discrete tasks. You need to complete the all of the tasks in this topic in consecutive order to complete the entire wizard. The installation tasks include:
After you download the software package to your computer, navigate to the folder and then double-click the Device Manager executable installation file to start the Setup Wizard.
When the wizard starts, you set the language and then read and accept the End User License Agreement. After these two steps, on the Choose Components page, click to clear Database server to disable installation of the PostgreSQL database.
After you select your components, on the Choose Install Location page, leave the default install location and then click Install. Citrix recommends that you use the default location to install Device Manager.
Device Manager requires a license. For more information about licenses for Device Manager, see Obtaining and Installing Licenses. You upload the .crt license file from your computer. When the upload is complete, the license details appear in the XenMobile Device Manager License dialog box.
You need to configure the Device Manager settings to connect to your database. In the Configure database connection dialog box, you select the SQL Server database. You provide the database name or use the default value. You need to complete the following information, as shown in the following figure:
After you configure the database connection, you then enter the keycode for Crystal Reports.
On the Crystal Report Java Reporting Components configuration page, to leave a watermark on the reports, leave the keycode blank. Or, to remove the watermark, enter your keycode for the product.
When you configure the connection between the Device Manager agent and the Device Manager server, you can configure the following connectors, which require the same information but serve different purposes:
When you configure connectors, you set the following parameters:
Device Manager supports root, server, and APNS certificates. Root certificates enable Device Manager to communicate with other XenMobile components. Server certificates enable secure communication between Device Manager and devices.
The installation wizard prompts you to install a root certificate from a Certificate Authority (CA) first and then the server certificate. For each certificate, you provide the following information:
For root certificates, you need to provide the common name for the CA that issued the root certificate. Leave the default name to associate it with the creation of the CA component and certificate. If you change this field, your devices may not receive the proper chain of certificates and will not be able to enroll.
For secure server certificates, you need to include the IP address or FQDN that is in the certificate. Users connect by using the IP address or FQDN contained within the certificate.
To allow users to connect from iOS devices, you must install an APNS certificate from Apple. When you install the certificate on Device Manager, you enter the associated private key password used to generate the original Certificate Signing Request (CSR) in the field in Private key password.
In Certificate file path, specify the file system location of a pre-authenticated APNS certificate file that you download and convert to PKCS#12 format from the Apple iOS Developer for Enterprise portal.
On the Configure tunnel port(s) used by remote support page, define the port range used by remote support for Android and Windows Mobile devices. The default is port 8081.
To connect to the Device Manager web console, you need to configure an account with the administrator role.
On the Extended management of the users page, you enter the administrator's name and password. After you enter the values, you can check the user name in Active Directory.
After you configure the administrator user and password, you can finish the installation wizard.
After you finish the wizard, you should do the following:
You use Active Directory with Device Manager to manage groups of users, not individual user accounts. Device Manager supports the following sources of user account information:
You can perform the following actions in Device Manager for LDAP connections:
When you create a new LDAP connection, you configure the LDAP directory settings and then you import a signed secure certificate. When you define the connection parameters, you need to grant the following rights to the Search User service account:
You can also map the LDAP directory attributes to the Device Manager Repository database. If you do not modify the default settings, Device Manager binds automatically to the LDAP directory. You can specify the base DN that defines the LDAP directory groups that are imported to Device Manager.
If a patch has been issued to resolve a problem that applies to your situation and Device Manager implementation, you may download one or more appropriate patches for your system.
Patches follow the naming convention of 'a_patch_###_xxxx.jar' where ### signs are the version release number for Device Manager and xxxx refers to the patch number.
To install the patch, copy the file 'a_patch_###_xxxx.jar' to the following directory %systemroot%\Program Files (x86)\Zenprise\ZenpriseDevice Manager\tomcat\webapps\zdm\WEB-INF\lib or the directory in which you installed Device Manager.
After you copy the file to the directory, restart the Device Manager service.
You upgrade the Device Manager server through an in-place upgrade process. The XenMobile Device Manager Setup wizard updates your existing Device Manager installation and database in one step.
XenMobile 8.7 supports direct upgrades from XenMobile 8.6 and XenMobile 8.5. To upgrade from earlier versions of XenMobile and Zenprise, you must first upgrade to XenMobile 8.5.
For details, see To perform a full manual backup of Device Manager server.
For details, see Device Manager System Requirements.
Backing up your Device Manger server installation and core application file system directory is crucial to a good disaster recovery or business continuity plan. This section describes backing up and restoring Device Manager.
You can back up Device Manager by using the following methods:
If you want to restore Device Manager, you also use pgAdmin or Microsoft SQL Server Management Studio.
To back up a default installation of the Device Manager server, you stop all services and make a copy of the entire application directory on the server.
Another method of backup for Device Manager server is to copy the application directories required for restoration and also perform a native SQL database server backup by using the default PostgreSQL utility pgAdmin. For a Microsoft SQL Server database installation, use the Microsoft SQL Server Management Studio application and follow the instructions provided by Microsoft or your database administrator to back up your database according to your needs. The following steps will guide you through the process using the default PostgreSQL pgAdmin III utility only.