OneDrive for Business High CPU

Had an issue where OneDrive for Business (installed with Office 365) was constantly using one CPU core. None if the fixes involving the cache or resetting the client worked. The problem seems to have started with recent (possibly after Office 365 1712 8827.2148) updates. What did work was the solution in this thread:

Condensed version: Stop using the old client (groove.exe) and use the personal client instead, which now seems to work (at least, the latest Windows 10 version) with business accounts as well.

(Note that this doesn’t apply to connections to onsite hosted sharepoint drives – there is apparently a fix coming sometime.)

The sequence is:

  1. Stop the OneDrive for Business client (right-click the system tray icon and choose exit, or kill it otherwise).
  2. Disable it from starting (use msconfig as an easy way to do this).
  3. Remove the existing OneDrive for Business folders (move them to a backup location)
  4. Open the personal OneDrive settings.
  5. Add an account and connect to the business account.


Office 365 install without activating

If you need to install Office 365 on a user’s laptop but not activate it (because you can only do it five times yourself), read on…

Get the deployment tool (link for Office 365 2016)

Run the executable – this will extract the setup.exe and configuration.xml files. Put these in a handy directory.

The default configuration.xml should be ok for downloading the installation sources (32-bit Office and Visio). Run setup.exe /download – this will download the office sources to a subdirectory Office\Data (there’s about 1.25 Gb of files). Note there is no progress indicator!

To install, edit the configuration.xml file to uncomment and change the Display option as follows;

<Display Level="None" AcceptEULA="FALSE" />

Run the setup tool again to install:

setup.exe /configure

(If no other options are given it will use the configuration.xml in the same directory and the install data sources in the Office\Data subdirectory).

Note: no progress is shown, except for the setup program eventually exiting.

This should result in a default install of Office and Visio, ready to be activated on first run.

If you are doing this for a system image, do not run any of the Office programs! Even if you cancel the activation dialog and exit, it still generates a unique ID for the install that you probably don’t want to clone.

To see the various other things the tool can do see the documentation linked from the download page. (One interesting thing – you apparently can install a version that allows multiple people on a system to use Office without it counting against their 5-system limit, such as on a terminal server. In this case we’d probably use the Office 2016 install activated against the KMS server, but someone might find this useful).

Volume licenced Office 2016 Repeated Activation Prompts

Had a situation that seems to be fairly common – get laptop, uninstall “Get Office” program, install Office 2016 and activate using KMS server, which seems to work fine. Then when you fire up one of the programs you get the “Lets get started” screen. You can close this and it works ok, but it is annoying.

To fix this see (deleting a couple of registry keys that make Office think it’s still in OEM mode).