Jan 25, 2023
10:25 AM
1 Kudo
This is expected as the docker component is built separately from the rest of the agent. The actual fnms-docker-monitor version can be obtained by running `fnms-docker-monitor.exe -V` from a terminal. This version may or may not change between agent releases depending on whether any changes have been made to the docker component.
... View more
Jan 28, 2022
05:30 PM
3 Kudos
The auto upgrade process does not make any attempts to control feature selection when installing an agent upgrade. This will result in the default feature selection from the agent MSI being used (which is all features to be installed). I've submitted issue FNML-75073 to address this behavior. At this time I don't know when this might be addressed.
You can use the msiexec command lines with the REMOVE property to uninstall the docker feature after an agent is installed as outlined in this thread. Alternately, if possible, it would be recommended that third party deployment software be used to work with deploying agents in your environment, as this would allow for the greatest control and flexibility in the deployment process, including working with upgrades.
... View more
Jan 11, 2022
12:00 PM
1 Kudo
This question was covered in another thread: Disable docker service or remove from installation
... View more
Jan 11, 2022
11:57 AM
3 Kudos
In terms or installing or removing the docker feature after the agent is installed, standard MSI functionality can be used to do so.
To remove the feature if it is already installed:
msiexec /I {ProductCode} REMOVE=docker /qb
To add the feature after the agent is already installed:
msiexec /I {ProductCode} ADDLOCAL=docker /qb
Again, use /qb to run with basic (minimum) UI or /qn to run silently. All MSI operations will need to be run from an account with admin privileges.
Note that the {ProductCode} from the above examples differs based on which version of the agent you are working with, as each version has a unique product code. You can look up the product code using Orca and looking for the ProductCode entry in the Property table, or you can use a tool such as MsiSleuth from InstallShield or the WiLstPrd.vbs script provided in the Windows Installer SDK. Either will be able to list installed MSI products are provide additional information such as their product codes. Once you have located the product code for the agent you are working with, you can substitute the string in the above command line examples.
... View more
Dec 14, 2021
12:49 PM
6 Kudos
You can either use the ADDLOCAL property when installing the agent, omitting the 'docker' feature, or use a transform to set the install level of the 'docker' feature to 0.
Using ADDLOCAL, specify the features to install. To install all features except 'docker':
msiexec.exe /I "C:\PathToMsi\FlexNet Inventory Agent.msi" ADDLOCAL="client,etc,aua,lnc,plc,sca,trk,upl,vdiendpointagent,Licensing" /qb
Note that running with full UI will modify the feature selection if a complete install is selected. Using /qb (basic UI) or /qn (silent) is recommended to avoid this.
Alternately, using an MSI editor that can create transforms, you can create a transform that is applied during installation with the TRANSFORMS property. Change the Level column of the 'docker' feature to 0 in the Feature table. This will disable the feature from being installed and prevent it from being displayed in the feature tree on the custom install dialog when running with UI.
... View more
Dec 08, 2020
11:26 PM
There are no plans for a 64-bit only FlexNet Inventory Agent for Windows.
The Docker support on Windows does make use of an additional Windows service and a 64-bit build of ndtrack to ensure we can reliably collect inventory from Windows Docker containers (Windows containers do not play nice with 32-bit binaries). These are additional binaries that are now installed with the agent MSI package but they do not replace any existing functionality. As such, the 64-bit build of ndtrack is not intended for use on a Docker host machine.
Aside from this, Windows platform support remains the same as in previous versions of the agent for Windows and will continue to function on 32-bit installations of Windows and continues to run as a 32-bit application on 64-bit versions of Windows.
... View more
Mar 16, 2020
11:06 AM
5 Kudos
At a high level, agent ID is generated using the following:
Physical Machines: SHA256(HostName + BIOS_Serial_Number + History_Iteration)
Virtual Machines: SHA256(VMID + GenerationID + History_Iteration) (where generation ID is available only for certain hypervisors running certain versions of Windows guests)
The agent ID is regenerated if enough conditions have changed, at which point the history iteration is incremented also:
Physical Machines: HostName and BIOS_Serial_Number both changed
Virtual machines are rather complicated to distinguish VMs that have been moved or cloned (copied). To account for a broad array of scenarios the following is used:
- If generation ID is present and changed, and all physical MAC addresses have changed, regenerate ID
- If VMID is present and changed, regenerate ID
- If all physical MAC addresses have changed, regenerate ID
The agent ID, the properties used to generate it, and all historical IDs and properties are sent in an NDI created with ndtrack.
Please note that these are implementation details that are subject to change across versions of the FNMS agent to account for future scenarios. Also note that while the agent ID helps to uniquely identify a machine it may not be used if other evidence is present. This is also an implementation detail that is subject to change across FNMS versions.
... View more
Feb 10, 2020
12:27 PM
4 Kudos
For anyone that has been experiencing 500 errors on their child beacons attempting to retrieve packages from a parent beacon, and the parent beacons are configured to use IIS as a host, please try running the attached PowerShell script on parent beacons _only_. (Extract MetaPkg_Perms_Workaround.ps1 from the attached zip file.) The script needs to be run from an admin PowerShell prompt.
The script will attempt to correct the permissions on files that are named ending in _metapkg.ndc.cab. The permissions on this file are preventing access when using IIS as the beacon web server.
Once the permissions are corrected you should be able to manually download the _metapkg.ndc.cab files from a web browser. If this succeeds, the package retrieval should start working for child level beacons.
Please let me know if this helps.
... View more
Oct 03, 2018
12:28 AM
The docs for VersionNT64 seem to be clear that the property is not set for x86 installers running on ARM64 machines: For compatibility reasons, the property is also undefined if the Template Summary property indicates the package is for 32-bit Intel systems and the operating system is a 64-bit architecture that is not Intel64 or x64 (such as ARM64). VersionNT64 Property - https://docs.microsoft.com/en-us/windows/desktop/msi/versionnt64 In addition, since InstallShield is mostly built as x86 architecture binaries, the ARM64 version of the OS is going to lie to any code InstallShield has that calls into the system to query for what architecture the system is. The end result is x86 processes on ARM64 Windows appear as if they are running on a 32-bit Intel machine (x86), including most of InstallShield's design, build, and runtime code, as indicated in this Build 2018 session: Windows 10 on ARM for developers - https://channel9.msdn.com/Events/Build/2018/BRK2438 InstallShield's 64-bit additions (for x64 architecture versions of Windows) were added at a time when ARM64 Windows did not exist, so this behavior is expected based on how the x86 emulation layer on ARM64 Windows is intended to function. I don't know what plans InstallShield has to support ARM64 going forward, especially if the platform fails to gain any appreciable traction. The question remains in this case though, in this scenario installing an x86 application on ARM64 versions of Windows, what is the use case for needing to know that the target machine is ARM64 and to access the native registry (i.e. the ARM64 registry) on the machine (when it won't really be usable by the application)?
... View more
Jan 12, 2018
12:00 PM
InstallScript MSI projects create their own ARP uninstall key which is what is used as the source of the ARP entry (the MSI uninstall key is hidden from ARP). InstallScript MSI uninstall keys are under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall and are always named 'InstallShield_{ProductCode}'. The uninstall string will always reference the cached setup.exe installed at \InstallShield Installation Information\{ProductCode} to allow the product to uninstall correctly. msiexec.exe can't be used to uninstall an InstallScript MSI project. If this is required a Basic MSI project should be used instead.
... View more
Mar 10, 2017
04:48 PM
There were some issues caused by what methods we had used to lock down DLL loading in the original release of IS 2016 and the hotfixes for older versions of InstallShield in this KB. While the code used was not specific to a version of Windows, the issues reported to us almost exclusively occurred on Vista/2008 and 7/2008 R2. This came down to how DLL loading is handled on those versions of Windows and what we were using to avoid loading unexpected DLLs. IS 2016 SP1 changes how and what we use to mitigate CVE-2016-2542. This change is also not specific to any version of Windows but is implemented for all versions supported by InstallShield. Most of the hotfixes available here have been updated for more recent versions of InstallShield with the same fix for IS 2016 SP1 to avoid unexpected behavior. These were updated around mid/late-February. You should be able to download an updated version for IS 2013 SP1 that includes the 2016 SP1 changes.
... View more
Nov 29, 2016
05:57 PM
This error essentially is indicating that the MSI package either has no digital signature, or the certificate used does not terminate in a trusted root. Are there any other digital signing errors in your build log, or any SigningHelper messages? If no such information is present in the log, does the MSI contained in the release Disk1 folder contain a digital signature (right-click the MSI in Windows Explorer, select Properties and look for the Digital Signature tab)? If it does, what state does Windows consider the signature based on the 'Digital Signature Information' field (double-click a listed signature to view it)?
... View more
Nov 29, 2016
05:44 PM
These parameters are invalid when using DLG_INFO_ALTIMAGE_HIDPI. As the DialogSetInfo documentation states: szInfoString When DLG_INFO_ALTIMAGE_HIDPI is passed in nInfoType, this parameter specifies the file name of a high DPI image to display, optionally including the path. If no path to the file is specific, the file is assumed to be in SUPPORTDIR. If this file does not exist, DialogSetInfo returns ISERR_FILE_NOT_FOUND. nParameter When nInfoType is DLG_INFO_ALTIMAGE_HIDPI, nParameter specifies the DPI scaling percentage. For example, pass 200 for a 200% image scale, 150 for a 150% scale, etc. The minimum supported scaling value is 25. If 0 is passed for this value, no image is displayed. If DLG_INFO_ALTIMAGE_REVERT_IMAGE is passed, the previous image used is displayed. As such, the DialogSetInfo call needs to be something like the following when using DLG_INFO_ALTIMAGE_HIDPI: DialogSetInfo( DLG_INFO_ALTIMAGE_HIDPI, "My.png", 200 ); If my.png is not present in SUPPORTDIR, DialogSetInfo will return an error.
... View more
Nov 28, 2016
04:54 PM
The expected values passed to the szInfoString and nParameter parameters of DialogSetInfo are treated differently when passing DLG_INFO_ALTIMAGE_HIDPI. szInfoString should be the image file (including the path; SUPPORTDIR is assumed otherwise) to be used, and nParameter should be set to the scaling factor of the image (100, 125, 150, etc.). If these parameters are not valid, DialogSetInfo will return an error. Images should be sized/scaled as expected for the normal dialog header area image (the old InstallShield header image is 180x75 pixels, the new image is considered 200% scale and is 360x150 pixels). Since DLG_INFO_ALTIMAGE_HIDPI was added in a service pack for IS 2015, I don't recall if the parameter information was updated in the DialogSetInfo doc. It is available in the IS 2016 docs here: http://helpnet.flexerasoftware.com/installshield23helplib/installshield23helplib.htm#Subsystems/LangRef/helplibrary/LangrefDialogSetInfo.htm
... View more
Nov 10, 2016
12:03 PM
At this time we would recommend using IS 2015 SP1 without hotfix IOJ-1745445 installed. This would provide functional parity with the updated setup launchers posted earlier in this thread for IS 2016.
... View more
Latest posts by joshstechnij
Subject | Views | Posted |
---|---|---|
184 | Jan 25, 2023 10:25 AM | |
1356 | Jan 28, 2022 05:30 PM | |
836 | Jan 11, 2022 12:00 PM | |
1576 | Jan 11, 2022 11:57 AM | |
1784 | Dec 14, 2021 12:49 PM | |
1129 | Dec 08, 2020 11:26 PM | |
6526 | Mar 16, 2020 11:06 AM | |
3111 | Feb 10, 2020 12:27 PM | |
2520 | Oct 03, 2018 12:28 AM | |
1126 | Jan 12, 2018 12:00 PM |
Activity Feed
- Got a Kudo for Re: FNMS Agent executables with different version. Feb 07, 2023 12:27 AM
- Posted Re: FNMS Agent executables with different version on FlexNet Manager Forum. Jan 25, 2023 10:25 AM
- Got a Kudo for Re: InstallShield 2009 Standalone Build version. Nov 07, 2022 04:17 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Feb 01, 2022 09:54 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Jan 31, 2022 12:46 PM
- Got a Kudo for Re: Disable docker service or remove from installation. Jan 31, 2022 01:38 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Jan 30, 2022 05:38 PM
- Posted Re: Disable docker service or remove from installation on FlexNet Manager Forum. Jan 28, 2022 05:30 PM
- Got a Kudo for Re: Disable agent component FlexeraDockerMon. Jan 13, 2022 12:50 PM
- Got a Kudo for Re: Disable docker service or remove from installation. Jan 12, 2022 02:48 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Jan 11, 2022 03:26 PM
- Posted Re: Disable agent component FlexeraDockerMon on FlexNet Manager Forum. Jan 11, 2022 12:00 PM
- Posted Re: Disable docker service or remove from installation on FlexNet Manager Forum. Jan 11, 2022 11:57 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Dec 21, 2021 04:52 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Dec 15, 2021 01:34 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Dec 15, 2021 01:14 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Dec 15, 2021 01:08 AM
- Got a Kudo for Re: Disable docker service or remove from installation. Dec 14, 2021 05:32 PM
- Got a Kudo for Re: Disable docker service or remove from installation. Dec 14, 2021 03:17 PM
- Posted Re: Disable docker service or remove from installation on FlexNet Manager Forum. Dec 14, 2021 12:49 PM