About donald_helliwell

jasonlu · ‎Mar 09, 2023

@gliu , thanks. In my test rig, I removed sysadmin from the FDP service account, leaving only db_owner and public on both databases, then applied the latest update to v5.5.62. This worked without issue. j

didiercottereau · ‎Nov 24, 2021

Hello I will suggest to run the PS1 script with this flag : .\Config.ps1 "Config\FNMS Windows Authentication Config.xml" forceupdateconfig You will enter all information needed to connect to the different central servers as web server and batch server. I had the same issue on my UAT environment

ChrisG · ‎Nov 23, 2021

The agent can be installed on computers that have application server components (including the batch server) installed. This will normally "just work", but there can be some nuances which may need to be considered in uncommon situations. Some ideas of nuances to look out for are: If the agent version is different from the version of the server components, then it is possible that incompatibilities may arise. That is uncommon, but is something to watch out for. Depending on how you're managing the agent version installed on other computers, you may need to manage the agent versions installed on the batch server as an exception to keep it synchronized with the version of the server components. Because the batch server is effectively the root of the beacon hierarchy, you may run in to some obscure behaviors with the data flow of files that are "uploaded" from the agent components on this computer. In general it will "just work", but it's something to watch. Some internal tracing of various components on the batch server can be configured using a file named "etap.trace". When the agent is installed, it is possible you may need to use a file named "etcp.trace" in the agent installation directory in lieu of "etap.trace" for doing this.

erwinlindemann · ‎Aug 23, 2021

Hi Donald, During a recent lengthy support case (#01944043) related to NFS file system scanning, I learned that in addition to the documented 'nfs' file system type, there is a number of additional NFS related file system types (tmpfs,ufs,lofs,cifs) that you can use as options for the 'IncludeFileSystemType' command line parameter for the Flexera agent. As an example, on many Unix/Linux systems, the root-directory "/" is mounted as a FS from type "tmpfs". In case the command line statement for running the Flexera agent provided by @dhoagland1 does not run successfully, can you try to modify the statement to include additional NFS file system types please, like in: ndtrack -t machine -o IncludeNetworkDrives=True -o IncludeFileSystemType=tmpfs,nfs -o IncludeDirectory="/opt/wls;/opt/tomcat"

ImIronMan · ‎May 26, 2021

Hi @winvarma We have not tried re-configuring o365 reader version is 3. - readerV3 And as per KB article that bug should be fixed in 2019 R1. So afraid if changing those settings on fnms 2020R2 could cause any other issues or miss any potential information from o365

winvarma · ‎Apr 14, 2021

Hi @donald_helliwell , could you please elaborate your query. Regards,

mfranz · ‎Mar 19, 2021

No, have you any idea what type of events you want to track?

kclausen · ‎Dec 03, 2020

@dparab27 - Since Exadata is just running the Oracle Linux OS, there would not be any difference in how the agent is installed on an Exadata appliance, vs a normal server running Oracle Linux, or Red Hat Enterprise Linux, or etc.......

ChrisG · ‎Nov 09, 2020

The "SAP" button only appears in the UI for operators whose rights grant them access to SAP functionality. To avoid the button appearing for users, make sure their role memberships grant no rights to access SAP functionality by selecting "None" from the "Privileges" dropdown list in the configuration of relevant roles:

ChrisG · ‎Oct 28, 2020

I think you've touched on the primary options available here: Configure FlexNet agents so that they can run without trusting the certificate that is used to encrypt HTTPS traffic. This is done by setting the CheckServerCertificate agent preference to False. Configure the computers that FlexNet agents are installed on so that they trust the certificate that is installed on the beacon. Some other technical possibilities (although they may be impractical) are: Change the certificate on the beacon to one that will be trusted by all computers in the agent runs on. Use plain unencrypted HTTP rather than HTTPS for agent->beacon communications.

ChrisG · ‎Oct 14, 2020

The normal schedule for an operational agent (using current versions of FlexNet Manager Suite) is to attempt to update policy twice a day: once at a randomly chosen time between 12:05am and 1:05am, and once between 12:05pm and 1:05pm. If the agent does not have a normal operational schedule installed (for example, because it has not yet successfully applied policy at least once), a default schedule is used. I don't recall the exact details of when policy update attempts are made with the default schedule, but think it may be done once a day at a random time and/or after a reboot - and the details may depend on whether you're running on a Windows OS or UNIX-like OS. If anybody else knows these default schedule details with more certainty please post here!

ChrisG · ‎Aug 19, 2020

The following thread contains some good discussion on the principle of including the agent in deployment images: Using Flexera Inventory agent as part of deployment package. The TLDR summary of that discussion is that the general consensus is it is normally better to deploy the agent post imaging as part of the software payload installed on computers, and not as part of the image itself. With that said, in principle there is no absolute blocker to including the agent in an image. Generally the AgentID will be regenerated when an image is installed on a new computer, resulting in FlexNet identifying the computer as a unique device from other devices the image is installed on. See the following for some information about the process of generating (and re-generating) AgentID values: Questions on the FlexNet inventory agent unique identifier (AgentID) property

mfranz · ‎Jul 16, 2020

Hi Donald, I guess this could answer your question: https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-enable-Beacon-Reverse-Proxy-Setup/ta-p/152864 Best regards, Markward

jdempsey · ‎Jan 17, 2020

There is one function in particular that I know is used to get the list of available applications when creating catalog items (though I don't recall the exact name of it). However, my understanding is that there are other functions and stored procedures used as well. The reason we require more general EXECUTE permission is that we don't have a definitive list of the functions and stored procedures that App Broker uses. Also, Microsoft could potentially add others in the future that Flexera may want to leverage for new functionality. What I do know is that the functions/stored procedures that are used are only "selecting" data. We do not perform any "writes" through SQL. All write-related activity is done through ConfigMgr's WMI SDK calls, which is the reason for the console permissions. On that note, I'm sure I've said this in other conversation threads, but within Flexera Services, we almost never give the account Full Admin in the ConfigMgr console. We generally use Application Administrator and Operating System Deployment Manager roles. I've yet to hit a use case that didn't work with those two roles.

CharlesW · ‎Oct 29, 2019

Yes, the step in the helpnet article is correct.. Namely, on the "Logon Information panel" of the install, uncheck the "validate Account and Password" checkbox and click Next to proceed with the installation. If you have this checkbox selected, then the installer uses the computer browser service to validate the account, but typically this service is disabled, or not installed. If the account can not be validated, then you will see the error you are seeing.

Online Status	Offline
Date Last Visited	‎Mar 30, 2023 07:28 PM

Re: Reduced Data Platform Service Account permissions after installation

Re: after Upgraded 2021 R1 IIS service failed to start

Re: Can the FlexNet inventory agent be installed on the FNMS batch server?

Re: Unable to get inventory from remote NFS file system

Re: Previously working Microsoft 365 connector not working after token refresh

Re: Does anyone have experience migrating clients from VMware Cloud Health to Flexera cloud module(s...

Re: FNMS integration with LogRhythym

Re: Installing Flexera agents on ExaData Oracle inventory in FNMS cloud

Re: Is it possible to remove the SAP button from FNMS?

Re: Windows workgroup servers getting certificate error when communicating with the beacon.

Re: Windows FlexNet inventory agent policy download

Re: FlexNet inventory agent ID question

Re: Does anyone have experience configuring the FlexNet Beacons and Inventory Agents to work with a ...

Re: Why does the App Broker service account require Execute permissons on the SCCM database?

Re: AppPortal 2019 R1 installation issue: "Server not found. Verify that the specified server exists...

Reduced Data Platform Service Account permissions after installation

Can the FlexNet inventory agent be installed on the FNMS batch server?

Re: after Upgraded 2021 R1 IIS service failed to start

Re: Unable to get inventory from remote NFS file system

Unable to get inventory from remote NFS file system

Does anyone have experience migrating clients from VMware Cloud Health to Flexera cloud module(s)?

FNMS integration with LogRhythym

Previously working Microsoft 365 connector not working after token refresh

Re: Installing Flexera agents on ExaData Oracle inventory in FNMS cloud

Is it possible to remove the SAP button from FNMS?