Flexera Community Knowledge Base

Knowledge Base Categories
This is a quick guide on how to enable ETDP Tracing. This can be performed on the batch, application, beacon and agent and is used primarily when the normal logging solutions do not provide enough information, even with debug settings enabled. by generating a trace log you can track much more activity although tracking everything can result in very large files so be warned to only use this when necessary and do not forget to turn it off when you're done,   First, go to your fnms component, in our case, this is the beacon: (be aware you may need to first disable the relevant flexera service via services.msc before this file can be opened or saved)   Once open find the following line and define a valid file-path-   Then we can uncomment some lines to trace those elements, I will do 2 for our case: Once done, save the document and attempt to perform the problem action again, once its complete grab the .log file at the location specified earlier on and compress and send it to support. It will be quite large prior to compressing, Once done its usually best to set these # parts back else disk space may become an issue in the future,
View full article
Summary If SQL Server (unknown component) is the only SQL Database software record that gets recognized from the Managesoft agent inventory, it's likely that there is a WMI Namespace access problem with that system. Symptoms If SQL Server (unknown component) is the only SQL Database software record that gets recognized from the Managesoft agent inventory, it's possible that there is a WMI Namespace access problem with that system.   Cause This is usually caused because the agent cannot gather the WMI class information from the server, there could be a couple of causes for this including access issues, corrupt namespace, etc. Please follow the Resolution section below to find more detail. Resolution 1. On the SQL Server machine in question, launch 'wbemtest' from the run menu 2. Press 'connect' and connect to the following namespace: *If SQL Server 2005 & earlier - root\Microsoft\SqlServer\ComputerManagement *If SQL Server 2008 - root\Microsoft\SqlServer\ComputerManagement10 *If SQL Server 2012 - root\Microsoft\SqlServer\ComputerManagement11 *If SQL Server 2014 - root\Microsoft\SqlServer\ComputerManagement12 3. After connecting to the namespace, click Enum Instances and do a search for "sqlservice" in the superclass name field Look for any MSSQL instances (serviceType=1) in the query results 4. If MSSQL doesn't show up in this list then run the following command: *If SQL Server 2005 or below: mofcomp "%programfiles(x86)%\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof" If SQL Server 2008: mofcomp "%programfiles(x86)%\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof" If SQL Server 2012: mofcomp "%programfiles(x86)%\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof" If SQL Server 2014: mofcomp "%programfiles(x86)%\Microsoft SQL Server\120\Shared\sqlmgmproviderxpsp2up.mof" 5. Re-run the wbemtest and check to see if any MSSQL instances now show up. If it does and the evidence still doesn't trigger a proper SQL Server recognition, then there could be an ARL mismatch problem with one of the WMI evidence records (IOJ-1659934). Ask for the NDI file for further debugging.   Additional Information It's possible to verify the Edition value stored in the SKUNAME property in WMI as well by running the following query after connecting to the namespace in wbemtest: select * from SqlServiceAdvancedProperty where SQLServiceType = 1 AND PropertyName = 'SKUNAME'
View full article
We might find that we want to inventory every machine in our working environment including the FlexNet Beacon server. Although, It is not advisable to install beacon and agent in one server, for they share some registry keys and system configurations which can drastically affect the functionality of the beacon and it'll take a lot of time just to figure out which is which, and leads to re-installing the beacon just to find that it stopped working for reals. However... Good news! it is possible to gather inventory for the beacon server because installing the FlexNet Beacon comes along components of the FlexNet Inventory Agent. Here's how to inventory a beacon: Create a scheduled task that will run the following executable; C:\Program Files (x86)\Flexera Software\Inventory Beacon\Tracker\ndtrack.exe -t Machine Then, double check and re-configure registry keys: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Tracker\CurrentVersion MachineInventoryDirectory = C:\ProgramData\Flexera Software\Incoming\Inventories UserInventoryDirectory = C:\ProgramData\Flexera Software\Incoming\Inventories InventorySettingsPath = C:\ProgramData\Flexera Software\Beacon\InventorySettings WMIConfigFile = C:\Program Files (x86)\Flexera Software\Inventory Beacon\Tracker\wmitrack.ini
View full article
Symptoms: Since the ExcludeDirectory value is coming from policy to be used to apply configuration locally on a machine, the agent overwrites any previous values in config.ini if it is present in the policy which overwrites custom exclusions  Diagnosis: There is no way to stop the agent from doing this at this time for Agents get most of their configurations through policy. Solution: If you do not want any value for exclude directory set in policy, you will need to remove the policy property from the BeaconTargetPropertyValue_MT table as the Inventory Settings page on the FNMS UI seems to set an empty value if the include directory or exclude directory was previously set. Note, as such, this is not an issue with the FNMS agent but the inventory settings UI. This workaround is for On-premise customer's only, for it'll require updating the FNMS database To find configured policy values run the following query: SELECT   [BeaconTargetPropertyID] , [BeaconTargetID] , [KeyName] , [Value] , [TenantID] FROM   [FNMP] . [dbo] . [BeaconTargetPropertyValue_MT] ORDER BY   [FNMP] . [dbo] . [BeaconTargetPropertyValue_MT] .BeaconTargetID Deleting any records where KeyName is CTrackerExcludeDirectory (and the BeaconTargetID links to 'target__unix' in the BeaconTarget_MT table) Then running 'UPDATE BeaconPolicy SET RevisionNumber = RevisionNumber + 1' will remove the exclude directory from the beacon policy, and then agent policy. 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. Also 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 to be applied to remove it.   On going enhancement to locally preserve ExcludeDirectory configurations for Unix-like devices: Enhancement#  IOJ-2119539 FNMS-68635 
View full article
Summary When FlexNet Beacon Server is only using TLS v1.2, policy download fails and the Beacon Engine is no longer able to communicate to the Application Server Symptoms When disabling SSL 3.0 and TLS 1.0 , the Beacon Engine is still trying to communicate over the older protocol according to the following line in the BeaconEngine.log file: [psClientSecurityPolicy|Async] [INFO ] Security protocols Ssl3, Tls are in use. Policy downloads will fail as following: 2018-01-08 11:26:13,003 [Services.PolicyService|policy] [ERROR] Failed to download policy. Flexera.SaaS.Transport.Core.ComplianceApiFatalException: Download failed for item https://fnmsbatchuat.FlexDemo.com/inventory-beacons/api/policy/?BeaconUID={25E6AD55-0000-48C2-0000-F75DA5FB384C} (An error occurred while sending the request.) ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc) at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential) at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint) at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output) at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.TlsStream.CallProcessAuthentication(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState) at System.Net.TlsStream.UnsafeBeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState) at System.Net.PooledStream.UnsafeBeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar) --- End of inner exception stack trace --- --- End of inner exception stack trace --- at Flexera.SaaS.Transport.Rules.PolicyClient.DownloadPolicy(String currentVersion, String inventorySettingsRevision) at Flexera.Beacon.Engine.Services.PolicyService.GetPolicyFromServer(Int32 currentRevisionNumber, String inventorySettingsRevision) at Flexera.Beacon.Engine.Services.PolicyService.UpdatePolicy(IActivityLogger activityLogger) Cause Microsoft .NET Framework v4.5.x and below are using a weak encryption cipher that is not compatible with TLS v1.1 and 1.2, but we have seen the same behaviour in .NET v4.6.x that comes with Windows Server 2016 as well. Microsoft has a KB Article in regards to older .NET Framework below: https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/2960358 Workaround The workaround is to force Microsoft .NET Framework to use a strong cipher by adding the following Registry Key: Open RegEdit.exe as an Administrator Navigate to the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] Right click in an empty area and create a DWORD value named SchUseStrongCrypto and give it a value of 00000001 Once that is complete, restart the FlexNet Beacon Engine service and you should starting seeing this line in the BeaconEngine.log file instead: ? [psClientSecurityPolicy|Async] [INFO ] Security protocols Tls, Tls11, Tls12 are in use.   Additional Information Additional changes to the Beacon may be required in order to force TLS 1.1 or 1.2 on your beacon.  Please review  Transport Layer Security (TLS) 1.1 & 1.2 Configuration for further information. Additionally, we also have this KB article  which goes into further detail about setting up the certificates and other TLS related information.
View full article
There are 3 different ways to get the cost in App Portal. Catalog Cost -> The cost is updated in wd_webpackages table. Inventory group Cost (SCCM "legacy" Inventory)-> The cost is calculated from WD_License table (This is the cost get saved once you create the inventory – Compliance Management -> Add Inventory) Manually override the cost based on localization- currency settings (WD_Package_Cost)   The calculate/get the cost based on the Admin Settings. (AppPortal -> Settings -> CatalogManagement -> Open catalog Properties -> General -> Inventory tab -> "Use the cost of the inventory group".) Please see the below screenshot:   You can execute the below query to get the cost data: SELECT WP.UseInventoryCost , wp.PackageID, wp.PackageTitle, (Case WP.UseInventoryCost WHEN 0 THEN ISNULL(WP.CatalogCost, 0) ELSE ISNULL(l.LicenseCost, 0) END) AS LicenseCost FROM WD_WebPackages wp INNER JOIN WD_License l ON wp.LicenseID_FK = l.LicenseID Further to the above query, the cost gets updated based on Currency as well (get calculated based on currency settings and the above query result), as well as there is a way to manually override the cost based on country too (WD_Package_Cost). See the below screenshot: Note: If FNMS is configured in App Broker, the SCCM inventory Group option won't available in the catalog properties on UI. Furthermore, it is necessary to have a "legacy" App Portal license in order to configure SCCM inventory.
View full article
Summary If administrator access to the admin site has been lost, for whatever reason, it is possible to set admin permissions back to the default settings. Symptoms If the message "You do not have access to this area" is displayed when trying to access the App Portal admin site, even though the logged in user has admin permissions, then it is possible that the permissions may have been corrupted or changed inadvertently. Cause This issue is caused by having an invalid AD user GUID in the WD_NodeSecurity table. This may occur if a user who previously had admin permissions is deleted from Active Directory. Resolution The attached web service may help to identify which GUIDs might be bad.. Based on the GUIDs that are found, an attempt can be made to selectively cleanup the bad guids from the WD_NodeSecurity table, without deleting all records.. To use this web service, copy the attached ValidateSecurityGUIDs.asmx to the web/ws folder under the App Portal install directory.. Once you have done this, hit the following URL in a browser: http://localhost/esd/ws/ValidateSecurityGUIDs.asmx Invoke the function named FindInvalidAdminSecurityGUIDs This will display a list of GUIDs which can not be looked up in AD. This would typically indicate that they are bad.. The list will be displayed in the browser, and also in the log file named badGUIDS.log.. For each guid in the list, run the following query against the App Portal DB: delete from wd_NodeSecurity where nodeGroup = '<guid>' I'd expect that this will be a fairly small list, and quite possibly only a single guid.. If you see a large number of guid's reported, let me know, as something else may be wrong. Note: once you clean up the bad guids, you will need to restart your browser session for the permissions to take effect. If the above steps do not address the issue, then a sure fire way to resolve the issue is by completely resetting the admin permissions back to their default. The following query will reset all admin permissions: delete from WD_NodeSecurity After making this change to the database, perform an iisreset, and restart the browser.. Full administrator access will be restored for all users. It will then be necessary to reset the desired admin security permissions.. 
View full article
Description This KB article is describing a current product defect (reported in 2019 release): Symptom: In some circumstances, when trying to test "My Apps" by using the "License Reclamation Campaign Condition" to include only particular group or collection. Even when user add "Group and OU" and "Collection" to target users but unfortunately every time save it, close and reopen it's not there.    Root Cause: When App Portal tries to check the application in the My Apps, it's querying the application FUID from product FlexNet Manager Suite.  It works fine when the application is an 'Flexera' application which generated from ARL library.  this doesn't work when linking a 'local' application which is not released from FNMS ARL library, but is created manually. The issue is the LENGTH()  of FUID from ARL title is shorter than Local ARL which causing product code fail by passing the local FUID.  Error message  – CampaignConditions.log contains below error while using test for saving: <![LOG[No campaign collection condition attached with flexera Id : app: //71551CCE-6301-428D-97A2-51156143/LOCAL-APP-128564, Campaign Type : 1]LOG]!><time= "11:52:48.000+240" date= "5-11-2020" component= "GetCollectionConditions" context= "" type=" 1 " thread=" 4 " file=" Website"> <![LOG[ String or binary data would be truncated. The statement has been terminated. Error while saving LicenseReclamation Campaign conditions : String or binary data would be truncated. The statement has been terminated. at System .Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System .Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System .Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean & dataReady) at System .Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted) at System .Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System .Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean & usedCache, Boolean asyncWrite, Boolean inRetry) at System .Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean & usedCache, Boolean asyncWrite, Boolean inRetry) at System .Data.SqlClient.SqlCommand.ExecuteNonQuery() at AppPortal.Infrastructure.Repositories.CampaignRepository.SaveCampaignConditions( String flexeraId, List`1 campaignConditiondProperties, CampaignType campaignType)]LOG]!><time= "11:53:17.000+240" date= "5-11-2020" component= "SaveCampaignConditions" context= "" type=" 1 " thread=" 2 " file=" Website"> Workaround Currently there is no 'good' workaround, but try to link application which is released from Flexera source (ARL title). You can submit ARL content submission on the local evidence to ask FNMS content team to add your interested title in future ARL release so that the application title then will have a FUID from Flexera Resolution The defect is logged under Bug ID:  IOJ-2115054  currently is on the defect queue.
View full article
Description This KB article describes a product error which is caused when the AP server is rebooted, other times the error is random and is resolved by rebooting the server or doing an iisreset. Logs attached see error in the website.lo at 6/27/2014 7:24:42 AM Server Error in '/ESD' Application. Replication Scenario -------------------------------------------------------------------------------- Index was outside the bounds of the array. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.IndexOutOfRangeException: Index was outside the bounds of the array. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [IndexOutOfRangeException: Index was outside the bounds of the array.] System.Collections.Generic.List`1.Add(T item) +34 Westwind.Globalization.DbSimpleResourceProvider..ctor(String virtualPath, String className) in C:\AppPortal\Current\Source\AppPortal\WestwindWebToolkit\Westwind.Globalization\DbSimpleResourceProvider\DbSimpleResourceProvider.cs:121 Westwind.Globalization.DbSimpleResourceProviderFactory.CreateGlobalResourceProvider(String classname) in C:\AppPortal\Current\Source\AppPortal\WestwindWebToolkit\Westwind.Globalization\DbSimpleResourceProvider\DbSimpleResourceProviderFactory.cs:24 System.Web.Compilation.ResourceExpressionBuilder.GetGlobalResourceProvider(String classKey) +122 ASP.packages_aspx.__BuildControllblCurrentCart() +116 ASP.packages_aspx.__BuildControltipCart() +454 ASP.packages_aspx.__BuildControlContent1(Control __ctrl) +709 System.Web.UI.CompiledTemplateBuilder.InstantiateIn(Control container) +12 System.Web.UI.MasterPage.InstantiateInContentPlaceHolder(Control contentPlaceHolder, ITemplate template) +87 ASP.esd_master.__BuildControlcph1() +136 ASP.esd_master.__BuildControlform1() +639 ASP.esd_master.__BuildControlTree(esd_master __ctrl) +119 ASP.esd_master.FrameworkInitialize() +46 System.Web.UI.UserControl.InitializeAsUserControlInternal() +35 System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection) +9043442 System.Web.UI.Page.get_Master() +54 System.Web.UI.Page.ApplyMasterPage() +15 System.Web.UI.Page.PerformPreInit() +45 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +328 Workaround Typically if this error is encountered, the issue can be resolved by performing an iisreset.. On occasion, it may be necessary to reboot the server. The ESD Service should not be impacted, as the issue pertains to localization of strings within the web UI. Resolution The defect has been permanently fixed in 2019 R1 SP1 release.
View full article
There are 4 severity levels used to classify a case. Please select the appropriate severity to help with case routing.    Severity Service Definition Characterized by... Critical – 1 Follow the Sun The product can’t be used. No workaround exists. Data corrupted or lost System failure or lockup occurs; performance degradation Incorrect answers when necessary for useful operation Program aborts when used correctly Corruption of O/S or system due to incorrect use of the product Serious -2 Normal Business Hours The product can’t be used but a work-around exists. Much harder to use than reasonably expected Defect with awkward or inefficient work-around Defect with misleading output Documentation functionally incorrect Program aborts when used incorrectly Medium -3 Normal Business Hours The product is useable with a moderate workaround that can be provided. Confusing user interface Program aborts in malicious use Defect is not serious to the operations of the user Inefficient algorithm leads to a substantial waste of time/space Defect causes a preferred feature not to be used Low – 4 Normal Business Hours The product is useable with a simple workaround or fix. Grammatical error in output Ugly screen layout User misunderstanding because of somewhat unclear documentation Cosmetic documentation error where correct use of the product is obvious Enhancement Request   Related articles About Support Connecting Your Community Account to your Organization Flexera Bug Process Support Contacts Support Plan Information Opening Cases Best practices for Case Submission Using the Open Case Window Screen Error when creating a support ticket Case Portal How to View All Cases from Your Company How to Filter Case by Status Case Watcher Functionality How to Download Your Cases Other Questions Why Am I Getting Reminder Emails about My Support Cases?
View full article
Summary How to enable tracing for Inventory Agent to gather more details on Inventory and Software gathering Problems Synopsis Some Software gathering like Microsoft SQL Server without Edition or Oracle inventory sometimes require more logging than the tracker.log to be able to understand what tasks have the Agent performed step by step. Discussion Non-windows Agents already have an etcp.trace file in its install directory. Windows Agents (prior to FNMS 2016 R1) and all Lite Agents, however, don't use the etcp.trace file by default, so you can follow the additional instructions in the Workaround section below. To enable tracing, you need to: 1) Open your etcp.trace file with notepad or any other text editor, which is located by default next to the Inventory Agent's install location. If you don't have one, please download the ndtrack.trace file as instructed in the Workaround section below. 2) To enable trace logs for all Error and Inventory tasks (which are already enabled in the attached ndtrack .trace file), remove the Hash Sign (#) prior to: +Inventory +Error 3) You need to set the location you want the log to be created in, please ensure that this folder location already exists as the folder path must already exist for the file to be created successfully. Enter your location after the filename= field that has no Hash Signs. 4) Now you can run the Agent manually with administrator/root privileges. Below are a few examples after navigating to the directory ndtrack is in: For Windows Agents and Lite Agents: ndtrack.exe -t Machine -o LogFile=C:\Temp\tracker.log -o Upload=false -o MachineInventoryDirectory=C:\Temp For non-Windows Agents: ./ndtrack -t Machine -o LogFile=/tmp/log/managesoft/tracker.log -o Upload=false -o MachineInventoryDirectory=/tmp/log/managesoft For non-Windows Lite Agents: ./ndtrack.sh -t Machine -o LogFile=/tmp/log/managesoft/tracker.log -o Upload=false -o MachineInventoryDirectory=/tmp/log/managesoft 5) Collect the generated files once it's complete: tracker.log managesoft*.log *.NDI Note: Once complete, be sure to add back the Hash Sign (#) to +Inventory and +Error to disable tracing so the extra logging isn't continuously generated.  In order to enable a trace for other than a non-Windows Full Agent or a Windows Agent FNMS 2016 R1 and above, please download the attached ndtrack.trace file to the following directory and change the filename= path to where you want the log written to: For Windows Agents prior to FNMS 2016 R1: Save next to ndtrack.exe, which is by default at C:\Program Files (x86)\ManageSoft\Tracker (for 64-bit machines) or C:\Program Files\ManageSoft\Tracker (for 32-bit machines) For Windows Lite Agents: Save next to ndtrack.exe For non-Windows Lite Agents: Save in root /etc directory  
View full article
Application Version General Availability End of Standard Lifecycle End of Limited Lifecycle Lifecycle as of Today AdminStudio 2019 R2 2019-08-13 2022-08-13 2023-08-13 Standard Life Cycle AdminStudio 2019 2019-03-07 2022-03-07 2023-03-07 Standard Life Cycle AdminStudio 2018 2018-04-27 2021-04-27 2022-04-27 Standard Life Cycle AdminStudio 2016 2016-06-23 2019-06-23 2020-06-23 No Support AdminStudio 2015 2015-07-28 2018-07-28 2019-07-28 No Support AdminStudio Inventory and Rationalization 2015 2015-07-21 2018-07-21 2019-07-21 No Support AdminStudio 2014 2014-07-24 2017-07-31 2018-07-31 No Support AdminStudio 2013 R2 2013-11-22 2016-11-22 2017-11-22 No Support AdminStudio 2013 2013-07-16 2016-07-31 2017-07-31 No Support AdminStudio 11.5 2012-07-16 2015-07-31 2016-07-31 No Support AdminStudio for Symantec 11.5 2012-07-16 2015-07-31 2016-07-31 No Support AdminStudio 11.0 2012-01-26 2015-01-31 2016-01-31 No Support AdminStudio for Symantec 11.0 2012-01-26 2015-01-31 2016-01-31 No Support The date format used is YYYY-MM-DD Versions not listed should be assumed as past extended lifecycle   Read a complete description of the   Flexera lifecycle and end-of-life policy
View full article
As we can see circled our issue is that the edition on this product is not being detected, it's coming up as Unspecified.   This is our evidence page, as seen there is evidence for the circled records and we have information for the Name, Version and Publisher   Again much of the same as previous, we have information for the Name, Version and Publisher in our file evidence   And this is the explanation of our issue. Since in this example, we are using SCCM to gather this information while it has the ability to both gather the name and version as shown in previous screenshots it does not have the capability to gather the Edition which is separate (see first screenshot, {Pro, Standard, etc}) Since the Edition is what the licence complies against the version number alone is not sufficient and so this licence is created with an “unspecified edition” The FNMS agent does have the capability to do this but unfortunately, SCCM does not.
View full article
Within the FNMS WebUI, On your Data Inputs Page: From Web Help: This should take during the next full reconcile and will remove this connection along with any data from the FNMS DB that has been inserted by this connection, so If I removed an SCCM Connection for example it would remove all SCCM records from the system
View full article
When a managesoft component reports an error its possible to get windows to automatically email the entry, this only works for the older components (agent components) which are used both on the agent and some parts of the beacon   Computer Management     System Tools        Event Viewer           Application and Services Logs              Managesoft   Windows lets you trigger scheduled tasks to start when a variety of events happen, e.g.: time of day system startup user login event recorded in event log Armed with this knowledge, you can create a scheduled task that runs when an error is reported. Choose on an event, basic, and select the log “managesoft” Here is a list of the fnms components that write logs into the windows logs, If you are not sure what these mean I would recommend reading the following pdf, chapter 1, “understanding what, where , how and why”: https://helpnet.flexerasoftware.com/FlexNetManagerSuite2019R2/EN/WebHelp/PDF%20Documents/On-Prem/GatheringFlexNetInventory.pdf After selecting your log of choice set the event ID to “1” As we can see in the windows logs Event ID 1 is an Error report After that ensure enabled is ticked and select okay This scheduled task's action can then be set to something that sends you an alert - in your choice of methods (e.g. triggers a shutdown). You might just want it to send an e-mail: So every time this fnms component reports an error it should send an email automatically, you can also set this up for the scheduled tasks as well as other windows components. I have set this up in the past to activate under a variety of scenarios and also to execute scripts instead of emailing (see the actions tab in the last screenshot)
View full article
There are 2 directories on these systems we need in Flexera Support, I shall go through the process on where each one is in this guide, First, open up a terminal and go to the root directory- Then we need to Navigate to our first folder, /var/opt/managesoft/ This folder contains all the operational settings for the Agent, we request you send us all the contents of this folder in an archive. [in particular both ‘etc’ and ‘log’]   Next, we need to navigate to our second folder, /opt/managesoft/ This folder contains all the installation files for the Agent, we request you send us all the contents of this folder in an archive. [in particular ‘bin’]   If unsure on how to create an archive, please refer to the next section which goes over creation in the terminal     The tar command on Linux is often used to create .tar.gz or .tgz archive files, also called “tarballs.” This command has a large number of options, but you just need to remember a few letters to quickly create archives with tar. The tar command can extract the resulting archives, too. The GNU tar command included with Linux distributions has integrated compression. It can create a .tar archive and then compress it with gzip or bzip2 compression in a single command. That’s why the resulting file is a .tar.gz file or .tar.bz2 file. Compress an Entire Directory or a Single File Use the following command to compress an entire directory or a single file on Linux. It’ll also compress every other directory inside a directory you specify–in other words, it works recursively. tar -czvf name-of-archive.tar.gz /path/to/directory-or-file Here’s what those switches actually mean: -c: Create an archive. -z: Compress the archive with gzip. -v: Display progress in the terminal while creating the archive, also known as “verbose” mode. The v is always optional in these commands, but it’s helpful. -f: Allows you to specify the filename of the archive. Let’s say you have a directory named “stuff” in the current directory and you want to save it to a file named archive.tar.gz. You’d run the following command: tar -czvf archive.tar.gz stuff Or, let’s say there’s a directory at /usr/local/something on the current system and you want to compress it to a file named archive.tar.gz. You’d run the following command: tar -czvf archive.tar.gz /usr/local/something Compress Multiple Directories or Files at Once While tar is frequently used to compress a single directory, you could also use it to compress multiple directories, multiple individual files, or both. Just provide a list of files or directories instead of a single one. For example, let’s say you want to compress the /home/ubuntu/Downloads directory, the /usr/local/stuff directory, and the /home/ubuntu/Documents/notes.txt file. You’d just run the following command: tar -czvf archive.tar.gz /home/ubuntu/Downloads /usr/local/stuff /home/ubuntu/Documents/notes.txt Just list as many directories or files as you want to back up.
View full article
Question: Why and how to Enable the DebugLogLevel to 5 in Adminstudio Registry entry: Answer: The DebugLogLevel will be set to 0 by default. The reason for enabling the DebugLogLevel to 5 in the Registry is, this setting will provide a detailed entry of all the tasks that are performed on Adminstudio in the log files ISCMIDE.log and AdminStudio Host.log which will help in debugging the issue. Steps to be followed to set debug log level to 5: 1. Login to the machine where Adminstudio is installed. 2. Open Regedit and navigate to Regedit>HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\InstallShield\AdminStudio>DebugLogLevel. By default, the DebugLogLevel is set to 0. 3. Double click on DebugLogLevel and set the value to 5 and click on the OK button.   4. Stop and then Restart the Adminstudio Host process. 5. By default, the log files 'ISCMIDE.log' and 'AdminStudio Host.log' will be present in the following path: C:\Program Files (x86)\AdminStudio\2019\Common.  
View full article
Within FNMS you have the ability on many pages including the System Tasks page below to download logs, you can perform this action in the administrator role, however, you can also enable this functionality for additional users. to do this, please follow the screenshot steps below Remember to save once edited, you may need to be an admin to change this setting
View full article
Summary: This article helps you to retrieve information on SLA time taken for a particular Step/Phase and information on SLA clock stopped time and resumed time through SQL queries. Discussion: --The difference between the minimum (Changedate) of AuditTypeCode '90' and maximum (ChangedDate) of AuditTypeCode '100' gives you the time taken for a particular step in the below query. select ap.ApplicationLName,mn.WFMinorItemID, mn.WFMinorItemDesc, adt.AuditTypeCode,min(adt.ChangedDate) from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMinorItemTpl mn on mn.WFMinorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (90 ) and adt.ApplicationID='b75bda5b-a685-480c-b9c7-018054ed379e' group by ap.ApplicationLName,mn.WFMinorItemID, mn.WFMinorItemDesc,adt.AuditTypeCode order by 3 desc select ap.ApplicationLName, mn.WFMinorItemDesc, adt.AuditTypeCode,max(adt.ChangedDate) from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMinorItemTpl mn on mn.WFMinorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (100 ) and adt.ApplicationID='b75bda5b-a685-480c-b9c7-018054ed379e' group by ap.ApplicationLName, mn.WFMinorItemDesc,adt.AuditTypeCode order by 2 desc --The difference between the minimum (Changedate) of AuditTypeCode '500 'and maximum (ChangedDate) of AuditTypeCode '501' gives you the time taken for a particular phase in the below query. select ap.ApplicationLName,mj.WFMajorItemName, adt.AuditTypeCode,min(adt.ChangedDate) from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMajorItemTpl mj on mj.WFMajorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (500 ) and adt.ApplicationID='b75bda5b-a685-480c-b9c7-018054ed379e' group by ap.ApplicationLName,mj.WFMajorItemName,adt.AuditTypeCode select ap.ApplicationLName, mj.WFMajorItemName, adt.AuditTypeCode,max(adt.ChangedDate) from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMajorItemTpl mj on mj.WFMajorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (501) and adt.ApplicationID='b75bda5b-a685-480c-b9c7-018054ed379e' group by ap.ApplicationLName, mj.WFMajorItemName,adt.AuditTypeCode --SQL query to retrieve information on SLA clock stopped time and resumed time select ap.ApplicationLName,mj.WFMajorItemName, adt.AuditTypeCode, adt.ChangedDate from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMajorItemTpl mj on mj.WFMajorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (401) and adt.ApplicationID='4a569a1b-4b88-43f8-8bf0-9c914999d614' group by ap.ApplicationLName,adt.AuditTypeCode,mj.WFMajorItemName,adt.ChangedDate select ap.ApplicationLName, mj.WFMajorItemName, adt.AuditTypeCode,adt.ChangedDate from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMajorItemTpl mj on mj.WFMajorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (400) and adt.ApplicationID='4a569a1b-4b88-43f8-8bf0-9c914999d614' group by ap.ApplicationLName, mj.WFMajorItemName,adt.AuditTypeCode,adt.ChangedDate  
View full article
Symptoms: when creating a schedule for AWS in the beacon UI the AWS schedule is not applied or created whereas this should happen Diagnosis: (no “AWS Import” Schedule listed) Solution: Workaround: close beacon UI stop beacon service navigate to beacon programdata folder C:\ProgramData\Flexera Software\Beacon rename "schedule.xml" to "schedule.bak" (or just erase or store in an archive) start the beacon engine service & launch the beacon ui this will create a new schedule.xml which should solve this issue   Fix: This was a bug that was fixed in FNMS 2019r1 version of the beacon, the bug subject was: Default schedule "AWS imports" is not created if schedule.xml already exists during upgrade
View full article