Agent Client Collector Framework flips the os_domain value on the Windows Server records - Support and Troubleshooting

Agent Client Collector Framework flips the os_domain value on the Windows Server records Summary When Agent Client Collector Framework is installed, the os_domain value of the host CIs in the CMDB can be observed to be flipping by Discovery and ACC.

This is because the 'collect host data' UI action fetches the os_domain value from the server using the below command:-

wmic computersystem get domain /format:list

During Discovery, the 'Windows OS - Servers' Pattern is setting the os_domain value from NBT using the command 'nbtstat -n' because the system property 'glide.discovery.domain.name.nbt' is set to true by default.

If the system property 'glide.discovery.domain.name.nbt' is set to false, Discovery will fetch the os_domain using the below command using WMI Query and the os_domain will not be flipped:- "SELECT Name,Domain,Manufacturer,Model,UserName FROM Win32_ComputerSystem"

But it is possible that the value of os_domain field fetched from NBT is preferred over the value fetched from WMI query. In such scenarios we can configure Reconciliation Rules to prevent ACC from updating the CIs which were already updated by Discovery.

Instructions Workaround:-

A Reconciliation Rule on Computer class should be sufficient in this scenario because Windows Server class is a child of Computer class and the Reconciliation Rules are derived from parent class to all its child classes unless overridden.

Steps to configure Reconciliation Rules to prevent ACC from updating the Computer class and its sub classes:- 1. Go to CI Class Manager > Hierarchy > Computer > Reconciliation Rules 2. Under Reconciliation Rules, click on Add. 3. Set 'Discovery Source' as 'ServiceNow', Priority as 100 and click on Next 4. Enable 'Apply to all attributes', click on Next and click on Save. 5. Repeat the steps 3 and 4 for other Discovery Source's being used to update the CMDB with the same priority 100. 6. Create Reconciliation Rules for ACC with 'Discovery Source' as 'Agent Client Collector', 'ACC-Visibility' with Priority as 200 (lower priority).

With the above configuration, the Discovery source 'Agent Client Collector' or 'ACC-Visibility' will not be able to update the Computer class records or its sub classes records if they were already updated by Discovery or any other source configured with priority 100.

After the above configuration, please validate that all the Discovery Source's are able to update the CIs as expected. If not please configure additional Reconciliation Rules as required by your environment.

Note:- When Reconciliation Rules are configured for a class then for every 'Discovery Source' that you would like to update that class, a Reconciliation Rule should be configured. If there exists no Reconciliation Rule for a specific 'Discovery Source' then that Discovery Source will not be able to update that class or its sub-class records.

Doc for reference:- Reconciliation Rules