Information about client software available for deployment using Mobility is stored in a manifest file.
It is normally hosted in AWS, along with the setup files for the software, however it is possible to host this on premise with the manifest file and your own web server. The steps for doing it are described here. These instructions are also contained in the download package - see the file hosting.docx.
Current Files can be downloaded here: Software Deployment Files
Hosting the deployment manifest file and software packages
Information about client software available for deployment using Mobility is stored in a manifest file. It is
normally hosted on Amazon S3, along with the setup files for the software. It is possible to host this on premise with the manifest file and your own web server. The steps for doing it are described here.
The supported client versions for Mobility are 10.51 and newer, for Locality it is 2.10 and newer
Setting up the deployment manifest files and software setup files on a web server
- The simplest way to set up a web server is to set up Internet Information Services (IIS) on the Windows Server hosting the Mobility server. The default installation of IIS is sufficient.
- Expand the provided ZIP file which already contains the latest versions of Locality and Mobility along with the corresponding Manifest file
- Move the extracted “deploy” folder to your web server directory. For example \inetpub\wwwroot\deploy
- Ensure that following file structure exists:
Changing the deployment resource location
By default the deployment resource location points to Amazon S3. You must change a server setting to point to the web server you have set up with the deployment content.
- In the Mobility console, select Server Settings from the Configure menu.
- Select the Deployment – Resource Location setting and enter the URL of the deploy directory on your web server. For example: http://yourserver/deploy
Testing your content
Confirm you see the latest software when you go to the Create a deployment page. Test a deployment to a single device to confirm the client can download the setup image from the IIS server.