Deployment Solution

Ever since we upgraded to SP6, some of our jobs do not error out anymore.  They just get stuck at executing script on the DS console.  The local DAgent also says executing, but when i check the event logs it shows the error message. 

In the past DS 6.9 SP4, if it errors out, it will show it in the DS console.  Now it doesnt after the upgrade.  Does anyone know how to get it to so?

Thanks

 

Hey baldiesrt,

Not sure if this applies to you but in our environment the encryption box keeps getting checked somehow under the security tab preventing the agent from communicating with the server.  I have found that if you uncheck that encryption box it starts communicating fine again.  We never really had this issue before upgrading and since the box seems to keep checking itself under the default agent settings,  I am chalking it up to an altiris bug.  I could be doing something wrong though.  Hope this helps! :)

Thanks Joel.

I assume you mean the encryption box located under security tab on the local dagent settings?  Mine is not checked there.  Is there a setting on the DS console?

Hey baldiesrt, Yes sorry, that was the setting I was referring to. It sounds like you are experiencing something different than my suggestion but just for the sake of sharing information, there is a global option that appears in the Control Panel. It can be found under Altiris Deployment Solution > Options > Transport tab called "Allow Encrypted Sessions." This is also a registry setting that we force off in our environment because we don't use it. What is the error message that appears in the event log?

Thanks Joel.

I am getting error message 1638 from the event log, meaning that another product version is already  installed.  I usually get that error prompted in the deployment console but it just gets hung there.  Its been 2 days and it still stuck at executing script.

Besides this job, there are many other jobs having this issue that we normally dont.  For example, we have a standard package group that gets rolled out to every pc after imaging.  After SP6 upgrade, few of those job actually fails and report an error 1.  I had to add an exception to error 1 and then it proceeded onto the next time.  We never had these errors before with the thousands of pc we imaged in the last year.

Any help would be greatly appreciated. 

Thanks