DS6.9 SP2 AClient Password issue
Just did the update to SP2 from SP1. Now all alients that were already in the DS console update like they should but then the password is not what it was. Now I can right click and push the new password and that fixes it. But I can't select under tools\options\Agent settings and force the settings we want down. That does not work. Also since we have image jobs along with other scripted task to go after the image those fail now with user and password not correct but if I wait and run the job after the agent updates (not the image job but the other jobs) They work just fine. So my question is .... is there a default password being pushed down with the new alient or is there a step I need to do to force it to use what we had. Any help would be great.
AL
Comments
That's wierd becasue I had
That's wierd becasue I had the same thing happen to me when i went to 6.9 sp1...
Anyway you should be able to right click "all computers" ( or whatever sub folder has the objects) and choose "Change Agent Settings" -> PRODUCTION AGENT.
Then click SECURITY tab and change the password there. Clicking OK will push that setting out to all those pc's.
Let me guess...
Did you by any chance have the passwords configured as unencrypted? DS since6.9 SP1 seems to assume that the aclient passwords are encypted, so if they were set as plain text the assumption appears to be that this plain text string is now the encrypted password. The result is you always get an incorrect password when trying to login to the Aclient properties.
If you are setting the aclient configuration through inp files this issue also gets you, as if you try to use an unencrypted password (even with EncryptedPassword=No) it will still assume an encypted password and fail.
As you've found, setting this through the console works transparently as this route takes on the assumption of encrypted passwords. This is watchpoint if you are delivering sysprep images which install the aclient from a .inp file.
I've raised with Altiris Support, but no KB exists for this issue as yet.
Kind Regards,
Ian./
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
KB article now up..
Support have now confirmed this to be an issue, and this has been logged as a defect.
https://kb.altiris.com/article.asp?article=47461
Kind Regards,
Ian./
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
Thank you ianatkin one last question
Do you think this will be fixed in 6.9 or will this be a fixed in 7?
T
Thanks
AL
that's upto management and the developers really....
As with any bug fix, its a matter of balancing the impact of each defect and weighing this up in each case against the internal costs of fixing the code.
I was very surprised to see this hadn't been listed as a bug before now, so I fear this will have a low impact. Either just a few customers are accessing the aclient properties, or perhaps most are using encrypted passwords anyway. Or maybe a combination of both!
For now, I recommend:
Kind Regards,
Ian./
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
Would you like to reply?
Login or Register to post your comment.