Upgrades and GPO's - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

ssearles
Posts: 65
Joined: Tue Oct 30, 2007 12:54 pm

Upgrades and GPO's

Trying to get an installer that I've built, with Upgrades turned on, to work via a GPO.

Now if I run the installer with a msiexec it works perfectly. It uninstalls and reinstalls the new version without a hitch.

but now, I'm trying to get the same capability to happen via a GPO that's been set up. From my reading, you can get a GPO based MSI to go off one of two ways:

1) Replace the old MSI with the new one (assuming same name) and invoke a 'Redeploy Application' command.

2) Build another GPO for the express purpose of upgrading and old one (with old MSI) with a new one.

Admittedly, i know not much about GPO's and have no access to build/test my own in our network, but I really want to get option #1 to go, because otherwise I'd be dependent on other people to make new GPO's anytime an update might need to be deployed/added. I simply want to be able to recompile and replace my existing MSI's as needed.


Does anyone have any pointers on why this wouldn't be working (a Redeploy only uninstalled hte old installation but will not fire a reinstall) or if there's anything i may be missing in my settings???


Thx in advance!
Ionut
Posts: 605
Joined: Tue Nov 22, 2005 11:29 am
Contact: Website

Hi,

Indeed, it seems that when using the first option (which is the recommended approach) a new version package will only uninstall an older version, but the new package will not be installed.

Therefore, when creating an updated MSI intended for GPO deployment, you only need to modify the project (adding the new resources as necessary) and then rebuild the package (without changing the ProductVersion and ProductCode since this will require creating a new package object). After this, redeploy the package object using the "Redeploy application" command in the GPO editor.

Another method would be to first remove the installed application ("Remove" command) and then create a new package object ("New -> Package" command).

The following document may prove useful, use Word Viewer to open it:
http://home.fnal.gov/~jklemenc/dl/AD-MS ... ummies.doc

Regards,
Ionut
Last edited by Ionut on Mon Feb 25, 2008 1:58 pm, edited 1 time in total.
Denis Toma
Advanced Installer Team
http://www.advancedinstaller.com/
ssearles
Posts: 65
Joined: Tue Oct 30, 2007 12:54 pm

Ionut wrote: The following document may prove useful, use Word Viewer to open it:
http://home.fnal.gov/~jklemenc/dl/AD-MS ... ummies.doc

Regards,
Ionut

Actually that's the document I read and basing my theory on... I guess I just misinterpretted it.


So, if I understand you correctly, changing the product version is a bad idea/method if using a GPO???
Ionut
Posts: 605
Joined: Tue Nov 22, 2005 11:29 am
Contact: Website

Hi,
So, if I understand you correctly, changing the product version is a bad idea/method if using a GPO???
Not necessarily, it is just that GPO deployments work differently than normal MSI installations.

You can use the second method I have mentioned above (removing the existing package and then creating a new package object). Note that this does not imply creating a new GPO, just a new package object inside the already defined GPO.

Regards,
Ionut
Denis Toma
Advanced Installer Team
http://www.advancedinstaller.com/

Return to “Common Problems”