For what it's worth, I have also seen situations where the agent shows no current user is logged in, but I have the person on the phone telling me they are logged in. I have connected to their computer just fine tohelp them in Windows and it will still show them as not logged in.
If I remember correctly,the user has toshut down the computer to resolve it, a restartor log off will not work.
The Kaseya system tray icon has not shown up in the tray for the two years that we have been using Kaseya when using RDP. If you vnc in, you will see and I beleive that you rdp /console you will see it. The icon is only visible in the console.
New question - should I be having this issue (no Current User) when connecting via RDP to a Windows XP system, or do I need to run the scripts below which seem to apply more to an actual Terminal Server? Thanks for the replies.
It is possible for this to occur during the initial installation via LAN Watch. Using the RPC service to deploy the Agent installation over the LAN, the "admin" user account used for installation may be holding on to the KaUsrTsk application even after the install completes. In that case, a reboot is required to close that session out in order for KaUsrTsk to begin functioning correctly for normal users.
ChrisRowland wrote: New question - should I be having this issue (no Current User) when connecting via RDP to a Windows XP system, or do I need to run the scripts below which seem to apply more to an actual Terminal Server? Thanks for the replies.
Thanks, Chris, for clarifying the use of an Agent version v126.96.36.199 in your case on your SBS server. Thedefault behavior as described was put in place in v188.8.131.52, so that matches my expectations.
As for your new question, applying the scripts as described below will also allow KaUsrTsk to interact with the desktop (i.e agent icon and current user info) in an RDP session to an XP box just like it does for an 2000 or 2003 terminal server.