You must provide the VMware Horizon Cloud Service team with a services subnet and a desktop subnet that are not being used inside your infrastructure, and those subnets must include enough IP addresses to cover the number of desktops or RDSH servers that are provisioned.
Setting Option Code 74 in the desktop subnet DHCP scope directs the desktops and RDSH servers to the tenant appliances. The VMware Horizon Cloud Service team provides the two IP addresses of the tenant appliances during the deployment process.
- Failure to set Option Code 74 properly – If not done properly, the desktops and RDSH servers are unable to locate and register with the tenant appliances. End users are unable to access published desktop and application resources.
- Failure to provide a unique services and desktop subnet – Think of the services and desktop subnet as an extension of your local infrastructure, even though it is in the cloud. If you provide a subnet that is already in use, conflicts can occur, and network traffic might not properly flow between Horizon Cloud Service and your network.
- Failure to consider sizing – If you do not provide a desktop subnet with enough IP addresses to cover the targeted number of desktops and RDSH servers, you must set up another subnet to support the increased capacity. For example, if you provide the /24 in CIDR format for the subnet, you get exactly 252 addresses. Adding additional subnets upfront allows for seamless capacity expansion when needed.
If you cannot configure DHCP Option 74 due to network constraints or other reasons, you can manually configure the DaaS Agent to communicate to the tenant appliances. The VMware Horizon Cloud Service team provides the two IP addresses of the tenant appliances and manually configures the DaaS Agent using the monitor.ini file.