Failed to Populate Assigned To attribute in Computer CI using ACC-V

[MuthanaS]

Hello Everyone

I hope you are doing alright

We are using ACC-V for data collection on Windows-based computers which are AD-joined. Those computers are accessed via AD accounts. When the agent collects data, it does not populate the assigned field. I have enabled the system property "sn_acc_vis_content.set_assigned_to" and I have noticed that Recent Input ECC Queues data does not get the Assigned to Users (See attached) and only get the local users. According to the document below, we need to use Log on As a Local System User instead of the default ServiceNow user for running the Agent Client Collector. Does this mean we can't get logged-in users with the default Log on as the service account we use during ACC setup? Or is there a way to get those details and populate the CI?

Link to Documentation 

[SamD93108872890]

Do you have any further info on how it matches? We are getting fnamelastname returned in the payload for logged in user.  The users on our user table all have the format of fname.lastname@domain.com. I am having trouble understanding how this matching should work when the logged in user will frequently not match the user ID on the user table.

[MuthanaS]

I don't know how you can map users in this case but I assume you will need to edit your pattern or probe. Check out the post below and it might help

https://www.servicenow.com/community/itom-forum/how-can-you-capture-the-quot-last-logged-in-user-quo...

[SamD93108872890]

Can you advise what format your usernames are coming in via the ACC payload and what format your user names are in on your users table? In our case the payload is delivering them as fname.lastname or fnamelname but our user table has user IDs of fname.lastname@company.com

[dougw]

I am in the same boat - although well past running it as localservice - and so far have not found a solution.  I get back logged_in_users["smithj"],"computer_system_username":"smithj","ad_domain":"fully.qualified.domain.name" and to match our users it needs to be user@fqdn.

[NeenaPatel]

Hi All / @Steven Parker 

We are in the same boat we noticed we are not getting the Assigned To because we ran the package as the default Service Now User.

If we amend the service to Local Log On User does this mean we have to redeploy the agent and does that mean I will see duplicate agents?

Thanks

Neena