Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-06 16:49:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update LAB_05-Implement_Intersite_Connectivity.md

Browse Source
This commit is contained in:
staleycyn 2024-02-11 06:23:05 -08:00 committed by GitHub
parent 51863b4559
commit 8ba5034ebd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md
View File

@ -196,14 +196,11 @@ In this task, you create a virtual network peering to enable communications betw
1. Switch to the **ManufacturingVnet** and verify the **ManufacturingVnet-to-CoreServicesVnet** peering is listed. Ensure the **Peering status** is **Connected**. You may need to **Refresh** the page. 1. Switch to the **ManufacturingVnet** and verify the **ManufacturingVnet-to-CoreServicesVnet** peering is listed. Ensure the **Peering status** is **Connected**. You may need to **Refresh** the page.
## Task 5: Use Azure PowerShell to test the connection between virtual machines ## Task 5: Use Azure PowerShell to test the connection between virtual machines
In this task, you retest the connection between the virtual machines in different virtual networks. In this task, you retest the connection between the virtual machines in different virtual networks.
>**Note:** You can use Network Watcher as you did in Task 3. Or for something different try Azure PowerShell.
### Verify the private IP address of the CoreServicesVM ### Verify the private IP address of the CoreServicesVM
1. From the Azure portal, search for and select the `CoreServicesVM` virtual machine. 1. From the Azure portal, search for and select the `CoreServicesVM` virtual machine.
@ -212,6 +209,8 @@ In this task, you retest the connection between the virtual machines in differen
### Test the connection to the CoreServicesVM from the **ManufacturingVM**. ### Test the connection to the CoreServicesVM from the **ManufacturingVM**.
>**Did you know?** There are many ways to check connections. In this task, you use **Run command**. You could also continue to use Network Watcher. Or you could use a [Remote Desktop Connection](https://learn.microsoft.com/azure/virtual-machines/windows/connect-rdp#connect-to-the-virtual-machine) to the access the virtual machine. Once connected, use **test-connection**. As you have time, give RDP a try.
1. Switch to the `ManufacturingVM` virtual machine. 1. Switch to the `ManufacturingVM` virtual machine.
1. In the **Operations** blade, select the **Run command** blade. 1. In the **Operations** blade, select the **Run command** blade.
@ -222,6 +221,7 @@ In this task, you retest the connection between the virtual machines in differen
Test-NetConnection <CoreServicesVM private IP address> -port 3389 Test-NetConnection <CoreServicesVM private IP address> -port 3389
``` ```
1. It may take a couple of minutes for the script to time out. The top of the page shows an informational message *Script execution in progress.* 1. It may take a couple of minutes for the script to time out. The top of the page shows an informational message *Script execution in progress.*
1. The test connection should succeed because peering has been configured. Your computer name and remote address in this graphic may be different. 1. The test connection should succeed because peering has been configured. Your computer name and remote address in this graphic may be different.