Software Deployment

Follow up :
When I connect directly to the Siebel Server from a workstation
without my MSI package installed, it downloads and installes the files correctly.
The ActiveXstates the name and status correctly.

I have succesfully created a package for this, using WinInstall. I did a snapshot of the toolbar downloading, making sure I rebooted before the final snapshot. There is a fair amount of CLSID registry in the package and it took a few attempts to create a package that installed and worked. I will try and dig out the notes on this or better still give you a copy of the registry and file tables to cross check against what you've captured.

I have taken the problem from scratch :
- - - -
On a test machine with no Siebel Option Pack installed, I connected to the Siebel Web Server,
on connection it asked to install the "Siebel Option Pack for IE", I refused the installation.
- - - -
I created my WisePS package, add the 7 DLL's (that where pre registered) and INF,
and verifed that they added the HKCR\Interface\CLSID's.
I did not add the registery setting (http://www.appdeploy.com/packages/detail.asp?id=285)used to display the Siebel ActiveX component in the Dowloaded Proragram Files folder.
- - - -
On the same test machine I installed my package,
there was in fact no Siebel ActiveX component in the Downloaded Program Files folder displayed,
but when I connected again the Siebel Web Sever,
it did not ask to download and install the "Siebel Option Pack for IE", and passed on,
which to my sense means that it was reconized as being already installed.
- - - -
So my problem stays but has changed, being how (which registery entries entry) can I have my actual working MSI package, and have the Siebel ActiveX component displayed correctly in the Downloaded Program Files folder ?

Try the following:

Include ALL registry settings under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units in your package
In Windows Installer Editor, open the Tables tab in Setup Editor
Open the File table. Check the File column to determine the key for the record that corresponds to SiebelOptionPack.inf.
Go back to Installation Expert. In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{91C3F7AE-DD1F-4DF1-951F-F78369A5EE33}\DownloadInformation change the value of INF to [#<whatever the key was you just checked]

Ex: [#SiebelOptionPack.inf]

Test it out again using the same scenario as the one you just mentioned.

I tried the following :
Took the working package and added the following registery :
- - - -
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution installUnits\{83CA11A6-FF53-4852-9FA2-E2EDCC80C1C1}]
"SystemComponent"=dword:00000000
"Installer"="MSICD"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{83CA11A6-FF53-4852-9FA2-E2EDCC80C1C1}\Contains]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{83CA11A6-FF53-4852-9FA2-E2EDCC80C1C1}\Contains\Files]
"C:\\WINDOWS\\Downloaded Program Files\\ieop_vcm_04ba31a7-776d-4787-a6aa-7587092636c0.dll"=""
"C:\\WINDOWS\\Downloaded Program Files\\ieop_key_04ba31a7-776d-4787-a6aa-7587092636c0.dll"=""
"C:\\WINDOWS\\Downloaded Program Files\\ieop_cmn_04ba31a7-776d-4787-a6aa-7587092636c0.dll"=""
"C:\\WINDOWS\\Downloaded Program Files\\ieop_rpc_04ba31a7-776d-4787-a6aa-7587092636c0.dll"=""
"C:\\WINDOWS\\Downloaded Program Files\\ieop_aom_04ba31a7-776d-4787-a6aa-7587092636c0.dll"=""
"C:\\WINDOWS\\Downloaded Program Files\\ieop_aui_04ba31a7-776d-4787-a6aa-7587092636c0.dll"=""
"C:\\WINDOWS\\Downloaded Program Files\\ieop_prf_04ba31a7-776d-4787-a6aa-7587092636c0.dll"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{83CA11A6-FF53-4852-9FA2-E2EDCC80C1C1}\DownloadInformation]
"CODEBASE"=""
"INF"=[#SiebelOptionPack.inf1]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{83CA11A6-FF53-4852-9FA2-E2EDCC80C1C1}\InstalledVersion]
@="7,5,3,16278"
"LastModified"="Mon, 17 Mar 2006 08:05:49 GMT"
- - - -
"SiebelOptionPack.inf1" being the file name in the file table for the INF file
- - - -
I installed the new package, the install was OK, the files where OK, I connected to the Siebel Server, and it didn't ask me to download the Siebel Option pack for IE. Meaning it reconized it as being alreday installed.
But when I look in the Downloaded Program Files folder I see the following :

Program File - Status - Total Size - creation date - last accessed - Version

{83CA11A6-FF53-4852-9FA2-E2EDCC80C1C1} - Unknown - 4KB - blabla - blabla - 7,5,3,16278
MailClient Class - Installed - 312 KB - blabla - blabla - 7,5,3,16278
SiebelHTMLApplication Class - Installed - 80 KB - blabla - blabla - 7,5,3,16278
- - - -
The problem stays, is the "INF"=[#SiebelOptionPack.inf1] good ?

Hello,

I have posted a request to Siebel support, and here is there answer :

Thank you for contacting Siebel Technical Support. I have taken ownership of the issue you recently submitted. I understand from your problem description that you are going to pre-deploying Siebel Internet Explorer Option Pack by using a custom msi package. After you have tested this pre-deploy method you have noted that there are no files under c:\winnt\downloaded program files location on the client system.
Even though everything else works as expected, you are not sure if the option pack has been deployed successful due to not visible files.

It is expected behavior, when using the script described on support web in Technical Note 418 to pre-deploy the ActiveX components, they won’t be visible in the Internet Explorer and at the corresponding location “C:\WINNT\Downloaded Program Files”. But the components will work as the script registers the dll files necessary to operate the High Interactive client.

ActiveX components will only show up in the Internet Explorer if the dll files have been downloaded and been registered by the Internet explorer itself.
That's the reason why you will not see any ActiveX components in the “C:\WINNT\Downloaded Program Files” when pre-deploying with a script.
- - - -
Is it possible to have the ActiveX visible in the Downloaded Program Files folder via a MSI package, or is it impossible?

Here are a list of all of the registry keys you need in order to get the ActiveX plugin to appear in Downloaded Program Files (copied and pasted relevant section from registry.idt)

Registry Root Key Name Value Component_
s72 i2 l255 L255 L0 s72
Registry Registry
WIREG00001253 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC} Installer MSICD WICOMP00000001
WIREG00001254 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC} SystemComponent #0 WICOMP00000001
WIREG00001257 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\Contains\Files [WindowsFolder]Downloaded Program Files\ieop_aom_625b75a1-6dc2-4592-b043-a45626bed7b2.dll WICOMP00000001
WIREG00001258 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\Contains\Files [WindowsFolder]Downloaded Program Files\ieop_aui_625b75a1-6dc2-4592-b043-a45626bed7b2.dll WICOMP00000001
WIREG00001259 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\Contains\Files [WindowsFolder]Downloaded Program Files\ieop_cmn_625b75a1-6dc2-4592-b043-a45626bed7b2.dll WICOMP00000001
WIREG00001260 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\Contains\Files [WindowsFolder]Downloaded Program Files\ieop_key_625b75a1-6dc2-4592-b043-a45626bed7b2.dll WICOMP00000001
WIREG00001261 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\Contains\Files [WindowsFolder]Downloaded Program Files\ieop_prf_625b75a1-6dc2-4592-b043-a45626bed7b2.dll WICOMP00000001
WIREG00001262 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\Contains\Files [WindowsFolder]Downloaded Program Files\ieop_rpc_625b75a1-6dc2-4592-b043-a45626bed7b2.dll WICOMP00000001
WIREG00001263 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\Contains\Files [WindowsFolder]Downloaded Program Files\ieop_vcm_625b75a1-6dc2-4592-b043-a45626bed7b2.dll WICOMP00000001
WIREG00001265 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\DownloadInformation CODEBASE http://localhost/16192/applets/SiebelOptionPack.cab WICOMP00000001
WIREG00001266 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\DownloadInformation INF [WindowsFolder]Downloaded Program Files\SiebelOptionPack.inf WICOMP00000001
WIREG00001268 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\InstalledVersion 7,5,3,8 WICOMP00000001
WIREG00001269 2 SOFTWARE\Microsoft\Code Store Database\Distribution Units\{84147158-773D-4E89-AAEF-561EC76DA3DC}\InstalledVersion LastModified Fri, 20 Aug 2004 15:30:10 GMT WICOMP00000001
WIREG00001519 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_aom_625b75a1-6dc2-4592-b043-a45626bed7b2.dll .Owner {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001520 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_aom_625b75a1-6dc2-4592-b043-a45626bed7b2.dll {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001522 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_aui_625b75a1-6dc2-4592-b043-a45626bed7b2.dll .Owner {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001523 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_aui_625b75a1-6dc2-4592-b043-a45626bed7b2.dll {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001525 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_cmn_625b75a1-6dc2-4592-b043-a45626bed7b2.dll .Owner {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001526 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_cmn_625b75a1-6dc2-4592-b043-a45626bed7b2.dll {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001528 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_key_625b75a1-6dc2-4592-b043-a45626bed7b2.dll .Owner {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001529 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_key_625b75a1-6dc2-4592-b043-a45626bed7b2.dll {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001531 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_prf_625b75a1-6dc2-4592-b043-a45626bed7b2.dll .Owner {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001532 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_prf_625b75a1-6dc2-4592-b043-a45626bed7b2.dll {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001534 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_rpc_625b75a1-6dc2-4592-b043-a45626bed7b2.dll .Owner {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001535 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_rpc_625b75a1-6dc2-4592-b043-a45626bed7b2.dll {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001537 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_vcm_625b75a1-6dc2-4592-b043-a45626bed7b2.dll .Owner {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001
WIREG00001538 2 SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/Downloaded Program Files/ieop_vcm_625b75a1-6dc2-4592-b043-a45626bed7b2.dll {84147158-773D-4E89-AAEF-561EC76DA3DC} WICOMP00000001