Frequently Asked Questions:

1. What does this program do?
2. What keys does it monitor?
3. How do I use this program?
4. What Registry Settings Are there?
5. Does this work in Citrix?
6. How do I centrally deploy the program with Group Policy?

 What does this program do?

This small program runs in the system tray and will “protect” a specified list of Office Add-Ins from getting disabled.  The admin specifies a list of program names that this program should “monitor” and prevent from getting disabled.  The program will monitor the registry and check when an Office Application writes to the StartupItems folder within the Resiliency registry key within Office. If a value is written to the monitored registry folder the application will compare the value to a specified regex pattern to see if it finds a match.  If it does it will delete the value from the registry.

The end result of this process is that when an Office Application hangs/crashes/etc when add-in xyz is active the user should no longer receive the "Do you want to disable add-in xyz?" the next time they load the Office Application.

The program is designed to work with Office 2007/2010 (and possibly 2013)

What keys does it monitor:

Anything written to the Office Apps Resiliency folders:





How do I use this program:

The program runs as a system tray application in the context of the user who is logged on to the system.

When 1st launched it will look for its configuration settings in the following locations:

1. HKCU\Software\Policies\AddInMon

2. HKCU\Software\AddInMon

If it finds settings it will load them from the registry and automatically start monitoring the Office applications for add-in disables based on the regex pattern.

If there are no settings found then the pogram will just sit in the system tray and do nothing until configured.

You can double click the tray icon to see in real-time what add-ins are being used. With the program open start using an office application and be amazed as what add-ins are being loaded/unloaded in real-time. Once you get a feel for what applications are running you can create a regular expression to start "protecting" particular addins from being disabled

What Registry Settings Are there:

HKCU\Software\AddInMon\Debug REG_SZ Values:True or False

If set this will write out a debug logfile to the users %temp%\AddInMonDebug.txt

      HKCU\Software\AddInMon\RegEx REG_SZ Values:Any Regular Expression Pattern

This value controls what the AddinMon will block from being saved in the StartupItems folder. Any set of strings containing the path or dll name of the add-in you would like to "protect" from being disabled should be listed in the regular expression.

For example we use: interwoven|interaction|vault


Does this work in Citrix:

           Yes, because the program runs under the context of the current user and the program is reviewing the HKCU registry hive it is full supported and does not require admin rights to run.  The application currently runs on a per user basis.  If you have ten users logged in to the Citrix server there would be ten addinmon.exe processes running.  The application is very lightweight and should not affect performance of the server or user experience.


How do I centrally deploy the program with Group Policy:

        The only thing required to use this program is the one file called addinmon.exe and the setting of one registry key.  You can use group policy to deploy both to the users desktops and then put a shortcut to automatically start addinmon.exe upon logon. 

Step 1. Deploy Addinmon.exe


         Deploy addinmon.exe via User GPO.  Host the file addinmon.exe on a file server and copy locally to the users profile and/or c: drive. 


Step 2. Configure Registry Settings

            Configure the registry to notify the addin monitor as to what add-ins your are trying to protect. Be sure to use the pipe symbol “|” to delineate between the different addins you want to protect.  You any need to specify a part of the add-in name as it will match anywhere the string is found with the addin name and/or path to the actually dll the addin is running from.

                       For example we use: interwoven|interaction|vault



Step 3. Auto Start addinmon.exe on Logon

Configure the registry via GPO to put a shortuct to addinmon.exe in the StartUp folder for the current user


Last edited Dec 17, 2012 at 8:44 PM by mgplex99, version 13