Creating and Configuring a Smart Device Server Profile

A smart device server profile allows you to configure push notifications, HTTPS configuration, and smart device administration. A smart device server profile can have its status set to enabled or disabled. The profile must be enabled before you can apply it. The home location for the profile is the location you have selected when you create the profile.

A smart device server may have more than one profile applied to it.

You must have one smart device server profile for each smart device server if you use the Central File Store, because the SDS public address must be configured for each smart device server in order to use the Central File Store correctly.

To create a smart device server profile:

1.From the Profiles tab, click New Profile.
The New Profile dialog box appears.

2.Click Smart device server.

3.Type the name of the profile in the Name text box and configure the profile settings.

A smart device server profile has the following configuration options:

Push Notifications	Enables Avalanche to communicate with smart devices through the use of service-specific data encryption. If you only use the ANS enabler, then you do not need to complete these fields. •Google GCM. Enter a Google Project Number and API key to allow Android devices to communicate directly with your smart device server using GCM. For more information, see Configuring GCM for Android. •Apple iOS. Add a certificate and create a password to allow iOS devices to communicate with your smart device server.
HTTPS Configuration	Allows Avalanche to communicate with 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.
Smart Device Administration	•Smart Device Client Administrator Password. This password allows an Android device user to override app restrictions. •Automatic Smart Device Check-in. Define how frequently smart devices check in to the server for new configurations or files. If you do not enable the option, devices default to checking in every 24 hours. Performing an Update Now command for a device does not reset the interval.
Device Folder Assignment	Define how devices are assigned to folders after they enroll. If you do not configure this option, it inherits the settings from the nearest profile assigned to a parent location. •Static by user. The device is placed in the folder associated with its enrollment rule when it first enrolls. Then users can move it to the desired folder. The device stays in that folder until a user moves or re-enrolls it. •Dynamic by selection criteria. When devices check in to the server, the server evaluates the selection criteria of the folders and puts each device into the first folder with matching selection criteria. The server does this each time a device checks in, so if the folders or selection criteria change, the device would automatically be moved to the first matching folder when it checks in. Even if a device is manually moved to a different folder by an administrator, it will be moved to the first matching folder the next time the device checks in.
UDP Service Discovery	Listens for devices enrolling by bulk enrollment and broadcasts the server location for those devices. For more information about bulk enrollment, see Connecting Android Devices to the Avalanche Server.

This page refers to an older version of the product.
View the current version of the User Guide.

The topic was:

Inaccurate

Incomplete

Not what I expected

Other

Privacy and Legal