Run installation program as 32-bit process on 64-bit clients.īecause we combined multiple products into one installation source, Office Setup does not automatically know which product we want to install. Setup.exe /adminfile "OCT-ProPlus2016-x86-Silent-Install-.MSP" /config "proplus.ww\config.xml"
CANNOT FIND PROPLUSWW.MSI PLUS
Microsoft Office Professional Plus 2016 (32-bit)
Keeping in mind that our example is 32-bit Office Professional Plus 2016, here are the settings.
CANNOT FIND PROPLUSWW.MSI WINDOWS
Although Office has a Windows Installer-based setup process, using setup.exe is required. This is where we supply Office Setup with our Office Customization Tool settings as well as our uninstallation settings. Fill out the Specify information about this application page.Click Next, and then click Next again to begin customization.
CANNOT FIND PROPLUSWW.MSI SOFTWARE
\ \ fileserver \ software $ \ Microsoft \ Office Professional Plus 2016 ( 32 - bit ) \ proplus. For example, the MSI file for 32-bit Office Professional Plus is located in the proplus.ww folder. In the Location box, type the network path to the specific product’s MSI file under your installation source.On the General – Specify settings for this application page, select Automatically detect information about this application from installation files, and choose Windows Installer (*.msi file) as the Type.In the ribbon, click Create Application.In Configuration Manager Console, in the Software Library workspace, navigate to Overview > Application Management > Applications.Then we’ll go back and edit the Application to add our uninstallation command, prerequisite applications, and system requirements. First, we’ll point ConfigMgr to the product MSI so that as many properties as possible populate automatically. Building the Configuration Manager Applicationīuilding the Configuration Manager Application for Office is a two-pass process. Office Setup uses these files during installation, so our uninstallation settings must be saved elsewhere. Warning: Don’t change the existing config.xml files in the installation source. I named my file “Config-ProPlus2016-Silent-Uninstall-.xml” in the root of my deployment folder: \\fileserver\software$\Microsoft\Office Professional Plus 2016 (32-bit). Open your favorite text editor, and save the following text as UTF-8. (You may recall that we added this property to the customization file for installation, but we don’t have a customization file for uninstallation.) To do that, we’ll use the Setting element of config.xml. This documentation doesn’t mention it, but because Configuration Manager Applications must not initiate a reboot, I’m going to add the SETUP_REBOOT property with a value of “Never” in order to be certain that the uninstallation process will not restart the computer unexpectedly. Basically we need to use a custom config.xml file to instruct the setup program to perform a quiet uninstallation. The Setup command-line options reference for Office 2013 on TechNet has a helpful section describing uninstallation. Silent UninstallationĪs we did in the Customizing Setup post, we will consult the Office 2013 documentation to help us. Next time, we’ll use our new Applications along with our Offscrub package to build a task sequence for deployment. Then we’ll walk through the Application-building process. That takes a little bit of work, and so we’ll do that first. This provides Software Center with the ability to remove it, thus giving users an “app store” experience. One of my rules for a Configuration Manager Application is that it must have an uninstallation command. There is just one bit of housekeeping to take care of first. It’s been a long process, but it’s finally time to build the Application objects in System Center Configuration Manager for Microsoft Office and its sibling programs.