Follow these steps to download and deploy the Horizon Cloud Connector appliance for a pod deployment that uses the federated architecture with AVS. In the federated architecture, you must deploy Horizon Cloud Connector into the native Microsoft Azure infrastructure of your pod's environment.
Important: Use this page solely when you have access to a first-gen tenant environment in the first-gen control plane. As described in KB-92424, the first-gen control plane has reached end of availability (EOA). See that article for details.
For background information on Horizon pod deployment architectures, see First-Gen Tenants - Horizon Pod Deployment Architectures with First-Gen Horizon Cloud. For detailed information about working with an AVS environment, see the Microsoft Azure documentation at https://docs.microsoft.com/en-us/azure/azure-vmware/.
The following is a high-level overview of the steps required to deploy Horizon Cloud Connector into the native Azure infrastructure within your pod's environment:
- Download the Horizon Cloud Connector VHD file.
- Create an Azure storage container and upload the appliance VHD to that storage container.
- Create a virtual machine (VM) image from the uploaded VHD.
- Create the Horizon Cloud Connector VM from the VM image.
Prerequisites
- Verify that you have met the connector-related prerequisites described in First-Gen Tenants - Horizon Pod and Horizon Cloud Connector - Preparing to Onboard to First-Gen Control Plane Services.
- Verify that you have met the DNS, ports, and protocols requirements for using Horizon Cloud Connector to pair a Horizon pod with Horizon Cloud.
- The Horizon Cloud Connector virtual appliance must reach the Internet to talk to the Horizon Cloud control plane. If your environment requires use of a proxy server and proxy configuration for deployed appliances to reach the Internet, verify that you have reviewed the proxy-related information, known limitations, and known issues when using proxy settings with the Horizon Cloud Connector appliance. See the proxy-related information in First-Gen Tenants - Horizon Pod and Horizon Cloud Connector - Preparing to Onboard to First-Gen Control Plane Services, Horizon Cloud Connector Known Considerations, and Modifying Proxy Settings for Horizon Cloud Connector 1.6.
- To locate the required VM sizing, see Horizon 8 Pods with First-Generation Horizon Cloud Control Plane - Requirements Checklist - Appropriately Updated at the Service Update of November 2, 2023
Procedure
-
Download the Horizon Cloud Connector disk image using the link provided in your subscription email.
The Horizon Cloud Connector disk image is available as a VHD file compressed into a ZIP package after you log in to Customer Connect using your Customer Connect account credentials. Download and extract the VHD file to your local system.
Important: To enable the most up-to-date features, obtain the latest Horizon Cloud Connector disk image. All Horizon Cloud features and services are supported in the latest version except for automated updates of Horizon Cloud Connector.
The following features and services are not supported for Horizon pods in AVS when paired with Horizon Cloud Connector 1.9 or earlier:
- Automated updates of Horizon Cloud Connector
- Universal Broker and multi-cloud assignments
- Cloud Monitoring Server (CMS)
- Horizon Image Management Service Before uploading the disk image file to your AVS environment, you must first create an Azure storage container and share it using a shared access signature.
-
In the Azure portal, navigate to your storage account and create a storage container for the VHD file. For more information, see https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview.
During the creation of the shared access signature, a SAS token is generated. You must construct a storage account URL for the disk image file by appending the SAS token to the storage container URL.
-
In the Azure Portal, navigate to that container's properties and take note of its storage container URL for the next steps. In Azure, the standard endpoint for a blob storage container has the pattern
https://<storage-account>.blob.core.windows.net/<container-name>. -
Create a shared access signature. View the storage account in the Azure Portal and navigate to Security + networking > Shared access signature. Specify Container for the allowed resource type and generate the SAS by clicking Generate SAS and connection string. After clicking the button, the portal displays the SAS token and blob service SAS URL below the button. Take note of the generated SAS token for the next steps.
-
Construct the storage account URL using this format:
<StorageContainerPath>/HorizonCloudConnectorDiskImageName.vhd<SAS-Token>The following is an example of a storage account URL:
https://mystorageaccount.blob.core.windows.net/horizon-cloud-connector-2.4.1.0-23063000.azure.vhd?sv=2020-01-01&ss=bfqt&srt=sco&sp=rwdlapx&se=2020-01-01T12:00:00Z&st=2020-01-01T06:00:00Z&spr=https&sig=dUPul74l4K0ah%2FdoCpaTTjY4t2Js8kBY%3D
-
-
Upload the disk image file to the storage account URL that you created.
-
Download and install the AzCopy utility on the local system where you extracted the VHD file containing the Horizon Cloud Connector disk image.
For more information about the AzCopy utility, see https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10.
-
To upload the VHD file, run the following command in the AzCopy utility:
azcopy cp <Path to extracted VHD file> “<StorageAccountURL>” --blob-type PageBlobThe following shows an example of an upload command issued from a local Windows computer:
azcopy cp c:\horizon-cloud-connector-2.4.1.0-23063000.azure.vhd "https://mystorageaccount.blob.core.windows.net/horizon-cloud-connector-2.4.1.0-23063000.azure.vhd?sv=2020-01-01&ss=bfqt&srt=sco&sp=rwdlapx&se=2020-01-01T12:00:00Z&st=2020-01-01T06:00:00Z&spr=https&sig=dUPul74l4K0ah%2FdoCpaTTjY4t2Js8kBY%3D" --blob-type PageBlob
-
-
Create a virtual machine (VM) image from the uploaded VHD file.
-
In the Azure portal, navigate to Images and create a new VM image. Enter a name for the image, and specify the target location and resource group.
-
Specify the following options:
- Set the OS type option to Linux.
- Set the VM generation option to Gen1.
-
For the Storage blob, browse to the storage account and container that you created, and select the VHD file that you uploaded.
-
Click Create to create the VM image from the VHD file.
-
-
Deploy the Horizon Cloud Connector appliance by creating the appliance VM from the VM image.
-
In the Azure portal, open the VM image that you created in the previous step. Click Create VM.
-
Specify the following settings:
- Enter a name for the new VM. This will be the hostname of the Horizon Cloud Connector appliance.
- For VM Sizing, see Horizon 8 Pods with First-Generation Horizon Cloud Control Plane - Requirements Checklist - Appropriately Updated at the Service Update of November 2, 2023
-
For the Administrator account, specify
ccadminas the user name. You must create thisccadminuser account in order to allow SSH access to the appliance. -
For SSH Access, specify the SSH Public Key authentication method.
Note: Both SSH Public Key and Password authentication methods are supported. However, SSH Public Key provides stronger security and is the preferred method.
-
For Firewall settings, configure the following ports:
- Port 443 for HTTPS
- Port 22 for SSH If you intend to configure a firewall and proxy server for the appliance, you must also configure the appliance to allow certain public URLs. For more information, see First-Gen Tenants - DNS, Ports, and Protocols Requirements When Using Horizon Cloud Connector and a Horizon Pod.
-
For Network settings, specify a public IP Address allocation if you need to allow access to appliance over a public network. Also, specify the public inbound ports for HTTPS and SSH.
-
Navigate to VM Properties and take note of the IP address and FQDN of the appliance VM. You will need this information later to access the browser-based Horizon Cloud Connector configuration portal.
-
-
If your environment requires use of an HTTP proxy server for your virtual appliances to access the Internet, configure proxy-related settings for the appliance, as described in Modifying Proxy Settings for Horizon Cloud Connector.
-
Configure the required certificates, as described in Configure a CA-Signed Certificate for the Horizon Cloud Connector Virtual Appliance.
-
Complete the steps in Enable SSH Access to the Horizon Cloud Connector Using a Command Line Interface.
-
If you want to use a fully qualified domain name (FQDN) for the Horizon Cloud Connector appliance and resolve the host name, create a forward and reverse lookup record in your DNS server that maps that FQDN to the Horizon Cloud Connector virtual appliance's static IP.
What to do next
Continue with the pod onboarding workflow by following the steps in First-Gen Tenants - Verify the Horizon Pod and Virtual Appliance Are Ready to Be Paired with First-Gen Horizon Control Plane. Then proceed to First-Gen Tenants - Complete Pairing the Horizon Pod with First-Gen Horizon Cloud Using the Horizon Cloud Connector Configuration Portal.
Questa pagina è stata utile?