About intannh

intannh · ‎Mar 08, 2020

Hello, I came across Raw evidence type = uninstall while doing validation on inventory in FNMS. Could anyone enlighten me, what does this mean? Thank you!

intannh · ‎Feb 26, 2020

thank you!

intannh · ‎Feb 24, 2020

hello, where can I find more details about FNMS integration with IBM ILMT i.e. pre-requisites, integration steps, type of data imported etc. Appreciate your assistance. Thank you. Regards, inh

intannh · ‎Feb 02, 2020

Hello, is there in the Flexera product map or plan to include Microsoft Intune ?

intannh · ‎Jan 15, 2020

Hello, Would like to check if FNMS support integration with Microsoft Intune? If no, are there any plan to let this works? Thank you, your response is highly appreciated. Best regards, Intan

intannh · ‎Jan 07, 2020

Hi, has anyone performed FlexNet agent deployment using 3rd party tools for non-windows platform? Would like to check what are the tools that can do this, similar like SCCM push deployment. We are looking at large number of vms (non-windows) to deploy flexnet agent for. Any feedback would be appreciated. Regards intan

intannh · ‎Nov 18, 2019

thank you Chris for your prompt response!

intannh · ‎Nov 17, 2019

Hi, What are the changes that we need to apply on beacon settings when customer change DNS/DHCP server? They're on FNMS cloud. Thank you!

intannh · ‎Sep 12, 2019

Does Flexnet Agent support Xen hypervisor (model HVM domU) ? Regards, tan

intannh · ‎Jul 24, 2019

We managed to solve this. As you pointed out, the cause was the compliance db wasn't properly migrated. Resolution: Verify CMSchemaVersion should be 13.2 unless it wasn't properly migrated Because it wasn't properly migrated, we had to remove cm-migr1310-MigrateSAPRoleConsumptionBulkCopy.sql lines from ComplianceMigration.xml as this cause an error (customer no longer use SAP) Remove SAP related sql's from cm-migr1310-migpost.sql Rerun mgsDatabaseUpdate.exe for compliance db Verify the CMSchemaVersion = 13.2 Reconfigure the system FNMS is working fine now. Thank you.

intannh · ‎Jul 19, 2019

Hi, We just completed the upgrade from FNMS 2018 R2 to FNMS 2019 R1. However, post upgrade the reconciliation process encountered an error with message Error: Exception has been thrown by the target of an invocation. Addition to that, unable to access few pages from web UI i.e. All Inventory page with Error ID: f73d4b45-4db3-4b4e-9d81-c487eabf27a9 Has anyone encountered this before? Thank you. Regards, Intan

intannh · ‎Jun 11, 2019

Hi, Would there be any impact to FNMS if customer change the password of existing installing administrator account i.e. fnms admin ? Thanks, Intan

intannh · ‎May 15, 2019

may I know whats the difference with the other one?

intannh · ‎May 14, 2019

Hi, Apparently customer changed the default value of [FNMSCompliance_TEST].[dbo].[SoftwareTitle_MT]. We have resolved the error after revert back to the default value. So basically what we did: 1. Revert [FNMSCompliance_TEST].[dbo].[SoftwareTitle_MT] to default value which is 3. 2. Run the migration script again and upgrade completed successfully. 3. Customer may change back to the number they want if necessary once system upgrade completed. Thanks.

intannh · ‎May 13, 2019

Hi, Anyone encountered error while upgrading FNMS 2016 R1 SP1 to FNMS 2019 R1 before? Preparing to run step 'Check migrated database against schema'. Required minimum database compatibility level: SQL Server 2008 (100) Found database compatibility level: SQL Server 2008 (100) Required version: 13.2 Found version: 13.2 Executing step Checking that all database objects are owned by dbo...Validated Running 'ComplianceSchema_schemacheck.sql'. Returned row: MigrationErrors: Column default value is wrong: SoftwareTitle_MT.UsagePeriod, is "((24))" should be "(3)" There was an error while attempting to run 'ComplianceSchema_schemacheck.sql'. Returned row count 1 does not equal expected row count 0 Stack Trace at ManageSoft.Database.Update.FileStep.ExecuteReader(SqlConnection p_SqlConnection) File steps for Check migrated database against schema failed.

Online Status	Offline
Date Last Visited	‎Apr 28, 2020 08:08 AM

Application evidence type

Re: integration to ILMT

integration to ILMT

Re: FNMS Intune connector?

Microsoft Intune integration with FNMS

FlexNet agent 3rd party deployment on non-windows platform

Re: DNS change

DNS change

Flexnet Agent for Xen hypervisor

Re: Error: Exception has been thrown by the target of an invocation

Reconciliation fails with error after upgrade to FNMS 2019 R1: "Exception has been thrown by the tar...

Change password of fnms install account

Re: FNMS Upgrade - compliance schema migration error