Windows

Disabled Add-ins in Microsoft Office

Hi,
Another little fix here. Many companies will have certain add-ins in their Microsoft Office products, and sometimes things go wrong. Often if an Office product crashes, it will blame an active plugin and bring up the prompt asking if you want to disable the add-in:

For most people presented with more than a line of text and a ‘Yes/No’ option, they’ll just click ‘Yes’ and continue on their merry way – not realising they’ve just crippled some functionality.

In Office 2010, it’s a bit of a pain to re-enable an add-in manually: Click File > Options > Add-ins > Drop down Manage and choose ‘Disabled Add-ins’ > Go > Choose the add-in > Click Enable > Click OK > Click OK > Have a nap. Hard work!

So, what I decided to do was use Group Policy to automatically wipe from the registry anything that’s disabled. This will happen on 90 minute intervals, and at login time – so for some users, it’s easier to train them to log off and back on (or reboot) if they’re having that important add-in disabled.

The relevant keys to delete are:

HKCU\Software\Microsoft\Office\14.0\Outlook\Resiliency\DisabledItems
HKCU\Software\Microsoft\Office\14.0\Word\Resiliency\DisabledItems
HKCU\Software\Microsoft\Office\14.0\Excel\Resiliency\DisabledItems

I am doing this with a Registry Group Policy Preference set to ‘Delete’

Of course this could be added to a login script if you use those, or if it’s a really common problem a desktop shortcut or reg file that deletes the key when the user choose to. All it needs to contain is this:

[-HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Resiliency\DisabledItems]
[-HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Resiliency\DisabledItems]
[-HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Excel\Resiliency\DisabledItems]

Note that this is for Office 2010, but the same works for 2007 and 2003, just the version path needs to be changed – for 2003, it’s 11.0 and 2007 is 12.0 (no unlucky 13.0).

SCSM 2010 and SCOM 2012 Consoles

Hi,
Thought I’d share this quick one, not many people will run into it, but anyway:

It seems that the SCSM 2010 console and the SCOM 2012 console can’t co-exist on the same box. A bit of a pain if you’ve built your centralised tool box.

I found this Microsoft Technet thread about the issue: http://social.technet.microsoft.com/Forums/en-US/systemcenterservicemanager/thread/33de3e93-207b-44cc-8afb-7c8aa7d774f4

The symptom is trying to launch the SCSM 2010 console and getting the error:

Failed to connect to server ‘scsmserver’
The container could not findĀ a component with name ‘ConfigurationExtension’…

The fix, is pretty much to uninstall SCOM 2012 console, and reinstall SCSM 2010. Bit of a pain, and hoping that SCSM 2012 can co-exist with SCOM 2012.