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.
- Flexera Community
- :
- AdminStudio
- :
- AdminStudio Forum
- :
- Re: Flexera software update captured in adminstudio repackage Legacy Package
Subscribe
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 11, 2013
05:43 AM
Flexera software update captured in adminstudio repackage Legacy Package
Hi,
I am using Adminstudio ZENworks Edition 10 sp2 on a W7 x64.
I disabled adminstudio's updates (Tools\Options\Updates to never).
I am repackaging a software with "Repackaging wizard".
When i edit the project in order to build the msi, i don't see any files or registry entries referring to Flexera software update.
It seems that FLEXnet software update was added during the msi build.
Unfortunately, when i deploy the msi on a target computer, the shortcut Flexera software update and the service is present.
How to not have FLEXnet software update when i build the msi?
Thank you for your help
David
I am using Adminstudio ZENworks Edition 10 sp2 on a W7 x64.
I disabled adminstudio's updates (Tools\Options\Updates to never).
I am repackaging a software with "Repackaging wizard".
When i edit the project in order to build the msi, i don't see any files or registry entries referring to Flexera software update.
It seems that FLEXnet software update was added during the msi build.
Unfortunately, when i deploy the msi on a target computer, the shortcut Flexera software update and the service is present.
How to not have FLEXnet software update when i build the msi?
Thank you for your help
David
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
3 Replies
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 11, 2013
10:43 AM
I haven't used the Zenworks Edition however I believe it the Editor tool which allows you to make further customizations before building your msi. It allows for further customization than the repackager.
You should be able to build an InstallShield project file, then open the project up in InstallShield.
Check the shortcuts to see if any shortcuts to the flexnet updater are getting created. Also, take a look at the redistributables view and uncheck any flexnet connect merge modules that may be included.
You should be able to build an InstallShield project file, then open the project up in InstallShield.
Check the shortcuts to see if any shortcuts to the flexnet updater are getting created. Also, take a look at the redistributables view and uncheck any flexnet connect merge modules that may be included.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 16, 2013
05:54 PM
I had the same problem 3 years ago. I was surprised not more people were complaining about this:
http://community.flexerasoftware.com/showthread.php?195549-ISUSPM-causes-System32-to-open-at-startup&p=461741#post461741
Anyway, the solution is simply to delete the merge modules for FLEXnet software update and it will never bother you again. The files are named something like fnc1160_full.msm depending on version, and there are two of them.
Who uses that **** anyway?
http://community.flexerasoftware.com/showthread.php?195549-ISUSPM-causes-System32-to-open-at-startup&p=461741#post461741
Anyway, the solution is simply to delete the merge modules for FLEXnet software update and it will never bother you again. The files are named something like fnc1160_full.msm depending on version, and there are two of them.
Who uses that **** anyway?
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 17, 2013
03:13 AM
Thank you all for your answers.
Actually, in order to resolve this point, in the repackager software, in "Repackaged Output\Advanced Settings", i unchecked "Replace files with merge modules whenever possible".
Thank you
David
Actually, in order to resolve this point, in the repackager software, in "Repackaged Output\Advanced Settings", i unchecked "Replace files with merge modules whenever possible".
Thank you
David
