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/configure-github-enterprise-server.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ GitHub Enterprise Server requires a valid license key. You can sign up for a [tr
17
17
18
18
## Install GitHub Enterprise Server on VMware
19
19
20
-
1. Download [the current release of GitHub Enterprise Server](https://enterprise.github.com/releases/2.19.0/download) for VMware ESXi/vSphere (OVA) and [deploy the OVA template](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-virtual-machine-administration-guide-8-0/deploying-ovf-templatesvsphere-vm-admin/deploy-an-ovf-template-flex-and-h5vsphere-vm-admin.html) you downloaded.
20
+
1. Download [the current release of GitHub Enterprise Server](https://enterprise.github.com/releases/2.19.0/download) for VMware ESXi/vSphere (OVA) and [deploy the OVA template](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-virtual-machine-administration-guide-8-0.html) you downloaded.
21
21
22
22
:::image type="content" source="media/github-enterprise-server/github-options.png" alt-text="Screenshot showing the GitHub Enterprise Server on VMware installation options.":::
Copy file name to clipboardExpand all lines: articles/azure-vmware/install-vmware-hcx.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ Use the following steps to download the VMware HCX Connector OVA file, and then
93
93
1. Under **Administration** > **System Updates**, select **Request Download Link**. If the box is greyed, wait a few seconds for it to generate a link.
94
94
95
95
1. Either download or receive a link for the VMware HCX Connector OVA file you deploy on your local vCenter Server.
96
-
1. In your on-premises vCenter Server, select an [OVF template](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-virtual-machine-administration-guide-8-0/deploying-ovf-templatesvsphere-vm-admin/deploy-an-ovf-template-flex-and-h5vsphere-vm-admin.html) to deploy the VMware HCX Connector to your on-premises vSphere cluster.
96
+
1. In your on-premises vCenter Server, select an [OVF template](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-virtual-machine-administration-guide-8-0.html) to deploy the VMware HCX Connector to your on-premises vSphere cluster.
97
97
1. Navigate to and select the OVA file that you downloaded and then select **Open**.
98
98
99
99
:::image type="content" source="media/tutorial-vmware-hcx/select-ovf-template.png" alt-text="Screenshot of browsing to an OVF template." lightbox="media/tutorial-vmware-hcx/select-ovf-template.png":::
Copy file name to clipboardExpand all lines: articles/azure-vmware/move-azure-vmware-solution-across-regions.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ You can move Azure VMware Solution resources to a different region for several r
18
18
19
19
This article helps you plan and migrate Azure VMware Solution from one Azure region to another, such as Azure region A to Azure region B.
20
20
21
-
The diagram shows the recommended ExpressRoute connectivity between the two Azure VMware Solution environments. An HCX site pairing and service mesh are created between the two environments. The HCX migration traffic and Layer-2 extension moves (depicted by the purple line) between the two environments. For VMware recommended HCX planning, see [Planning an HCX Migration](https://www.vmware.com/docs/vmware-cloud-planning-an-hcx-migration).
21
+
The diagram shows the recommended ExpressRoute connectivity between the two Azure VMware Solution environments. An HCX site pairing and service mesh are created between the two environments. The HCX migration traffic and Layer-2 extension moves (depicted by the purple line) between the two environments. For VMware recommended HCX planning, see [Planning an HCX Migration](https://docs.vmware.com/en/VMware-HCX/index.html).
22
22
23
23
:::image type="content" source="media/move-across-regions/move-ea-csp-across-regions-2.png" alt-text="Diagram showing ExpressRoute Global Reach communication between the source and target Azure VMware Solution environments." border="false" lightbox="media/move-across-regions/move-ea-csp-across-regions-2.png":::
24
24
@@ -56,7 +56,7 @@ The following steps show how to prepare your Azure VMware Solution private cloud
56
56
57
57
1.[Export the contents of an inventory list view to a CSV file](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vcenter-and-host-management-8-0/using-the-vsphere-client-host-management/working-with-the-vsphere-client-inventory-host-management.html#GUID-C0E8DD52-677E-464F-A3EA-044EE20B7B92-en).
58
58
59
-
1.[Sort workloads into migration groups (migration wave)](https://www.vmware.com/docs/vmware-cloud-planning-an-hcx-migration).
59
+
1.[Sort workloads into migration groups (migration wave)](https://docs.vmware.com/en/VMware-HCX/index.html).
60
60
61
61
62
62
### Deploy the target environment
@@ -281,7 +281,7 @@ In this step, use VMware HCX to migrate the VMs from the source to the target. Y
281
281
282
282
Besides vMotion, other methods, like Bulk and Cold vMotion, are also recommended. Learn more about:
283
283
284
-
-[Plan an HCX Migration](https://www.vmware.com/docs/vmware-cloud-planning-an-hcx-migration)
284
+
-[Plan an HCX Migration](https://docs.vmware.com/en/VMware-HCX/index.html)
285
285
286
286
-[Migrate Virtual Machines with HCX](https://docs.vmware.com/en/VMware-HCX/services/user-guide/GUID-14D48C15-3D75-485B-850F-C5FCB96B5637.html)
287
287
@@ -294,7 +294,7 @@ In this step, perform a final gateway cutover to terminate the extended networks
294
294
295
295
Before the gateway cutover, verify all migrated workload services and performance. Once application and web service owners accept the performance (except for any latency issues), you can continue with the gateway cutover. Once the cutover is completed, you need to modify the public DNS A and PTR records.
296
296
297
-
For VMware recommendations, see [Cutover of extended networks](https://www.vmware.com/docs/vmware-cloud-planning-an-hcx-migration).
297
+
For VMware recommendations, see [Cutover of extended networks](https://docs.vmware.com/en/VMware-HCX/index.html).
0 commit comments