Logged-on User: Blank or Wrong - since upgrade to AClient 6.9.366 (X86)
Updated: 23 May 2010 | 5 comments
Hi,
Since upgrading to the latest AClient 6.9.366 the machines are reporting back as the wrong logged on User...
Either Blank or Administrator rather than the actual logged on user. Even after restarting the service and running a 'Get Inventory' command from the DS server they are still reporting the wrong logged on user and/or blank.
If it wasn't for Symantec changing the registry strings for the SVS agent and therefore breaking DS I wouldn't have upgraded in the first place!
Any idea's on a fix?
Thanks,
RL
P.S. Anyone know why Symantec decided to remove the password protection on the DAgent? This and other things.
To me it just looks like DS and NS are just being used as a playground since the transition to Symantec!
discussion Filed Under:
Comments
DAgent or Aclient?
One of my co-workers brought this kb article 44900 to my attention. I try to use the aclient with XP, and the fix mentioned appears only for the Dagent.
I have seen similar issues with the aclient though.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Definitely stay with AClient
Definitely stay with AClient for XP. I only use DAgent when I have to for Vista or 2003.
re: Definitely stay with AClient
Just a clarification: AClient works fine in 2003, 2008 is where you will need the DAgent.
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
oops
I meant 2008, I just forgot the other side of the 8 so it looks like a 3. ;)
The issue I am seeing..
as I mentioned, is related to the issue presented in the initial topic. Using the latest 'public' version of aclient 6.9.366, clients will appear 'off' in the console. However if you are able to physically get to (or use RDP) to the machine, you will see the Altiris Client service is running and active.
This was an issue a few years back with the TCP socket closing, however I haven't seen it recently (fixed in 6.8 'gold' I think). Even verbose logging on the client side didn't present much in the way of an error trail.
Restarting the Altiris Client Service or rebooting reconnects the client to the server, and any scheduled jobs fire off as expected.
So, if the fix mentioned in 44900 is only for the DAgent, I'll have to pursue this with support.
(Edit: updated with proper version of aclient being used)
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Would you like to reply?
Login or Register to post your comment.