I have been tasked with developing instructions for our customers who use SMS to deploy our application in the recommended process for deploying .msp update files for these applications.
In my test configuration, I have successfully created a software package for the .msi file and the application is successfully installed on the client machines using the per-system unattended method.
I now have an update.exe which contains the embedded .msp file and want to distribute this to all users including Vista clients. What is the best recommended method for doing this? What would be easiest for administrators?
My ideas so far are:
1. Admin uncompresses the original setup using msiexec /a <path to msi> TARGETDIR=<path_to_uncompressed_msi>
2. Once the admin has an uncompressed setup then they can merge the patch file with the uncompressed setup using msiexec /p <path_to_msp> /a <path_to_msi>
3. Here is where I am not sure of what the best method is, should the administrator create a new package and deploy it? It is a minor update. Can the administrator just deploy the upgrade.exe and that would work too?
In my test configuration, I have successfully created a software package for the .msi file and the application is successfully installed on the client machines using the per-system unattended method.
I now have an update.exe which contains the embedded .msp file and want to distribute this to all users including Vista clients. What is the best recommended method for doing this? What would be easiest for administrators?
My ideas so far are:
1. Admin uncompresses the original setup using msiexec /a <path to msi> TARGETDIR=<path_to_uncompressed_msi>
2. Once the admin has an uncompressed setup then they can merge the patch file with the uncompressed setup using msiexec /p <path_to_msp> /a <path_to_msi>
3. Here is where I am not sure of what the best method is, should the administrator create a new package and deploy it? It is a minor update. Can the administrator just deploy the upgrade.exe and that would work too?