How do I skip reboots when pushing packages using Configuration Manager 2007?

Hello,

I am trying to push several Adobe Patches (9.3, 9.3.1, and 9.3.2) using Configuration Manager 2007. I am using the /norestart at the end of each package, and telling Configuration Manager that no action is necessary. However, it still says reboot pending when I check the status after 9.3.0 or 9.3.1 installs. I don't want users to have to reboot several time to do the install. I can run the command line outside of configuration mananger and it works fine.

Here is the cmd lin I am running;
msiexec /p <filename>.msp /qb! /norestart

Any help would be greatly appreciated!
droworleyAsked:
Who is Participating?
 
tint846Commented:
try these switch:

/sAll /rs /l /msi /qb- /norestart EULA_ACCEPT=YES
0
 
jebCommented:
you could also try this
/sAll /rs /l /msi /qb- REBOOT=ReallySuppress
0
 
merowingerCommented:
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
droworleyAuthor Commented:
As far as I understand the /norestart is equal to ReallySuppress. I have found out that you can run multiple patches in one line;

msiexec /p patch1.msp;patch2.msp

I am going to try that and see if it works.

Thanks!
0
 
jebCommented:
actually its not. the /norestart works like REBOOT=supress. here is a decent explanation

The Windows Installer REBOOT property can be set to "force", "suppress" and "reallysuppress". This last one raises some eyebrows- here is the break down:

Force
Always prompt for a reboot at the end of the installation. The UI always prompts the user with an option to reboot at the end. If there is no user interface the system automatically reboots at the end of the installation.

Suppress
Suppress prompts for a reboot at the end of the installation. The installer still prompts the user with an option to reboot during the installation whenever it encounters the ForceReboot action. If there is no user interface, the system automatically reboots at each
ForceReboot. Reboots at the end of the installation, for example caused by an attempt to install a file in use, are suppressed.

ReallySuppress
Suppress all reboots and reboot prompts initiated by ForceReboot during the installation. Suppress all reboots and reboot prompts at the end of the installation. Both the reboot prompt and the reboot itself are suppressed. For example, reboots at the end of the installation, caused by an attempt to install a file in use, are suppressed.

Another property, REBOOTPROMPT can be set to Suppress (or just S) so that any reboot performed by the Windows Installer happens automatically without interaction from the user. Setting this property does not initiate a reboot if one is not needed, it only suppresses the display of any prompts for reboots to the user.
0
 
jebCommented:
Did any of these work for you?
0
 
droworleyAuthor Commented:
I am giving you both some point on this one. The problem is with msiexec itself. It was returning an exit code of 3010. Look that up and you will find out that it mean ERROR_SUCCESS_REBOOT_PENDING. Now your command lines were correct, but I had to run it using the Setup.exe, not the AcroRead.msi.

So this is what my final command line looked like;

Setup.exe /rs /msi TRANSFORMS=AcroRead.mst /qb!

The ! takes away the cancel button...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.