I am trying to silent install some software using SCCM. I have everything set up on the server and client sides. All clients can successfully communicate with the server.

I already have .iss files recorded and setup for the install. And .xml files necessary for software configuration. These folders are in the same location as the setup.exe program

Usually to command line silent install this product, the command used is:

setup.exe /s /f1"C:\setupfolder\ISS\setup.iss" /config"C:\setupfolder\config\setup.xml" /serial"xxxxxxxxxxxxxx"

Unfortunately when I input this into the Package/Program setup for deployment, and advertise this package (as mandatory, after updating distribution points), it gets sent to the client, and the install is initiated (I see this in task manager on the clients), but it quits after a couple of seconds without the product being installed

Appreciate any help on this, especially how to change my command line to where it is compatible with SCCM deployment.

Thanks

it depends on the product being installed and the installer engine that product uses. looking at your example, it appears to be an installshield engine. search appdeploy.com for the product you are installing, there are manygood examples there.

in general, i've found that the installshield setup.exe often requires an extra argument of /f2c:\windows\temp\something123.log
it doesn't seem to write a log file unless an error occurs. but without the logfile argument the install will fail.
not all installshield packages seem to require this.

i've also found that testing a package using the psexec.exe -s -i cmd.exe (to simulate the ConfigMgr SYSTEM account environment) is very helpful.

Thanks so much for the reply,

these are company products that are being tested with SCCM, and that have the above configuration for Silent install.

I don't expect them to be on appdeploy.com (and they are not, I checked...) I'll go ahead and try including the /f2"" argument in the command line for the program and see what happens.

Do I need to have the program in a special location? Right now I have it in a shared folder on the desktop, along with the .iss and .xml files. Do i have to manually copy these to the distribution folder?

Thanks

It should work from a shared folder on the desktop but if it were my Enterprise I would put it someplace a bit more robust and accessible than that.

Do I need to have the program in a special location? Right now I have it in a shared folder on the desktop, along with the .iss and .xml files. Do i have to manually copy these to the distribution folder?

depends on your packaging practice. either Run from DP vs. Download & run locally. the decision you make here can give you rapid success or great grief, and it's experience/familiarity with the package content and your client OS environment & version that is the key (well, so far for us :)

also, don't discount appdeploy.com just because your home-brewed app isn't there. Installshield (as an installer engine) is fairly consistent in behaviour - although it does change a bit between versions. the older IS engines were frequently used in very simple ways. these days there are a lot more custom actions and complexity baked in. (showing my age now....)

What does the apps install log file show?  Is there an error that is occurring iduring the installation of the app?

You can also check the execmgr.log file and see what might be the cause.

Hi guys,

I figured it out. (i think).

I hadn't accounted for the fact that SCCM was sending the program to a different location from the one specified in the command line (That i have been using for ages).

What I had to do was to change the location I specified in my command line to the right folder location (C:\WINDOWS\system32\CCM\Cache\........)

That sorted me out, the programs are now installing on the clients.

Going to play around/test this a bit more! 

Thanks everyone really appreciate all the help I have received here

• Marked as answer by EnamT Thursday, March 03, 2011 6:22 PM

Bende bu sorunu byle zdm.

gelarabul.com