Hi Ujas, There are multiple approaches, each of them somehow trying to force these hosts into the DC license. Edit: has been discussed in the past. Group Assignment You could assign a specific location/cost center/corporate unit to these hosts and then limit the DC license to these elements using the "Group assignment" tab. You'll also have to make sure the license consumption order is set correctly. Manual allocation You could simply allocate those machines to the DC license yourself. Depending on the quantity and fluctuation in your environment, you might want to go for an automated option. In that case, please have a look at option 3. Automatic allocation You can certainly define a "logic" in SQL to identify those hosts (I've done so myself in the past repeatedly). The results can be fed to a business import to automatically allocate these machines to the correct license regularly. There are a few more details to consider, but I guess you should get the general idea from this description. Best regards, Markward ... View more

1) Yes.  This is not performed with an agent, FNMS connects to the VMware vCenter SDK 2) How were these users originally created within FNMS?  For example, if they were imported from Active Directory, then if you delete them from FNMS - they will be recreated the next time you import from Active Directory. 3) Assuming that you have FlexNet Manager for Data Centers, then this information is exposed on the "VMware Inventory" view.  There will be 1 row of data on this view for each ESX host that indicates what version/edition of vSphere is on that host, and which vCenter is managing this ESX Host.  The vSphere License Key is also shown listing the current capacity of the key and how many current processors are consuming against that key (showing if you are under or over consumed) 4) At the present time, FNMS does not support the Citrix XenServer hypervisor 5) Support for the KVM hypervisor was added to FNMS 2019 R2 ... View more