Skip to content

Commit 1505215

Browse files
Freshness in progress.
1 parent 2af12a3 commit 1505215

6 files changed

+42
-42
lines changed

articles/lab-services/class-type-networking-gns3.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Set up a GNS3 networking lab
33
titleSuffix: Azure Lab Services
4-
description: Learn how to set up a lab using Azure Lab Services to teach networking with GNS3. Emulate, configure, test, and toubleshoot networks using GNS3.
4+
description: Learn how to set up a lab using Azure Lab Services to teach networking with GNS3. Emulate, configure, test, and troubleshoot networks using GNS3.
55
services: lab-services
66
ms.service: lab-services
7-
author: ntrogh
8-
ms.author: nicktrog
7+
author: RoseHJM
8+
ms.author: rosemalcolm
99
ms.topic: how-to
1010
ms.date: 03/06/2024
1111
#customer intent: As an instructor, I want to create lab virtual machines with GNS3 so that students can start to learn about networking with GNS3 in a standard configuration.
@@ -49,42 +49,42 @@ To configure the template VM, complete the following tasks:
4949

5050
### Prepare template machine for nested virtualization
5151

52-
To prepare the template virtual machine for nested virtualization, follow the detailed steps in [enable nested virtualization](how-to-enable-nested-virtualization-template-vm.md).
52+
To prepare the template virtual machine for nested virtualization, follow the detailed steps in [Enable Nested Virtualization](how-to-enable-nested-virtualization-template-vm-using-script.md).
5353

54-
If you created a lab template VM with a non-admin account, add that account to the **Hyper-V Administrators** group. For more information about using nested virtualization with a non-admin account, see [these best practices](concept-nested-virtualization-template-vm.md#non-admin-user).
54+
If you create a lab template VM with an account without administrator privileges, add that account to the **Hyper-V Administrators** group. For more information about using nested virtualization with such an account, see [these best practices](concept-nested-virtualization-template-vm.md#non-admin-user).
5555

5656
### Install GNS3
5757

5858
1. Connect to the template VM by using Remote Desktop.
5959

60-
1. To install GNS3 on Windows, follow the detailed instructions on [the GNS3 website]((https://docs.gns3.com/docs/getting-started/installation/windows).
60+
1. To install GNS3 on Windows, follow the detailed instructions on [the GNS3 website](https://docs.gns3.com/docs/getting-started/installation/windows).
6161

62-
1. Make sure to select **GNS3 VM** in the **Choose Components** page:
62+
1. Make sure to select **GNS3 VM** in the **Choose Components** page:
6363

64-
:::image type="content" source="./media/class-type-networking-gns3/gns3-select-vm.png" alt-text="Screenshot that shows the Choose Components page in the GNS3 installation wizard, with the GNS3 VM option selected.":::
64+
:::image type="content" source="./media/class-type-networking-gns3/gns3-select-vm.png" alt-text="Screenshot that shows the Choose Components page in the GNS3 installation wizard, with the GNS3 VM option selected.":::
6565

66-
1. On the **GNS3 VM** page, select the **Hyper-V** option:
66+
1. On the **GNS3 VM** page, select the **Hyper-V** option:
6767

68-
:::image type="content" source="./media/class-type-networking-gns3/gns3-vm-hyper-v.png" alt-text="Screenshot that shows the GNS3 VM page in the GNS3 installation wizard, with the Hyper-V option selected.":::
68+
:::image type="content" source="./media/class-type-networking-gns3/gns3-vm-hyper-v.png" alt-text="Screenshot that shows the GNS3 VM page in the GNS3 installation wizard, with the Hyper-V option selected.":::
6969

70-
When you select the Hyper-V option, the installer downloads the PowerShell script and VHD files to create the GNS3 VM in the Hyper-V manager.
70+
When you select the Hyper-V option, the installer downloads the PowerShell script and VHD files to create the GNS3 VM in the Hyper-V manager.
7171

72-
1. Continue the installation with the default values.
72+
1. Continue the installation with the default values.
7373

7474
> [!IMPORTANT]
7575
> After the setup completes, don't start GNS3.
7676
7777
### Create GNS3 VM
7878

79-
When the setup finishes, a zip file `GNS3.VM.Hyper-V.2.2.x.zip` is downloaded to the same folder as the installation file. The zip file contains the virtual disks and the PowerShell script to create the Hyper-V virtual machine.
79+
When the setup finishes, you see a zip file *GNS3.VM.Hyper-V.2.2.x.zip* in the same folder as the installation file. The zip file contains the virtual disks and the PowerShell script to create the Hyper-V virtual machine.
8080

8181
To create the GNS 3 VM:
8282

8383
1. Connect to the template VM by using Remote Desktop.
8484

85-
1. Extract all files in the `GNS3.VM.Hyper-V.2.2.17.zip` file. If the template VM has a non-admin account for lab users, extract the files in a location accessible to the non-admin account.
85+
1. Extract all files in the *GNS3.VM.Hyper-V.2.2.17.zip* file. If the template VM has a non-admin account for lab users, extract the files in a location accessible to the non-admin account.
8686

87-
1. Right-select the `create-vm.ps1` PowerShell script, and then select **Run with PowerShell**.
87+
1. Right-select the *create-vm.ps1* PowerShell script, and then select **Run with PowerShell**.
8888

8989
1. When the `Execution Policy Change` request shows, enter **Y** to execute the script.
9090

@@ -94,11 +94,11 @@ To create the GNS 3 VM:
9494

9595
### Configure GNS3 to use Hyper-V VM
9696

97-
Now that you installed GNS3, and added the GNS3 VM, configure GNS 3 to use the Hyper-V virtual machine.
97+
After you install GNS3 and add the GNS3 VM, configure GNS 3 to use the Hyper-V virtual machine.
9898

9999
1. Connect to the template VM by using Remote Desktop.
100100

101-
1. Start GNS3. The [GNS3 Setup wizard](https://docs.gns3.com/docs/getting-started/setup-wizard-gns3-vm#local-gns3-vm-setup-wizard) starts automatically.
101+
1. Start GNS3. The [GNS3 Setup wizard](https://docs.gns3.com/docs/getting-started/setup-wizard-gns3-vm#local-gns3-vm-setup-wizard) opens.
102102

103103
1. Select the **Run appliances from a virtual machine** option, and select **Next**.
104104

@@ -120,7 +120,7 @@ Now that you installed GNS3, and added the GNS3 VM, configure GNS 3 to use the H
120120

121121
Next, you can add appliances for the class. To install appliances from the GNS3 marketplace, follow the detailed steps from [the GNS3 documentation](https://docs.gns3.com/docs/using-gns3/beginners/install-from-marketplace).
122122

123-
If the template VM has a non-admin account for lab users, install the appliances to a location accessible to the non-admin account. Optionally, you can set the preferences for the admin and non-admin user to look for appliances and projects in a location accessible by both users.
123+
If the template VM has a non-admin account for lab users, install the appliances to a location accessible to the account. Optionally, you can set the preferences for the admin and non-admin user to look for appliances and projects in a location accessible by both users.
124124

125125
### Prepare to publish template
126126

@@ -130,8 +130,8 @@ Now that you set up the template virtual machine, verify the following key point
130130
- Stop GNS3. Publishing while GNS3 is running can lead to unintended side effects.
131131
- Clean up any installation files or other unnecessary files from the template VM.
132132

133-
>[!IMPORTANT]
134-
>Publishing while the VM is still running, corrupts the template virtual machine and creates unusable lab virtual machines.
133+
> [!IMPORTANT]
134+
> Publishing while the VM is still running corrupts the template virtual machine and creates unusable lab virtual machines.
135135
136136
## Estimate cost
137137

articles/lab-services/connect-virtual-machine-windows-rdp.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,11 @@ titleSuffix: Azure Lab Services
44
description: Learn how to connect using remote desktop (RDP) from Windows to a virtual machine in Azure Lab Services.
55
services: lab-services
66
ms.service: lab-services
7-
author: ntrogh
8-
ms.author: nicktrog
7+
author: RoseHJM
8+
ms.author: rosemalcolm
99
ms.topic: how-to
10-
ms.date: 02/17/2023
10+
ms.date: 03/06/2024
11+
#customer intent: As a learner, I want to connect to virtual machines in a lab by using RDP in order to use the lab resources.
1112
---
1213

1314
# Connect to a VM using Remote Desktop Protocol on Windows
@@ -26,11 +27,11 @@ To connect to a lab VM in Azure Lab Services:
2627

2728
1. On the tile for your VM, select the **Connect** icon.
2829

29-
To connect to a lab VM, the vm must be running. Learn how you can [start a VM](how-to-use-lab.md#start-or-stop-the-vm).
30+
To connect to a lab VM, the virtual machine must be running. Learn how you can [start a VM](how-to-use-lab.md#start-or-stop-the-vm).
3031

3132
:::image type="content" source="./media/connect-virtual-machine-windows-rdp/connect-vm.png" alt-text="Screenshot of My virtual machines page for Azure Lab Services, highlighting the connect button on the VM tile.":::
3233

33-
1. If you’re connecting to a Linux VM, select the **Connect via RDP** option.
34+
1. To connect to a Linux VM, select the **Connect via RDP** option.
3435

3536
:::image type="content" source="./media/connect-virtual-machine-windows-rdp/student-vm-connect-options.png" alt-text="Screenshot that shows VM tile for student, highlighting the connect button and showing the SSH and RDP connection options.":::
3637

articles/lab-services/how-to-access-lab-virtual-machine.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ titleSuffix: Azure Lab Services
44
description: Learn how to access a lab in Azure Lab Services. Use Teams, Canvas, or the Lab Services website to view, start, stop, and connect to a lab.
55
services: lab-services
66
ms.service: lab-services
7-
author: ntrogh
8-
ms.author: nicktrog
7+
author: RoseHJM
8+
ms.author: rosemalcolm
99
ms.topic: how-to
1010
ms.date: 03/06/2024
1111
#customer intent: As a student, I want to connect to a virtual machine in Azure Lab Services to use the learning resources.

articles/lab-services/how-to-request-capacity-increase.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,25 @@
11
---
2-
title: Request a core limit increase
2+
title: Request a core limit increase
33
titleSuffix: Azure Lab Services
44
description: Learn how to request a core limit (quota) increase to expand capacity for your labs in Azure Lab Services.
55
services: lab-services
66
ms.service: lab-services
77
ms.topic: how-to
8-
ms.author: nicktrog
9-
author: ntrogh
10-
ms.date: 03/03/2023
8+
ms.author: rosemalcolm
9+
author: RoseHJM
10+
ms.date: 03/06/2024
11+
#customer intent: As a lab administrator, I want more VM cores available for my subscription so that I can support more students.
1112
---
1213

13-
<!-- As a lab administrator, I want more VM cores available for my subscription so that I can support more students. -->
14-
1514
# Request a core limit increase
1615

1716
This article describes how to collect the information and how to submit a support request for increasing the number of cores for Azure Lab Services in your Azure subscription.
1817

19-
When you reach the cores limit for your subscription, you can request a core limit increase (sometimes called an increase in capacity, or a quota increase) to continue using Azure Lab Services. The request process allows the Azure Lab Services team to ensure that your subscription isn't involved in any cases of fraud or unintentional, sudden large-scale deployments.
18+
When you reach the cores limit for your subscription, you can request a core limit increase (sometimes called an increase in capacity, or a quota increase) to continue using Azure Lab Services. The request process allows the Azure Lab Services team to ensure that your subscription isn't involved in any cases of fraud or unintentional, sudden large-scale deployments.
2019

21-
### Prerequisites
20+
## Prerequisites
2221

23-
[!INCLUDE [Create support request](./includes/lab-services-prerequisite-create-support-request.md)]
22+
- [!INCLUDE [Create support request](./includes/lab-services-prerequisite-create-support-request.md)]
2423

2524
## Prepare to submit a request
2625

@@ -112,7 +111,7 @@ You can follow these steps to request a core limit increase:
112111

113112
1. On the **Additional details** tab, select **Enter details** in the **Problem details** section.
114113

115-
:::image type="content" source="./media/how-to-request-capacity-increase/enter-details-link.png" alt-text="Screenshot of the Additional details page with Enter details highlighted.":::
114+
:::image type="content" source="./media/how-to-request-capacity-increase/enter-details-link.png" alt-text="Screenshot of the Additional details page with Enter details highlighted.":::
116115

117116
## Make core limit increase request
118117

@@ -189,7 +188,7 @@ To complete the support request, enter the following information:
189188
1. Select **Next**.
190189

191190
1. On the **Review + create** tab, review the information, and then select **Create**.
192-
191+
193192
## Related content
194193

195194
- For more information about capacity limits, see [Capacity limits in Azure Lab Services](capacity-limits.md).

articles/lab-services/includes/lab-services-prerequisite-create-support-request.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,4 @@ ms.topic: include
66

77
- To create a support request, your Azure account needs the [Owner](/azure/role-based-access-control/built-in-roles#owner), [Contributor](/azure/role-based-access-control/built-in-roles#contributor), or [Support Request Contributor](/azure/role-based-access-control/built-in-roles#support-request-contributor) role at the subscription level.
88

9-
- To verify current quota for a subscription before submitting a support request, your Azure account needs the [Owner](/azure/role-based-access-control/built-in-roles#owner) or [Contributor](/azure/role-based-access-control/built-in-roles#contributor) role at the subscription level.
9+
- To verify current quota for a subscription before you submit a support request, your Azure account needs the [Owner](/azure/role-based-access-control/built-in-roles#owner) or [Contributor](/azure/role-based-access-control/built-in-roles#contributor) role at the subscription level.

articles/lab-services/includes/lab-services-request-capacity-best-practices.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ ms.author: nicktrog
66
ms.date: 12/01/2022
77
---
88

9-
The time it takes to assign capacity varies depending on the VM size, region, and number of cores requested. You won't have to go through the process of requesting extra capacity often, but to ensure you have the resources you require when you need them, you should:
9+
The time it takes to assign capacity varies depending on the VM size, region, and number of cores requested. You don't need to go through the process of requesting extra capacity often. To ensure you have the resources you require when you need them, you should:
1010

1111
- Request capacity as far in advance as possible.
12-
- If possible, be flexible on the region where you're requesting capacity.
13-
- Recognize that capacity remains assigned for the lifetime of a subscription. When lab plans or labs are deleted, the capacity remains assigned to the subscription.
12+
- Be flexible on the region where you're requesting capacity, if possible.
13+
- Recognize that capacity remains assigned for the lifetime of a subscription. When lab plans or labs are deleted, the capacity remains assigned to the subscription.
1414
- Request extra capacity only if you need more than is already assigned to your subscription.
1515
- Make incremental requests for VM cores rather than making large, bulk requests. Break requests for large numbers of cores into smaller requests for extra flexibility in how those requests are fulfilled.

0 commit comments

Comments
 (0)