For most customers, a single VCF License Server, which is automatically deployed as part of a VMware Cloud Foundation (VCF) or VMware vSphere Foundation (VVF) deployment, is sufficient to provide centralized license management for all VCF components. A single VCF License Server and VCF Operations instance can manage both VCF and VVF entitlements, so deploying additional VCF License Servers provides no additional benefit.
While additional VCF License Servers (LS) can certainly be deployed, the primary use cases are replacing an existing VCF LS or supporting extreme edge deployments where vCenter Server has limited connectivity to the primary data center and requires a VCF LS to be co-located with the edge deployment.
The VCF LS is provided as a virtual appliance in OVA format. The typical deployment workflow uses vCenter Server, where the VCF LS uses OVF properties, like most virtual appliances, to configure itself during deployment.
With that said, if you need to deploy the VCF LS directly to an ESX host, this is certainly possible using OVF Tool, which can inject the required OVF properties as part of the deployment workflow.
