Creating and Configuring a Mobile Device Server Profile

Uses AES encryption for information. Only Enablers that support AES encryption (Enabler 5.0 or newer) will be able to connect to the server when strict transport encryption is enabled.

Forces mobile devices to communicate with a single known server. Mobile devices must first connect to the network through a serial connection (RS232) to receive information about the server with which they are allowed to communicate. When you enable this option, the mobile device will challenge any mobile device server attempting contact for a password. If the mobile device server does not have the correct password, the mobile device will not allow a TCP/IP connection.

Allows only the specified number of devices to update simultaneously.

Allows devices to be dynamically reassigned to a folder with matching selection criteria each time the device checks in with Avalanche.

The mobile device server assigns devices to specific groups and folders based on selection criteria. The properties of a device determine its folder placement on Avalanche, and thus the payloads it receives. By selecting this option, each time a mobile device checks in, it is assigned to a folder with selection criteria matching the device's properties. If the device properties haven't changed, it stays in the same folder. If they have changed, the device is reassigned to a folder with the new selection criteria and receives the payloads associated with that location.

If this option isn't selected, when a device is assigned to a group and folder, it remains in that location even if the device's properties are altered to match another folder's selection criteria.

The mobile device server assigns each device a terminal ID the first time that the device communicates with the mobile device server. The number the mobile device server selects is the lowest number available in a range of numbers you can configure.

You also have the option to use a C‑style format to create a template for the terminal ID range. For example, Seattle‑%d would generate IDs such as Seattle‑4, and Seattle‑%05d would generate IDs such as Seattle‑00004.

To change a terminal ID that has already been assigned to a device, click Edit Terminal ID on the Properties tab of the Mobile Device Details dialog box.

The current Avalanche log file is saved as Avalanche.log to the <Avalanche Installation Directory>\Service directory. Once the current log file reaches the maximum size, it is saved as Avalanche.log.<num> (where <num> is a number between 000 and 999), and a new Avalanche.log file is created.

The following logging options are available on a mobile device server:

Critical. Writes the least information to the log file, reporting only critical errors that have caused the mobile device server to crash.

Error. Writes errors that are caused by configuration and/or communication problems and critical messages to the log file.

Warning. Writes critical messages, error messages, and indicates possible operational problems in the log file.

Info. The recommended logging level. This logging level documents the flow of operation and writes enough information to the log file to diagnose most problems.

Debug. Writes large amounts of information to the log file that can be used to diagnose problems.

Max Log Size. Specifies the maximum size (in KB) of the log file before beginning a new file.

Allows the server to terminate the license lease after the specified time period without contacting the device. If this option is disabled, the server will attempt to contact any devices that have not communicated with the server in the configured time period. If the device does not respond, the license lease will be terminated.

Configures the number of seconds before the device advances to the next server. Ensure the Server Advance Delay setting is a multiple of the Server Connect Timeout setting. For example, if you have your Server Connect Timeout set to 10 seconds and the Server Advance Delay set to 60 seconds, the mobile device will attempt to contact the server six times (every 10 seconds for 60 seconds).

Causes the mobile device server to discard software profile data collected from the devices without sending it to the Enterprise Server.

When a package’s .PPF file specifies files that are to be downloaded from Home, this option provides the path to Home on the machine local to the mobile device server. If no path is specified, Home is defined as the mobile device server installation directory.

Causes the mobile device server to verify the existence and state of each file of each package individually rather than consulting the meta-file which would normally provide information on those files.