The packaging consultants role is to create an installation from a set of information that can produce a working installation, as opposed to creating a method to make an application work. While the packager can bring useful skills to the process, ultimately it is the application owner who is the expert on any given application and responsible for finding a working configuration. This is then fed back to the packager so that it can be incorporated to the installation package.
MSI, App-V, SCCM, Appsense, Citrix. This blog contains hints and tips on these technologies. Primarily it is an online notebook of items that I may need to refer to in the future, or things I constantly forget!
Friday, April 20, 2012
Friday, April 13, 2012
HP ALM Client
The MSI is a “vendor” MSI but is actually
generated from a backend system to enable client installations. The base MSI does not have many entries eg Extensions Table that would normally be expected. As a result any resources that are installed via an accompanying transform must have the standard table entries added to support the installation of those resources.
In the case of the package above Microsoft Office Addins were requested to be included within the pacakge. These were captured separately, and the resulting WSI (wise) capture results were used as a guide to author those resources into a transform for the main HP ALM Client MSI.
In the case of the package above Microsoft Office Addins were requested to be included within the pacakge. These were captured separately, and the resulting WSI (wise) capture results were used as a guide to author those resources into a transform for the main HP ALM Client MSI.
Subscribe to:
Posts (Atom)