So I have a test environment where I test applications before installing them to actual user computers. I was working on zap file for Creative Suite 2 to do an unattended install. I found if I have a file called AdobeInstallerConfiguration.xml setup.exe uses that config without any switches.

My zap file (called cs2.zap) looks like this, (it sits on a path called \\2k3svr\apps\cs2 in the same dir as the setup files)

[Application]
FriendlyName = "Creative Suite 2"
SetupCommand = "setup.exe"
DisplayVersion = 2.0
Publisher = "Adobe Systems Inc."

What happens is the app shows up in add/remove just fine, but when I click install it just opens the shared path in a window that the files are on and does not execute setup.exe. I've tried with and without quotes, and with the absolute path as well - but with no luck.

Any suggestions?
0 Comments   [ + ] Show Comments

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.

Answers

0
Actually I just figured it out - double quotes around the setup command fixed the issue.

Funny thing is - some ms sites say no quotes, some say single quotes. The GPO help file that comes with the OS says double quotes - that works.
Answered 11/23/2005 by: AngelWorks
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity