This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- Re: Remotely uninstall a patch
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 04, 2011
06:42 AM
Remotely uninstall a patch
Hi there,
we're using FLEXnet Connect 12.0 in combination with InstallShield 2009 Professional to update our customers applications. Applying patches works quite well and we can easily upgrade the local program versions via patches (MSP packages).
But what about unisnatlling a patch? Is there any possibility to force the local msiexec to uninstall specific patches remotely? We need it because some of the customers a running testing trials and we want them to go back to a earlier version of the application.
Might the command line switches (Tab 2 in the Update definition site on the FLEXnet Connect Publisher Site) be the holy grail to do it?
And if yes, how?
Thanks in advance!!!
Rob
we're using FLEXnet Connect 12.0 in combination with InstallShield 2009 Professional to update our customers applications. Applying patches works quite well and we can easily upgrade the local program versions via patches (MSP packages).
But what about unisnatlling a patch? Is there any possibility to force the local msiexec to uninstall specific patches remotely? We need it because some of the customers a running testing trials and we want them to go back to a earlier version of the application.
Might the command line switches (Tab 2 in the Update definition site on the FLEXnet Connect Publisher Site) be the holy grail to do it?
And if yes, how?
Thanks in advance!!!
Rob
(2) Replies
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 08, 2011
12:18 PM
Command-line switches should work fine for you. The first step in this process would be to re-distribute the source MSI package you want to use. The MSDN article here describes the MSIPATCHTOREMOVE property, which you should set as part of your FNC command-lines.
http://msdn.microsoft.com/en-us/library/aa372104(v=vs.85).aspx
In this case, you might do like MSIPATCHTOREMOVE={Code}, which would result in:
msiexec /i {YOURMSINAME} MSIPATCHTOREMOVE={Code}
Alternatively, consider authoring a small executable that you can deliver using the Windows Installer API, MsiRemovePatches, to remove the patch via code. This can make your patch removal process more agile and extensible if you use many different products and versions.
Unfortunately, there's not really an update type that delivers only a command-line to run on a target machine, so some type of deliverable would be required for the user to download and run.
http://msdn.microsoft.com/en-us/library/aa372104(v=vs.85).aspx
In this case, you might do like MSIPATCHTOREMOVE={Code}, which would result in:
msiexec /i {YOURMSINAME} MSIPATCHTOREMOVE={Code}
Alternatively, consider authoring a small executable that you can deliver using the Windows Installer API, MsiRemovePatches, to remove the patch via code. This can make your patch removal process more agile and extensible if you use many different products and versions.
Unfortunately, there's not really an update type that delivers only a command-line to run on a target machine, so some type of deliverable would be required for the user to download and run.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 18, 2011
05:07 AM
Thanks very much. We've found a way doing that!
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)