Configuring General System Settings

Sets Avalanche so that profiles cannot be applied at the My Enterprise level. This option is only available to administrator users.

Logs the user out after the set number of minutes of inactivity. This option is only available to administrator users.

Sets how often the page refreshes. This option is only available to administrator users.

Number of days an alert is displayed in the Current Alerts panel.

The number of alerts to display.

Maximum number of alerts to store. Alerts are stored in the database on the Enterprise Server. This option is only available for administrative users.

Provide settings for an email server so that Avalanche can send email when alerts are generated. Provide the address of the email server, a username and password to access it, and the port it listens on. If desired, you can specify a reply-to address or an address that the message will be sent from.

Enables Edit Lock to prevent conflicts between users who modify the same item at the same time. If a user is editing an item (such as a profile), he has a limited amount of time to make and save his changes before the edit lock times out. When the edit lock times out, a prompt will appear asking if he wants to extend the edit lock. If he does not respond to the prompt, the Edit Lock will be canceled, changes will not be saved, and other users will be able to edit the item.

Sets the amount of time the user has before the Edit Lock prompt appears.

Sets the amount of time between when the prompt appears and when the edit lock is canceled.

If you want to configure the maximum threshold for enterprise server messages allowed in the backlog, type the number of messages in the text box under Message backlog. If the spillover threshold is reached, the device servers are throttled and further messages are stored in a file to disk until the backlog is reduced. When device servers are throttled, they will no longer send device statistics updates to the enterprise server. After the backlog has been reduced, messages are pulled from the store file back into the log and the device servers are no longer throttled. This option is only available to administrator users.

For information on audit logging, see Configuring Audit Logging. This option is only available to administrator users.

Changes the display language for the Avalanche Console. This setting only affects the Console for the user who configures it.

Changes the time zone affecting the times displayed in the Avalanche Console. This setting only affects the Console for the user who configures it.

Sets the URL template structure for accessing the Data Repository. By default, this is set to https://*/AvalancheDataRepository.

If the Data Repository URL Template is altered, all File payloads must be saved again to update to the new file location.

Sets a password that is required by the device in order to remove payloads from iOS devices. This password also allows an Android device user to override app restrictions.

Forces Smart devices to check in to the Avalanche server at the specified interval. Performing an Update Now command for a device does not reset the interval.

If this option is not enabled, a Smart device checks in only when the following actions are performed:

•An Avalanche Console user selects a device and clicks Update Now.

•An Avalanche Console user performs a deployment and selects the Request immediate check-in for all Smart devices option.

•The device user re-enrolls or uses the Enabler to Sync.

The credentials used for the LDAP integration services associated with LANDESK Mobility Manager. In order to use these options, you must select the LDAP for Login and Enrollment option within Authentication Options as well as the Enable User Targeting option. You must provide the credentials to a LANDESK administrator account to facilitate mobile device management in Mobility Manager. You must also provide this information if you want to use LDAP credentials to log in to Avalanche. For more information, see LANDESK Mobility Manager.

•LDMS Core Server. The address and credentials to access the LDMS core server.

•LDAP Account. The address and credentials to access the LDAP server. Required to enroll Windows 8 devices.

•Cloud Services Appliance. If you are using a CSA to facilitate communication between the Avalanche servers and the LDMS core server, enable the checkbox and provide the publicly available address of the CSA. An address must be entered here if you wish to enable secure communication with wrapped apps.

Displays a message on the login screen and at the top of the Console for all users.

Enables Avalanche to communicate wirelessly with Smart devices through the use of service-specific data encryption.

•Google GCM. Enter a Google Project Number and API key to allow Android devices to communicate directly with your Smart device server. These details are required for Android devices even if you only use ANS Enablers. To enable communication with Android devices, see GCM for Android.

•Apple iOS. Upload a signed APNS certificate and enter the password associated. To enable communication with iOS devices, see APNS Certificate for iOS.

Allows Avalanche to communicate wirelessly with Smart and mobile devices using SSL certificates. This requires uploading a certificate, entering the password associated with it, and typing the Smart device server address. For information on creating a certificate, see SSL Certificates.

Sets connection options for Remote Control on Android devices. The server address can be specified by IP or hostname. The HTTP protocol should be entered in the Server Protocol field rather than included with the server address. By default, this field is blank.

Allows Avalanche to suspend or throttle communication between the enterprise and device servers. To configure server-to-server communication, see Restricting Server-to-Server Communication.

Avalanche allows Console users to log in to the Avalanche Console using the same information they use to log in to the network (with an LDAP/Active Directory server). It is disabled by default.

•Integrated Login Disabled. If you don't have a LANDESK Mobility Manager account or server, choosing this option will not ask for authentication credentials. Selected by default.

•LDAP. The address to access the LDAP server. To enable SSL security, select LDAPS.

•LDAP for Login and Enrollment. The address and credentials for the LDAP core server and account. Required to enroll Windows 8 devices and for integration with LANDESK Mobility Manager.

Specifies enrollment credentials to be used with bulk enrollment of Windows Embedded Handheld 8.1 devices on Avalanche. This method of enrollment does not require LDAP credentials. For more information on bulk enrollment, see Windows Phone Bulk Enrollment.

•Enrollment User Email. The email address to be used for enrolling multiple Windows Embedded Handheld 8.1 devices. The email domain entered here must be a domain added to the E-mail domain panel, or else Windows devices cannot enroll.

•Enrollment Password. The password associated with the email address used in the Enrollment User Email field.

•Confirm Password. Confirms the enrollment password.

The prov.xml file must be modified on each device to include bulk enrollment credentials. The following text must be added to the file with your own substitutions for each value:

<characteristic type="EnterpriseExt">

<characteristic type="MDM">

<parm name="Server" value="https://aod.wavelink.com/EnrollmentServer/DeviceEnrollmentService.svc" />

<parm name="Username" value="[email protected]" />

<parm name="Password" value="password" />

<parm name="EnableDeviceEnrollment" value="true" datatype="boolean" />

</characteristic>

</characteristic>

The values for the Server, Username, and Password in System Settings must match the credentials included on the prov.xml file.

If the provisioning file is added or altered after initially booting the Smart device for the first time, the Windows Embedded Handheld device must be reset and go through OOBE provisioning again. Once set up, the Smart phone enrolls in Avalanche based on the bulk enrollment credentials and automatically appears on the Inventory page.

For support information about accessing and modifying the provisioning file for Windows Embedded Handheld 8.1 devices, visit the Microsoft Developer Network website.

Generates a public and private key pair file for use in the Apple Device Enrollment Program (DEP). When the Generate button is clicked, your browser automatically downloads the certificate file. Entries for the certificate and key files are added to the table below, in addition to any other previously-generated certificates and keys. All previously-generated certificates and keys can still be downloaded.

Generating a certificate and key is required to set up a mobile device management (MDM) server on the Apple Console. For more information, see Apple Device Enrollment Program.

Adds custom links to the Tools menu for direct access to other pages. To add links, see Creating Links in the Tools Menu.

Adds a Simple Certificate Enrollment Protocol (SCEP) for issuing certificates to network devices. Connecting with a Certificate Authority through SCEP allows you to distribute and revoke active certificates, enroll certificates, and query certificates on managed mobile devices. The credentials used here to connect with a Certificate Authority are created as part of the SCEP setup process.

•Name. A label to identify the Certificate Authority being used.

•Description. A brief description of the Certificate Authority being used or what devices are to use certificates from it.

•SCEP URL. The IP or hostname for your SCEP server, as defined during the Microsoft SCEP server setup. This URL must be HTTPS. For example, an SCEP URL would look like:

https://scep.domain.com/CertSrv/mscep/mscep.dll

•Static Challenge. A static password used when sending certificate requests to a Certificate Authority. When a device communicates with the Certificate Management Server, it transmits this password for each authentication.

•Subject name. This field is the common name for each issued certificate. It is not currently editable and defaults to the serial number of the device being issued.

•Private key length. Defines the length of private keys devices must have to request certificates from the SCEP server. You can set this to 1024 or 2048. This length is typically set during the Microsoft SCEP setup process.