Office 365 Click to Run – Configuration and Testing Part 2

Hello Readers

This is the next part in my Office 365 Click to Run Configuration and Testing series. In this Part I will look at deploying Office 365 Click to Run to a user base that has the following installed on Client Machines;

  • Office 2010 Standard
  • Lync 2013 Client


If you have already seen Part 1 you will know that I have created a script to remove both components and then install Office Click to Run. So I will be deploying Office C2R via Group Policy using a Shutdown Script that point the following share \\dc01\OfficeC2R which contains all the required components to install Office 365 Click to Run.

The script I am using looks like this;


So now we will need to configure Group Policy for the deployment of Office 365 Click to Run.

Launch Group Policy Editor

Right Click “Group Policy Objects” and Press “New


Give you new Group Policy Object a name. I will be calling mind Office 365 Click to Run Deployment and Press “OK

You will now need to right click your new Group Policy and Press “Edit


Browse to “Computer Configuration\Policies\Windows Settings\Scripts (Startup\Shutdown)

Double Click “Shutdown” Press “Add


Browse to your Script Location and Press “Open” then Press “OK” and close Group Policy Management Editor.

You will now need to assign this Group Policy to your container that holds your test or production clients you want to deploy Click to Run to.


As you can see I have assigned the Policy to my Workstation OU but one thing I will be changing will be the Security Filtering as I want to have more control of the which machines pick up the Policy. I have created a Security Group called “Office 365 Click to Run Deployment” and assigned two workstations this group


You may need to do GPUPDATE /Force to make sure the Client Machines pick up the Group Policy. As you can see my client machine has picked up the Group Policy


I have switched on Verbose Message of Log Off and On so I can see what is happening on the shutdown process of the client hopefully your shutdown of the client should take a lot longer than normal.

Once the shutdown as completed, start up your client machine and you should see your Office version removed and …


You will now see Office Click to Run installed


This completes this post, you also have the option to deploy Click to Run via App-V. I will try get a post about the process for App-V as well


Andrew Price


8 thoughts on “Office 365 Click to Run – Configuration and Testing Part 2”

  1. Hi Andrew,

    Thanks for sharing this article.
    In Office 2013 OCT, there is a specific setting to migrate user preferences from old (office 2010) versions, to make sure user settings are not lost.
    But with Office 365, I not able to figure how to achieve this to ensure user settings are no lost after upgrade.
    Is there any way to do this?


    1. Hi there

      not to my current knowledge Office group may have introduced a feature but I am not 100%. It might be worth watching the Office 365 Garage series to see if its mentioned


  2. Hi Andrew, I’ve used your blog to help deliver Office click to run at our business but I have a question for you. Each time the PC’s shutdown it appears the PC is trying to uninstall the legacy office and reinstall the C2R. Have you found this happening and have you been able to get it to run only once?
    Thanks, Ben.

      1. Hey,

        Yep I deployed it in a GPO applied to selected Computers in a Shutdown script, just as you have in described. Office 2010 is scrubbed and Office CR2 is installed fine. But each time the PC shuts down it looks like the script runs again.

        I’m not sure how to set the GPO to run once? Other can possibly adding a reg query into the shutdown script?

        Great posts btw!

        1. If C2R has successfully deployed I would remove the target machines from the Security Filtering or Once you have C2R out and working there is no need to use the GPO so you can unlink it from OUs. C2R will update via the defined information in the configuration.xml and you wont need to install it via GPOs.

Leave a Reply

Your email address will not be published. Required fields are marked *