SCCM - Program will not install silently (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message


jerryabouelnasr -> SCCM - Program will not install silently (4/21/2008 1:26:06 PM)

I have a package that consists of 3 chained programs. The first two are .msi and the last is a registry modification.

I have tried getting the first application to install silently numerous ways. <msiexec /i applicationName.msi /qn> <msiexec /i applicationName.msi /quiet> & a lot of variations with quotes placed in various parts of the string.

The install is kicking off, but we're getting prompted for configuration options that the application wants answered.

When I manually navigate to a command prompt, to the local cache directory and run the install command, which I see in the execmgr log as genuinely being the command that is executed, the install runs silent. If I run it under the local system account, the install also kicks off perfecly silent. For some reason, when it's allowed to run on its own, it will not install silently. Any ideas?

Thanks a bunch all,

Jerry




jsandys -> RE: SCCM - Program will not install silently (4/21/2008 2:40:51 PM)

It sounds like you have a wrapper MSI that is extracting another MSI and executing it.  The wrapper MSI executes silently and then passes control to the second MSI but not the silent command-line.  The trick here is to get at the contained MSI, they are usually extracted to the %temp% folder once you start the wrapper.

Opinion:  Software developers are clueless and have no idea how their products are actually used or maintained and thus we end up with idiotic things like this.  Just give me the damn MSI.  OK, off my soap-box.




phaustein -> RE: SCCM - Program will not install silently (4/21/2008 6:41:57 PM)

Which package is prompting for configuration?  Did you test each application seperately and then added one one and retest?  Verify that the settings for each of the programs are set the same.




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/21/2008 6:45:45 PM)

Why would that apply only when the msixec string is run through the SCCM client and not when I manually run the install command? Shouldn't it apply regardless?




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/21/2008 6:47:02 PM)

The first package is prompting. I'm going to try running it seperately now, just to isolate variables, but I don't see what the difference would be.




jsandys -> RE: SCCM - Program will not install silently (4/22/2008 10:09:12 AM)

When you say you run the command in execmgr.log, how is it different than the progam command line specified in the package?




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/22/2008 1:55:11 PM)

It's not different at all. It's the same exact command. If I manually run it from a command prompt (either as a local user with admin rights or within the LSA's security context (using psexec)), it works as expected.




phaustein -> RE: SCCM - Program will not install silently (4/22/2008 2:45:15 PM)

Does it work within SCCM seperately?




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/22/2008 3:55:38 PM)

Nope! Tried it. Also tried calling the command from a batch file instead of just using the program's command line. :(




phaustein -> RE: SCCM - Program will not install silently (4/22/2008 4:03:24 PM)

So to clarify, the application fails to run silent when run within SCCM seperately from the chain package, right?




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/22/2008 4:21:30 PM)

Correct.




phaustein -> RE: SCCM - Program will not install silently (4/22/2008 4:27:59 PM)

What's different between the 2 packages programs?  You said one works, but the other prompts, correct?




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/22/2008 6:12:52 PM)

Sorry, I'm probably not explaining things clearly. It doesn't work through SCCM at all.  The only time it runs silent is if I run the command from a command prompt. I navigate to the cache folder and call the command manually, as specified in the Program's command line (also, as logged in the execmgr.log). It then runs silent. When SCCM is allowed to run its course and initiate the install, it's no longer silent. Meaning, the installation program requests input.




phaustein -> RE: SCCM - Program will not install silently (4/22/2008 6:19:18 PM)

Can you post the command-line of the package? Can you tell me what settings you have set in the program of this package?




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/22/2008 6:49:58 PM)

I posted some of the variations in my original post. Currently, I've embedded into a batch file:

msiexec /i AppName.msi /qn REBOOT=ReallySuppress /l*v "c:\windows\temp\sutter_xyloc_install.log"

I've also tried NUMEROUS variations:
Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i AppName.msi /qn REBOOT=ReallySuppress /l*v "c:\windows\temp\appname_install.log"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.4.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i AppName.msi /qn REBOOT=ReallySuppress /l*v "c:\windows\temp\appname_install.log"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.4.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i AppName.msi /qn REBOOT=ReallySuppress /l*v "c:\windows\temp\appname_install.log"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.4.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i AppName.msi /qn REBOOT=ReallySuppress /l*v "c:\windows\temp\appname_install.log"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.4.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i AppName.msi /qn REBOOT=ReallySuppress /l*v "c:\windows\temp\appname_install.log"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.4.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i "AppName.msi" /qn REBOOT=ReallySuppress /l*v "c:\windows\temp\appname_install.log"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.7.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i "AppName.msi" /qn /norestart
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.9.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i "AppName.msi" /qn /norestart
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.9.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /i "AppName.msi" /qn
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.10.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /q ALLUSERS=2 /i "AppName.msi"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.11.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /q ALLUSERS=2 /i "AppName.msi"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.11.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /q ALLUSERS=2 /i "AppName.msi"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.11.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /q ALLUSERS=2 /i "AppName.msi"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.11.System\
User context: NT AUTHORITY\SYSTEM

Program started for advertisement "PAF2018A" ("PAF000F4" - "App Client 8.5.0").
Command line: "C:\WINDOWS\system32\msiexec.exe" /quiet /i "AppName.msi"
Working directory: C:\WINDOWS\system32\CCM\Cache\PAF000F4.12.System\
User context: NT AUTHORITY\SYSTEM


As far as program settings, the relevant parts I imagine that you are asking regarding are the "Run:" option and the "Suppress program notifications." I've left each default - "Normal" and Unchecked. I've also tried "Hidden" and Suppressing program notifications. No results.






jsandys -> RE: SCCM - Program will not install silently (4/22/2008 7:21:32 PM)

I would like to actually look at this MSI.  I'm starting to feel like it's very poorly written -- not uncommon mind you.




phaustein -> RE: SCCM - Program will not install silently (4/22/2008 7:32:56 PM)

It looks like you've got all the bases covered. I can't say why its prompting during the install. It must be something special about the application. Is this a custom app or COTS?




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/23/2008 1:01:02 AM)

That is what my suspiciion has been, in addition to my boss'. I just wanted to sanity check and try and see if there was something obvious that we might be missing. It's just strange that the problem only manifests when the install is called through the sccm client. I would be happy to send you the .msi if you pm me your email address.

thx/much




jerryabouelnasr -> RE: SCCM - Program will not install silently (4/23/2008 1:15:39 AM)

:) It's more like commercial off your neighborhood cornerstore shelf....I've barked up that tree a bit, but I can't get much more than "put all your computers into an OU and apply a GPO that assigns the app." I have neither the time to dig into the .msi too much. I would like to take te msiexec log from a manual install and compare it to that of the one called by the cm client but i've spun my wheels too long on this and am going to have to move on b/c of priorities. I sincerely thank you for your help. If I'm afforded the opportunity later on and find a soln, I'll come back and post.

Jerry




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.1875