Office365 banner

Office 365 Installer

Install any Office 365 product silently

Description

• Windows only
• Silently installs Office, can be run against user workstations as they are logged in and using the device.
• Only end user visible if they have prior Office versions running, as the installation will terminate them.
• Can be used on top of Office 2013 products, will upgrade them in place assuming they were of the Office 365 variants.
• Can be set to x86 or x64, and to any supported language.
• Can remove previous Office installs with an optional flag
• No need to have user credentials, once the software installs, it will prompt the user for credentials on first run to activate.
• Requires Office 365 licensing.


**If this procedure fails, check the procedure logs, found at Agent>Agent Logs>Agent Admin Logs>Procedure History.**

This procedure is built around the Microsoft Office Click 2 Run toolkit, as documented here: https://support.microsoft.com/en-us/help/2842297/product-ids-that-are-supported-by-the-office-deployment-tool-for-click

Should the procedure stop working suddenly, the Office C2R Deployment toolkit must be replaced with a newer version. Download here :https://www.microsoft.com/en-us/download/details.aspx?id=49117 Upload to the shared files directory as indicated in the install instructions, and update lines 23, 26 and 33 to reflect new EXE name.

NOTE: There is an incompatibility between Office 2016 and Project / Visio 2013. There is no workaround other than switching to Project / Visio 2016. This is a Microsoft issue, not a failing with the script.

UPDATE NOTES:
4.27.18: 1.0.1 Added verbose logging and free space checking. Procedure will fail if the system has less than the needed 3gb of free space on the OS Volume. When the procedure is first installed, if it has any issues, please check the logs, they include troubleshooting steps for the most common issues.
5.16.18: 1.0.2 Updates 7zip and the C2R toolkits to the latest versions.
1.22.19: 1.1.0 Removed need for 7zip components, updated C2R toolkit, added 2019 supported products bringing the total supported from 24 to 51, and cleaned up code
1.25.19: 1.1.1 Added option to remove older installs of Office. Changed language from 'en-us' to match the language of the target workstation. Office installer logs now write to C:\Temp\OfficeInstallLogs
2.2.19: 1.1.2 Fixed bug where lack of user input in the ProductID field would not default to 1, but would instead break the script. Removed cost, script is now free.

Developer
  • Name: Quinn Van Order
  • Company: SWAT Systems
  • Website: http://www.swatsystems.com/
  • Contact Developer
  • Summary
  • Office 365 Installer
  • 98 Downloads
  • Version: 1.1.2
  • Released on November 2nd, 2017
  • Reviews
    Gravatar for samuel@finkeltron.com
    by samuel@finkeltron.com on January 15th, 2018

    The instructions were unclear at first but developer was quick to help. Procedure works perfectly.

    Gravatar for Oliver Heymanns
    by Oliver Heymanns on December 6th, 2017

    Nice Script, works perfectly and saves a lot of time. For Information, we deploy Office 2016 german Version.

    Discussion
    Gravatar for samuel@finkeltron.com
    samuel@finkeltron.com about 1 year ago

    I get error
    Script Summary: Failed THEN in step 5 (Line 14)

    Gravatar for Quinn Van Order
    Quinn Van Order about 1 year ago

    Hey Samuel, line 14 is one of the writefile commands. When this occurs, it generally means the component files it relies upon cannot be found. As per the installation instructions please verify that you have placed the components in a directory named "O365" within the Kaseya shared files directory, and that the write file commands are correctly pointed at said components. If you used a different folder name, you can simply alter the writefile commands to point in the right direction.

    Gravatar for samuel@finkeltron.com
    samuel@finkeltron.com about 1 year ago

    It's all working now that the instructions are a bit more clear. Thank you.

    Gravatar for samuel@finkeltron.com
    samuel@finkeltron.com about 1 year ago

    It's all working now that the instructions are a bit more clear. Thank you.

    Gravatar for John Rutkowski
    John Rutkowski about 1 year ago

    Got a Success on the Script but no Office Pro Plus. Office 2013 32 is installed

    Gravatar for Quinn Van Order
    Quinn Van Order about 1 year ago

    Hey John, That is interesting! I will reach out to you directly, but I have a suspicion that the situation here is something along the lines of "User had a box copy of office 2013 installed, and it included either Projects or Visio". In that case, this procedure will complete, but office will fail to install, as there is a system breaking incompatibility between those 2 office products and the Click2Run version of office 2016. A planned future revision of this script will log when it hits this eventuality. When testing the script for the first time, it may be wise to throw it against a vanilla setup, just to make sure the core functionality is there.

    I will email you directly to get to the bottom of this!
    -Q

    Gravatar for John Rutkowski
    John Rutkowski about 1 year ago

    Thanks for the speedy reply. The existing copy is Open Value licenses version, no Project or Visio, I looked. I'll thorw an Uninstall command at the beginning

    Gravatar for John Rutkowski
    John Rutkowski about 1 year ago

    Thanks for the speedy reply. The existing copy is Open Value licenses version, no Project or Visio, I looked. I'll thorw an Uninstall command at the beginning

    Gravatar for Quinn Van Order
    Quinn Van Order about 1 year ago

    Hey John, I have never encountered that flavor of office, so its possible this is an edge case I had not accounted for. Worst case, removing the previous office prior to deployment should solve your issue. That said, if your use case is entirely or predominately with machines in this configuration, I would be happy to update this script to account for this situation.

    Gravatar for John Rutkowski
    John Rutkowski about 1 year ago

    I set the CONFIGURATION.XML View value to FULL just to see where it gets to, so far the progress bar sits with just a small red bit,

    Gravatar for John Rutkowski
    John Rutkowski about 1 year ago

    The is the Microsoft licensed version before Office365 came into existence. Open Value, Open Business are the other names. I have used the Deployment tool, I know it works, but somethings is amiss.

    Gravatar for Quinn Van Order
    Quinn Van Order about 1 year ago

    Interesting, so all the moving parts are doing what they should be doing, it almost sounds like a networking issue, if the c2r toolkit is running but is unable to grab the files, I would investigate if you have any network schenanagins in play that may interrupt it phoning home to microsoft. I would advise you setup a tester machine with a fresh copy of windows, and run the script against that just to verify its working in a best case scenario. Testing a new script acquisition against a production machine may send you down a rabbit hole!

    Gravatar for Reinier Onestinghel
    Reinier Onestinghel 10 months ago

    Hi Quinn, would your Agent Procedure also work for MacOS clients?

    Gravatar for Joseph Mayes
    Joseph Mayes 5 months ago

    Hi Quinn, I am having an issue where the Procedure completes but gives an  error in logs: "10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run anhmp Medium Prereq::ShowPrereqFailure: A Prereq check has failed. We can't install  The following product(s) can’t be installed at the same time:   O365ProPlusRetail  "

    Tried uninstalling Office 2010 also before running the script. End goal is to install Office 365 Pro Plus to be ready for business user sign in and activation...


    10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run General Telemetry ckvrc Medium ChannelValidator::GetIncomingChannel {"MachineId": "47953fe06217d844be1f6571df88c977", "SessionID": "3077907d-3dfe-4e5a-8266-3ad2b646d771", "GeoID": 244, "Ver": "16.0.10827.20150", "C2RClientVer": "0.0", "ContextData": "Incoming channel type: monthly."} BCD1C001-BA37-4307-AEEB-F68B995105CD

    10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run General Telemetry ckvre Medium ChannelValidator::GetErrorMessageBodyParam {"MachineId": "47953fe06217d844be1f6571df88c977", "SessionID": "3077907d-3dfe-4e5a-8266-3ad2b646d771", "GeoID": 244, "Ver": "16.0.10827.20150", "C2RClientVer": "0.0", "ContextData": "Blocking apps: O365ProPlusRetail]"} BCD1C001-BA37-4307-AEEB-F68B995105CD

    10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run anhmp Medium Prereq::ShowPrereqFailure: A Prereq check has failed. We can't install  The following product(s) can’t be installed at the same time:   O365ProPlusRetail    https://officeredir.microsoft.com/r/rlidOfficeWebHelp?p1=OCSAC2RClickToRun&ver=16&clid=1033&helpid=%2221-BOOTSTRAPPER_PREREQ-mismatched_channel_internal%22&app=webview BCD1C001-BA37-4307-AEEB-F68B995105CD

    10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run aoh88 Medium RunPrereqs::HandleStateAction Prereq check has failed. BCD1C001-BA37-4307-AEEB-F68B995105CD

    10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run General Telemetry aoh9b Medium HandlePrereqFailure::HandleStateAction {"MachineId": "47953fe06217d844be1f6571df88c977", "SessionID": "3077907d-3dfe-4e5a-8266-3ad2b646d771", "GeoID": 244, "Ver": "16.0.10827.20150", "C2RClientVer": "0.0", "ContextData": "HandlePrereqFailure::HandleStateAction: Fatal failure. Showing UI and quitting bootstrapper."} BCD1C001-BA37-4307-AEEB-F68B995105CD

    10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run General Telemetry aoh9g Medium TryShowUI::HandleStateAction {"MachineId": "47953fe06217d844be1f6571df88c977", "SessionID": "3077907d-3dfe-4e5a-8266-3ad2b646d771", "GeoID": 244, "Ver": "16.0.10827.20150", "C2RClientVer": "0.0", "ContextData": "Failure has occured, admin has disabled failure UI."} BCD1C001-BA37-4307-AEEB-F68B995105CD

    10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run aoh72 Medium ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0 BCD1C001-BA37-4307-AEEB-F68B995105CD

    10/10/2018 18:11:43.820 SETUP (0x1108) 0xf20 Click-To-Run General Telemetry arqpm Medium wWinMain {"MachineId": "47953fe06217d844be1f6571df88c977", "SessionID": "3077907d-3dfe-4e5a-8266-3ad2b646d771", "GeoID": 244, "Ver": "16.0.10827.20150", "C2RClientVer": "0.0", "ContextData": "AdminBootstrapper::Main: Installation came back with 1603."} BCD1C001-BA37-4307-AEEB-F68B995105CD

    Gravatar for Louis Sorace
    Louis Sorace 5 months ago

    Quinn,

    I had a question regarding tailoring this script for a single version of office, I am trying to incorporate it into a master script to automate our computer deployments, unfortunately when calling the procedure into another one I don't get the prompt to select the version. Any advice here would be appreciated.

    Louis

    Gravatar for Bryan Donahue
    Bryan Donahue 2 months ago

    Hello, 

    Everything has been working great with this procedure up until recently. The procedure is finishing Successful but Office is not installed on the client. Did not notice any problems in the log. We have made no changes to the procedure since it was originally setup in July 2018. Has anything changed recently?

    Gravatar for Valdes Help Desk
    Valdes Help Desk 2 months ago

    I concur with Bryan Donahue, ours also stopped working within the last 10 days or so. 

    Gravatar for Doug Herring
    Doug Herring 2 months ago

    Ditto to Bryan and Valdes. Recently purchased and cannot get working.
    Sent message to creator via this site and no response in a few days.

    Gravatar for Seth
    Seth 2 months ago

    Ditto Bryan, Valdes, and Doug.

    Gravatar for Quinn Van Order
    Quinn Van Order 2 months ago

    Hey all,

    It looks like Msft has changed how this tool functions, I am working on a fix now. In short, there is now a newer version of the tool which has different configs for 32 bit and 64 bit. Sorry for the late response, it has been some time since I have logged into the exchange. I hope to have a fix in the next few days. I will reply back to this when the fix is live on this site, as it can take a little bit for Kaseya to approve changes to the source files.

    @Louis - To make the procedure run for a single target version at any time, edit the script to change the variable on line 2 from "Prompt when procedure is scheduled" to "constant value" and input the number you wish to have be your fixed version.

    @Reinier - Unfortunately nope, the underlying tools are windows only. I have found no comparable way to do this on Mac

    @Joseph - In that case, the script has successfully run, and the failing is with the c2r toolkit itself, something Microsoft would be able to handle, but based on those logs, it appears you have something else in place that is terminating the install. I would check for incompatible software, project and visio of different versions are a frequent culprit.

    Gravatar for Quinn Van Order
    Quinn Van Order about 2 months ago

    Update: I have completed repairs, added support for the new products that the C2R toolkit works with, bringing supported products from 24 to 51. Changes have been uploaded and are pending review. Within the next day or so, they should be available to re-download via this portal. Also of note, the reliance on 7zip has been removed, so those components can be removed from the shared files directory within the VSA.

    Gravatar for Quinn Van Order
    Quinn Van Order about 2 months ago

    The new version appears to be live, let me know if issues persist.

    Gravatar for Miguel Aleman
    Miguel Aleman about 1 month ago

    Hello Quinn- I was wondering where i would be able to find a list for option 1?  We are testing between O365 C2R and Office 2019 C2R and i didnt see the latter listed as an option.  Once we define which version we are going to use, i would like to hardcode that value.  Can you let me know what option is for either of those? In both of these cases we would use the pro plus option.

    Gravatar for Quinn Van Order
    Quinn Van Order about 1 month ago

    The procedure description includes the product list. Due to a restrictive character limit, I was barely able to hold the whole list, and as such the description holds nothing but said list. As for hardcoding, the procedure install directions go over that, as do the comments within the procedure. The short version is alter the relevant variable from prompt to constant, and set it as desired. 

    Gravatar for Miguel Aleman
    Miguel Aleman about 1 month ago

    Quinn-

    Thanks for the quick reply, I caught my rookie mistake way to late and was not able to remove the comment :/  i am trying to run this tool on a machine that had 2016 msi installation and can successfully remove the older version but the new installation is not completing as expected.  The logs all point to the activity, install, cofig etc.  I have modified the config file to use display "true" and will hopefully find what the root cause is.



    Gravatar for Quinn Van Order
    Quinn Van Order about 1 month ago

    Sounds like a plan, however I suspect that you won't see any GUI regardless of your display flag, as the install is run in the system context. 

    The procedure itself logs to kaseya, assuming it indicates no errors, and completes as expected, then the procedure worked, and the failing is on the c2r side of things. That is the purpose of the office 365 logging. I would suggest pursuing any issues mentioned in those logs. Happy to help with the script side of things, but I cannot support the c2r side of things, and suggest you field those questions directly to Microsoft. 

    Gravatar for Miguel Aleman
    Miguel Aleman about 1 month ago

    Quinn- I was previously using another procedure to scrub the older office versions and then had created the install setup for office 2019.  Manual interaction working with the configuration.xml file but when i tried to do this via the shell action or via a .bat file it wouldnt run.

    Certainly may have some issue with connection to ms site or other... 


    Gravatar for Quinn Van Order
    Quinn Van Order about 1 month ago

    Does the procedure logs within kasyea indicate success?

    Gravatar for Miguel Aleman
    Miguel Aleman about 1 month ago

    Quinn- I left the procedure running yest and the test machine had the selected version installed when i came in this am.  No user interaction but I cannot tell exactly how long or how it finally completed?  The logs have this as a successful install as of 3:12 pm (cst) but i had checked around that time and there were no icons in the start menu.


    I have deployed this to another machine at of 9:05am and at this time (12:28) there is still no start menu items or folders.  The procedure shows a complete successful and the kaseya agent icon flashed with the office installation complete message.


    ?- is the download being throttled by bits?

    Wondering what your standard install time is in your environment?


    I did check the logs and did not find anything flagged as failed, the url that is listed is accessible and not blocked by our web filters.

    Gravatar for Patrick
    Patrick about 1 month ago

    Is there any known issues with scheduling to run on multiple machines over a period of time?

    I have configured the script to use constant variables in lieu of prompting.  When I look at the procedure log it appears as if everything ran fine but nothing appears to have happened.  There is no log created nor do I see an empty O365 file.  If I run on the same machines using run now, it works as intended.

    Gravatar for Miguel Aleman
    Miguel Aleman about 1 month ago

    Quinn-

    I have identified a few urls that are being blocked by our webfilter, although i get a success flag return on the procedure i am assuming that this could be a problem?


    officecdn.microsoft.com

    client-office365-tas.msedge.net

    a-0020.a-msedge.net

    webshell.suite.office.com