applicationPackaging created the topic: Implements Nested MSI Based on Featutre Selection
Purpose
Use Patch Creation to create a Windows Installer patch file (.MSP) that updates installed versions of a Windows Installer-based application. A patch file can update one or several previous versions. Unlike full installations, a patch installation contains only the information necessary to update an installed version of the application.
________________________________________
Note
If this tool is disabled, it means you do not have a license to use it. With Enterprise Management Server, it might also mean you do not have permission to use it.
________________________________________
Before You Begin Read about what you need to create a patch in the online help.
How to Use
1. Double-click the Patch Creation icon.
The Welcome dialog appears, listing the basic steps for creating a patch file. The wizard guides you through each step.
2. Click Next.
The Specify Patch Settings File dialog appears.
3. Mark one of the following:
? Create a new patch file
This creates a new patch settings file (.PCP).
? Open an existing patch settings file (.PCP file)
If you mark this, also specify the .PCP file.
4. Click Next.
The Specify Previous Versions dialog appears, where you select .MSI files of previous versions that this patch will update, referred to as targets. When this patch is run on a destination computer, it verifies that a valid target exists before installation. You must add at least one previous version to this list.
5. To add a previous version, click Add, complete the Previous Version Details dialog, and click OK.
6. If you are prompted to run an administrative installation, click Yes.
The administrative installation is performed. After it finishes, the Specify Previous Versions dialog appears again.
7. Repeat the steps above to add additional previous versions.
8. When you finish, click Next on the Specify Previous Versions dialog.
The Specify Upgrade Version dialog appears.
9. Complete the dialog:
? Upgrade MSI path
The earlier versions of the application will be upgraded to the version you specify here. By default, the path to the current installation’s .MSI appears.
? Advanced
Click this to enter advanced settings. The Advanced Upgrade Version Details dialog appears. Complete the dialog and click OK.
? Add a Digital Signature to the Patch
(Windows Installer 3.0 or later.) Mark this to digitally sign the patch.
10. Click Next on the Specify Upgrade Version dialog.
11. If you are prompted to run an administrative installation again, click Yes. If you are prompted to update the package code, click Yes.
If you marked the option to add a digital signature, the Specify Digital Signature Settings dialog appears. A warning message appears if the original installation was not signed.
12. To add a digital signature to the patch, complete the Specify Digital Signature Settings dialog and click Next.
13. If you are prompted to run an administrative installation again, click Yes. If you are prompted to update the package code, click Yes.
If Windows Installer 3.0 or later is installed on your computer, the Patch Sequencing dialog appears. Complete the dialog and click OK. Otherwise, the Compile Patch dialog appears.
14. Complete the Compile Patch dialog:
? Output .MSP file
Specify a full path for the patch file that you distribute to end users.
? Advanced Settings
Click Advanced to display the Advanced Patch Settings dialog. Complete the dialog and click OK.
? Patch Removal
To make this patch removable through Add/Remove Programs, click Allow Removal and complete the Patch Removal Settings dialog.
? Multi-patch Media Settings
During patch creation, entries are made in the Media table of the patch installation. Options in this section populate the Media table. For each subsequent patch, the file sequence start number and the disk ID start number must be higher than the one in the previous .MSI or patch file. To enter these numbers accurately, you must have access to the most recent patch file distributed to end users. Click Browse to specify the patch file; the file sequence and disk ID numbers are read from the patch.
15. Click Next to begin the patch creation process.
During patch creation, you might see a message stating that the versions between the target image (previous version) and upgrade image (new version) do not match. This is normal; click Yes if this message appears.
The Compile Patch dialog notifies you when patch creation is completed.
16. Click View Log to view a log file of all actions performed to create the patch.
If the patch file could not be created, use this log file to determine the source of the error.
- DevOps Certified Professionals (DCP)
- Site Reliability Engineering Certified Professionals (SRECP)
- Master in DevOps Engineering (MDE)
- DevSecOps Certified Professionals (DSOCP)
URL - https://www.devopsschool.com/certification/
My Linkedin - https://www.linkedin.com/in/rajeshkumarin
- Apache Lucene Query Example - April 8, 2024
- Google Cloud: Step by Step Tutorials for setting up Multi-cluster Ingress (MCI) - April 7, 2024
- What is Multi-cluster Ingress (MCI) - April 7, 2024
