How to block OS updates in the Android Device?

How to block OS updates in the Android Device?

As IT administrators, there exist multiple situations in which limiting OS updates on  Android devices is necessary. A few potential scenarios include:
  • The latest OS might not be entirely compatible with critical enterprise app(s), leading to bugs and problems.
  • Simultaneous updates on numerous devices could impact the bandwidth of the enterprise network.
  • Glitches in the newest OS might hinder the proper functioning of enterprise apps.

Blocking the operating system updates isn't within the MDM capability, as these updates are managed by Google Android. However, we can  postpone the operating system updates on Android devices

Pre-requisites
Android devices must be running Android 6.0 or later versions and must be provisioned as Device Owner


Process for modifying the OS update through the WeGuard Enterprise Portal

  • Login to the WeGuard Console and click on "Policy Groups"


  • Choose the Policy.


  • Go to "Security", and find "System Updates'' on the right. By default, it shows a drop down with Types of Updates


  • Click on the drop down and you will see the options Unspecified, Automatic, Windowed and Postpone.


  • Let’s see what happens when each one is selected:
  • Unspecified: Triggers update prompts until installations are complete. Opting for the Unspecified policy prompts users to update their OS, granting them the choice to proceed with installation.
  • Automatic: Installs system updates upon availability without user interaction, bypassing potential delays.
  • Windowed: Updates install daily within user-defined window (0-1439 minutes after local midnight), no user interaction.
  • Postpone: Defers system update installation for 30 days. After this period, a notification prompts the user to install updates. The installation is necessary once the 30-day duration ends.

  • Admins choose a preferred option and click "SAVE AND CONTINUE" to apply the chosen policy to devices




We hope this article was useful. Thank you for reading.
For more WeGuard insights, please explore the Visual Knowledge-base Series
For more details, please visit https://www.weguard.com
If you need any help on this, do call up WeGuard Support at +1(737) 931-1410 Ext. 102 or contact WeGuard Support Email or Initiate Chat



    • Related Articles

    • Device Security Features - What is Device Hardening?

      ​​Hello and Welcome to WeGuard Enterprise Visual Knowledge-base Series. In this KB article, We will explain how to harden your device for security measures.  ​ We will discuss the process of securing a device by reducing its surface of vulnerability. ...

    • Managing Device Password Policies and Enforced Resets on Android Devices

      WeGuard provides administrators with two levels of password management: Restrictions, which define the rules for user-created passwords, and Enforcement, which allows an administrator to push a specific password to all devices in a policy group. This ...

    • Configuring Location (GPS) Settings on Android Devices

      Administrators can remotely manage Location (GPS) settings on Android devices via the WeGuard Console. By setting the location status to ON, OFF, or NONE, organizations can ensure compliance with security policies while optimizing operational ...

    • Android Device Removal and Unenrollment Guide

      IT admins need to delete devices from the organization that are no longer in use or no longer supported. To streamline this process, WeGuard provides the option to remove the MDM with or without resetting the device. This document explains how to: ...

    • System Applications - How to add custom launcher for dialer (phone) application?

      Hello and Welcome to WeGuard Enterprise Visual Knowledge-base Series. In this KB article, We will explain how to add a custom launcher for native dialer (phone) application on WeGuard Enterprise Portal. Procedure explained in this article is written ...