Important: Part of a series outlining the deployment of a production on premise Symantec Mobility: Suite solution. This is meant to be used supplementary to the published Mobility: Suite Administration and On-premise Installation guides. If there are any recommendations made in this walkthrough which contradict the above mentioned guides, use the recommendations in the guides
To be followed after completing HOWTO110252, HOWTO110253, HOWTO110256 and HOWTO110255.
UPDATE For Mobility 5.3 or later: Install three required packages by entering the following as root:
sudo yum -y install unzip libtool-ltdl mysql
1. Once the system restarts, log back into the console, as root.
2. Install wget by entering the following:
sudo yum –y install wget
3. The Symantec Mobility ISO may be either uploaded to the FE see How to transfer files to a Linux machine or downloaded using wget…
4. Download the Symantec Mobility: Suite ISO by typing the following, as root:
sudo wget <Direct link to the Symantec Mobility 5.2 or later ISO> /tmp/symantec.iso
Note: To obtain a valid copy of Mobility: Suite, contact a Symantec Sales Engineer or Partner.
5. Create and mount the symantec.iso by entering the following two lines:
sudo mount –o loop /tmp/symantec.iso /mnt/iso
Note: In this step, the ISO name is symantec.iso, substitute the actual name and/or path to the ISO.
6. Change the working directory to the mounted location:
7. Verify the contents of the ISO were properly loaded by entering:
8. Write down the server’s IP address (if issued via DHCP) that is displayed after entering the following command:
9. After the ISO is successfully mounted, as shown above, continue to Installation Part I.
1. Begin the Mobility: Suite installation by entering the following, as root, from the mounted ISO’s location:
2. Ensure that Install Mobility Manager is selected and OK to continue.
Tip: Use the Tab and arrow keys to toggle the selection.
3. Agreeing to the Symantec Corporation terms will allow the installation to proceed:
4. Same for Java, as above:
5. Take note of the default directories and OK to continue:
6. Set the HTTP Configuration wizard port as 8000 (default) and Tab to OK to continue:
7. Select: I want to use my own production database option and OK:
Note: The local-trial-database is not recommended for a production environment. For a Proof of Concept (POC) managing less than 250 devices, the trial database will be sufficient.
8. For deployments managing less than 15,000 devices select Local trail server, otherwise an off-box RabbitMQ server and fall-over server must be created see HOWTO107258
Note: The local trial RabbitMQ instance may only be accessed from the local host, a future off-box RabbitMQ server may be added at a later time.
9. After reviewing the configuration, arrow-down to select Start Installation and OK to continue.
10. The primary installation will take about 10-30 minutes to complete.
11. Do not cancel this process. When the script completes the following line will appear:
Please configure your Mobility Manager by navigating your internet browser to
Installation cannot finalize until configuration is complete:
Note: If any errors in this process will be logged to /var/log/nukona/appcenter-install.log. If the above is not shown, reboot the server and repeat parts IV & V. To troubleshoot the Installation Part II section see
12. Only after the terminal shows message from the previous step, continue to Installation Part II: The Configurator.
The following items have been included into this article as search terms: