I am having a problem pushing some apps using SMS 2003. The packages run fine when manually installed. Even when being pushed using SMS 2.0. But when I try to push using SMS 2003, I get an error 1606.

I have a theory that since SMS 2003 uses the local system account to install, and the local system account doesn't have its own profile on the computer, it fails when trying to write to profile related areas. If this were the case though I think a lot more people would have the same issue.

Some of the apps I'm having a problem with are Architectural Desktop and ChemOffice.

Any information would be appreciated


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Enable Windows Installer logging on the PC and try reading the log. I think the likely cause of your error is that the MSI is trying to write to a network location but is having issues. Your log should provide better details.
Answered 07/06/2005 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Your theory could very well be correct. Try installing your MSI's with 'ALLUSERS=1' or 'ALLUSERS=2' to avoid the 'Current User problem' associated with the system account.

Just reminded me of the same issue with Tivoli.......

Answered 07/20/2005 by: de_bas
Yellow Belt

Please log in to comment