\\NAS\Office365\O201032BIT\Setup.exe/uninstall standard /config \\NAS\Office365\SilientUninstallConfig.xml Set the Script Name to: “Office2010 Removal” and enter the following into the batch file field: Mine has been set to,Notify users before run, Options = OK/Cancel, Timeout = 15mins, TimeoutAction=Cancel, Snooze Duration=5, Initial message = “Office 365 Installation -PLEASE SAVE AND CLOSE YOUR WORK FIRST - Click OK to proceed.”Ĭhange the Schedule to run every 15 mins (or however adjust tomeet your requirements)Ĭhange Verify to: “Verify a directory exists” and set the pathto: “C:\program files (x86)\Microsoft Office\Office14”Ĭhange on Success to run a batch file. I’ve used the same account we use toinstall Microsoft Updates Under “Deploy” select the device label “D_Office_365_Install”Ĭhange the Operating Systems to “Microsoft Windows All” (thiswill enable the ability to use batch files when we come to setting up thetasks)Ĭhange the Windows Run As to use an account that has localadministrative rights to the machines. In this example I have create mineas: “D_Office_365_Install”Ĭreate a new Online KScript, in this example mine has beencalled: “SC_Office_365_Deployment”Įnter in a desired description and notes.
Save the XML file with the name of Configuration.xml into the root of the share, \\NAS\OFFICE365Ĭreate a manual device label. Edit the XML file so the SourcePath is pointing to your share,and adjust the Channel depending on your Office 365 agreement, ours has beenset to Monthly, please see my XML below:ħ.
Download the office Deployment tools and extract the contentsto the root if \\NAS\OFFICE365:Ħ. Save the XML file to the root of the share with the name of SilientUninstallConfig.xmlĥ.
For Office 2010 Pro change “standard”for “ ProPlus”:Ĥ. Create a XML file using notepad with the following config,note this is for Office 2010 standard.
Within the share I copied the contents of "C:\ProgramFiles (x86)\Common Files\Microsoft Shared\OFFICE14\Office SetupController" from a working Office 2010 computer to a folder called “Office201032BIT”on \\NAS\OFFICE365ģ. In this example I’llrefer to the share as, “\\NAS\OFFICE365”Ģ. As our environment isn't massive, we chose to create anew share off our distribution NAS and granted users read and write access it.For larger environments it might be wise to use a DFS. Step 1 - Creating a network share to host the Office 2010uninstall and Office 2016 Installation files.ġ. If so I've managed to find asolution within our environment. It goes on to add, among other things, that support for Office 2016 was meant to be for only five years and these are going to run out in less than two months and a half from now.I'm unsure if you still require assistance in removing Office2010 Standard and deploying Office 2016 via KACE. In fact, most online help content will be retired.“
But here’s what the end of support means for you:
Rest assured that all your Office 2016 apps will continue to function-they won’t disappear from your Mac, nor will you lose any data. “ Support for Office 2016 for Mac will end on October 13, 2020. (Curiously, it is the same day as the EOL of Office 2010 for Windows.) More about the EOL of Office 2016 for Mac here: