Best practices: Office Content Delivery Network configuration for cloud managed

The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see Best practices.

Cloud Managed will use the Office Content Delivery Network (CDN) for the source files to deploy the Office 365 ProPlus packages. However, they will utilize automation scripts for OffScrub and to initiate the Office 365 ProPlus deployment.

The Office 365 configuration script does the following:

  • Run OffScrub

    • Remove all Office 2010 MSI components if found

    • Remove Office 2013 MSI core suite if found, but leave 2013 Project and Visio intact if previously installed

    • Leave user data in place

  • Install Office 365 ProPlus with proper channel, architecture, and languages from Office CDN


The following table includes the OffScrub Command lines that Cloud Managed used for the script sequence to remove previous versions of Office:

Context for program
Command line
Office 2010 Removal
Command prompt cscript Offscrub2010.vbs clientall /bypass 1 /log c:\temp /nocancel /q
Office 2013 MSI Removal
Command prompt cscript OffScrub2013.vbs ProPlus /bypass 1 /log c:\temp /nocancel /q

Office source location

Cloud Managed will utilize scripts to complete the Office 365 client configurations. The following is an example of the Office source location for Cloud Managed 32-bit Semi-Annual Channel. It includes the ODT setup.exe, Office 365 client install XML files, and corresponding batch files.

Cloud managed source locations

An example batch file for the package is as follows:

Context for program
Command line
Semi-Annual Channel 32-bit
Setup.exe /configure Install_ProPlus_SAC.xml