Loading
search-img

oqueck (Flexera Software) asked a question.

March 5, 2020 at 5:20 PM
ESX Query tool working and vCenter Discovery & Inventory not

Hi,

we've implemented FlexNet Manager Suite 2019 R2 and are wondering, why importing all VMware vCenter hosts is working fine when using the Flexera ESX Query tool, but when we want to achieve the same with our Discovery & Inventory rule no vCenters are discovered and no inventory scan files are created. Would the Flexera ESX Query tool be capable of collecting more information then FlexNet Manager Suite in certain cases like e. g. some free version of VMware or would could be the root cause for this different behavior and is there an easy way to figure this out ?

Thanks & best regards

Oliver 

  • 15 answers
  • 389 views

  • Portal User

    Hi @oqueck  - Try setting the parameters in the attached screenshot if the discovery step isn't working. I wish the dependency on the network discovery scan would get removed, there's been many instances where ESXquery works fine but the beacon does not.

    As far ESXQuery, I don't believe it brings in any vCenter license info so you may lose that if you decide to do the introspections outside of the beacon, however not sure if this is still the case with the latest version.

    • discovery
    Selected as Best

  • AamerSharif (Flexera)

    Would the Flexera ESX Query tool be capable of collecting more information then FlexNet Manager Suite in certain cases

    Aamer: No it would not. ESX Query tool uses the same implementation. Free VMWare API restriction is within the VMWare API not in FNMS solution OR ESX Query tool

    It looks like discovery process may not be discovering VMWare vCenter API. Please check the generated discovery file by vmware rule (created to collect VMWare inventory data), Is it in scope, If yes, discovery file should have port and VMWare API information. If discovery could not find API, it would not collect VMWare inventory. You a

    Rule execution logs and generated discovery files, are good starting point (discovery and vmware inventory log) created by that rule execution to narrow down the problem.

    This could be due to multiple reasons e.g. ICMP is blocked (inventory only option can help by setting the VMware vCenter Server and port on the discovered device through advance tab on discovered device properties and use known discovered device for inventory only), device not in scope etc.

    Hope this will help to narrow it down.

    Cheers

    Aamer

     

    Expand Post

    • Portal User

      Hi @oqueck  - Try setting the parameters in the attached screenshot if the discovery step isn't working. I wish the dependency on the network discovery scan would get removed, there's been many instances where ESXquery works fine but the beacon does not.

      As far ESXQuery, I don't believe it brings in any vCenter license info so you may lose that if you decide to do the introspections outside of the beacon, however not sure if this is still the case with the latest version.

      • discovery
      Selected as Best

      • oqueck (Flexera Software)

        Hi Peter,

        your screenshot solved my issue.

        Thank you soo much &

        best regards

        Oliver

        Expand Post

        • romanmensch

          Hello Community and Hello Oliver @oqueck  ,

          I have a vCenter that I can read out well with the associated VMs.

           

          Now I have another vCenter from another organization that up until now only brings the nodes.

          Do you think that is true?

          It is because too few rights in the vCenter ? or as here describe the reg key setting?

          Thanks a lot for help

          Expand Post
          • vcenter_only_nodes

          • JohnSorensenDK (Flexera Software)

            @romanmensch  

            Are you sure that you've collected inventory from the virtual machines belonging to the vCenter from another organization that only brings the nodes?

            Also please be aware that the registry settings in above screen shots are a bit dated compared to the available configuration options as per the latest version. Please refer to online documentation for the latest and greatest configuration options.

            Thanks,

            Expand Post

          • 0_Captain Kirk (Flexera Software)

            @romanmensch   - When connecting to vCenter, you will not see the individual VMs under an ESX Host until hardware/software inventory from the VM is received - either from a 3rd-party tool such as SCCM, or from the FlexNet Agent.

            • romanmensch

              I guess that's it, thank you. In another cluster, we probably get all information from the SCCM or because the Flexera agent is installed on the VM's.

      • DiannaB

        Hi @Inactive User  ,

        Do you know if this solution worked on a Windows Server 2019 Beacon (with FNMS 2019 R2 installed)?  We have the same issue so I added these two registry parameters but it didn't appear to make any difference.  We get two lines in our discovery log and then the beacon stops running other rules and we have to reboot the beacon to free it up:

        2020-03-09 15:09:47,922 [iscoveryActionExecuter | Async] [INFO] Executing rule 'vCenter - XXXX....

        2020-0309 15:09:47,938 [iscoveryActionExecuter | Async] [INFO] This task was run manually by 'xxxxx….

        Thanks!

        Expand Post

        • DiannaB

          P.S. This rule works fine if we run it from a Windows Server 2012 or 2016 beacon.

        • Portal User

          Hi @DiannaB ,

          I haven't done any sort of testing on Windows Server 2019 so I'm not sure how that may factor into this. There may be a platform supportability issue with mgsipscan on v2019 but that's just a complete guess

10 of 15

+1.800.374.4353
CONTACT SALES SUPPORT HUB FLEXERA REVENERA
© 2026 Flexera. All rights reserved.
Privacy policy Terms and conditions Revenera Community Help
Loading
Feed Detail