About craig_moore

craig_moore · ‎Oct 01, 2020

do you know if the enhancement open for gMSA functionality has been added yet? (issue number IOJ-1922401). Thanks Craig

craig_moore · ‎Jun 03, 2020

Just had call with Flexera on this is apparently a bug. Details below...until fix we need to adjust our steps when upgrading other customers where file exclusions are configured. #CustCall Provided customer workaround Logged as bug and enhancement Please refer to, Bug: IOJ-2119536 Enhancement: IOJ-2119539 Workaround: Only for on-prem: Run query, against FNMSCompliance db: SELECT [BeaconTargetPropertyID] ,[BeaconTargetID] ,[KeyName] ,[Value] ,[TenantID] FROM [FNMP].[dbo].[BeaconTargetPropertyValue_MT] ORDER BY [FNMP].[dbo].[BeaconTargetPropertyValue_MT].BeaconTargetID Delete any records where KeyName is CTrackerExcludeDirectory (and the BeaconTargetID links to 'target__unix' in the BeaconTarget_MT table) 'UPDATE BeaconPolicy SET RevisionNumber = RevisionNumber + 1' - This will remove the exclude directory from the beacon policy, and then agent policy (for Unix devices). Note that the cached device configuration contents.ndc on an agent device will cause the 'original' value to be restored to config.ini on the next policy run after exclude directory is removed from the FNMS db policy properties. If this is not desired, the 'cache' and 'pkgcache' directories on the agent machine in /var/opt/managesoft/launcher should be deleted and then policy reapplied. However, please note that if the Inventory Settings page in the FNMS UI is saved again, the exclude directory property will be added to BeaconTargetPropertyValue_MT again, requiring the above workaround (1 - 4) to be applied to remove it.

craig_moore · ‎May 27, 2020

We typically install two environments with our FNMS deployments (dev/test and prod) and are wondering from a MS-SQL requirement and to save on licensing costs if we can install SQL server standard edition in prod and free SQL server developer edition in test. My understanding is that the developer edition has the same features as enterprise edition but am wondering if there are other reasons why I should NOT install developer edition in test/dev environment. Thanks Craig

craig_moore · ‎May 27, 2020

we just completed upgrade from 2018 r1 to 2019 r2 and noticed that the files exclusions we had configured in the config.ini on several Unix servers appear to have been removed. Note that the agents have not been upgraded yet. An example of the config.ini entry is below and am wondering if the new feature where you can configure exclusions from UI pushed down via policy which is now removing the existing exclusions in the config.ini file on the yet to be upgraded agents. Now that we have upgraded the application server is it now that manual updates of config.ini on specific servers is not supported and all exclusions must be configured on UI and applied globally? Thanks Craig IncludeDirectory=/ ExcludeDirectory=/ENTERPRISE-LDAP/*,/UNIX-LDAP/*,/var/crash,/cores ExcludeEmbedFileContentDirectory=/ENTERPRISE-LDAP/*,/UNIX-LDAP/*,/var/crash,/cores InventorySettingsPath=/var/opt/managesoft/tracker/inventorysettings/

craig_moore · ‎May 06, 2020

I feel like this maybe a silly question but we have a existing implementation of FNMS supporting servers so we only have FNMS datacenter license. We are looking to deploy as an initial test the FNMS agent for a few EUC devices before we procure additional licenses. Will that work if we still only have the FNMS datacenter license? Thanks Craig

craig_moore · ‎Apr 29, 2020

Did you try installing agent on your Photon Linux based VCSA 6.5/6.7 vCenters appliance to obtain an inventory for this device? We have a similar issue where the Vcenter job creates an NDI and shell record for the VCSA appliance but is missing critical information such as serial number. Am thinking we need to install the agent (assuming works) on this device to fill out the shell record. Something doesn't seen quite right with the process though. Craig

craig_moore · ‎Apr 14, 2020

@ChrisG I see creating a bearer token is required for cloud which can be obtained by going to Accounts > All Accounts > Create an account > Service account in the web UI. Adda new account, and the token will be displayed once when the account is created. I don't a reference to service account in the web UI, am I missing something? Thanks Craig

craig_moore · ‎Mar 05, 2020

What is the recommended method to import MAC inventory into FNMS 2019 R2 where Jamf deployed? I don't believe a Tier 1 adapter exists so was thinking to leverage Jamf to deploy FNMS agent and obtain MAC inventory from FNMS agent. I believe Data Platform has a connector to Jamf but we do not have that tool so is not an option here. Please advise Thanks

craig_moore · ‎Feb 10, 2020

Quick (hopefully) clarification on if the FNMS agents can be installed on your FNMS infrastructure servers (e.g. batch and beacon servers). My understanding previously was it was recommended NOT to install the FNMS agent on these servers as will cause issues. I wanted to confirm that this is still the case and if yes the reasons why the FNMS cannot be installed and also how an inventory can then be obtained from these FNMS infrastructure servers. Thanks

craig_moore · ‎Feb 05, 2020

We have an existing FNMS 2018 implementation with ~5,000 agents deployed through the environment connecting to a couple of beacons. Client now wants to stand up a new FNMS 2019 R2 environment on new hardware. My question is what would be the recommendation to get the servers where old agent deployed to report into the new environment. We have had problems trying to reconfigure agent to point to new environment especially with Windows and we are thinking the best approach might be to uninstall the old agent and redeploy the new agent pointing to the new environment. Please advise. Thanks Craig

craig_moore · ‎Feb 03, 2020

We have an customer that we are deploying FNMS 2019 R2 within AWS and they are asking us if FNMS will support installation against Amazon RDS (MS-SQL Engine) instead of a standard MS SQL server installation. Not familiar with Amazon RDS so wanted to confirm with community if this would work and be supported by Flexera. Thanks Craig

craig_moore · ‎Nov 22, 2019

Toby, Any additional updates you can provide that are included with 2019 R2. Will the practice guide need to be updated to reflect those changes in R2? Thanks, that post on 2019 r1 updates aroudn IBM peak consumption was very informative! Craig

craig_moore · ‎Nov 07, 2019

Working on a project where there is a requirement to enable remote users to report back their FNMS agent inventory while not on the corporate network. We are wondering if there exists a document outlining a best practices configuration and/or if anyone can provide guidance on supporting this requirement. We are thinking deploy beacon in DMZ but wondering on how best to configure to minimize security risk etc. Thanks Craig

craig_moore · ‎Oct 10, 2019

Found a trailing space in the connection name that I inadvertently used when I created the SCCM job on the beacon. There is a KD that discusses spaces as an issue so was planning to remove space and retry... https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/Error-Object-reference-not-set-to-an-instance-of-an-object-When/ta-p/5339

craig_moore · ‎Oct 10, 2019

I have two SCCM jobs running.. First SCCM job works fine and reports in as expected. The second SCCM job completes the Gathering inventory data task successfully but remaining tasks in job are pending. When I check on beacon I see the file generated from the gathering inventory data task is placed in the C:\ProgramData\Flexera Software\Beacon\IntermediateData\BadPackages directory. In the upload.log file on beacon I see following errors: 2019-10-09 20:10:10,160 [Upload.UploadProcess ] [INFO ] Found 2 new package(s) to upload 2019-10-09 20:10:10,191 [Upload.UploadProcess ] [ERROR] Package upload failed System.NullReferenceException: Object reference not set to an instance of an object. at Flexera.SaaS.Transport.Upload.UploadProcess.ProcessPackageList(Int32 exitCode, List`1 packages) 2019-10-09 20:10:10,300 [Upload.UploadProcess ] [INFO ] Processing package 'L[S=IBM SCCM Prod Instance ]_201910090810_9592d2b3-2aae-43c6-b515-85ad93dc1da8.zip' in C:\ProgramData\Flexera Software\Beacon\IntermediateData Any ideas on how to troubleshoot further why file is getting moved to badpackages folder? Thanks Craig

Online Status	Offline
Date Last Visited	‎Aug 26, 2021 08:17 PM

Re: Using gMSA account for the FNMS service sccount

Re: Exclusions removed on agent after upgrade

SQL Developer Edition in Test environments

Exclusions removed on agent after upgrade

Obtaining EUC inventory with just FNMS Data center license

Re: Photon OS - VMWare Discovery and Inventory and FlexNet Inventory Agent

Re: Access or Update FNMS Cloud Data using PowerShell

Import Inventory from MAC devices via Jamf

Install FNMS agent on FNMS infrastructure servers

Standing up new FNMS environment - legacy agent question.

FNMS installed on Amazon RDS MS-SQL engine

Re: IBM PVU Peak - should it be reset to 0 in v2019R1?

Support for FNMS agent inventory for devices outside network

Re: Fiel generated for SCCM job ends up in BadPackages folder

Fiel generated for SCCM job ends up in BadPackages folder

Re: Nutanix AHV Inventory using FNMS Agent

Re: Nutanix AHV Inventory using FNMS Agent

Re: Revocation server offline error

Re: Revocation server offline error

Revocation server offline error

authentication method when Gathering inventory from internet facing devices

Re: VMware Stand-alone Inventory Agent for FlexNet Manager Suite

Re: Nutanix AHV Inventory using FNMS Agent

How to configure FNMS to treat same host name to support DR setup and vCenter

Re: Limit SCCM import job