Proplusww.msi Office 2016 Download

[Melissa Alvarado]

Ive been searching all over and haven't found many people describing a similar issue, and I wondered if anyone here could help. I'm installing Office 2013 w/SP1 during my OSD task sequence. I've created a custom.msp and have it in my updates folder - that is applying correctly. What is not applying, however are all the other patches in the updates folder. I have followed the procedure here: -us/library/cc178995(v=office.15).aspx#section4 using the script provided to collect updates from a fully patched Office installation. I put all of them in the updates folder on my network installation source. In my SetupExe...log I am seeing the following first, in which it looks like it detects all the patches and says that most of them are applicable.

A short amount of time after the OSD process is complete, software center shows a ton of Office 2013 patches ready to install, adding a significant amount of time to the process. Anyone have any ideas for something I could check or correct? I've tried rebuilding my installation directory from scratch, done the patch collection from different machines, etc., but nothing seems to work. Thanks!

First, in my deployed Office Application under the Programs tab I was just calling "setup.exe" as my Installation program. I assumed that because the updates were in the updates folder on my installation source and that it was applying my custom.msp that it was also checking for updates in that installation source. I checked the log again on a machine I had run my OSD on, and it wasn't even seeing the updates. (The log I previously posted was actually from a machine I had manually run the setup.exe on, a mistake on my part.)

It was not looking in the installation source updates folder, though - it was only checking in C:\Windows\ccmcache\7\updates. Therefore, I added the following line to the config.xml file in my proplus.ww folder in my installation source:

After doing that and testing out my task sequence, I checked my logs again. The installation updates folder was referenced this time. It still looked very similar to the one I posted above with a lot of Applying patch: and Warning: Unknown stage encountered while completing an MSI progress stage. Stage: 0 errors, but checking in "Programs and Features" I see that all of the office patches were applied.

What does ww stand for in terms of microsoft installers? At the root of their office product for example, there are folders like proplus.ww and proplus.en-us each of which contain various .exe and .msi files. But It looks like the .ww file contains the more important .msi file. (For example, If I am deploying software with SCCM, the .WW file/folder is the one I need to choose)

Step 5: Customising Install directory, organisation name and licencing options. In these steps you can configure where Office will be installed to and supply license details for activation. If you plan on using KMS you can view my article here on How to install kms server and activate office 2016. If you do not wish to use KMS here you should specify your MAK Key. You want to accept the terms of the licence agreement and choose Suppress Modal & No Cancel

The deployment part was quite straight forward after the configuration part was done. I basically followed a (very good) guide from -to-deploying-microsoft-office-2013-using-configmgr-2012/ with some minor changes for our environment. Nothing worth mentioning here though.

In most cases, proplusww.msi file problems are due to the Microsoft Office Professional Plus 2007-related file missing or being corrupted by malware or virus. If your MSI file is suffering from one of those troubles, replacing it with a fresh file should resolve the issue. We also recommend running a registry scan to clean up any invalid proplusww.msi references which could be cause of the error.

Please take caution in ensuring the file is placed in the correct file directory. Following these instructions carefully should resolve your proplusww.msi error, but we recommend running a brief check. Re-load Microsoft Office Professional Plus 2007 to observe if the issue has been successfully solved.

Ordinarily, proplusww.msi-related Blue Screen errors happen when a Microsoft-related device driver is loaded, during the install of Microsoft Office Professional Plus 2007 or related program, or while Windows is starting or shutting down. Documenting proplusww.msi problem occasions in Microsoft Office Professional Plus 2007 is key to determine cause of the Office Suite problems, and reporting them to Microsoft.

In this step-by-step guide, we will show you how to deploy Office 2016 using SCCM. To implement Office 2016 deployment using SCCM, we will use the Microsoft Office Customization tool to modify the setup.

The Office Deployment Tool allows the administrator to customize and manage Office 2016 Click-to-Run deployments. Administrators can use this tool to manage Office Click-to-Run installation sources, product or language combinations, and deployment configuration options.

For Office 2016 deployment, we have got the Microsoft Office Professional Plus 2016 32-bit volume license copy with us. We will use the same to customize and distribute it to Windows devices using Microsoft SCCM.

In this step, we will run the Office deployment tool. On the Configuration Manager server, run the command prompt as an administrator and change the path where Office 2016 setup files are located. Run the command setup.exe /admin.

The Microsoft Office Customization Tool allows you to customize the Office 2016 before you deploy it with SCCM. You can specify the KMS client key, modify setup preferences, add registry entries, configure office security settings and much more.

The next step is to make the application available to DP. Right-click the Office 2016 application, click on Distribute Content, choose your DP and wait until the application is available with DP. You can verify this by checking the Content Status of the Office 2016 application under Distribution Status.

Hello Prajwal,

Great job. Thanks a lot for this post . It was very helpful. Do you happen to have a post that guides the uninstallation of MS Office Professional Plus 2016 using SCCM? I need to carry this out in my environment.

Your help would be much appreciated.

Thanks

Your posts are very informative. What do you recommend in the settings of the customization tool if I want to have it display the progress window of uninstalling Office 2010 and then the progress window of installing 2016. We had issues of my command file killing the Office apps processes and then users trying to restart the applications while it was trying to uninstall 2010/install 2016. This caused some botched installations that our service desk had to fix. Basically I want something to display on the screen so that the user does not touch any Office applications until the whole process is completed. Thank you for your help.

Okay, maybe I am missing something. I noticed that you used the customization tool to create the MSP file, but I do not see any reference of that file in the Application setup for Office 2016. I would expect that you would have to the use the adminfile switch for the Installation Program portion where you have setup.exe.

All of our users do not have local admin access to their computers. I am creating applications in SCCM so they show up in the Software Catalog with Require Admin approval. Is there a way to set these applications to install without admin credentials once approval has been granted?

i did and edited the xml files. when i run Setup.exe /download Download.xml i get a message as restart your computer or there may not have enough free space available error message. I have enough free space on my dis. i restart the system, tried on several machines but no luck.

We are deploying MS office 2013 to production, we planned through the AD sites I request you to provide the AD SITES deployement query. We have 160 AD Sites. How to handle multiple ad sites in single query?

Followed same steps as mentioned but on the client side installation is failing,Checked Appforce logs(Error: 1. Looking for exit code 30030 in exit codes table,2. Unmatched exit code (30030) is considered an execution failure.).

Can you please help me out on this issue

I am trying to deploy Skype for Business (SFB) entry using SCCM 2012 R2 to our ORG. I am stuck where i am unable to find MSI for SFB even Microsoft O365 team were not able to provide. Can you please kind enough to assist me how can i create a package or application for SFB.exe and deploy it across our ORG. We are using Office 2010 PRO Plus in our environment.

Sir,

The setup was successful and application is created for Office 2016 setup but i have not yet deployed it. My client machines have office 2010 installed on them, so deploying office 2016 through SCCM will upgrade clients office 2010 to office 2016 or is it going to create another instance of office on the client machine?

Hi Prajwal,

Thanks a lot for the post. very helpful and it worked fine fine.

I installed 2016 and unfortunately it did not uninstall 2010. what would you suggest i should do to uninstall office 2010?

I followed the instruction and distributed the application. The problem I have is now I can not deeply to devices the only option I have is users I test to deploy to users but i tis not appearing in Software Center.

Hello Prajwal! I followed your guide for Office 2013 and 2016. Things appear to be working well with one exception. After Office 2016 installs, it says that a restart is required. I did modify the setup properties to include the SETUP_REBOOT and set value to Never. Any thoughts on this? Thanks!

Hello Sir! After following all of your directions my software installations stays at the installing status. The last step in the AppEnforce log says waiting for process 1560 to finish. Any advice to get Office to install?

3a8082e126