Populate Assign To of CI from Agent Client Collector

[SK Chand Basha]

Population of Assigned to From Agent Client Collector

The population of "Assigned To" attribute [assigned_to] is supported only for Windows and Mac OS end-user Computer class CIs - [cmdb_ci_computer]. It is not supported for Server class CIs (Windows Server or Linux Server), or other child classes of [cmdb_ci_computer].

1. Navigate to System Properties
2. Search for sn_acc_vis_content.set_assigned_to
3. Set value to true to override the Assigned to value from ACC.

 

This payload section contains different information for Windows.

"assigned_to_users": {"logged_in_users": [],"computer_system_username":""}

The information is collected as part of a Discovery check using the "endpoint_discovery.rb" command when including the "local_users" module.

Matching collected Username to sys_user Table.

• The users from the payload are evaluated to find a match in the sys_user table in the instance. 

Note :Default system behaviour searches against the "User ID" [user_name] field on the [sys_user] table based on the order defined on sn_acc_vis_content.assigned_to_user_order system property

• logged_in_users,computer_system_username
• First checking the “logged_in_users” then the " computer_system_username ".

• Valid values are either of the below: 

• "computer_system_username,logged_in_users"

• "logged_in_users,computer_system_username"

 

If have Azure AD or LDAP Integration to get user where UserID not matching with Payload value then need to include the field in this below property.

sn_acc_vis_content.column_name_for_user_mapping

• Only used for querying users on Windows devices
• Used to determine which column on "sys_user" to query
• Setting this property to any value will additionally add the "ad_domain" information to the query
• Changing "sn_acc_vis_content.column_name_for_user_mapping" to value: "u_samaccountname":

 

• While searching value it requires aDdomain.
• Accepted Formats
• Format 1: domain\username
• Format 2: username@domain
• Example: Based on user order system will take logged in user and search with user table on SamAccountName field with ADdomain+user
• In previous payload we are getting logged in user 91807 and ADdomain – WORKGROUP
• In user table system expects a value WORKGROUP\91807 OR WORKGROUP@91807

 

• Navigate to Agent Client Collector -> Agent
• Open an agent click on Collect Host Data
• Once completed click on Recent Input ECC Queues.

 

• In Payload field Search for logged_in_users and Verify On Host record assigned to field

If have any question feel free to post comments!

Happy Learning!!