Software Deployment

Is this an add-in for Office 2003 or 2007? ...
Office 2007 no longer supports Global addins, therefore you must install the add-ins for each user.

Try Installing your add-in through Radia and then log in(if you're not already) and run
msiexec /fu {GUID} /qb

The "/fu" will reinstall that products User components - HKCU entries, User profile files/shortcuts

If this works then simply add an Active Setup component to your installation and/or Try setting the ZSYSACCT variable in the SERVICE to N instead of Y.

this is vendor MSI which installs excel addins through some custom actions. I created MST to add excel addins with scripts.If the MSI already installs them, why is there a requirement for the transform to do the same thing in script? I don't get it...

As im sure you know your radia application is installing in the system context, if you need stuff going into HKCU then you will need to write a script to insert the data into the correct location in the registry. I have written such scripts that seem to work using WMI so it is possible.

P

its like that since vendor msi contains custom action that installs excel addins only admin mode so i added scripts to add addins in user mode through active setup but till radia isn't able to reflect the addins.

i am struck in this sitution for quite sometime....

Im assumnig the problem your facing is to do with HKEY_CURRENT_USER entries in the registry, is that correct?

P

Its adding the addins in OPEN registry but its not able to shows the menus associated with the addins i user as well as admin.

What I would do is confirm that the vendor MSI in its default state works manually, if it does then publish the vendor MSI to Radia with NO transforms. From what I can tell you are trying to install the addin via a script rather than using the vendor custom action and this could potentially be dangerous as you may find the custom action does more than just add the excel addin itself, which is why your having problems. If all else fails do a drop and run of the vendor msi and avoid using radia, tbh I would be looking at other radia deployment options rather than trying to tweak a custom action from the vendor as i suspect your script is the problem.

Try using a basic radia msi publish deployment as well using msiexec, that way you avoid radia altogether, well mostly.

P

Following this post with interest and just wanted to add that there is an additional option avaiable which I have used on one particular site. In office 2003 (not checked other versions) there is a folder under the path "C:\Program Files\Microsoft Office\OFFICE11\Library" which can be used as a repository for Excel Addins.

When a user launches Excel and clicks the menu item "Tools->Addins" and the "Addins" window is displayed the Addin copied to the location above (e.g. Test.xla) will be listed as an available addin to be selected; note: the title of the addin displayed in the Addins window may be different from the file name, just check the Summary information tab of file's properties for confirmation. This then writes the correct "OPEN" "OPEN1" "OPEN2" etc. registry information under the HKCU hive for each selected addin.