Software Deployment Question

Deploy Sanford CardScan Outlook Add-in

07/26/2017 1142 views

Hello together,

I am trying to deploy the Sanford CardScan Outlook Add-in with SCCM.

Download: http://www.cardscan.com/support/cs_dl_v9_client.asp?v=o

I was able to extract the .MSI and the installation works, I am using the following command line:

SET INSTALLFILE=CardScan_for_Outlook.msi

MSIEXEC /i "%~dp0%INSTALLFILE%" ALLUSERS=1 /qn /norestart

The problem is, that the add-in doesn't activate automatically. I have to go to add-ins in Outlook, select add add-in, and navigate to the installation path and select:

"C:\Program Files (x86)\CardScan\CardScan for Outlook\adxloader.dll"

That is not a good solution for the users.

Has somebody an idea?

Kind regards,


0 Comments   [ + ] Show comments


All Answers

Office add-ins are added per-user so you need to determine where in HKCU the data's getting written and then author an MST which:

- creates the user profile stuff
- either a) alters the feature so that the feature containing the above becomes the parent of a feature which contains an advertised entry-point (in order to trigger self-healing) or b) if there are no advertised entry-points, creates entries for use by Active Setup (also to trigger self-healing).
Answered 07/28/2017 by: VBScab
Red Belt


I think I can find the settings in registry which are written when the add-in is activated, even if it seems to be a lot.

Which changes exactly have to be done for the .mst when I open the .msi with Orca?

We also often make a preinstallation on computers where no user have been logged on still.

Would the add-in activate when a user logs-on then?

Answered 07/28/2017 by: NamelessOne
Senior White Belt

Would the add-in activate when a user logs-on then?
No, it has to be put into HKEY_CURRENT_USER.

Which changes exactly have to be done for the .mst when I open the .msi with Orca?
It's too long-winded to repeat here. Google for John McFadyen's blog about self-healing and search IT Ninja, too. You'll find plenty of responses about it.

Oh and get InstEdit. It's Orca on steroids. For one, when you open an MST or MSP, it intelligently stays in the source folder for you to select the base MSI, unlike Orca which pleases itself where the Hell it opens for browsing. More usefully, it tracks linked entries in tables so if you make a change that impacts a record in another table, it will prompt you, unlike Orca which is quite happy for you to unknowingly trash an MSI.
Answered 07/31/2017 by: VBScab
Red Belt


Thank you, I will give InstEdit a try.

In this case, I will probably just copy & paste the .DLL files and register them for the user, as it doesn't seem to be possible to install for system and get it automatically registered for user.

Answered 08/03/2017 by: NamelessOne
Senior White Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ