Failed to Populate Assigned To attribute in Computer CI using ACC-V
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2024 02:24 PM - edited ‎06-23-2024 02:25 PM
Hello Everyone
I use ACC-V on Windows computers to collect data and update CIs in our CMDB. Those computers are AD joined and the users logged in to those computers are AD users. Also, those users are already added to ServiceNow. ACC-V can collect data but Assigned to is not populated by the currently logged-in user on the computer (Windows 11). I have already enabled sys_property "sn_acc_vis_content.set_assigned_to". When looking at the "Recent Input ECC Queues", I can't see any domain users picked up and I only see local users. The document below states, "Create higher user privileges to fetch the logged-in user details. Use Log on As Local System User instead of the default ServiceNow user for running the Agent Client Collector.",
Does this mean we need to have a different user with Logon as a local system instead of the default logon as service account "servicenow" which is recommended when setup ACC-V? or there is any other way to get the field populated?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-03-2024 01:40 AM
Hi @MuthanaS ,
For WindowsYou need to identify if a server is domain controller or not. Since domain controller machines don’t have local accounts, local user information does not persist for such machines and is not populated.
For non-domain controller Windows machines, use OSquery commands to get user information through ACC-V: select uid, username, directory, type from users where type=local or type=special.
Also refer the below URL and check the permission.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ
Linkedin:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community Rising Star 2024
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-03-2024 03:55 AM
Hello Ajay
Thanks for your reply
This is not great. The "Assigned to" field is an important field to be populated and I am shocked it won't be populated if we use domain controllers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-30-2024 06:38 AM
hi @MuthanaS
While installing ACC from third party tool, pass one more command to run the ACC service under Local System and not Service account. That will resolve any issues of permissions.
We have been using this method recently for 1 customer and it does pick the user information. Maybe u can try for 1-2 systems and verify if it works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-30-2024 07:25 AM
Hi @MuthanaS
I am currently working with the Agent Client Collector in ServiceNow and have encountered an issue. I am unable to see local user details in the logs. Could you please guide me on where I can find this information?
Specifically:
- Where can I view the local user details collected by the Agent Client Collector?
- What exact information is collected for the local user?
- Mid Server Cluster for failover or load balancing. How it can configured when installing the agent.
I have attached screenshots of the commands that were executed. Your assistance in resolving this issue would be greatly appreciated.
Thank you