FlexNet Connect Knowledge Base

Newly Created Update Does Not Display for Windows Agent

SummaryIn Flexnet Connect 2015, changes were made to how an update type is identified. The product/update type is now identified at the update level, rather than at the product level.. If the update is not flagged with the correct type, then it will...

CharlesW Level 12 Flexeran Nov 06, 2018

FlexNet Connect 2015 How To

FlexNet Connect Client Does Not Show Update or Messages for Product

SummaryThe FlexNet Connect U client does not appear when checking for updates of a registered product.SynopsisWhen attempting to use the UI client (FlexNetConnectClient.exe) nothing is displayed when the show notification parameter, -sn, is used. The...

by ctang Level 3 Nov 06, 2018

FlexNet Connect 2014 R2 FlexNet Connect 2015 FlexNet Connect 2015 SP1 Product & Release Info

Getting a List of Registered Products when Using the Flexnet Connect .NET XT SDK

SummaryGetting a List of Registered Products when Using the Flexnet Connect .NET XT SDK.SynopsisEarlier versions of the FNC Windows Agent provided an EnumProducts() API to query those products which were registered with Flexnet Connect. This API is n...

CharlesW Level 12 Flexeran Nov 06, 2018

FlexNet Connect 2015 How To

Is VirtualBox VM detection possible?

SummaryThis article will explain if VirtualBox VM detection possible in the FlexNet Embedded 2014 R2 & FlexNet Connect 2015 C XT toolkit.QuestionIs VirtualBox VM detection possible?AnswerFlexNet Embedded 2014 R2 only supports detection on the followi...

jmcmillan Revenera Nov 06, 2018

FlexNet Connect 2015 Question

Featured Articles

Featured article

Summary: Several vulnerabilities have been reported in the Apache Log4j library. This article discusses the impact of the following vulnerabilities on FlexNet Connect: Log4j 2.x: CVE-2021-45105 CVE-2021-45046 CVE-2021-44228 Log4j 1.x: CVE-2021-4104 CVE-2019-17571 Description: The Log4j 2.x component is not used in FlexNet Connect Client or FlexNet Connect Back-Office 2017 R3, hence there is no impact from CVE-2021-45105, CVE-2021-45046, or CVE-2021-44228. There is no impact from CVE-2021-4104 or CVE-2019-17571 on FlexNet Connect Client or FlexNet Connect Back-Office 2017 R3 since the source code does not use any of the following: SocketAppender SocketServer class SMTPAppender JMSAppender which are the cause of the Log4j 1.x vulnerabilities mentioned above. Resolution: No resolution required. Workaround: No workaround required. Additional Information: Apache Security Site for CVE severity, score, and vector string: https://logging.apache.org/log4j/2.x/security.html

FlexNet Connect Knowledge Base

FlexNet Connect Knowledge Base

Featured Articles

Log4j vulnerability impact on FlexNet Connect