Cannot prevent M$ Project 2013 install from auto restart
I am getting ready to deploy Office 2013, including Project 2013 and Visio 2013 to our users. In general, all machines will be Win7 currently running Office 2010. The issue I am having involves the situation where Office and Project and Lync 2010 are installed on the PC.
I am using SCCM 2012 SP1 R2 and have created a Task Sequence that does the following..
Uninstalls Project 2010/Installs Project 2013 (conditions set to determine if it exists)
Uninstalls Visio 2010/Installs Visio 2013 (conditions set to determine if it exists)
Uninstalls Lync 2010 (conditions set to determine if it exists)
Uninstalls Office 2010/Installs Office 2013 (conditions set to determine if it exists)
Project has been configured via the Office Customization Tool to hide updates and auto activate. I have made changes to the config.xml file per Tech Net's instructions to prevent the PC from rebooting.
These are the elements I have altered:
<Setting Id="SETUP_REBOOT" Value="Never" />
<Setting Id="REBOOT" Value="ReallySuppress" />
The problem is, whenever any Office app is open during the install (even Lync) the Project 2010 uninstall/2013 install task automatically reboots the PC mid-task sequence. Even though it is running the following command line to install:
setup.exe /adminfile project.MSP /config prjpro.ww\config.xml
I am trying to avoid making the users have to close Lync since it opens automatically for most of them and will force the extra reboot if its still open when the install office kicks off. Does anyone have any other ideas?
Thanks,
-Adam
-
You are going to have to ensure that other office apps are not running when you perform this deployment. The reason that a reboot is taking place is that any running Office application is undoubtedly holding some files locked which need to be updated, and in these circumstances only a reboot will allow this to happen. What happens if you run the same deployment with all office apps shut down? - EdT 9 years ago
-
Same thing. Project and Visio 2013 always initiate a reboot when deployed with a task sequence. If I run setup.exe /adminfile project.MSP /config prjpro.ww\config.xml via command line (not through SCCM) there is not reboot. - quattro004 9 years ago
Answers (3)
So I think I have gotten this to as good a point as possible considering what I am trying to do. To solve the cronic reboot issues with both Project and Visio and sometimes Office, I grabbed a fresh copy of the install files from the .iso we have for each app, copied the MSP from out 2013 (non-SP1) version that has some of our custom config set in it. I did this for all three apps, then went about configuring the conifg.xml file accordingly.
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="Never" />
<Setting Id="REBOOT" Value="ReallySuppress"/>
I left the remaining elements commented out since they are either set in the MSP or not used in our case. After configuring the .xml files. I can get the apps to install silently without them triggering their own reboots provided all Office apps are closed. I can get away with Lync being open and since I call its uninstall with the first task in the seqeunce, its closed by the time the rest of the apps install.
I finally found a concrete solution to this.
The deployment has been available for download for users for roughly a month now and so far all has gone very well from a deployment standpoint. Some users are still experiencing double restarts, almost always do to some Office related app or process still running when the begin the install.
Because this is deployed in a Task Sequence, it makes it tougher to prevent unwanted restarts due to the way Task Sequences handle messages from the program during install. If a Restart required message appears in the install report, the Task Sequence will trigger a 30 second count down on its own a reboot the machine before it will continue with any remaining steps. It doesn't care about any reboot suppression buried in a config file, ini file or even in the command line of the Program in SCCM.
To get around this, I collected the names of all Office 2010 related processes (any .exe's) that we install, built a TASKKILL script written to force kill all instances of any open Office 2010 app and stuck it at the beginning of the Task Sequence. So far after numerous test with EVERY Office 2010 app open, it kills all of them, proceeds with the install, and only reboots at the very end when I call it in a Task.
Here is an example of one of the scripts to kill Access 2010 if it is open... TASKKILL /F /IM MSACCESS.EXE
/F force kills the app, no questions asked.
/IM specifies you are using the image name of the process. In this case its MSACCESS.EXE which is what you would see in Task Manager if Access was currently open.
Comments:
-
This actually was the next thing I tried. Project still doesn't seem to care. Even though the config.xml file is telling it to prevent a reboot, its sending a 'reboot required' message to SCCM via the task sequence report which is triggering the SCCM client on the PC to restart. - quattro004 9 years ago