/build/static/layout/Breadcrumb_cap_w.png

Microsoft Office 2007 Restart

I'm about to turn on logging to see what is causing this but was wondering if anyone has experienced this. Office will sometimes restart after it is installed. This appears to be totally random as machines with identical configurations have varying results. I doubt this is random at all but it is strange. Has anyone come across this random restart and know what causes it? I will post my log results soon.

0 Comments   [ + ] Show comments

Answers (11)

Posted by: MRaybone 15 years ago
Senior Yellow Belt
0
I had the same issue, but didn't find out what caused the behaviour. To get around the issue, I put a custom 'really suppress' reboot property into the .MST, and wrote a simple VB script that popped up a message box after the install telling the user that they would need to restart their machine at some point.
Posted by: dpolishsensation 15 years ago
Blue Belt
0
I think I've already tried this. I ran the OCT and added the Property REBOOT=REALLYSUPPRESS under the Modify Setup properties section but the workstations still restart. Is this the same thing you did? Also, did you build an MST or use the update folder and use an MSP? I'm using an MSP.
Posted by: spottedcoin 15 years ago
Senior Yellow Belt
0
we found that it was generally caused because the machine already had a pending reboot.
Posted by: MRaybone 15 years ago
Senior Yellow Belt
0
I'm using an MST. I unpacked SP1 and put the MSPs for that in the Update folder.
Posted by: dpolishsensation 15 years ago
Blue Belt
0
If you put the SP1 in the updates folder, will it run it automatically after running the setup.exe?
Posted by: anonymous_9363 15 years ago
Red Belt
0
From my reading of other posts about Office 2007, you need a CONFIG.XML file in the same location as Setup.EXE, with the setting:

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

Note the capitals: I believe they're required. A search of the Office stuff on Microsoft's main site or perhaps MSDN will turn up details and, I believe, a template CONFIG.XML for you to thrash with. Don't quote me, though - I have yet to encounter the joys of MS's new "let's take what we invented and make it even more impenetrable" game.
Posted by: MRaybone 15 years ago
Senior Yellow Belt
0
ORIGINAL: dpolishsensation
If you put the SP1 in the updates folder, will it run it automatically after running the setup.exe?


Yes. So long as you extract the .MSPs from the .EXE, it applies all the updates during the final stage of the Office 2007 installation.

For example, the files I have in my Updates folder are:
ClientSharedMUIsp1-en-us.msp
MAINMUIsp1-en-us.mspMAINWWsp1.msp
Office64WWsp1.msp
Proofsp1-en-us.msp
Proofsp1-es-es.msp
Proofsp1-fr-fr.msp

These were all extracted from the main Office 2007 SP1 .EXE.
Posted by: vjt914 15 years ago
Senior Yellow Belt
0
Hey,

VBScab is correct, you need to ensure you are including a reference to a config.xml in you install script, which should reside in the root of your office install source directory, or whichever product (Enterprise.WW) folder you're installing. Within the XML file, you will set the entry just as VBScab has it, and you'll be good to go.
Posted by: reds4eva 15 years ago
Second Degree Blue Belt
0
Same as what I said in 4 other threads.
The config.xml isnt in the root with setup.exe, although I doubt it would matter if it was as you reference the xml in the command line anyway. There is a ready made xml in the folder relevant to your product, (like vtj said above), in the Enterprise.WW or standard.ww, just include the edited xml in your command line.

%~DP0\setup.exe /adminfile %~DP0\updates\OffStd2007.MSP /config %~DP0Install\Standard.WW\config.xml
Posted by: anonymous_9363 15 years ago
Red Belt
0
ORIGINAL: reds4eva
Same as what I said in 4 other threads.
LOL. Get used to that, Dean. LMAO...
Posted by: davidkevanian 15 years ago
Senior Yellow Belt
0
I was able to suppress a restart by adding the property SETUP_REBOOT=Never in the MSP.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ