Main: General
Attribute name |
Description |
Name |
This field defines the name of the Windows client enrollment rule item. This field is mandatory. |
Data source (connector) |
This field defines the connector or component whose data is automatically processed with this rule. For example, if Connector name = Active Directory, this Windows client enrollment rule is automatically applied to devices that have been found by Miradore's Active Directory connector. |
Status |
This field shows the status of the Windows client enrollment rule. A disabled rule doesn't have any effect to the environment. Status of a rule can be changed using the form tasks menu. |
Main: Enrollment actions
Attribute name |
Description |
Client deployer |
This field defines the client deployer that is used to deploy/enroll the Miradore's management client to the devices which match to the rule. This field is mandatory. |
Deployer account |
This field defines the account that is used to run the client deployer component. This field is mandatory. |
Main: Scope (for processing Active Directory connector data)
Attribute name |
Description |
Operating systems |
This table allows to select a list of operating systems by checking the appropriate check boxes. Miradore uses the list to determine whether or not the operations defined by this rule should be performed for a device detected by a connector. For example, if "Windows 7 Enterprise" and "Windows XP Professional" options are checked in the list, Miradore will apply the operations defined in this rule only to such devices that have either of the selected operating systems installed. The operations defined in the rule are not applied to devices that have some other operating system installed. The listed operating systems are reported by Microsoft Active Directory connector. |
Additional OS filter |
This field is an additional operating system filter and it can be used to expand the list of operating systems in the "Operating systems" field. On the other hand, this field can be used to set more accurate, customized operating system filter. In this field, you may use * as a wildcard character. For example: Windows Server * would mean that the rule was applied to all devices whose operating system's name begins with Windows Server. Use ; character to separate multiple values. For example: Windows Server 2008 R2 Enterprise;Windows Server 2008 R2 Standard |
LDAP path (include) |
This field allows to use LDAP path of devices to define the target devices to which the operations defined in this rule should be applied to. In this field, you may use * as a wildcard character. Use ; character to separate multiple values. For example: *Laptops*;*Servers* would mean that the device LDAP path must contain either part of the defined value "Laptops" or "Servers". |
LDAP path (exclude) |
This field allows to use LDAP path of devices to define the target devices to which the operations defined in this rule should not be applied to. In this field, you may use * as a wildcard character. For example: *OU=Laptops* would filter out all devices whose LDAP path contains part OU=Laptops. Use ; character to separate multiple values. |
Domain |
This field allows to use device domain to define the target devices to which the operations defined in this rule should be applied to. In this field, you may use * as a wildcard character. Separate multiple values with the ; character. If you leave this field empty, the rule is applied according to the other rules despite of the device domain. |
Last seen less than (days ago) |
This field allows to filter the rule's target devices according to "Last logon date" attribute retrieved from Microsoft Active Directory. For example, if last seen date = 7, only devices that have been modified within 7 days are included as rule targets. This field is mandatory. |
Include removed assets |
This field defines whether the operations defined by this rule are applied to such devices whose asset configuration item has been removed from Miradore but which still are detected by a connector or network discovery. |
Include assets with client status unknown |
This field defines whether the operations defined by this rule are applied to such devices that have an active asset configuration item in Miradore, but the online status of the installed management client is unknown. |
Include assets with client status unmanaged |
This field defines whether the operations defined by this rule are applied to such devices that have an unmanaged asset configuration item in Miradore. An asset is unmanaged when it doesn't have a management client installed. |
Main: Scope (for processing network discovery data)
Attribute name |
Description |
Subnets |
This field allows to define subnet(s) where this enrollment rule is applied to. Multiple subnets can be selected to this field. |
Last seen less than (days ago) |
This field allows to filter the rule's target devices according to the last inventory date of the device. For example, if last seen date = 7, only devices that have been inventoried within the past 7 days ago are included as rule targets. This field is mandatory. |
Include removed assets |
This field defines whether the operations defined by this rule are applied to such devices whose asset configuration item has been removed from Miradore but which still are detected by a connector or network discovery. |
Include assets with client status unknown |
This field defines whether the operations defined by this rule are applied to such devices that have an active asset configuration item in Miradore, but the online status of the installed management client is unknown. |
Include assets with client status unmanaged |
This field defines whether the operations defined by this rule are applied to such devices that have an unmanaged asset configuration item in Miradore. An asset is unmanaged when it doesn't have a management client installed. |
Main: Scope (for processing Antivirus connectors' data)
Attribute name |
Description |
Antivirus client group |
This field allows to define antivirus client group(s) where this rule is applied to. You may use * as a wildcard character when defining this attribute, Use ; character as a delimiter to separate multiple values in this field. If this field is left empty, the rule is applied to devices according to other rules despite of this particular attribute. |
Antivirus server |
This field allows to define an antivirus server where this rule is applied to. You may use * as a wildcard character when defining this attribute, Use ; character as a delimiter to separate multiple values in this field. If this field is left empty, the rule is applied to devices according to other rules despite of this particular attribute. |
Antivirus server group |
This field allows to define antivirus server group(s) where this rule is applied to. This field can be used with Symantec Antivirus products. You may use * as a wildcard character when defining this attribute, Use ; character as a delimiter to separate multiple values in this field. If this field is left empty, the rule is applied to devices according to other rules despite of this particular attribute. |
Antivirus product name |
This field allows to define names of antivirus products where this rule is applied to. You may use * as a wildcard character when defining this attribute, Use ; character as a delimiter to separate multiple values in this field. If this field is left empty, the rule is applied to devices according to other rules despite of this particular attribute. |
Last seen less than (days ago) |
This field allows to filter rule's target devices according to "Last check-in time" attribute retrieved from an antivirus system. For example, if last seen date = 7, only devices that have checked in within the past 7 days are included as rule targets. This field is mandatory. |
Include removed assets |
This field defines whether the operations defined by this rule are applied to such devices whose asset configuration item has been removed from Miradore but which still are detected by a connector or network discovery. |
Include assets with client status unknown |
This field defines whether the operations defined by this rule are applied to such devices that have an active asset configuration item in Miradore, but the online status of the installed management client is unknown. |
Include assets with client status unmanaged |
This field defines whether the operations defined by this rule are applied to such devices that have an unmanaged asset configuration item in Miradore. An asset is unmanaged when it doesn't have a management client installed. |
Main: Additional information
Attribute name |
Description |
Attachments |
You may attach files into this field. About attaching files. This field is optional. |
Comments |
You may add comments related to this item here. This field is optional. |