Quantcast
Channel: TechNet Blogs
Viewing all articles
Browse latest Browse all 34890

Office Click-to-Run command lines to automate a Quick and Online Repair in Office 2013

$
0
0


Background

The June 2014 release (build 15.0.4623.1003 and later versions) of Office Click-to-Run from Office 365 allows you to automate both a quick and online repair of Office 2013.

Note - if using an Office build lower than 15.0.4569.1007 you will need to use integratedoffice.exe to perform a Quick Repair.  Further information on using integratedoffice.exe can be found here, Automating Quick Repairs in Office 365 ProPlus.


More Information

OfficeClicktoRun.exe is the executable that will allow you to automate a repair in Office 2013.  This executable will reside in one of the following locations based on the version of the Operating System:

64-bit OS:
C:\Program Files\Microsoft Office 15\ClientX64\

32-bit OS:
C:\Program Files\Microsoft Office 15\ClientX86

Here is the list of variables that can be used with OfficeClickToRun.exe:

Variable 

Possible Values 

Description 

RepairType 

QuickRepair | FullRepair 

This specifies if the user is going to run a Quick repair (QuickRepair) or an Online Repair (FullRepair).  Note - if running an Online repair, all Office applications will be reinstalled and will override any settings made in the configuration.xml file 

DisplayLevel 

True | False 

Setting the DisplayLevel to True will show a full UI and setting it to False will make the UI silent. 


For example, to do a silent Online Repair, run the following command from an elevated command prompt:

"C:\Program Files\Microsoft Office 15\ClientX64\OfficeClickToRun.exe" RepairType=FullRepair DisplayLevel=False


Related Information

For more information on the build versions of Office 2013 Click-to-Run, please see the following KB article
Microsoft Office 2013 Click-to-Run virtualization


Viewing all articles
Browse latest Browse all 34890

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>