About steffen

steffen · ‎Jan 30, 2023

Thanks for confirmation Aamer, we are really looking forward for that functionality in 2023R1 OnPrem! currently, using Agent 19 for z/os on FNMW 2022R2 (onPrem) the ndi files will be produced just fine and find their way into FNMSInventory. In FNMSCompliance though they are not visable most of the time, even each having unique AgentID. I expect that this functionality (3 Layers, Guest, LPAR, Mainframe) will be solved/created in the next on Prem release like already stated. Looks like in the current release the different guests will be merged (overwritten) and sometimes even enter as "VM Host"...so still some open topics to be resoved until next release... I fully understand that this functionality is not offically supported right now (enven though Flexera provided tha Agent Install Source!) Thanks and greetings Steffen

steffen · ‎Jan 20, 2023

In the latest release 2022r2 (19.0) OnPrem there is an Agent available for Linux on z/OS. We installed it on a SUSE guest (using root user). But there are a few thinks not showing as expected: in FNMS it is calssified as a Host - I would expect a VM there is no Serial Number shown I'm missing some Hierachy, like LPAR and Host which seams to be present in the ndi file (3Layers) each of the 3 layer has detailed HW info in the ndi file but only layer 3 is showing up as host but inside ndi file labled as "Layer3TypeName" Value="z/VM-guest" We dont use "Assets" in FNMS - is this possibly a prerequisite? I also could not find any Flexera documentation onto this topic Any comments are welcome or should I open up a case here? greetings Steffen

steffen · ‎Jan 05, 2023

I have a short question with regards to the Upward-Compatibility of the Agent: can we install/rollout the Agent 2022R2 for targets but still have our main FNMS Environment (Application + Beacons) on 2022R1? Of course we might not get some new Features of 2022R2 but thats ok for us. The reason beeing: we are continuoulsly rolling out new Agents, and I would like to have latest Versions available straigt away (saving us an upgrade later on and already getting some Agent-Enhancements). Also we could identify possibly Agent-Issues gracefully and not by having a big bang. We are planing to upgrade the main FNMS later this year - might also go onto a 2023 release if available in first halve of this year. Thanks and greetings Steffen

steffen · ‎Jan 05, 2023

Hi Darren, I ran into the same problem about one year ago sql server 2019 and FNMS 2021R1. I created a support case (02518130) The end of the sorry was that I switchend back db compatibility level to 110 (sql 2012) even improving on original reconciliation time! Flexera gave me approval for this level to be run even though its not the official recommended level. Using the official recommended settings (including disableling Optimizer components) for sql 2019 did not solve the additional 10h reconciliation time for me. We are now running FNMS 2022R1 still on a 110 level with great performance. By the way I also managed to get Cognos up and running on sql 2019 even though this is offically not supported. Hope this might help Greetings Steffen

steffen · ‎Nov 18, 2022

Dear Rudi, we have also seen that behaviour even daily updating libraries. I have solved this by removing all "Local" and "Flexera extended" Evidences from "All Evicences". Of course only related to Name like "sql" and Pubslisher = "Microsoft". A reconciliation is also required after that. Disclaimer: if you have customised Evidences / Applications for sql set up, they will be deleted as well and you will be running kind of like Out Of The Box loosing any customisation you might have done for SQL recognition.

steffen · ‎May 17, 2022

sorry for any confusion: Nicolas's scripts did not create these aditional Indexes - all green here 😉 However Flexera Support did do some perormance troubleshooting (Case #02518130) and looks like there is some clean ups missing in there! Thanks any many greetings Steffen

steffen · ‎May 17, 2022

Hi Chris, Indixes are created inside the attatched word: see "Managing Java Embedded Files Evidences In FNMS v2.docx" and look in second "View Code.docx" embedded file.

steffen · ‎May 17, 2022

Just a quick feedback - if you have this custom reporting installed and want to upgrade FNMS the database migration scripts will fail because of several extra index. I backed up the scripts to re-generate the indexes just in case and simply dropped them. (of course you could simply re-run these custom sql's in the attatched documentation) FNMS DB migration to 2022r1 was fine after that for me: drop INDEX [IX_ImportedInstalledFileEvidence_ComplianceConnectionID_ExternalFileID] ON [dbo].[ImportedInstalledFileEvidence_MT] drop INDEX [IX_ImportedInstallerEvidenceMapping_CConnectionID_EInstallerID] ON [dbo].[ImportedInstallerEvidenceMapping_MT] drop INDEX [IX_ImportedInstallerEvidence_ComplianceConnectionID_ExternalInstallerID] ON [dbo].[ImportedInstallerEvidence_MT] drop INDEX [IX_ImportedInstallerEvidenceMapping_ComplianceConnectionID_ExternalInstallerID] ON [dbo].[ImportedInstallerEvidenceMapping_MT] As I understand there are similar or same functionality now in FNMS 2022r1 anyway so this might be more in the way than helpful for people using 2022r1 greetings Steffen

steffen · ‎Nov 18, 2021

Thanks for the Answer Chris, do you have further details on this - I could only find 1 entry in windows Registry for the policy - or does this control all log file sizes? [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Policy Client\CurrentVersion] "LogFileSize"="4000000" ## recently we have seen some issues that e.g installation.old.log got 19GB!! causing system trouble (this is OnPrem 2021R1) - thanks - Steffen

steffen · ‎Aug 04, 2021

hi Markward, as far as I know there is NO Registry Entries for this - its only a setting inside mgssetup.ini I'm not shure if you can change that afterwards - simply exchange the mgssetup.ini against a new one - while Agent remains running and installed. @ Chris whats your opinion on this?

steffen · ‎Jun 02, 2021

In fact it looks like a know topic to me: https://docs.flexera.com/fnms/EN/Status/Issues/March2021.htm where this is only reported for Cloud release 2020 R2.2 and not for on Prem 2020r2! IOJ-2177310 Agent Auto upgrade with previously installed mgssetup.ini containing DESTRUCTIVEUNINSTALL = 1 removes all ManageSoft HKLM data Deploy a script to any Windows machines with the agent installed where DESTRUCTIVEUNINSTALL=1 was set in mgssetup.ini to either remove C:\Program Files\ManageSoft\mgssetup.ini or to modify the installed mgssetup.ini removing the DESTRUCTIVEUNINSTALL=1 entry.

steffen · ‎Jun 01, 2021

Thanks a lot Chris! yes we do have "Descructiveuninstall = 1". In the past we could manually deploy the agent and later down the line use FNMS to automaticly update to a new version once available - we did not identify issues like this before. We certainly will disable this now and have a closer look here. Thanks and greetings Steffen

steffen · ‎Jun 01, 2021

recently we started to get strange behaviour trying to install latest FNMS Agent (16.0.1) on Windows: If "Upgrade mode" is enabled (selected targets to latest version 16.0.1) we see following behaviour on Windows-only: initial installation looks fine initial download of policy from beacon fine update with new downloaded policy and agent update results in deleted reg.keys subsequent communication to beacon is lost after complete de-install + re-install steps 1)-4) are reproduced it is not clear to me why the agent is updating after initial call home, because we are already installing latest 16.0.1 version to start with. At least the following RegKeys getting deleted: desc0 = SelectorAlgorithm val0 = MgsIPMatch desc1 = NetworkSense val1 = False desc2 = CheckCertificateRevocation val2 = False desc3 = CheckServerCertificate val3 = False as well as all Download + Upload Servers looking at the installationlogs somehow SelectorAlgorithms getting "reset to default "MgsRandom","MgsPing" ,"MgsADSiteMatch" which cannot work since we have no DNS/ADSite in our ENV as a quick WorkAround we changes "Upgrademode" to "do not upgrade automatically"under inventory settings inside the GUI. now the initial Agent installation remains working withouth updates...! (Flexerainternal Case: #02434472) Greetings Steffen

steffen · ‎Apr 08, 2021

great stuff ! many thanks - this finally works for my corporate units as well, thanks mengmeng!

steffen · ‎Mar 01, 2021

thanks a lot for clarification! - thats how we did it anyway - we just wanted to be certain because we are importing USU (Aspera) StamrtTrack data into FNMS and have to translate SmartTrack internal Oracle SKUs into Flexera internal Oracle SKUs.

Online Status	Offline
Date Last Visited	‎Mar 21, 2023 06:54 AM

Re: Does FlexNet Inventory Agent support IBM Z Mainframe?

Re: Does FlexNet Inventory Agent support IBM Z Mainframe?

Re: FlexNet Manager Suite On-Premises 2022 R2

Re: FNMS on SQL 2019 and Legacy Cardinality Estimator (CE)

Re: Lots of SQL Server installations detected without edition

Re: Automating the Management of Embedded Java instances

Re: Automating the Management of Embedded Java instances

Re: Automating the Management of Embedded Java instances

Re: Does Flexera agent has self-housekeeping feature to clean up agent logs if older than xxx days ?

Re: Agent install/Autoupdate Problem (win 2020r2-16.0.1)

Re: Agent install/Autoupdate Problem (win 2020r2-16.0.1)

Re: Agent install/Autoupdate Problem (win 2020r2-16.0.1)

Agent install/Autoupdate Problem (win 2020r2-16.0.1)

Re: Corporate Unit Business Adapter Not creating levels

Re: Oracle SKUs for use with FlexNet Manager Suite

Re: Does FlexNet Inventory Agent support IBM Z Mainframe?

Re: Does FlexNet Inventory Agent support IBM Z Mainframe?

Re: FlexNet Manager Suite On-Premises 2022 R2

Re: FNMS on SQL 2019 and Legacy Cardinality Estimator (CE)

Re: Lots of SQL Server installations detected without edition

Re: Automating the Management of Embedded Java instances

Re: Automating the Management of Embedded Java instances

Re: Automating the Management of Embedded Java instances

Re: Does Flexera agent has self-housekeeping feature to clean up agent logs if older than xxx days ?

Re: Agent install/Autoupdate Problem (win 2020r2-16.0.1)