There are multiple ways to achieve the above task. I will list two methods and I will recommend the first method as its easy, simple, less error prone and has more changes of compliance with company policy.
Method 1: Use Corporate Package Distribution System such as CA DSM (not sure about SCCM)
• Create two normal packages and then import them in CA DSM, Set the reboot after installation on the install procedure of the first package. (DO NOT LET MSI reboot itself)
• In CA DSM create a policy with install procedures of both the packages.
Isn’t is simple. What happens that when the procedure is deployed on the package first package is installed and then CA DSM reboots the machine, once the machine comes back online then the second package is installed. If the installation of first package fails then CA DSM will not install the second package. :)
Method 2: Use of Active Setup
• Create package B, add the created package in the files section of package A. Set REBOOT property to Force.
• Set active setup in package A, in the stub section add the details to silently install package B.
NOTE: PLEASE FOR GOD SAKE, do not create a nested msi or create a script which will install the msi files.
No comments:
Post a Comment