Thanks. I would have no idea how to use a package and program to fix this. I don't understand why I can't be allowed to do a reinstall using SCCM. Will open a ticket up with Microsoft asking them for help.

ETA: What if I uninstalled Office 2013 from the client PC, and then tried to push it out again to the PC using an SCCM application? Would that work? Or would it still think it was already installed?

• Edited by RBanse Monday, June 15, 2015 6:29 PM

The issue is the detection that the app model does.  Since Office 2013 is already installed, a typical detection method will see it installed and not execute anything again.

Uninstalling office first would work.  You could look at developing a script that uninstalls office, re-installs it, and writes a file someplace.  Then use the detection rule to look for the file that you create.  The PowerShell application deployment toolkit would be a good tool for creating a script like that (http://psappdeploytoolkit.com).  That is just one option. . .

Jeff

• Marked as answer by RBanse 19 hours 23 minutes ago

The issue is the detection that the app model does.  Since Office 2013 is already installed, a typical detection method will see it installed and not execute anything again.

Uninstalling office first would work.  You could look at developing a script that uninstalls office, re-installs it, and writes a file someplace.  Then use the detection rule to look for the file that you create.  The PowerShell application deployment toolkit would be a good tool for creating a script like that (http://psappdeploytoolkit.com).  That is just one option. . .

Jeff

• Marked as answer by RBanse Tuesday, June 16, 2015 12:07 PM

Thanks everyone. I will probably just uninstall Office and install with the new MSI.

I have deployed an Office 2013 application to users but there was found to be a known bug in the files from Microsoft (http://blogs.technet.com/b/odsupport/archive/2014/03/11/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx)

These users were already upgraded with this bug and I would like to now upgrade them again with the latest files. I created a new deployment for this. Since they already have Office 2013, and this new deployment is Office 2013, will it work? Or will SCCM think that Office 2013 is already installed and will skip the install?

When you use the same detection method, ConfigMgr will indeed think that the application is already installed. It would require a unique detection method, specific to that scenario.

Another way would be to use and old-school package and program to make your adjustments.

Thanks. I would have no idea how to use a package and program to fix this. I don't understand why I can't be allowed to do a reinstall using SCCM. Will open a ticket up with Microsoft asking them for help.

ETA: What if I uninstalled Office 2013 from the client PC, and then tried to push it out again to the PC using an SCCM application? Would that work? Or would it still think it was already installed?

• Edited by RBanse 13 hours 3 minutes ago

I ended up contacting Microsoft and they created a program for me and we installed the missing Lync files that way. In case anyone else runs across this, we did the following:

1. Created a Package

2. The Program of this Package was setup as: setup.exe /modify proplus /config config.xml

3. The config.xml file was setup as:

<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" Reboot="ReallySuppress" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="Never" />
<OptionState Id="LYNCFiles" State="Local" Children="force" />
</Configuration>

The issue is the detection that the app model does.  Since Office 2013 is already installed, a typical detection method will see it installed and not execute anything again.

Uninstalling office first would work.  You could look at developing a script that uninstalls office, re-installs it, and writes a file someplace.  Then use the detection rule to look for the file that you create.  The PowerShell application deployment toolkit would be a good tool for creating a script like that (http://psappdeploytoolkit.com).  That is just one option. . .

Jeff

Client basically look at root\ccm\CIModels name space with class local_detect_Sync to check if the detection method true or not ,if detection method succeeded,it will skip the installation else install it. So you can either change the detection method value for the particular application to something else ,so client will try to install the app or have a unique detection value for the application.

here is another way to reinstall the application http://stackoverflow.com/questions/28950457/is-there-a-way-to-reinstall-an-application-in-sccm-2012