I created a setup.iss file by running setup.exe /r and am running this script from an install.bat file: <path>\setup.exe /f1<path>\setup.iss /s

If I run this install.bat file locally on the target computer, the install works fine but when I push this script from Altiris (DS6.9) as a task, the install does not work. Setup.log says:

[InstallShield Silent]
File=Log File

If I were to run this setup.exe manually, the first dialog box that comes up says it detected a mapped drive to the application server. If I run the same script without the /s option, I get an error saying it could not find any mapped drive. I tried pushing the script while logged in as a user who has this mapped drive as well as tried putting in the credentials of a domain user who has the drive into Altiris under the script task but got the same error.

Does anyone know what would cause the install to fail when pushed via altiris vs. running directly from the target computer? Any help or suggestions would be greatly 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


I don't know Altiris's deployment tool but my guess would be that, in common with most such systems, it uses the local System account to perform the installation. As you know, System has no concept of networking, much less any network access. You need to re-think the deployment, possibly copying the installer locally and running it via a command file or script.
Answered 01/22/2009 by: VBScab
Red Belt

Please log in to comment