Using device criticality
Multi-tenant SaaS platform | Single-tenant SaaS platform
| On-premises platform
Overview
Device criticality is an attribute that defines a device’s importance within your organization. First, you must agree on the criteria for importance, ensuring all 1E users have the same understanding of criticality and how it should be applied. Criticality is set on devices using an instruction, as described in Setting device criticality below.
1E allows you to use criticality to define the following:
-
Rules to create Management Groups. Refer to Management Groups.
-
Coverage for instructions. For example, you can choose to target an instruction to be sent only to devices whose criticality is set to any one of the following:
-
Undefined (or not set)
-
Non-critical
-
Low
-
Medium
-
High
-
Critical
-
Criticality is displayed in a number of places:
Module |
Page |
---|---|
Experience Analytics |
|
Endpoint Troubleshooting |
|
Endpoint Automation |
|
Content Distribution |
|
Patch Insights |
|
Settings |
Setting device criticality
Device criticality is set using the instruction Set the criticality of my devices to <criticality> where <criticality> is selected from the list above.
In Endpoint Troubleshooting, type the instruction and then choose the desired criticality from the drop-down list. Select the coverage for the instruction and submit it. After approval, devices which match the specified coverage value will have their criticality set to the specified value. Any devices that do not have their criticality set are reported as Undefined or Not set.
There is a corresponding instruction called What is the criticality of my devices?.