User Logon Reports - Knowledge Base
1. The User Logon Reports do not show any data. Why?
- Verify whether the Desktop Central Agents are installed
in the client systems that are specified in the Scope of Management.
- Ensure that User Logon Reports has been enabled. Click here for steps to enable.
- When you have two separate Desktop Central installations
and both have the same client computers in their scope.
- Check for any firewall running in the machine where Desktop
Central is installed. It might block the status update messages
that come from client machines. Ensure that the Desktop Central Port (default 8020) is added to the exceptions list.
- When any security software like Symantec or Mcaffe is running
in the client machines is blocking the agent communication.
Try after stopping it.
- First login after the Desktop Central agent installation
in the client machines will not reflect in the report.
I enable User Logon Reports, it takes a long time
for user logoff. Why?
When User Logon Reports is enabled, the Desktop Central agent
in the client computers executes a VBScript during user logon
and logoff to track these events. The VBS files should be associated
with WScript.exe so that it gets executed when you try to open
the file. When the user has associated the VBS files to be opened
in an editor, for example, when the Desktop Central agent tries
to execute this script, it does not execute as the default application
has been changed. It just waits there till it gets timed out,
causing delay in the logoff time. In such cases, the User Logon
details cannot be tracked for that particular user. Restoring
the file association will fix the issue.