When you want to add an Office program to an existing Office 365 ProPlus installation with PDQ Deploy or SCCM it’s necessary to add the FORCEAPPSHUTDOWN property to the XML file. If you don’t do that, you will probably get error code 17006 (or 0x426e(17006) in SCCM)
Fixing error 17006
If you already have a deployment setup you might have a config.xml file similar to this:
<Configuration>
<Add OfficeClientEdition="64" Channel="Monthly">
<Product ID="O365ProPlusRetail">
<Language ID="nl-nl" />
<ExcludeApp ID="Access" />
<ExcludeApp ID="InfoPath" />
<ExcludeApp ID="Publisher" />
</Product>
</Add>
<Updates Enabled="TRUE" Channel="Current" />
<Logging Level="Standard" Path="C:\temp"/>
<RemoveMSI All="TRUE"/>
<AppSettings>
<Setup Value="LazyAdmin" Name="Company"/>
</AppSetting>
<Display AcceptEULA="TRUE" Level="None"/>
</Configuration>
As you can see we excluded Access, InfoPath and Publisher in the default installation. When you want to add one of these apps later to the installation you will need to create a separate config file where you include the app in question.
For example, when you want to install Publisher, you only remove the ExcludeApp id line for Publisher. This way Office 365 ProPlus will be installed/updated with Publisher. Everything else that you exclude here will be removed. So keep that in mind.
For adding Publisher you create the following config file:
<Configuration>
<Add OfficeClientEdition="64" Channel="Monthly">
<Product ID="O365ProPlusRetail">
<Language ID="nl-nl" />
<ExcludeApp ID="Access" />
<ExcludeApp ID="InfoPath" />
<ExcludeApp ID="Publisher" />
</Product>
</Add>
<Updates Enabled="TRUE" Channel="Current" />
<Logging Level="Standard" Path="C:\temp"/>
<RemoveMSI All="TRUE"/>
<AppSettings>
<Setup Value="LazyAdmin" Name="Company"/>
</AppSetting>
<Display AcceptEULA="TRUE" Level="None"/>
<Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
</Configuration>
Notice line 18, here we added the ForceAppShutdown property. This will close any open Office 365 apps that will otherwise prevent the installation of the additional product.
Update Jan 2019
I noticed that this article was a little outdated. First off, the error code is still related to the fact the Office is running. So you will have to make sure every Office program is closed before you can update the installation.
But in the supplied examples there were a few outdated or incorrect lines:
Update channels
The channel names are changed. You can find the new channel names here in the Microsoft Documentation. Use Monthly to keep the clients up-to-date.
If you don’t want the clients to update them self, but keep control over the released versions. Then you can disable the update by setting the Updates to false.
<Updates UpdatePath="\\test\" Enabled="FALSE"/>
In large Enterprises, you might want to test the new releases before you roll it out. I use the targeted release for this and have assigned a couple of key users to be updated first. You can read more about targeted release for Office 365 here at Microsoft.
Activating
Setting the autoactivate to 1 isn’t necessary for Office 365. The user needs to sign in to active Office 365 or you can use the Azure Single Sign-On. Read more about setting SSO up here.
Use the Office Customization Tool
To create the config file for your environment you can use the new Office Configuration tool. This allows you to easily create the xml file to you specifications.
a little bit confused as you say:
“For adding Publisher you create the following config file:”
but then you proceed to keep the following line in the xml file:
Either way, I assume you had meant to remove that line from the example code.
I remove the one for OneNote and finally, after multiple failed deployments, I was able to install it!
Brilliant, just what i was looking for!
“Great find and post, but I wanted to point out a couple of things to your readers:
1) — this is not necessary with Office 365. In fact, this line does nothing. The product cannot activate unless an account with a subscription license authenticates via login”
What if your including other products such as visio and project?
Example with my PIDKEY excluded
If you assign the Visio and Project licenses through Office 365 then they still can activate it with a simple sign in. Or you can use Single Sign-On for this.
Great find and post, but I wanted to point out a couple of things to your readers:
1) — this is not necessary with Office 365. In fact, this line does nothing. The product cannot activate unless an account with a subscription license authenticates via login
2) — admins need to understand this is a bad practice. This allows ALL clients installed via this xml to update via the CDN, over the internet. The only control you would have is max versioning via GPO. Please go broad if you’re in an enterprise environment and you care about uptime
3) This is an odd fix. By default, I close ALL Office apps via PSADT. This works on some devices, but not all. I found this only happens if the device is already on Office 365 CTR and I’m simply replacing with my xml and Visio and/or Project
Wow, this is a great help. I’ve been trying to fix this all day and I was able to push and install Visio 365 Pro after following your directions. Thank you LazyAdmin you rock!