Creating and Configuring a Smart Device Server Profile

A smart device server profile allows you to configure push notifications, HTTPS configuration, smart device administration, and device folder assignment. 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.

Smart device profiles have the selection criteria for the profile built in to the payloads, and it cannot be configured. For example, an Android payload automatically has selection criteria that means the payload only goes to devices that have an Android OS. However, you can use additional selection criteria when the profiles are applied.

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. •Google Firebase Cloud Messaging (FCM). Add a Google-services file and service account file to allow Android devices to communicate with your smart device server using FCM. For more information, see Configuring FCM for Android. •Apple iOS. Add a certificate and create a password to allow iOS devices to communicate with your smart device server. For more information, see Obtaining an APNS Certificate for iOS.
HTTPS Configuration	Allows the smart device server to communicate with devices using SSL certificates. This requires uploading a certificate, entering the password associated with it, and entering the smart device server address. For more information, see Importing a Certificate for the Smart Device Server.
Smart Device Administration	•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. •Detect source address. Select if you want the source IP address for your devices reported in the IP Address field of the inventory. If this option is set to on, the router's IP address is reported. If set to Off, the device's IP address is reported. If set to Inherited, the setting configuration will be inherited from a parent folder's smart device server profile. (The device's IP address will always be reported in the Assigned IP Address field.)
Device Folder Assignment	Defines how devices are assigned to folders after they enroll. If you do not configure this option, the profile 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 as desired. •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 to those devices. For more information about bulk enrollment, see Connecting Android Devices.
Terminal ID assignment	Configure how terminal IDs for Android devices are determined. Android devices are assigned a terminal ID upon enrollment. Assigned IDs can be viewed from the device details page under properties. Currently, this feature only applies to standard Android devices, not Android Enterprise or iOS. The number the smart device server selects is the lowest number available in a configurable range. 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.