Good Question, mine seem to be working fine with XP, but I may push dagent and keep the icon hidden.  I have not looked to see if they have dagent on them as well.

I'm glad it's working for you.  It's good to know it's possible.

When I do a packet capture of Win7 boxes using dagent I see some packets go back and forth during log off using port 402 that seem to be passing login status info.

When I do a capture of an XP box using aclient I'm not seeing those packets.  It may have just been a bad capture and I will try again.

Try to create a new filter definition in the console using the fields "Computer Status" and "logged-on", to see which computer is in the logon screen or someone is logged on.

Regards,
tester2k5

If I create a filter for Status - Active it does show the XP and Win7 clients as having their aclient services active (blue) in the console.

If I create a filter for Logged On - Active it only works for Win7 clients.  XP clients do not show in the filter whether they are logged in or not.

Thanks much for the idea, though.  It does seem to confirm that XP clients just aren't able to update the console on their log on status.

I Use the AClient, but the HP Insight Control Deployment Server (former RDP) with primary HP boxes. But that should work also on the regulary Altiris DS. Are you able to remote control / push jobs on the clients when they shows up as not connected?

Check your Settings in the AClient:
- [x] "Connect directly to this Deployment Server"
- "Refresh connection after idle..."
- [_] "Encrypt session communication..."
 

XP clients do show as active and I can push jobs to them.  Unfortuately they don't show in the console whether anyone is logged into the computer.  With older version of the DS Console, and with Windows 7 clients on v6.9, the icon for the computer changes from a plain computer to a computer with a little head when someone is logged in.  With v6.9 and XP it remains a plain computer whether a user is logged in or not.

The setting you indicate are correct on the server.

Make sure that the Aclient version on the client matches the server. What you're describing usually happens when the versions don't match up.

That was my first thought, too.  However, server and workstation versions of aclient match exactly 6.9.453.0.

That is really werid. We are runing the same version as you, and our console reports the status correct on XP SP3 and W7 64 bit machines. Only on Win 7 32 bit does the agent status get flaky.

Hi all,

We have a script to query the db for the status within an event, based on which we can action or error out. Maybe this is of any help for some of you? Please see attached TXT file with a basic sample...

-BBC

Thanks very much, but unfortunately that doesn't really apply to our situation.  Our support desk needs to know, before using Remote Control, if a user is logged on or not.  These are paying customers at the computers so we're also not allowed to send a chat first or have a 'Will you permit this' dialog box pop up.

As you indicate, there are scripts we could use but the best way would be to get back to being able to tell at a glance if a user is logged in.

Make sure that AClntUsr.EXE is on the computers and is being run at login. That is the file that reports the logged on user to the server.

Check the following registry key on the clients:
HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Client Service\UserInfoInterval

If it's set to zero, it won't send the logon info, and I've got suspicions that this functionality is a bit buggy in 6.9SP4.

That key is set to 15 on our clients.

Phyrant - I believe AClntUsr.exe is no longer used in v6.9.  That functionality was supposed to be built into aclient.exe.  I did try using it though, but it made no difference.