The Agent does not show a logged in user even though one is logged in locally


The Kaseya Windows Agent checks in, but does not display a logged-in user even though one is logged in locally, why?


The Kaseya Agent Service Helper for KaUsrTsk is not being invoked from the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run registry key.


Check in the Task Manager on the affected machine to verify if the kausrtsk.exe (Kaseya Agent Service Helper) process is running. If it is not, in some cases, this key overall and/or the Agent Service Helper path has been removed by security programs and thus the kausrtsk.exe process is not automatically started.

To correct this, make sure that this Registry Key Helper is set to the following path:

"C:\Program Files\Kaseya\KSAAS<agentid>\KaUsrTsk.exe

(assuming the Kaseya Agent was installed in C:\ drive)

<agentid> is a 15 digit number, unique to each Kaseya agent


The following PowerShell script will help in ensuring that this registry is added. You can edit the script to remove "-remote" or keep it if necessary:

cd "C:\Program Files (x86)\Kaseya" 
$dir = dir "C:\Program Files (x86)\Kaseya" | ?{$_.PSISContainer} 
foreach ($d in $dir){ 
cd $d 
.\KaUsrTsk.exe -remote 
#echo "inside directory" 
Write-Host "Operation successful: $d" 
cd .. 


For more information, please refer to

Adding the -remote tag for KaUsrtsk.exe on Windows Agents

Have more questions?

Contact us

Was this article helpful?
0 out of 1 found this helpful

Provide feedback for the Documentation team!

Browse this section