Software Deployment

So, I create the initial GPO object using the original .msi and link it to the domain for the initial install. Now I would like to go over the scenarios we will use to update, hopefully doable through group policy.

Scenario 1 - Major Upgrade. How do I handle this? I've seen some videos where a second GPO is created then set to update the original GPO on the Upgrade tab of the Software settings.

I've also seen where the new .msi is just added to the same GPO with similar upgrade settings. What is the best way to carry out this scenario?

Scenario 2: Small Update via Patch. So the original GPO pointed to the oridinal .msi and now its time to update. I'm still a little (should say a lot) unclear on what's next and if I need to create a new GPO or do the admin/patch thing and point to the 'new', patched .msi in the same GPO.

I will try following the links above, but any clarification is greatly appreciated.

The overall goal of this was to get the steps needed and create a utility around GP to deploy with our software. I don't know that that will be an easy task though and it might just be as effective to document the steps to carry out through Microsoft's interfaces.

Thanks so much for all the help so far!! - Superfreak3 11 years ago

Also, I guess there would be a third scenario in that I may have to patch something again. I guess I could just apply the patch to the admin install of the previous step or patch. Again, I would ask if a separate copy would be needed or if I can just run the same GPO. - Superfreak3 11 years ago

Sorry, but here's another question. After watching some GPO videos I see that the presenter was running gpupdate /force /boot /logoff from the command line on the workstation to have the latest policy/changes enacted. I did notice in my testing that I at time had to reboot twice to have the software install.

What is the role of gpupdate and do I need to handle that on workstaitons that are to receive the software? - Superfreak3 11 years ago

This concept seemed to work for the patch...

msiexec /a MyFile.msi TARGETDIR="C:\SharedFolder" /qb

msiexec /p MyPatch.msp /a "C:\SharedFolder\MyFile.msi" /qb

I then added the patched .msi to the same GPO object and set it to upgrade earlier (not remove old first).

I would think that if another patch comes along, I can patch the current admin install .msi. The only question I would have is if I need to add another .msi to the GPO or if the newly updated admin .msi will update. I will test that next. - Superfreak3 11 years ago

I think the only way I can patch the same Admin Install is if I Redeploy Application in the Object's software settings (Actions). I don't now if that's really necessary. The other alternative is to continually make a copy of the latest Admin Install folder, apply the patch then add this new .msi to the GPO. Does that sound about right? - Superfreak3 11 years ago