About mfeinman

mfeinman · ‎Dec 15, 2022

@ChrisG , your guess was good. About 38,000 devices. --Mark

mfeinman · ‎Dec 12, 2022

Hi all ... My reconciliation process that ran last night (Sunday 12/11) was back to normal. Total time was about 6 1/4 hours and the double-wildcard step ran in 54 minutes: 2022-12-12 04:57:36,288 [INFO ] WriteFileEvidence - Match double ended wildcards 2022-12-12 04:57:36,288 [INFO ] Writer step 'WriteFileEvidence - Match double ended wildcards' with non-default execution path (Fallback) meets condition TestingOrFallback. 2022-12-12 05:52:21,608 [INFO ] Matched 40923 records to existing File Evidence with start and end wildcards 2022-12-12 05:52:21,608 [INFO ] Successfully processed in 54 minutes, 45 seconds (Is 54 minutes a decent time to match on 40,923 records?) --Mark

mfeinman · ‎Dec 09, 2022

Thanks for the documentation link. Very helpful to me in understanding the setup. So it appears there's three things required to make this work: Installing the agent on the VDI template (or "golden image"). This was done with the SCCM push during my agent deployment. Installing the Citrix Remote PowerShell SDK onto a beacon. (not done yet) Configuring a connection in the FlexNet Beacon UI to Citrix. (not done yet) At the moment, only #1 has been done. Is it OK to leave this "as is" (inventory agent running) or must it be stopped until I set up the inventory beacon connection? My assumption is, in this state, I'll just get inventory from the VDI template. --Mark

mfeinman · ‎Dec 08, 2022

Hi all ... Before my laptop received the Flexnet Inventory Agent, its inventory was passed to FNMS using an SCCM Inventory Adapter. FNMS listed the "inventory device type" as Computer. Now that my laptop has the Inventory Agent on it (version 2021 R1), the "inventory device type" was changed to "VM Host". I've noticed this same change for many other laptops in my organization. Is there something in the agent's NDI file that triggered this change by FNMS? My laptop is a HP ProBook 640 G5, if that helps. --Mark

mfeinman · ‎Dec 08, 2022

Hi all ... In my recent rollout of the Flexnet Inventory Agent for Windows (third-party deployment push of the 2021 R1 agent through SCCM), the agent was automatically installed on a Windows image in a non-persistent Citrix VDI environment. I know little about Citrix VDI. The question asked of me was "how does the agent work in a non-persistent VDI environment and what its impact might be?" I've read some prior postings about setting up Discovery & Inventory rules for collecting this inventory. None of these are done at this time. Could the experts kindly weigh in on my question or point me to documentation which answers it? If my question needs clarifying data (for example, "Windows image in a Citrix VDI environment" is too general), please let me know what is needed. Thanks for your help. --Mark

mfeinman · ‎Dec 08, 2022

The fact that you are running a different release of the FNMS server than I am, and that my FNMS server has the same issue as you, tells me that this is likely the result of "some change". I see further down that the current thought is Tibco wildcard entries in the ARL that are soon to be backed out. Hopefully that is the source of the issue.

mfeinman · ‎Dec 08, 2022

Thanks for the attention this issue is getting. In my case, the issue started with the 12/4 reconciliation. My ARL was updated on 12/3 (and is done weekly on Saturdays). (I originally thought it had something to do with my agent rollout but I now see that was just a big coincidence.) Edit: I am using FNMS 2019 R1 on prem (server upgrade is planned in a few weeks). --Mark

mfeinman · ‎Dec 07, 2022

I have exactly the same issue. In my case, it started recently with the rollout of the Inventory Agent to thousands of workstations. (The rollout went fine.) The agent version is 2021R1 but, for at least another month or two, my server is still at 2019R1. What server version are you running? --Mark

mfeinman · ‎Nov 14, 2022

Hi all ... Today I noticed many of my computers were assigned to the following two applications: ECM Sample Usage Application 1.0 ManageSoft Corp ECM Enterprise Usage Application 1.0 I also noticed that these two entries were just added to the ARL (version 2713). Isn't this application very old? If so, why would this be added now? --Mark

mfeinman · ‎Nov 14, 2022

Hi @darren_haehnel ... Yes, the DEV beacon entries were all removed and replaced by my PROD ones. I also specified this in my mgssetup.ini, which is likely why it worked for me: DESTRUCTIVEUNINSTALL = 1 The comment for that variable is: If set, forcibly removes any Tracker, Launcher & Schedule Agent registry keys under HKLM during uninstall. Some discussion of this variable can be found here: Flexera Agent Leftovers After Uninstallation - Community --Mark

mfeinman · ‎Nov 14, 2022

To kind of close the loop on this one ... In my case, it turns out that SCCM never activated the agent MSI because SCCM found the same version of the agent already installed and considered the deployment "compliant". The MSI itself never ran. This makes sense - if the version of the agent is the same as that being deployed, the assumption should be "hey the agent is already installed, nothing to see here, move along ...". So I did some experimentation with just the MSI and without SCCM. If I start out with 17.1 and attempt the “upgrade” to the same version, nothing changes. The MSI does run though, and the msiexec log indicates that the existing version was changed, though nothing really was changed. The revised mgssetup.ini does not get applied. However, if I uninstall the agent first (msiexec /x) and then install (msiexec /i), I get the desired change to the inventory beacon list (because the install here is a new install) - the mgssetup.ini file does get applied. So the answer to my own question: "Is an upgrade (or downgrade) triggered only if the already installed version is different from the one being requested?" is YES 🙂 --Mark

mfeinman · ‎Nov 04, 2022

Hi Darren ... Would I also see the entire beacon list (PROD and DEV) in the tracker.log file when the upload decision is made? --Mark

mfeinman · ‎Nov 04, 2022

Hi all ... I have a question about third-party agent deployment. Here's my use case: A Windows computer already has the 2021R1 version of the agent The already-installed agent points to Inventory Beacons tied to a DEV server. We used SCCM to push the installation command of the 2021R1 agent to this machine. (Yes, the agent versions are the same.) With this package, a bootstrap file was supplied that points the installation to a PROD Inventory Beacon. My expectation was that the installer would reinstall the same agent version and then point the agent to the production inventory beacon, get the list of all PROD inventory beacons, etc. However, when I checked the following morning, I didn't see this computer's inventory uploaded to the production FNMS. I still see it reporting to the DEV FNMS. I suspect that the installer detected that the same version of the agent already existed on the machine and didn’t do anything. (At the moment, I assume the SCCM push of the command was successful and am checking into that as well.) Is an upgrade (or downgrade) triggered only if the already installed version is different from the one being requested? --Mark

mfeinman · ‎Oct 25, 2022

Ahhh, OK - to paraphrase, the time zone of the computer running the agent is "added" to the time to get the full picture, so if a server is in the Pacific time zone, it'll run at 2:30pm Pacific time (or 5:30pm Eastern). Thanks for clarifying! --Mark

mfeinman · ‎Oct 25, 2022

Hi all ... My current agent schedule is set to daily, with a start time of 2:30pm, with an offset ("commence within") set to 2 hours. This schedule was set up before I assumed responsibility for my deployment. Doesn't that mean that inventory is only collected between 2:30pm and (roughly) 4:30pm? It's 12:17pm as I write this, and I'm seeing inventory coming into the Incoming folder well before 2:30pm; hence my question. --Mark

Online Status	Online
Date Last Visited	‎Mar 29, 2023 02:47 PM

Re: Reconcile takes 7 to 13 hours to complete

Re: Reconcile takes 7 to 13 hours to complete

Re: How Does the Flexnet Inventory Agent Work in a Non-Persistent Citrix VDI environment and What is...

What Entity Decides The "Inventory Device Type"?

How Does the Flexnet Inventory Agent Work in a Non-Persistent Citrix VDI environment and What is its...

Re: Reconcile takes 7 to 13 hours to complete

Re: Reconcile takes 7 to 13 hours to complete

Re: Reconcile takes 7 to 13 hours to complete

ARL Content Question re: "ECM Sample Usage Application 1.0 ManageSoft Corp"

Re: Third-Party Agent Deployment Question

Re: Third-Party Agent Deployment Question

Re: Third-Party Agent Deployment Question

Third-Party Agent Deployment Question

Re: Question About Agent Schedules

Question About Agent Schedules

ndtrack Questions Regarding High CPU utilization, the "LowProfile" Registry Entry, OneDrive Scanning...

Re: Adding/replacing beacons

Re: "Bootstrap Server 1" Registry Entry After The Original Bootstrap Beacon is Retired - Does It Nee...

"Bootstrap Server 1" Registry Entry After The Original Bootstrap Beacon is Retired - Does It Need to...

Re: Upgrading to server 2019 for FNMA

Re: More Than One Install Command For Linux X86_64?

More Than One Install Command For Linux X86_64?

Re: Healthcheck for Beacon

Re: Upgrading to server 2019 for FNMA

Re: [FNMS] Directory of an application installed on Flexera