Avatar of grg-it
grg-it asked on

Forcing a No Reboot during installation of Office 2007

I wrote a script to uninstall Office 2003 and install office 2007 for all users on my network.  I have since learned about creating a custom MSP file for installing Office 2007 and it has a option to remve previous versions of office which will alleviate that portion of my script.  However, I do not want the setup to reboot when it is done because I have a few other tasks that the script is going to do at the end.  I am using this command to run the setup.

Note: the installation source is copied to the C:\ drive before initiating the installation
C:\MSOffice2007ProPlus\setup.exe /adminfile CUSTOM.MSP (works but does not prevent restart)
adding the REBOOT=ReallySuppress does not work

Is there a setting in the MSP file that I can change to force a No reboot?
Microsoft OfficeVB ScriptSoftware

Avatar of undefined
Last Comment

8/22/2022 - Mon
Jared Luker

You can put in an entry into the config.xml for SETUP_REBOOT... more info here:

Jared Luker

<Setting Id="SETUP_REBOOT" Value="Never" />


Probably another page from the same technet article jared_luker cited above:

SETUP_REBOOT--Determines how Setup restarts the computer after installation. You must use all uppercase letters, SETUP_REBOOT.

AutoAlways--Always initiate a reboot. Do not prompt the user.

Always--Always prompt for a reboot at the end of setup.

IfNeeded--Prompt for a reboot at the end of setup if setup requires a reboot. (Default)

AutoIfNeeded--Initiate a reboot if setup requires a reboot. Do not prompt the user.

Never--Never initiate or prompt for a reboot.

You set these properties in the Modify Setup properties page of the OCT, or the Setting element in the Config.xml file.
Your help has saved me hundreds of hours of internet surfing.

However I am not using the Config.xml file I am using the CUSTOM.MSP.  Can I set that switch somewhere within the Office customization utility?  Or can I even use a config.xml file with a custom.msp file like:

<path> /adminfile Custom.msp /config config/xml   ?

From http://technet.microsoft.com/en-us/library/cc179022.aspx (again, the same article, different page)

Office Customization Tool
The Office Customization Tool (OCT) is part of the Setup program and is the recommended tool for most customizations. To start the tool, you run Setup.exe with the /admin command-line option and select a product to customize. Thereafter, the user interface looks very similar to the Custom Installation Wizardall the same options are available.

At the end of the process, the OCT saves your choices in a Setup customization file (MSP file), rather than the transform file (MST file) produced by the Custom Installation Wizard. Like a transform file, the customization file results in uniform default configuration of the product for all users. Unlike a transform file, however, which you had to specify explicitly on the command line or in the Setup.ini file, you can enable Setup to apply the customization file automatically by storing it in the Updates folder at the root of the network installation point.

So, do you mean that option not exposed in the Modify Setup properties page of the OCT as the http://technet.microsoft.com/en-us/library/cc179018.aspx page says?

I appreciate your response, but I am not very familair with using the OCT.  I navigated through its options one by one,  I passed over options I did not understand and when I was done I created the MSP file and associate the MSP file to the setup.exe by using this command: "<path> /adminfile CUSTOM.MSP"
I do not see any option within the OCT to disable the automatic restart after Office 2007 is installed.  Is this functionality even possible?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

The bad news (sort of) is that you might not even need your script to uninstall previous versions of office (the script could be used for other things though).

Here are the steps.
1) Create an .msp file (which you have done)
1a) If you like, one of the options for the .msp file is to remove previous versions of office (see picture)
2) Create a config.xml file. The bad news is that there are no tools to do this for you, you need to do it in notepad (at least there were no tools that I could find, it should be easy enough for someone to make a tool)
2a)Your config.xml file includes the line <Setting Id="Setup_Reboot" Value="Never" />
3) Save the config file in the root of your installation directory (I understand that you will be copying this and that's okay)
4) Save the .msp file in the Updates folder of your installation share
5) Run the install of the office. The path should look something like this:
    c:\office_install_folder\setup.exe /config //path_to_config_file/config.xml
As long as the .msp file is in the correct location it should work fine.

For your convenience here is a sample config.xml file that you could use:
<Configuration Product="Enterprise">
<Display Level="none" CompletionNotice="no" SuppressModal="no" AcceptEula="yes" />
<Setting Id="Setup_Reboot" Value="Never" />

Hope that helps

could you post a screen grab of the OCT with the Modify Setup properties item selected, please?

I'm still waiting for my copy of Office2007 Pro to be delivered.  :-|


I think I am with you on this so far but to be sure I understand correctly.  I place the MSP inside of the Updates folder.  The MSP file contains all of my settings, enterprise key and also can control display level so would I still need the <display level> tag within the XML?  

Using this command: c:\office_install_folder\setup.exe /config //path_to_config_file/config.xml
Will the setup know to use the MSP saved in the updates folder for all of my settings and use the xml only for preventing reboot?
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

zabu99 said:
> The Modify Setup properties is very underwhelming as it starts off blank. You add values to it.
> In the attached screen-shot I have added a value to control reboot during installation. This
> article has more information: http://technet.microsoft.com/en-us/library/cc179018(TechNet.10).aspx

Yeah... If you check https://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Q_23428542.html?cid=238#a21635000 you'll see that's the same page I pointed grg-it to, but apparently making the XML file is easier than putting that option in the MSP file using the customization tool. Thanks for the screen grab, though.

Darr247 - Yep, you pointed to it first; I don't mind if you get the points. :)

Either way is pretty easy. If I had just one flavor of install then I would personally favor using just the MSP.

No...  that's very gracious, but you posted the screen shots showing where to put the command in the OCT, and how to make the XML file, so (when grg-it gets it working) your answers were really more complete.

And I'm STILL waiting for delivery of my Office/Visio 2007 package to arrive.  :-|
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

Thank you for all the help.  zabu99, your solution with the MSP works perfectly and the MSP is how I want to go with this setup.  However, I do not think I need to use the No_Reboot command since my vbscript that calles the setup will also create a runonce registry entry to run a cleanup script after the computer restarts, otherwise I will have to program a restart.  I think I will take advantage of the reboot.

Editing the config.xml fixed my issue with getting a silent, no reboot install of Office 2007 using MDT 2010.  Why it doesn't suppress reboot by default, I don't know.