To create the config file for your environment you can use the new Office Configuration tool. The user needs to sign in to active Office 365 or you can use the Azure Single Sign-On. Setting the autoactivate to 1 isn’t necessary for Office 365. You can read more about targeted release for Office 365 here at Microsoft. I use the targeted release for this and have assigned a couple of key users to be updated first. In large Enterprises, you might want to test the new releases before you roll it out. Then you can disable the update by setting the Updates to false. If you don’t want the clients to update them self, but keep control over the released versions. Use Monthly to keep the clients up-to-date. You can find the new channel names here in the Microsoft Documentation. So you will have to make sure every Office program is closed before you can update the installation.īut in the supplied examples there were a few outdated or incorrect lines: Update channels First off, the error code is still related to the fact the Office is running. I noticed that this article was a little outdated. This will close any open Office 365 apps that will otherwise prevent the installation of the additional product. Notice line 18, here we added the ForceAppShutdownproperty. So keep that in mind.įor adding Publisher you create the following config file: Everything else that you exclude here will be removed. This way Office 365 ProPlus will be installed/updated with Publisher. 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.įor example, when you want to install Publisher, you only remove the ExcludeApp id line for Publisher.

If you already have a deployment setup you might have a config.xml file similar to this: Īs you can see we excluded Access, InfoPath and Publisher in the default installation. If you don’t do that, you will probably get error code 17006 (or 0x426e(17006) in SCCM) Fixing error 17006 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.

Lansweeper sccm