Updated MSI question
Over a year ago I deployed the Desktop Standard PolicyMaker Registry Extension client to the systems on my network. There is a newer version that I'd like to deploy. It probably wouldn't work correctly if I just replaced the old .msi with the new one. What's the best/proper method for getting the old version updated and after that's done, removing the old version from the GPO so new clients will just install the new version instead of the old one and then the new?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
fosteky
17 years ago
This is fairly easy as long as you have the "Uninstall when out of scope" option enabled on your currently deployed GPO (meaning your currently deployed application is in a "Managed" state).
If you do then:
1) make a new GPO that pushes the new MSI (enable "Uninstall when out of scope" option for the next time)
2) remove your existing AD group (that you use to grant this software to) out of your current GPO's scope and add it to the scope of the GPO you created in Step 1.
But if you don't have the "uninstall when out of scope" option enabled on your presently deployed GPO then the above won't work for you. In that case, if it's a Computer assigned GPO then I recommend switching that option on in your presently deployed GPO and power cycling your entire fleet (effectively swithing every installed instance to a "Managed" state) and THEN using the steps above. If it's a User assigned GPO (it'll be too difficult to ensure the MSI becomes "Managed" on every existing profile) then you should look at adding the MSI to the existing GPO as an upgrade, which I don't like doing. Creating layered GPOs necessitates multiple GPO foreground checks before the client finally receives the most recent MSI.
In my organization (where we just use plain old GPOs to manage all our packages) I always try to package for Computer assignment and also always enable "Uninstall when out of scope" as a best practice.
Hope this helps...
If you do then:
1) make a new GPO that pushes the new MSI (enable "Uninstall when out of scope" option for the next time)
2) remove your existing AD group (that you use to grant this software to) out of your current GPO's scope and add it to the scope of the GPO you created in Step 1.
But if you don't have the "uninstall when out of scope" option enabled on your presently deployed GPO then the above won't work for you. In that case, if it's a Computer assigned GPO then I recommend switching that option on in your presently deployed GPO and power cycling your entire fleet (effectively swithing every installed instance to a "Managed" state) and THEN using the steps above. If it's a User assigned GPO (it'll be too difficult to ensure the MSI becomes "Managed" on every existing profile) then you should look at adding the MSI to the existing GPO as an upgrade, which I don't like doing. Creating layered GPOs necessitates multiple GPO foreground checks before the client finally receives the most recent MSI.
In my organization (where we just use plain old GPOs to manage all our packages) I always try to package for Computer assignment and also always enable "Uninstall when out of scope" as a best practice.
Hope this helps...
Posted by:
Babscoole
17 years ago
Yes, helps alot. I didn't have "Uninstall when out of scope" enabled due to our sales crew always heading out on the road with their company laptops, but your reply set me in the right direction. Thanks.
Posted by:
AngelD
17 years ago
If you are deploying the package as per machine and as you do not have "Uninstall when out of scope" set you can just remove the existing application from the GPO, add the new version and set this new (MSI) to upgrade previous version.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.