Verizon Conferencing Add-in to Outlook 2003

Hi Everyone

What I have with me is an outlook add-in which is just becoming a pain in the neck in all ways possible.
Its a VSTO add-in for Outlook 2003. We got this request because the add-in is installed per-user and doesn't appear for other users. We need to make this work for all the users on the system.
The pre-requisites for this app are O2003pia.msi, vstor.exe, vstolp20.exe, extensibilitymsm.msi, lockbackRegKey.msi. These are all bundled in one ISO_prereq.exe.
I know this because all these get extracted and disappear from temp in a jiffy.
I tried to capture the rest of the installation, but my MSI just wouldn't work for even the user who installs it.
The files are installed into the folder "C:\Documents and Settings\UserName\Local Settings\Application Data\Verizon\Conferencing\InstantScheduler". There is also one file which goes into "C:\Program Files\Microsoft Office\OFFICE11\ADDINS\OTKLoadr.dll"
There are also the add-in registries that go into HKCU\SOFTWARE\Microsoft\Office\Outlook\Addins\InstantScheduler.

I have tried manually trying to make the add-in appear in outlook for other users by moving HKCU keys to HKLM, copying user specific files, but in vain. From what I have read online, if the HKCU keys in the setup project (the vsto add-in) are modified to go to HKLM, apparently things are fine. I have no idea which file needs to be modified in my case and how.. from a packager perspective, this is really frustrating ..
I just want to know if anyone could ever succesfully install a vsto add-in to outlook for all users on a machine and how :-(
Any help would be greatly appreciated.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 13 years ago
Red Belt
You need to find out which feature in which package installs the files to the user profile, along with the one - if different - which installs the registry value. If the feature has an advertised entry-point, such as a shortcut, then you need to create a user feature, move the feature above so that it becomes a child of the feature containing the entry-point. That way, self-healing will kick in when the entry-point is triggered and will install the user-level stuff.

If there is no advertised entry-point for the feature, use Active Setup. Remember that AS does not self-repair so if components get deleted, the WI engine won't fix them.
Posted by: msi_support 13 years ago
Orange Belt
Thanks for your support. The MSIs i mentioned are the prerequisites.. None of those actually have the add-in files in it.
After the pre-requisites install, there is something more to the installation that goes on, and I have captured the files and registries put in during that time, but those alone do not make the add-in appear in outlook.
The worst part is the main setup doesn't even install silently. (Even if i want to just push the app for that particular user)
Posted by: anonymous_9363 13 years ago
Red Belt
Fine, so it sounds like you have an MSI created from a capture? Excellent: you can create your own feature tree if you have an entry-point. I'll bet at least ONE of the support files registers a bunch of objects, in which case you can use COM advertising.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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