If you want to fully remove an installation of Office, the best way is to use a VBScript called Offscrub, which is provided by Microsoft. This script has been widely used for removing Office 2007, 2010 and 2013.
This script is also available for Office 2016 and Office 365, but it is slightly hidden.
Follow the below instructions:
- To retrieve it, go to this link: https://support.office.com/en-us/article/Uninstall-Office-2013-Office-2016-or-Office-365-from-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8?ui=en-US&rs=en-US&ad=US
- Go to Option 2 – Completely uninstall Office with the easy fix tool and download the easy fix tool which is a file called O15CTRRemove.diagcab.CAB
- Go to the download location and open the CAB file using 7-Zip or similar.
- Extract OffScrub_O16msi.vbs
- Done! Now you can run the script either manually on a computer or most likely as part of another script deployed through ConfigMgr 🙂
The other day I was upgrading a customer’s environment to ConfigMgr 1602 when I ran in to an issue. Following the upgrade to ConfigMgr 1511 I went in to the Updates and Servicing node to upgrade to 1602. I received a No items found message, even though the update had been properly synced according to the logs.
The reason why this happens is due to the scope of the object in the ConfigMgr RBA. If the account does not have access to All Security Scopes, the update will not be visible.
Solving this requires you to add the All Security Scopes to the Administrative User/Group which will run the update.
Go to Administration\Overview\Security\Administrative Users, right-click and go to Properties.
Press Add and All Security Scopes.
Once added, the All Security Scope will be visible.
Once you have added All Security Scopes, close the console and re-open it. Now the update should be visible 🙂
Microsoft recently released the Cumulative Update 1 which fixed a lot of bugs that was introduced with Configuration Manager 2012 R2 SP1. One of the nice features with Configuration Manager R2 SP1 CU1 is that it is now possible to Automatically Upgrade clients to the latest CU version. Automatic Client Upgrade was present before but it only worked for new builds of the client, i.e Service Packs.
One trick here to keep in mind is that when installing the Cumulative Update is that you need to update Automatic Updates in the Hierarchy Settings before you run the CU1 wizard.
If you don’t, you will not see this step in the wizard:
When selecting Automatically apply this happens:
- The latest client patch file is added to the Site Server
- Updates the content on all Distribution Points and on all Child Sites if you are running a CAS
- The Client Package will be upgraded on the Local Site. Note that you need to run the CU1 upgrade on all child sites as well if you have an hierarchy to make sure that the latest version is on all Management Points. This Client Package is used if there are no Distribution Points available during Client Installation.
This is how you enable Automatic Client Upgrade:
1. Select your Site and select Hierarchy Settings in the top ribbon.
2. Go to the Automatic Client Upgrade tab
3. Check Upgrade client automatically when new client updates are available and press OK in the window that pop ups
When enabling the Automatic Client Upgrade, Configuration Manager will create a Scheduled Task for each client machine that have a version number lower that the Latest Version property. The Schedule Task will be created with a random run interval, which means that all of the clients will not be updated at the same time, which could cause performance issues. Define during which interval the clients will be upgraded. 7 days is the default, which is usually fine, but change it according to your requirements.
Once you have configured the Automatic Client Upgrade, simply run through the CU1 installation wizard, and you will see the step where you can select Automatically Apply as I previously mentioned.
One confusion you might run in to is when you go back and check the Latest version property in the Automatic Client Upgrade tab again after the CU1 upgrade. This version will not be changed and will remain at the Configuration Manager R2 SP1 level.
Here is the TechNet article referencing this.