...
- Requirements for direct ESXi host binding:
- The VE license server must run in one of the VMs on the ESXi server.
- ESXi/vSphere version 6.5 and above.
- Valid license that supports the vSphere API feature. Otherwise the license server fails to start with the message
Failed to detect ESXi/vCenter Server. - Ports 443 (TCP) and 902 (TCP, UDP) must be accessible to the VE license server host.
- 100 MB of free disk space on the ESXi server to be used by the VE license server host.
- Administrative user (and password) on the ESXi/vSphere host used for the binding between license server and ESXi/vSphere host.
User and password on the ESXi/vSphere host used for the binding between license server and ESXi/vSphere host. This user must have at least the following permissions assigned to the user via a custom role definition (please note that the permission paths/names can be slightly different depending on the vSphere version):
Excerpt name ESXiPermissions - Datastore > Allocate Space
- VirtualMachine > Config > AddNewDisk
- VirtualMachine > Config > RemoveDisk
- Requirements for vCenter Server binding:
- The VE license server must run in a VM on one of the ESXi systems managed by the vCenter Server.
- vCenter Server version 6.5 and above.
- Ports 443 (TCP) and 902 (TCP, UDP) must be accessible to the VE license server host.
- 100 MB of free disk space on the vCenter Server to be used by the VE license server host.
- User and password on the vCenter Server used for the binding between license server and vCenter Server. This user must have at least the following permissions assigned to the user via a custom role definition (please note that the permission paths/names can be slightly different depending on the vSphere version) :
- Datastore > Allocate Space
- VirtualMachine > Config > AddNewDisk
- VirtualMachine > Config > RemoveDisk
...