You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/azure-vmware-solution-horizon.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Deploy Horizon on Azure VMware Solution
3
3
description: Learn how to deploy VMware Horizon on Azure VMware Solution.
4
4
ms.topic: how-to
5
-
ms.date: 09/29/2020
5
+
ms.date: 04/11/2022
6
6
---
7
7
8
8
@@ -29,12 +29,12 @@ Horizon 2006 and later versions on the Horizon 8 release line supports both on-p
29
29
30
30
## Deploy Horizon in a hybrid cloud
31
31
32
-
You can deploy Horizon in a hybrid cloud environment by using Horizon Cloud Pod Architecture (CPA) to interconnect on-premises and Azure datacenters. CPA scales up your deployment, builds a hybrid cloud, and provides redundancy for Business Continuity and Disaster Recovery. For more information, see [Expanding Existing Horizon 7 Environments](https://techzone.vmware.com/resource/business-continuity-vmware-horizon#_Toc41650874).
32
+
You can deploy Horizon in a hybrid cloud environment by using Horizon Cloud Pod Architecture (CPA) to interconnect on-premises and Azure data centers. CPA scales up your deployment, builds a hybrid cloud, and provides redundancy for Business Continuity and Disaster Recovery. For more information, see [Expanding Existing Horizon 7 Environments](https://techzone.vmware.com/resource/business-continuity-vmware-horizon#_Toc41650874).
33
33
34
34
>[!IMPORTANT]
35
35
>CPA is not a stretched deployment; each Horizon pod is distinct, and all Connection Servers that belong to each of the individual pods are required to be located in a single location and run on the same broadcast domain from a network perspective.
36
36
37
-
Like on-premises or private datacenter, you can deploy Horizon in an Azure VMware Solution private cloud. We'll discuss key differences in deploying Horizon on-premises and Azure VMware Solution in the following sections.
37
+
Like on-premises or private data centers, you can deploy Horizon in an Azure VMware Solution private cloud. We'll discuss key differences in deploying Horizon on-premises and Azure VMware Solution in the following sections.
38
38
39
39
The _Azure private cloud_ is conceptually the same as the _VMware SDDC_, a term typically used in Horizon documentation. The rest of this document uses both terms interchangeably.
40
40
@@ -43,11 +43,11 @@ The Horizon Cloud Connector is required for Horizon on Azure VMware Solution to
43
43
>[!IMPORTANT]
44
44
>Horizon Control Plane support for Horizon on Azure VMware Solution is not yet available. Be sure to download the VHD version of Horizon Cloud Connector.
45
45
46
-
## vCenter Cloud Admin role
46
+
## vCenter Server Cloud Admin role
47
47
48
-
Since Azure VMware Solution is an SDDC service and Azure manages the lifecycle of the SDDC on Azure VMware Solution, the vCenter permission model on Azure VMware Solution is limited by design.
48
+
Since Azure VMware Solution is an SDDC service and Azure manages the lifecycle of the SDDC on Azure VMware Solution, the vCenter Server permission model on Azure VMware Solution is limited by design.
49
49
50
-
Customers are required to use the Cloud Admin role, which has a limited set of vCenter permissions. The Horizon product was modified to work with the Cloud Admin role on Azure VMware Solution, specifically:
50
+
Customers are required to use the Cloud Admin role, which has a limited set of vCenter Server permissions. The Horizon product was modified to work with the Cloud Admin role on Azure VMware Solution, specifically:
51
51
52
52
* Instant clone provisioning was modified to run on Azure VMware Solution.
53
53
@@ -63,9 +63,9 @@ Customers are required to use the Cloud Admin role, which has a limited set of v
63
63
64
64
## Horizon on Azure VMware Solution deployment architecture
65
65
66
-
A typical Horizon architecture design uses a pod and block strategy. A block is a single vCenter, while multiple blocks combined make a pod. A Horizon pod is a unit of organization determined by Horizon scalability limits. Each Horizon pod has a separate management portal, and so a standard design practice is to minimize the number of pods.
66
+
A typical Horizon architecture design uses a pod and block strategy. A block is a single vCenter Server, while multiple blocks combined make a pod. A Horizon pod is a unit of organization determined by Horizon scalability limits. Each Horizon pod has a separate management portal, and so a standard design practice is to minimize the number of pods.
67
67
68
-
Every cloud has its own network connectivity scheme. Combined with VMware SDDC networking / NSX Edge, the Azure VMware Solution network connectivity presents unique requirements for deploying Horizon that is different from on-premises.
68
+
Every cloud has its own network connectivity scheme. Combined with VMware SDDC networking / NSX-T Data Center, the Azure VMware Solution network connectivity presents unique requirements for deploying Horizon that is different from on-premises.
69
69
70
70
Each Azure private cloud and SDDC can handle 4,000 desktop or application sessions, assuming:
71
71
@@ -106,27 +106,27 @@ You connect your AD domain controller in Azure Virtual Network with your on-prem
106
106
107
107
A variation on the basic example might be to support connectivity for on-premises resources. For example, users access desktops and generate virtual desktop application traffic or connect to an on-premises Horizon pod using CPA.
108
108
109
-
The diagram shows how to support connectivity for on-premises resources. To connect to your corporate network to the Azure Virtual Network, you'll need an ExpressRoute circuit. You'll also need to connect your corporate network with each of the private cloud and SDDCs using ExpressRoute Global Reach. It allows the connectivity from the SDDC to the ExpressRoute circuit and on-premises resources.
109
+
The diagram shows how to support connectivity for on-premises resources. To connect to your corporate network to the Azure Virtual Network, you'll need an ExpressRoute circuit. You'll also need to connect your corporate network with each of the private cloud and SDDCs using ExpressRoute Global Reach. It allows the connectivity from the SDDC to the ExpressRoute circuit and on-premises resources.
110
110
111
111
:::image type="content" source="media/vmware-horizon/connect-corporate-network-azure-virtual-network.png" alt-text="Diagram showing the connection of a corporate network to an Azure Virtual Network." border="false":::
112
112
113
113
### Multiple Horizon pods on Azure VMware Solution across multiple regions
114
114
115
-
Another scenario is scaling Horizon across multiple pods. In this scenario, you deploy two Horizon pods in two different regions and federate them using CPA. It's similar to the network configuration in the previous example, but with some additional cross-regional links.
115
+
Another scenario is scaling Horizon across multiple pods. In this scenario, you deploy two Horizon pods in two different regions and federate them using CPA. It's similar to the network configuration in the previous example, but with some additional cross-regional links.
116
116
117
117
You'll connect the Azure Virtual Network in each region to the private clouds/SDDCs in the other region. It allows Horizon connection servers part of the CPA federation to connect to all desktops under management. Adding extra private clouds/SDDCs to this configuration would allow you to scale to 24,000 sessions overall.
118
118
119
-
The same principles apply if you deploy two Horizon pods in the same region. Make sure to deploy the second Horizon pod in a *separate Azure Virtual Network*. Just like the single pod example, you can connect your corporate network and on-premises pod to this multi-pod/region example using ExpressRoute and Global Reach.
119
+
The same principles apply if you deploy two Horizon pods in the same region. Make sure to deploy the second Horizon pod in a *separate Azure Virtual Network*. Just like the single pod example, you can connect your corporate network and on-premises pod to this multi-pod/region example using ExpressRoute and Global Reach.
120
120
121
121
:::image type="content" source="media/vmware-horizon/multiple-horizon-pod-azure-vmware-solution.png" alt-text=" Diagram showing multiple Horizon pods on Azure VMware Solution across multiple regions." border="false":::
122
122
123
123
## Size Azure VMware Solution hosts for Horizon deployments
124
124
125
-
Horizon's sizing methodology on a host running in Azure VMware Solution is simpler than Horizon on-premises. That's because the Azure VMware Solution host is standardized. Exact host sizing helps determine the number of hosts needed to support your VDI requirements. It's central to determining the cost-per-desktop.
125
+
Horizon's sizing methodology on a host running in Azure VMware Solution is simpler than Horizon on-premises. That's because the Azure VMware Solution host is standardized. Exact host sizing helps determine the number of hosts needed to support your VDI requirements. It's central to determining the cost-per-desktop.
126
126
127
127
### Sizing tables
128
128
129
-
Specific vCPU/vRAM requirements for Horizon virtual desktops depend on the customer’s specific workload profile. Work with your MSFT and VMware sales team to help determine your vCPU/vRAM requirements for your virtual desktops.
129
+
Specific vCPU/vRAM requirements for Horizon virtual desktops depend on the customer’s specific workload profile. Work with your MSFT and VMware sales team to help determine your vCPU/vRAM requirements for your virtual desktops.
Copy file name to clipboardExpand all lines: articles/azure-vmware/bitnami-appliances-deployment.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Deploy Bitnami virtual appliances
3
3
description: Learn about the virtual appliances packed by Bitnami to deploy in your Azure VMware Solution private cloud.
4
4
ms.topic: how-to
5
-
ms.date: 09/15/2021
5
+
ms.date: 04/11/2022
6
6
7
7
---
8
8
@@ -54,11 +54,11 @@ In this article, you'll learn how to install and configure the following virtual
54
54
55
55
56
56
57
-
## Step 2. Access the local vCenter of your private cloud
57
+
## Step 2. Access the local vCenter Server of your private cloud
58
58
59
59
1. Sign in to the [Azure portal](https://portal.azure.com), select your private cloud, and then **Manage** > **Identity**.
60
60
61
-
1. Copy the vCenter URL, username, and password. You'll use them to access your virtual machine (VM).
61
+
1. Copy the vCenter Server URL, username, and password. You'll use them to access your virtual machine (VM).
62
62
63
63
1. Select **Overview**, select the VM, and then connect to it through RDP. If you need help with connecting, see [connect to a virtual machine](../virtual-machines/windows/connect-logon.md#connect-to-the-virtual-machine) for details.
64
64
@@ -71,7 +71,7 @@ In this article, you'll learn how to install and configure the following virtual
71
71
72
72
73
73
74
-
## Step 3. Install the Bitnami OVA/OVF file in vCenter
74
+
## Step 3. Install the Bitnami OVA/OVF file in vCenter Server
75
75
76
76
1. Right-click the cluster that you want to install the LAMP virtual appliance and select **Deploy OVF Template**.
77
77
@@ -97,7 +97,7 @@ In this article, you'll learn how to install and configure the following virtual
97
97
98
98
1. After the installation finishes, under **Actions**, select **Power on** to turn on the appliance.
99
99
100
-
1. From the vCenter console, select **Launch Web Console** and sign in to the Bitnami virtual appliance. Check the [Bitnami virtual appliance support documentation](https://docs.bitnami.com/vmware-marketplace/faq/get-started/find-credentials/) for the default username and password.
100
+
1. From the vCenter Server console, select **Launch Web Console** and sign in to the Bitnami virtual appliance. Check the [Bitnami virtual appliance support documentation](https://docs.bitnami.com/vmware-marketplace/faq/get-started/find-credentials/) for the default username and password.
101
101
102
102
>[!NOTE]
103
103
>You can change the default password to a more secure one. For more information, see ...
0 commit comments