Skip to content

Commit 6be39c3

Browse files
authored
Merge pull request #224389 from ntrogh/als-troubleshooting
[Azure Lab Services] Rethink troubleshooting guidance
2 parents 304fc8d + c4e05bb commit 6be39c3

File tree

6 files changed

+117
-54
lines changed

6 files changed

+117
-54
lines changed

.openpublishing.redirection.azure-productivity.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,11 @@
8989
"source_path": "articles/lab-services/how-to-enable-nested-virtualization-template-vm.md",
9090
"redirect_url": "/azure/lab-services/concept-nested-virtualization-template-vm",
9191
"redirect_document_id": true
92+
},
93+
{
94+
"source_path": "articles/lab-services/troubleshoot.md",
95+
"redirect_url": "/azure/lab-services/troubleshoot-lab-creation",
96+
"redirect_document_id": true
9297
}
9398
]
9499
}

articles/lab-services/TOC.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -211,8 +211,6 @@
211211
href: how-to-enable-shutdown-disconnect.md
212212
- name: View support information
213213
href: lab-creator-support-information.md
214-
- name: Troubleshooting lab creation
215-
href: troubleshoot.md
216214
- name: Connect to VMs in labs (student)
217215
items:
218216
- name: Access labs
@@ -287,8 +285,10 @@
287285
href: reference-powershell-module.md
288286
- name: Troubleshoot & debug
289287
items:
290-
- name: Troubleshoot lab VM Access
291-
href: troubleshoot-access-lab-vm.md
288+
- name: Troubleshoot lab creation
289+
href: troubleshoot-lab-creation.md
290+
- name: Troubleshoot lab VM Access
291+
href: troubleshoot-access-lab-vm.md
292292
- name: Reference
293293
items:
294294
- name: .NET
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
ms.service: lab-services
3+
ms.date: 01/17/2023
4+
ms.topic: include
5+
ms.service: lab-services
6+
---
7+
8+
If you have questions or need help, [create a support request](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview?DMC=troubleshoot), or ask [Azure community support](/answers/topics/azure-labservices.html).

articles/lab-services/troubleshoot-access-lab-vm.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,12 @@ ms.date: 12/05/2022
1414

1515
In this article, you learn about the different approaches for troubleshooting lab VMs. Understand how each approach affects your lab environment and user data on the lab VM. There can be different reasons why you're unable to connect to a lab VM in Azure Lab Services, or why you're stuck to complete a course. For example, the underlying VM is experiencing issues, your organization's firewall settings have changed, or a software change in the lab VM operating system.
1616

17+
## Prerequisites
18+
19+
- To change settings for the lab plan, your Azure account needs the Owner or Contributor Azure Active Directory role on the lab plan. Learn more about the [Azure Lab Services built-in roles](./administrator-guide.md#rbac-roles).
20+
21+
- To redeploy or reset a lab VM, you need to be either the lab user that is assigned to the VM, or your Azure account has the Owner, Contributor, Lab Creator, Lab Contributor, or Lab Operator role. Learn more about the [Azure Lab Services built-in roles](./administrator-guide.md#rbac-roles).
22+
1723
## Symptoms
1824

1925
To use and access a lab VM, you connect to it by using Remote Desktop (RDP) or Secure Shell (SSH). You may experience difficulties to access your lab VM:
@@ -88,9 +94,9 @@ As students use a lab VM to advance through a course, they might get stuck at sp
8894

8995
Learn how to [set up a new lab](./tutorial-setup-lab.md#create-a-lab) and how to [create and manage templates](./how-to-create-manage-template.md).
9096

91-
## Contact us for help
97+
## Advanced troubleshooting
9298

93-
If you have questions or need help, [create a support request](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview?DMC=troubleshoot), or ask [Azure community support](/answers/topics/azure-labservices.html).
99+
[!INCLUDE [contact Azure support](includes/lab-services-contact-azure-support.md)]
94100

95101
## Next steps
96102

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
---
2+
title: Troubleshoot lab creation
3+
titleSuffix: Azure Lab Services
4+
description: Learn how to resolve common issues with creating a lab in Azure Lab Services.
5+
services: lab-services
6+
ms.service: lab-services
7+
author: ntrogh
8+
ms.author: nicktrog
9+
ms.topic: troubleshooting
10+
ms.date: 01/19/2023
11+
---
12+
13+
# Troubleshoot lab creation in Azure Lab Services
14+
15+
In this article, you learn how to resolve common issues with creating a lab in Azure Lab Services. The options that are available to a lab creator for creating a lab on a lab plan depend on the lab plan configuration settings. For example, in the lab plan you can specify which virtual machine images or sizes are available.
16+
17+
## Prerequisites
18+
19+
- To change settings for the lab plan, your Azure account needs the Owner or Contributor Azure Active Directory role on the lab plan. Learn more about the [Azure Lab Services built-in roles](./administrator-guide.md#rbac-roles).
20+
21+
## Virtual machine image is not available
22+
23+
On the lab plan, you can configure the list of available VM images for creating a lab:
24+
25+
1. Select VM images from the Azure Marketplace
26+
1. Select custom VM images from an Azure compute gallery
27+
28+
Verify the following potential causes for a VM image not to be available.
29+
30+
### Virtual machine image is not enabled
31+
32+
In the lab plan configuration, you can enable or disable specific VM images for both Marketplace images and Azure Compute Gallery images. To enable images, see [how to specify Azure Marketplace images](specify-marketplace-images.md) or [how to enable image in an Azure compute gallery](./how-to-attach-detach-shared-image-gallery.md#enable-and-disable-images).
33+
34+
### Azure compute gallery is not connected to the lab plan
35+
36+
To use custom VM images, you have to connect an Azure compute gallery to your lab plan. [Verify if the compute gallery is attached to the lab plan](./how-to-attach-detach-shared-image-gallery.md), or [save a custom image to your compute gallery](./approaches-for-custom-image-creation.md).
37+
38+
### Virtual machine image is not in the same location as the lab plan
39+
40+
To use a custom VM image from a compute gallery, the image has to be replicated in the same location as the lab plan. You can configure replication in the compute gallery. Learn more about how to [store and share images in an Azure compute gallery](/azure/virtual-machines/shared-image-galleries).
41+
42+
### Virtual machine image size is too large or uses multiple disks
43+
44+
Azure Lab Services doesn't support VM image sizes that are larger than 127 GB, or images with multiple disks.
45+
46+
## Virtual machine size is not available
47+
48+
On the lab plan, you can configure which VM sizes are available for creating a lab. In addition, your Azure subscription has a quota for the number of CPU or GPU cores that are available.
49+
50+
Verify the following potential causes for a VM size not to be available.
51+
52+
### VM size is restricted on the lab plan
53+
54+
On the lab plan, you can set a policy to restrict which VM SKU sizes are available for creating labs. For example, you can prevent labs to use GPU-powered virtual machines. Learn how you can [configure VM size restrictions for creating labs](./how-to-use-restrict-allowed-virtual-machine-sku-sizes-policy.md).
55+
56+
### Quota limit is reached
57+
58+
Your Azure subscription has limits (quota) on the number of cores you use. The quota is based on specific VM size and Azure region. To learn more about [capacity limits in Azure Lab Services](./capacity-limits.md).
59+
60+
If you've reached the limit of VM cores of a specific VM size, or if the quota is granted for a different region than the region of the lab plan, the VM size isn't available for creating labs.
61+
62+
[Determine your current VM core usage and the quota](./how-to-determine-your-quota-usage.md) for your Azure subscription.
63+
64+
Learn how you can [request a VM core limit increase](capacity-limits.md#request-a-limit-increase).
65+
66+
>[!TIP]
67+
> You can also run a script to query for lab quotas across all your regions. For more information, see the [PowerShell Quota script](https://aka.ms/azlabs/scripts/quota-powershell).
68+
69+
## Azure region or location is not available
70+
71+
When you create a lab, you need to select an Azure region where the lab will be hosted. On the lab plan, you can configure which Azure regions are available for creating labs.
72+
73+
Verify the following potential causes for an Azure region not to be available.
74+
75+
### Azure region is not enabled on the lab plan
76+
77+
On the lab plan, you can enable one or multiple regions for creating labs. Learn how you can [configure Azure regions for creating labs](./create-and-configure-labs-admin.md).
78+
79+
### Lab plan and lab are in a different region than the virtual network
80+
81+
When your lab plan uses advanced networking, the lab plan and all labs must be in the same region as the virtual network. For more information, see [Use Azure Lab Services advanced networking](how-to-connect-vnet-injection.md).
82+
83+
## Advanced troubleshooting
84+
85+
[!INCLUDE [contact Azure support](includes/lab-services-contact-azure-support.md)]
86+
87+
## Next steps
88+
89+
For more information about setting up and managing labs, see:
90+
91+
- [Manage lab plans](how-to-manage-lab-plans.md)
92+
- [Lab setup guide](setup-guide.md)

articles/lab-services/troubleshoot.md

Lines changed: 0 additions & 48 deletions
This file was deleted.

0 commit comments

Comments
 (0)