Management groups rules
Rules used to create Management Groups, and which connectors that provide the data to support the rules.
For details of how to create and use Management Groups, please refer to Management Groups.
The number of rules that a single Management Group can contain is variable because of many factors including SQL Server version, server configuration and rule type used. 1E recommends not exceeding 10,000 rules per rule-based Management Group.
|
Rule name |
Description |
SCCM |
ServiceNow |
1E Platform |
OracleLMS |
BigFix |
BigFixInv |
Intune |
vCenter |
WSUS |
|---|---|---|---|---|---|---|---|---|---|---|
|
Device ADSite Name |
AD Site the device is connected to. |
|
|
|
|
|
|
|
|
|
|
Device Assigned Cores |
Maximum number of assigned cores for the device. Derived from |
|
|
|
|
|
|
|
|
|
|
Device Classification |
Classification of the device. For example, Test, Production or Development. Production is the default. |
|
|
|
|
|
|
|
|
|
|
Device Computer Name |
Hostname of the computer. |
|
|
|
|
|
|
|
|
|
|
Device Criticality |
By default, Device Criticality is set as one of the following, as described in Using Device Criticality.
|
|
|
|
|
|
|
|
|
|
|
Device Domain Name |
Domain the device is installed on. |
|
|
|
|
|
|
|
|
|
|
Device Inventory date |
Date that the device was last updated. |
|
|
|
|
|
|
|
|
|
|
Device Matched Device Type |
Normalized device type based on chassis type. For example Desktop. |
|
|
|
|
|
|
|
|
|
|
Device Matched Family |
Normalized family of the device. For example, Aspire. |
|
|
|
|
|
|
|
|
|
|
Device Matched Model |
Normalized model of the device. For example, A30. |
|
|
|
|
|
|
|
|
|
|
Device Matched Socket count |
Normalized socket count of the device. For example, 1. |
|
|
|
|
|
|
|
|
|
|
Device Matched Vendor |
Normalized vendor name of the device. For example, Acer Inc.. |
|
|
|
|
|
|
|
|
|
|
Device Netbios Domain name |
NetBIOS version of the device's domain name. |
|
|
|
|
|
|
|
|
|
|
Device Netbios Name |
NetBIOS version of the device name. |
|
|
|
|
|
|
|
|
|
|
Device OS |
The normalized product title of the OS that is running on the device. |
|
|
|
|
|
|
|
|
|
|
Device Purchase date |
Date that the device was purchased. |
|
|
|
|
|
|
|
|
|
|
Device Serial |
Serial number of the computer. |
|
|
|
|
|
|
|
|
|
|
Device User Primary Username |
The primary user of the device. |
|
|
|
|
|
|
|
|
|
|
OU Name (Deprecated) |
Name of the OU that the device is in. For example Sales. All OUs with the same name will be used, therefore the OU Path rule should be used instead. The OU Name rule is deprecated and should be re-defined using OU Path. This rule is deprecated, which means it will continue to work until it is removed in a future version of 1E. |
|
|
|
|
|
|
|
|
|
|
OU Path |
The name or path of the OU location in the AD hierarchy, using pipe | as the delimiter. For example, to get all the computers in OU=Sales, OU=Workstations, DC=acme, DC=local you can either specify Sales or - if there is more than one OU called Sales in the AD structure - specify the whole path acme.local|Workstations|Sales. Note that the DC and OU parts of a distinguished name are treated differently. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Chip Module Count |
Normalized chip module count of the processor. For example, 1. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Core Count |
Normalized core count of the processor. For example, 2. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Family |
Normalized family name of the processor. For example, Athlon 64 X2. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Model |
Normalized model name of the processor. For example, 3250e. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Processor Type |
Normalized type of the processor. For example, Desktop. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Release Date |
Normalized release date of the processor. For example, 31-03-2008. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Speed M Hz |
Normalized speed of the processor. For example, 2.100. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Threads per Core |
Normalized threads per core of the processor. For example, 1. |
|
|
|
|
|
|
|
|
|
|
Processor Matched Vendor |
Normalized vendor name of the processor. For example, Advanced Micro Devices, Inc. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Colloquial Version |
Software colloquial version contained in the inventory source. For example, 2012. This will usually be blank. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Edition |
Software edition contained in the inventory source. For example, Standard. This will usually be blank in SCCM unless the relevant MOF extensions have been installed. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Is Partial Version Matched |
Flag that indicates whether the software title was partial matched or not (TRUE/1) or not (FALSE/0). |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched Colloquial Version |
Normalized software colloquial version. For example, 2016. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched Edition |
Normalized software edition. For example, Standard. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched End of Support |
Normalized software end of support date that of that version. For example, 31-10-2008. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched is Bundle |
Flag indicating whether the normalized software is a bundle (TRUE/1) or not (FALSE/0). |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched Is License Required |
Flag indicating whether that normalized software title requires a license (TRUE/1) or not (FALSE/0). |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched Release Date |
Normalized software release date of that version. For example, 31-10-2008. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched Title |
Normalized software title. For example, Office. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched Vendor |
Normalized software vendor name. For example, Microsoft Corporation. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Matched Version |
Normalized software version. For example, 10.2.233. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Title |
Software title contained in the inventory source. For example, Office Standard en_pack. |
|
|
|
|
|
|
|
|
|
|
Product Catalog UN Standard Product Service Code |
UNSPC code of the normalized software title. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Vendor |
Software vendor name contained in the inventory source. For example, Microsoft. |
|
|
|
|
|
|
|
|
|
|
Product Catalog Version |
Software version number contained in the inventory source. For example, 10.2.233. |
|
|
|
|
|
|
|
|
|
|
Product Install Date |
Date that software installation was installed according to the inventory source. |
|
|
|
|
|
|
|
|
|
|
Product Instance Name |
Instance name if used by a product, for example MSSQLSERVER for SQL Server. |
|
|
|
|
|
|
|
|
|
|
Product Last Used date |
Date that software installation was last run according to the inventory source. |
|
|
|
|
|
|
|
|
|
|
Product Usage Category |
Usage category assigned to a specific installation of a normalized software title. Potential categories are:
|
|
|
|
|
|
|
|
|
|
