PROBLEM
You are referencing the database view vAgentConfiguration and looking at the CurrentUser value.
You find that this does not always return the expected value - even though a user is logged in, the value returned is <null>
CAUSE
This is not the best source for this information. The value in this table is not updated frequently. A restart of the agent process with the user logged in WILL trigger this value to be updated, but this is not ideal.
WORKAROUND / SOLUTION
Instead of vAgentConfiguration/CurrentUser, use the more correct vAgentLabel/CurrentLogin
This gives you "live" information about the logged in user.
vAgentConfiguration/currentUser does not return expected result
Have more questions?
Was this article helpful?
Provide feedback for the Documentation team!
Browse this section
- Gathering Agent Logs For Connectivity Issues
- How can I remove the Badge Icon on my Agent?
- 'K Agent Update Done' script loops on Machines.
- 9.5 Agent: "Installation of the Agent Failed" on Windows systems.
- Adding the -remote tag for KaUsrtsk.exe on Windows Agents
- Agent account name is not the same as the Computer name
- Agent deleted but the licence count is unchanged
- Agent Failing to Change Machine Groups
- Agent Not Installing - Curl.exe/proxy issue
- Agent Procedures appear stuck / not running on a newly installed Agent
- See more