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/lab-services/classroom-labs/administrator-guide.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,6 +152,9 @@ The location that a classroom lab exists in varies based on the following factor
152
152
153
153
When there is **no** VNet peered and [lab creators are allowed to pick the lab location](https://docs.microsoft.com/azure/lab-services/classroom-labs/allow-lab-creator-pick-lab-location), the locations that can be selected by the lab creator are based on available capacity.
154
154
155
+
> [!NOTE]
156
+
> To help ensure that there is sufficient VM capacity for a region, it's important that you first request capacity through the lab account or when creating the lab.
157
+
155
158
A general rule is to set a resource's region to one that is closest to its users. For classroom labs, this means creating the classroom lab closest to your students. For online courses where students are located all over the world, you need to use your best judgment to create a classroom lab that's centrally located. Or, split a class into multiple classroom labs based on your students' region.
156
159
157
160
### Shared image gallery
@@ -165,7 +168,7 @@ When administrators or lab creators create a classroom lab, they can choose from
165
168
| ---- | ----- | ------ | ------------- |
166
169
| Small| <ul><li>2 Cores</li><li>3.5 GB RAM</li> |[Standard_A2_v2](https://docs.microsoft.com/azure/virtual-machines/av2-series?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json)| This size is best suited for command line, opening web browser, low traffic web servers, small to medium databases. |
167
170
| Medium | <ul><li>4 Cores</li><li>7 GB RAM</li> |[Standard_A4_v2](https://docs.microsoft.com/azure/virtual-machines/av2-series?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json)| This size is best suited for relational databases, in-memory caching, and analytics. |
168
-
| Medium (Nested virtualization) | <ul><li>4 Cores</li><li>16 GB RAM</li></ul> |[Standard_DC4s_v2](https://docs.microsoft.com/azure/virtual-machines/dcv2-series?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json)| This size is best suited for relational databases, in-memory caching, and analytics. This size also supports nested virtualization. |
171
+
| Medium (Nested virtualization) | <ul><li>4 Cores</li><li>16 GB RAM</li></ul> |[Standard_D4s_v3](https://docs.microsoft.com/azure/virtual-machines/dv3-dsv3-series?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json#dsv3-series)| This size is best suited for relational databases, in-memory caching, and analytics. This size also supports nested virtualization. |
169
172
| Large | <ul><li>8 Cores</li><li>32 GB RAM</li></ul> |[Standard_DC8_v2](https://docs.microsoft.com/azure/virtual-machines/dcv2-series?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json)| This size is best suited for applications that need faster CPUs, better local disk performance, large databases, large memory caches. This size also supports nested virtualization. |
170
173
| Small GPU (Visualization) | <ul><li>6 Cores</li><li>56 GB RAM</li> |[Standard_NV6](https://docs.microsoft.com/azure/virtual-machines/nv-series)| This size is best suited for remote visualization, streaming, gaming, encoding using frameworks such as OpenGL and DirectX. |
171
174
| Small GPU (Compute) | <ul><li>6 Cores</li><li>56 GB RAM</li></ul> |[Standard_NC6](https://docs.microsoft.com/azure/virtual-machines/nc-series)|This size is best suited for computer-intensive applications like Artificial Intelligence and Deep Learning. |
@@ -76,6 +76,9 @@ Or, you can choose to follow these manual steps using the template VM:
76
76
77
77
1. Finally, to combine this behavior with the **automatic shutdown on disconnect** setting, you should follow steps in the how-to article: [Enable automatic shutdown of VMs on disconnect](https://docs.microsoft.com/azure/lab-services/classroom-labs/how-to-enable-shutdown-disconnect).
78
78
79
+
> [!WARNING]
80
+
> After configuring this setting using either PowerShell to modify the registry setting directly or manually using the Group Policy editor, you must first restart the VM for the settings to take effect. Also, if you configure the setting using the registry, the Group Policy editor doesn't always refresh to reflect changes to the registry setting; however, the registry setting still takes effect as expected and you will see the RDP session disconnected when idle for the length of time that you've specified.
81
+
79
82
## Remove Windows shutdown command from Start menu
80
83
81
84
Windows **Local Group Policy** settings also allow you to remove the shutdown command from the **Start** menu.
0 commit comments