You can actually add the 2 add-ins as follows:

Open Excel 2007 -> Office Button -> Excel Options -> Add-Ins -> From Manage drop down menu select "Excel Addins" -> select check box before "Solver Add-in" and "Analysis Toolpak" and click OK

There you go. Those two Add-ins are added now in Excel 2007. I'm sure there will be registry entries which are causing these settings, particularly under HKCY\Software\Microsoft\Office.

Just try searching for registry keys and export them to a registry file. Now you have registry keys, add them to your PATCH using OCT.

I hope this helps. Let me know if you need anything more.

Thanks,
Eshwar

>Now you have registry keys, add them to your PATCH using OCT
That's a *really* bad idea. Why? Because MS add-in handling is peculiarly inept, relying as it does on a brain-dead numbering scheme to indicate which add-ins are to be added. So, let's say the user has 2 add-ins set up to load. These will be stored in 2 registry entries, e.g.,

HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPEN
HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPEN2

which contain the path and name of the add-ins.

Now, along comes your patch with 2 add-ins. If, as one would expect by default, the add-ins therein contain the same value names, i.e. OPEN and OPEN2, they will overwrite the user's entries. This is a sub-optimal way to change user's attitude to IT.

Find a (well-written) script which uses the Excel Automation object model to add (and remove) add-ins.

VBScab,
I do not agree with your logic in this particular case. As i have tried this already on my own before answering the question.

try adding the following

Let us say you have two existing registry keys [OPEN/OPEN2] with the same values as follows:

HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPEN
HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPEN2

Now i'm adding the following 2 registry entries [OPENa/OPENs] as follows:  

HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPENa    for analysis add-in 
HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPENs   for solver add-in

Once you install the registry keys, launch Excel 2007 application and check for the addins and close the application. Now goto registry and check for the registry entries. You will see the following 4 registry entries:

HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPEN
HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPEN1
HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPEN2
HKEY_CURRENT_USER\Software\Microsoft\Office\[OfficeVersionNbr]\Excel\Options\OPEN23

Just try this and let me know if this isn't really working.

Thanks,
Eshwar

No, the best way is to use the Automation model! As Homer would say 'Meh...' I'll go back to engaging me head with the wall. Less painful.

As VBScab notes, Excel Automation, or a custom action, is required to manage Excel add-ins correctly, including the UNINSTALL.

So if you have registry keys, OPEN, OPEN1, OPEN2, OPEN3, and you remove the add-in associated with OPEN1, then you need to renumber all registry entries after OPEN1 so that there are no "gaps" in the sequence. Otherwise, the addins after the "gap" will not appear in the add-ins list in Excel.

However, the first time installation of Office 2007 may be treated as a special case, as long as your user profile is not a roaming profile with old Office entries in HKCU.
Assuming a clean profile and a first time office 2007 install, it should be possible to get away with hard coding all the OPENx registry keys in sequence. However, at reinstall time, unless you add custom actions to nuke HKCU registry keys first, the end result may be unpredictable.

I'm packaging Office 2007 Service Pack 2. This information will surly help me.

Hi All,
Currently I am working on Office 2007 Pro Plus application.
I have created two packages out of it

[1]  Package with word,excel and power point(using msp)
[2]  Package with word,excel,power point and access(using msp)

Now both these packages have same GUID.My requirements are both these packages should have a different GUID,as office 2007 pro plus gets installed from the same source files how we can make it happen?
Any help is really appreciated..

Why do you require both packages to have a different GUID? Which GUID do you mean?

Frankly, I would strongly recommend that you do not change ANY standard office GUIDs, otherwise it is highly likely that you will be unable to apply any future service packs or office updates to your installation. I have seen many well-intentioned attempts to modify the Office MSI's, all of which have ended in grief.

In case of MSPs its not GUID but the names of the MSPs that are stored in UPDATES folder. All the patches [MSPs] that are stored under UPDATES folder are installed alphabetically.

However if you want to create unique configurations [like you specified above], you must store the customization files in a separate folder inside the source and specify the customization file you want on the command line.

Setup.exe /adminfile [path]

where path is the the complete path of the patch file.

Example
\\server\share\Office2k7\setup.exe /adminfile \\server\share\Office2k7\CustomPatch\WEP.msp
\\server\share\Office2k7\setup.exe /adminfile \\server\share\Office2k7\CustomPatch\WEPA.msp

Note:
WEP.msp [word,excel and power point]
WEPA.msp [word,excel,power point and access]

Hi All,
Thanks for your response.
These two packages will be deployed by Tivoli and the deployment team says  we need to ensure all the packages should have a unique product code(GUID Code)(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{Product code or GUID}).This is rule they follow for all the applications,I think this for tracking the applications on user's machine.
Look forward to hear from you soon.

with MS Office GUIDs, I'd invite them to do it themselves and have them suffer the consequences, not you.

There are different versions of Office - std, pro, enterprise, etc.
If your tivoli nobrains insist on different GUIDs, then the simple answer is to use a different version of Office 2007 instead of using the same version with different MSP files. Different versions of Office should have different GUIDs and that solves your problem.

Otherwise, suggest they discuss this with Microsoft, and see if Microsoft will permit them to change the product GUID, which I suspect is a licence violation.

Hi All,
Thanks all  for  response.
The Tivoli team is in touch with microsoft for this.I should be update you all on that a soon as hear from them.