Knowledgebase : Faronics Products
This document will detail the process of enrolling an Android Device as Work Owned device in the Faronics MDM solution.

Step 1 – Ensure that your device supports Android for Work.

Some devices may not provide full support for Android for Work, in general most newer devices from major manufacturers will. To check you can look at the link below for a list of devices that Google certifies as supporting Android for Work;
If the device is not listed in the list of devices supported you may still be able to enroll the device provided that the device manufacturer provides full support for Android for Work in the device and the device is running Android 5.1 or higher.

Step 2 – Reset your device.

Devices can only be added to the MDM solution as a work owned device during the initial setup. To begin initiate a reset of the device by opening the settings on the device and browsing to General Management  Reset -- > Factory data reset.

Step 3 – Follow device prompts to setup the device stopping at the screen where you are asked for your Google Account details.

In the screen where you would normally enter in your email address enter in the value afw#deepfreeze as shown in the screen shot below.

Google Play Services showing afw#deepfreeze code.

Click Next.

Step 4 – Accept the installation of the Deep Freeze MDM application.

Next the Deep Freeze MDM application will be installed on the device, click Accept on the prompts that are shown to allow the App to be installed.

MDM Package Installation

Step 5 – Enter in your Enrollment Code to complete the installation process.

The next screen will prompt you for your enrollment code, this code will be the unique identifier that links your device to your MDM solution. Enter the enrollment code in the box provided and click on Enroll Device.

MDM Enrollment Code

After clicking on Enroll this Device the device will prompt you to acknowledge the installation of the work profile.

Ack_MDM Install


Step 6 – Allow usage access and Mobile Data Usage history for the Deep Freeze MDM application.

Next the Deep Freeze MDM Application will open showing any potential alerts that need to be addressed such as the Mobile Data Usage History permission. 

Select the appropriate prompts to allow the MDM application access to Mobile Data History.

Once enabled enrollment is complete and the device will begin installing any applications assigned to it.

Deep Freeze Cloud is designed to minimize the impact on your network in order to reduce the consumption of resources on your internet connection. Once installed the Cloud Agent on each workstation will send a heartbeat to our cloud servers to check for any updated policies that need to be applied. This heartbeat will normally occur when the computer boots up and then once every 6 to 8 hours after the system is started. This heartbeat, provided that no actions are being taken on the client, is about 13kb in traffic.

Deployment of the Cloud Agent will require that the Cloud Agent be downloaded and that the various product installers for your policies be downloaded for installation. In total a policy that enables all products currently would require approximately 108mb of data to be downloaded for installation as well as a full set of Antivirus Updates.

Antivirus updates will vary in size and frequency as they are updated to include changes to support the detection of new threats, at this time a full set of antivirus updates is about 235 mb and incremental updates generally are about 250 kb per update.

In the event that there are events on the workstation that need to be reported to the Cloud Service (Malware detection, Anti-Executable Violations, Power Saving Results) additional traffic will be consumed. Some common tasks are listed below to provide an idea of the expected traffic loads.

  • Power Saving Event Occurs (Monitor off / Sleep / Wake Event) – 1.5kb
  • Configuring Deep Freeze (With a maintenance mode) – 20kb
  • Assigning an Antivirus Policy (With common settings) – 35kb
  • Disabling / Enabling Active Protection in Antivirus – 4.9kb
  • Assigning an Anti-Executable Policy (With 200 files in the policy) – 99kb

Working with workstations through Deep Freeze on Demand does incur additional traffic, as shown below;

  • Reboot 1 workstation - 6 kb
  • Reboot 3 workstations - 16 kb
  • Shutdown 1 workstation - 6 kb
  • Shutdown 3 workstations - 16 kb
  • Reboot Thawed 1 workstation - 6 kb
  • Reboot Thawed 3 workstation - 16 kb
  • Reboot Frozen 1 workstations - 7 kb
  • Reboot Frozen 3 workstations - 15 kb
  • Reboot Thawed Locked 1 workstation -6 kb
  • Reboot Thawed Locked 3 workstations - 15 kb
  • Send Message (default) 1 workstation - 4 kb
  • Send Message (default) 3 workstations - 8 kb
  • Lock Keyboard and Mouse 1 workstation - 9 kb
  • Lock Keyboard and Mouse 3 workstations - 23 kb
  • Unlock Keyboard and Mouse 1 workstation - 8 kb
  • Unlock Keyboard and Mouse 3 workstations - 23 kb

Based on this information it is possible to calculate out the expected data load for each workstation based on the expected number of actions that will be taken on a workstation over time.

With no other actions taking place on the client systems administrators could expect to see about 60 kb of traffic from each workstation managed through the Cloud Console in a average work day in addition to the Antivirus updates applied to the workstations.