Scripting

Hello

I'm unsure if you still require assistance in removing Office2010 Standard and deploying Office 2016 via KACE. If so I've managed to find asolution within our environment.

Step 1 - Creating a network share to host the Office 2010uninstall and Office 2016 Installation files.

1. 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. In this example I’llrefer to the share as,  “\\NAS\OFFICE365”

2. 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

3. Create a XML file using notepad with the following config,note this is for Office 2010 standard. For Office 2010 Pro change “standard”for “ProPlus”:

<ConfigurationProduct="Standard">

<DisplayLevel="none" CompletionNotice="no"SuppressModal="yes" AcceptEula="yes" />

</Configuration>

4. Save the XML file to the root of the share with the name of SilientUninstallConfig.xml

5. Download the office Deployment tools and extract the contentsto the root if \\NAS\OFFICE365:

Deployment tool link: https://docs.microsoft.com/en-us/deployoffice/overview-of-the-office-2016-deployment-tool

6. 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:

<AddOfficeClientEdition="32" Channel="Monthly"SourcePath="\\NAS\OFFICE365">

    <ProductID="O365ProPlusRetail">

      <Language ID="en-us" />

    </Product>

    <ProductID="VisioProRetail">

      <Language ID="en-us" />

    </Product>

  </Add>

7. Save the XML file with the name of Configuration.xml into the root of the share, \\NAS\OFFICE365

Step 2 – Setting up theKACE Script

1. Create a manual device label. In this example I have create mineas: “D_Office_365_Install”

2. Create a new Online KScript, in this example mine has beencalled: “SC_Office_365_Deployment”

3. Tick the “Enable” box

4. Enter in a desired description and notes.

5. Under “Deploy” select the device label “D_Office_365_Install”

6. Change the Operating Systems to “Microsoft Windows All” (thiswill enable the ability to use batch files when we come to setting up thetasks)

7. Change the Windows Run As to use an account that has localadministrative rights to the machines. I’ve used the same account we use toinstall Microsoft Updates

8. Set the desired Notification parameters. 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..”

9. Change the Schedule to run every 15 mins (or however adjust tomeet your requirements)

Step 3 –Creating Tasks

Task 1

1. Set attempts to 1

2. Change the “On Failure” to Continue

3. Change Verify to: “Verify a directory exists” and set the pathto: “C:\program files (x86)\Microsoft Office\Office14”

4. Change on Success to run a batch file. Set the Script Name to: “Office2010 Removal” and enter the following into the batch file field:

\\NAS\Office365\O201032BIT\Setup.exe/uninstall standard /config \\NAS\Office365\SilientUninstallConfig.xml

Tick “Wait for completion” then clickSave Changes

1. Change Remediation to Log message, Type = Status, Message = “Office2010 does exist” then click Save Changes

2. Change “On Remediation Success” to “Log message”, Type = Status,Message = “Office 2010 removal script completed”. Click Save Changes.

3. Change On Remediation Failure to “Log message”, Type = Status,message = “Office 2010 removal script failed” then click Save Changes

Task 2

1. Set attempts to 1

2. Change the “On Failure” to break

3. Change Verify to “Verify that the directory exists” and set thepath to: “C:\program files (x86)\Microsoft Office\Office16”, then click savechanges

4. Change “On Success” to “Log Message”, type status, message “Office365  is already installed”, then clickSave Changes

5. Change “Remediation” to Run a batch file, set the script name to“Install Office 365”, enter the following into the bath file field:

\\NAS\Office365\setup.exe/configure \\NAS\Office365\configuration.xml

1. Tick the “Wait for completion box and click save changes

2. Change “On Remediation Success” to “Log message”, type  = status, Message  = “Office 365 Installation was successful”,click save changes

3. Change “On Remediation Failure” to “Log message”, Type = status,Message = “Office 365 Installation failed”. Click save changes

4. Click Save at the bottom of the screen to save the script.

To test the above, apply the D_Office_365_Install label to atest machine running Office 2010 Standard. Force Inventory and wait for theKACE prompt to appear. Click OK to start the script, this will uninstall Office2010 Standard, then reboot once finished.

Log back into the machine and wait for the KACE prompt again.Click ok and let the script run again, this will then install Office 2016.

Remove the user from the label.

If the script runs again it will just cancel itself off, sothere is no harm if you forget to remove the device from the label. The enduser will get prompted to run the script again, which will no doubt prompt acall to your service desk. As the script will just cancel itself as it willdetect Office 2016 is installed you won’t need to worry.