About darren_haehnel

darren_haehnel · ‎Jan 12, 2023

I've been using a script to copy NDI files to multiple environments for the past year+ and have never had to worry about any beacon info.

darren_haehnel · ‎Jan 06, 2023

Thanks @ChrisG. This was performed as prescribed in our situation and still, performance was not acceptable.

darren_haehnel · ‎Jan 05, 2023

Hi @mfeinman , We have our SQL 2019 server configured per the FNMS upgrade guide. It's running at compatibility level 150.

darren_haehnel · ‎Dec 28, 2022

This year we migrated from Win/SQL 2012 servers to Win/SQL 2019 servers for our FNMS environments. One area we struggled with post migration was the duration of the "Inventory Import and License Reconcile" batch job. Ours is scheduled to start at 7pm and pre-migration would finish around 2:30am (+/- 1hr). After migration, the job would run past 4:30am (much longer still when everyone had the ARL issue with double wildcard matches). Our DBA's compared the old and new servers and looked for any opportunities to get us back to prior performance levels. We also analyzed the database using a leading observability tool. We experimented a bit with enabling the Legacy Cardinality Estimator (Cardinality Estimation (SQL Server) - SQL Server | Microsoft Learn) and found our batch job duration improved by roughly 25%, returning us to the 7-8 hour run time, with this one "simple" change. I'm curious if anyone else has experimented with this setting, found similar results, or if there might be any negative consequences. So far, we have left the Legacy CE enabled and found no trouble.

darren_haehnel · ‎Dec 21, 2022

Are you unable to have a domain account created in the DB domain with the correct permissions in the sql instance?

darren_haehnel · ‎Dec 16, 2022

I think the potential for future issues depends on how Flexera implements certificates and code signing in future releases. I believe the problem exists if they have upgrade code signed by old as well as new certificates and the transition isn't effectively managed. This has been (and still is) a significant gap in their upgrade instructions which caused more than a month of delay/trouble for us. Anyway, I'm glad the "Trustworthy ON/Upgrade/Trustworthy OFF" process worked for you.

darren_haehnel · ‎Nov 14, 2022

Thanks for the follow-up Mark. I am curious if the uninstall removed your Dev beacon registry entries or if they remained after the "new" installation using the updated mgssetup.ini.

darren_haehnel · ‎Nov 07, 2022

Hi Mark, Yes, you would see each of the beacon servers the agent is aware of in the "Prioritizing servers for upload" section of the Tracker.log. The server with the lowest priority value would be the first beacon where an upload is attempted. -Darren

darren_haehnel · ‎Nov 04, 2022

Hi Mark, In all likelihood the machine still has the existing registry entries for the DEV beacons. It should also now have the Prod beacon(s) but the agent will determine the first beacon to communicate with (based on availability, ping response time, etc) and only upload inventory to that beacon. You may want to develop a separate SCCM "package" that would eliminate any of the Dev beacon's from the registry prior to running your new SCCM Prod package on the machine. -Darren

darren_haehnel · ‎Nov 01, 2022

FWIW, we have a few non-prod implementations of FNMS on premise. While we do have non-prod beacon's, I would not recommend ever having agents point at those non-prod beacons. We use a PowerShell script to copy XXX inventory files on some frequency (I chose daily) to the Incoming folder on the non-prod beacon's for processing. If you wanted full inventory between your prod and non-prod instances, you could copy all of the files. Of course, there are other inputs to consider (ie: enterprise structure, people, contracts, licenses, etc.) depending on what you feel you need to mimic/replicate into your non-prod environment.

darren_haehnel · ‎Oct 27, 2022

If you have a file that you're importing from, you could do a Select 'Domain\' + [UserName]

darren_haehnel · ‎Sep 21, 2022

I see in the documentation that we can add an extension type (on Unix) in the config.ini using the "IncludeExtension" option. We want to apply this change to all agents in our estate. Is there a way to add a new extension type without going to each deployed device and updating the config.ini? Also, if we do have to update the config.ini, either manually or scripted, on each device, does anyone know if adding "IncludeExtension=jar" in the config.ini would overwrite the default values of .sys, .sys2, .swtag, .swidtag, .cmptag, .sig, .exe, and .lax or would it append to the list? (ie: Do we need to have ALL extensions in the "IncludeExtension" value or just any new, non-default extensions?)

darren_haehnel · ‎Sep 20, 2022

@colmkw2 I came here to say the same thing about IOK-819328. Fortunately for us, the issue was identified before a mass upgrade and we only had to back-rev a few hundred devices.

darren_haehnel · ‎Sep 13, 2022

In our environment we do not use the AWS connector. We have a consolidated list of all instances across all of our accounts in an S3 bucket that gets refreshed daily. Within that data is a field for the environment and we have a mapping table that maps those values to the FNMS Device Roles. It's not perfect as the environment field is free form text so we have to update the mappings when new values appear. We have some automation that looks up each devices serial number in FNMS to see if the new mapped value matches. If there's a difference, the entry makes it onto a worksheet that gets saved to the server and processed by a business importer which sets the new values.

darren_haehnel · ‎Aug 29, 2022

@marius , If you're having some assembly permissions issues we had quite a bit of trouble with the version of the sqlproceduresclr assembly. What we had in our database was an unsigned version. I worked with Brad Wong to get the assembly un-installed and to install the newer, signed version. We were running FNMS 2021 R1 but performed a migration from SQL 2012 to SQL 2017 (and then to SQL 2019). It was migrating to SQL 2017 where we noticed the assembly version previously installed was not signed. You could also set the database "Trustworthy" to "true" but we didn't want to go that route for security reasons.

Online Status	Offline
Date Last Visited	‎Mar 20, 2023 11:29 AM

Re: Query Regarding Beacon

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

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

FNMS on SQL 2019 and Legacy Cardinality Estimator (CE)

Re: Installing FNMS when the data base is in a different domain

Re: Compliance Database Upgrade Error (Could Not Load Assembly "sqlproceduresclr") Going From FNMS 2...

Re: Third-Party Agent Deployment Question

Re: Third-Party Agent Deployment Question

Re: Third-Party Agent Deployment Question

Re: Need documentation for setting up non- production instance in felxera

Re: Business Adapter Regular expression

Re: What data does the FlexNet inventory agent gather as file and installer evidence?

Re: Agent Upgrade

Re: Device Role for Cloud Instances

Re: Steps to redirect FNMS to the new database server

Re: Query Regarding Beacon

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

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

FNMS on SQL 2019 and Legacy Cardinality Estimator (CE)

Re: Installing FNMS when the data base is in a different domain

Re: Compliance Database Upgrade Error (Could Not Load Assembly "sqlproceduresclr") Going From FNMS 2...

Re: Third-Party Agent Deployment Question

Re: Third-Party Agent Deployment Question

Re: Third-Party Agent Deployment Question

Re: Need documentation for setting up non- production instance in felxera