1. Configuration priority scheme

Device configuration can be handled using a few ways. These ways are layered based on priority.

Highest priority settings (overruling all other setting) is on the device itself. Currently supported direct device settings (when supported by device type):
 - OS version
 - hostname

Second highest priority settings
 - Assigned configuration profile

Lowest priority settings
 - Installed OS version defaults

This scheme gives the user possibility to apply a few device-individual settings on top of the onfiguration profile, which may be shared between a number of devices.

2. Data availability and configuration timing

When device first registers to the system, it's configuration is not available right from the start. There are a few things the device is sending into the system:

 - device configuration request
   - first request not accompained with any metrics or data
 - device defaults
   - after successful configuration the defaults are sent (one-time action) together with first information data
 - 'small' information package
   - sent on every cycle
   - this contains mainly metrics data telling device load, temperature, memory and some statistics
 - 'big' information package
   - sent on every 'big' cycle - by default once per 6 small cycles
   - contains configuration

Device data timing - after agent installation (defaults):

 <1 minute: registration request
 6 minutes: basic device data available (Arriving -> Synchronized)
 30 minutes: device initial configuration available

As for pushing a configuration profile to the device the fastest timing could be:

 <1 minute: registration request
 6 minutes: basic device data available (Arriving -> Synchronized)
 11 minutes: configuration profile sent to device (Synchronized -> Sync pending)
 30 minutes: device configuration SYNC status confirmed (Sync pending -> Synchronized / Sync Error)