Installshield MSI User Component Registry KeyPath location

Although this can be anywhere in the user registry, Installshield creates keys in the following location to act as keypaths for user components.

HKCU\SOFTWARE\InstallShield Repackaged Applications\[Manufacturer]\[ProductName]\[ComponentName]    StringValue  Name: Installed    Data: 1

Messaging integration with Outlook via CDO.DLL

Prior to Outlook 2007, Collaboration Data Objects CDO.dll was used to enable apps to utilise the outlook client for messaging.  Starting with Outlook 2007 MS begain to change the model for external apps usage of outlook client messaging.  This article give more details about the situation.  Ultimately these messaging access methods are no longer supported and should be redesigned by developers.

http://support.microsoft.com/kb/2028411

IsUninst.exe command line parameters

Copied from
http://www.symantec.com/connect/blogs/uninstall-setupexe-isuninstexe

If any vendor app is using Isuninst.exe for the app uninstall, you will find some useful command line parameters attached.
The silent mode parameter for Isuninst.exe is -a.
The complete uninstallation command for the Windows client is:

Sample: 
C:\WINDOWS\Isuninst.exe -a -f "C:\Program Files\F-Secure\Ssh\Uninst.isu"

Uninst.exe Command Line Parameters

The command line parameters for uninst are listed below:
Parameter:
-y Suppresses the message box that asks the user to confirm that uninstallation should proceed. The feedback dialog box is still displayed, as is the shared file dialog box (which is displayed when the reference count of a shared DLL is decremented to zero).
-x Deletes all files, including those core components that normally do not get removed. (All user interface elements are displayed.)
-f<log file name> Specifies the location and name of the uninstallation log file.

For example: 
-f"C:\Program Files\Company Name\Uninst.isu" 

-c<DLL filename> Specifies the location and name of the external DLL that is to be used at the time of uninstallation.

For example: 
-c"C:\Program Files\Company Name\Custom.dll"

-a Runs the uninstaller in silent mode. In this mode unInstallShield will not display any messages to the end user indicating that the uninstallation has taken place. When running in silent mode, if unInstallShield encounters a shared file for which it would normally display the dialog box asking the user whether to remove the shared file, it will automatically reduce the reference count to zero and not remove the file. Therefore, running unInstallShield in silent mode is functionally equivalent to an uninstallation in which the user selects the "No to all" option when this dialog box first appears.
-d Identifies a single file that is to be deleted. The display of user interface elements is the same as when the -a switch is used.

For example: -dC:\Temp\Filename.ext 

-m Creates an uninstallation .mif file. If you do not specify a filename, the default (Uninst.mif) is used. You cannot specify a path-the file must be placed in the Windows System folder.

Setting up a SCCM 2007 package

This is really about naming conventions and keeping the environment consistant and easy to navigate as time goes by.  If even small differences in the process occur, the environment can become frustratingly varied make it difficult to check and find things.

Create the package
The important point here is to properly complete the Name, Manufacturer, Version fields.  The package names are listed using these fields to if you want the list to appear correctly in proper alphabetical order you must be consistant - preferably always using the Manufacturer field as this the first item used in the package list.

I think the preference here may be to use a tool to generate an SMS (package definition file) file which is then imported.  It can quickly populate the required fields consistantly - if the MSI has been created to standards!) - still worth checking text in the file before importing to make sure the fields are correct and as you wish them to appear in SCCM. 

Create the programs - install/uninstall
It is a very good idea to refer to the program type AND package name in the program title.  This is because the program title can be easily seen in the SCCM client infomation if it is interogated using the SCCM Client Center tool.  Be consistant: Manufacturer - App/Package/Product/Name -Version 
 e.g. Install - Adobe Acrobat Reader X 10.1.6
Consider using the import for the Windows Installer tab because this can provide the source location to repair from when the MSI installs on the target machine.

remember to Copy to Distribution Points :)

Create the AD Group.
If you are using AD groups queries from collections - Create the AD group. Be consistant: Manufacturer - App/Package/Product/Name -Version 

Create the Collection
Be consistant: Manufacturer - App/Package/Product/Name -Version 

Create the Advert
Be consistant: Manufacturer - App/Package/Product/Name -Version 
Put a - Install or a -Uninstall etc at the end of the advert name so that the purpose of the advert can be easily determined.