'You're not eligible for an Azure free account' when trying to sign up with .edu domain account
Hi Team, I am not sure if this is a suitable place I can raise this however since I was not sure whom to reach I dared to write it here. Apologies in advance. A university student with .edu domain when trying to sign up for Azure for Students account at https://azure.microsoft.com/en-us/free/students/ is prompting with following message although the expectation was that- a 100$ Azure account would be immediately provisioned. However, later when I checked into https://www.microsoftazuresponsorships.com/ with the same login, I could see 100$ balance but without a subscription. Now, I am unable to use this 100$ worth credit. Is there a way to access this offer? Am I missing something here? PS: Until a month before, it was possible for student users in the same .edu.np domain to sign up for an active Azure for Student subscription with 100$ credit. Many thanks for your attention. Thanks, Pradeep Kandel[Resolved] Lab Services Outage: Cannot perform actions on a lab
[Final Update] 3/31 20:00 UTC Hello everyone, We would like to share a final update on the outage in Azure Lab Services. The outage has now been resolved. Thank you so much for your patience throughout the outage. Please read about the details of what happened and what we’re doing as preventative steps for the future in our blog post. The labs that were affected by the outage are now in following two states: The lab was recovered All labs that were recovered should now operate as normal and will no longer be marked as affected by the outage. Please note that if you need to increase the lab capacity (i.e. increase the number of virtual machines in the VM pool) of these labs, you will need to republish the labs first. If you can’t republish but still need to increase lab capacity, please contact us at AzLabsCOVIDSupport@microsoft.com for help. The lab was not recoverable, and needs to be deleted and recreated Unfortunately, some labs affected by the outage were not recoverable. These labs will be marked as not recoverable (see screenshot below), and your users will no longer see the labs’ virtual machines in their 'My virtual machines' view. As much as it pains us to say this, it means loss of data for the users. To recreate these labs, please follow the steps below: Click on a lab that could not be recovered Go to the Users tab of the lab and click the “Export CSV” button to download a CSV file of the users list. The other tabs (Template, Schedule, Settings, etc.) will be read-only in case you need to copy over the info to the new lab In the My labs view, click on the “+ New lab” button, and set up the lab as before Once the lab is created, go to the Users tab. Click on the “Add users” > “Upload CSV” to import the CSV file of users into the new lab. Please note that you need to update the user quota (of hours) in this new lab. Click on the “Invite all” button to send out an email to your lab users with the registration link to your lab. Users will be able to click on the registration link to get access to virtual machines in your new lab. Delete the old lab. We understand that this can potentially be a lot of effort, and we are deeply sorry for the inconvenience this has caused. Please do not hesitate to contact us at AzLabsCOVIDSupport@microsoft.com if there’s anything we can do on our end to help. -Labs Team ------------------------------------------------------------------------------------------------ [Update] 3/26 17:00 UTC We would like to inform you that we are actively working on resolving the issue. How do I know if my lab is impacted in the outage? One or many of your labs would be impacted if you see the following banner when you navigate to labs.azure.com To identify specific impacted labs, navigate to a lab; if you see the following banner on your lab, that means it is impacted. The fastest way to mitigate the issue is to create a new lab. Please feel free to add a comment below if you have problems creating a new lab and/or any other questions. We apologize for the inconvenience and thank you for your patience. ------------------------------------------------------------------------------------------------ [Update] 3/26 02:11 UTC We would like to inform you that we are actively working on resolving the issue. The current mitigation is to create a new lab. Please feel free to add a comment below if you have problems creating a new lab and/or any other questions. We apologize for the inconvenience and thank you for your patience. ------------------------------------------------------------------------------------------------ [Update] 3/25 21:00 UTC As we investigate the issue further, we would like to share that the current mitigation to resolve these errors is to create a new lab. Here is a link to learn more on creating a new lab in lab services. We apologize for the inconvenience and thank you for your patience. ------------------------------------------------------------------------------------------------ Hey everyone, We are currently experiencing issues with certain labs where users are not able to perform specific actions such as start/stop lab virtual machines and/or publish a lab. We would like to inform you that we are actively looking into the issue and will continue providing updates on this post until the problem is resolved. We apologize for the inconvenience and thank you for your patience. - Lab Services team
Azure Lab Services - Planned Outage - April 19, 2024
Hello Everyone, On April 19th, 2024, we will be updating our system between 1:00-10:00 pm UTC. Please expect downtime for most common operations like create/ update/ delete labs, start/stop virtual machines etc. The service will be available after the update. We will provide update on this post once the service update is complete. Thank you for your patience. - Lab Services team.
Internet issues with Nested Virtualization Hyper-V VMs when publishing template
On a number of occassions when we deploy an existing template or publish a template for our Hyper-V classes, the Hyper-V VMs lose the ability to connect to the internet. After some playing around I found that the NetNat service often fails to run which causes the internet to not work through the Nat created on the host VM template. Is anyone else getting this issue? To setup the NAT to allow internet access to the Hyper-V VMs, I run the script provided by MS doco on Azure Lab Services (https://docs.microsoft.com/en-us/azure/lab-services/classroom-labs/how-to-enable-nested-virtualization-template-vm-using-script). I run this on the template before publishing. I'm not sure how the Nat service works but WinNat service isn't visible in the Services.msc gui or if you do a "get-service -Name *" in Powershell. To verify if the NAT service is running, run Get-NetNat and you should see if the Nat Active status is True or False. If it's false, internet won't work for your Hyper-V VMs. To fix it I put a script on the template and get it to run when the user logs into the VM via registry Check_NetNat_Service.ps1 $netnat = Get-NetNat If ($netnat.Active -eq "False") { Start-Service WinNat Write-Host "WinNat Service has been started" -ForegroundColor Green } Else { Write-Host "WinNat Service is already running" -ForegroundColor Cyan } From what I can see. The publishing breaks or causes the NAT service to not run on the deployed VMs. This is a bit annoying to configure as most teachers won't understand how to fix this, so I need to set this up for these types of labs.
Hadoop on Azure labs
Hello- I'm working on installing Hadoop on the Azure lab environment. I have followed these steps:https://kontext.tech/column/hadoop/377/latest-hadoop-321-installation-on-windows-10-step-by-step-guide and am using this template: Windows 10 Pro, Version 1909 Medium|4 cores|7GB RAM I keep getting an error when I try to format the namenode and I can't figure it out. I'm wondering if anyone has had success installing hadoop on Azure lab. This is the error I'm getting 2020-10-13 18:07:46,044 INFO util.GSet: VM type = 64-bit 2020-10-13 18:07:46,046 INFO util.GSet: 0.029999999329447746% max memory 889 MB = 273.1 KB 2020-10-13 18:07:46,046 INFO util.GSet: capacity = 2^15 = 32768 entries 2020-10-13 18:07:46,220 INFO namenode.FSImage: Allocated new BlockPoolId: BP-2025207759-10.140.18.4-1602612466198 2020-10-13 18:07:46,375 WARN namenode.NameNode: Encountered exception during format: ExitCodeException exitCode=-1073741515: at org.apache.hadoop.util.Shell.runCommand(Shell.java:1008) at org.apache.hadoop.util.Shell.run(Shell.java:901) at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:1213) at org.apache.hadoop.util.Shell.execCommand(Shell.java:1307) at org.apache.hadoop.util.Shell.execCommand(Shell.java:1289) at org.apache.hadoop.fs.FileUtil.execCommand(FileUtil.java:1350) at org.apache.hadoop.fs.FileUtil.execSetPermission(FileUtil.java:1341) at org.apache.hadoop.fs.FileUtil.setPermission(FileUtil.java:1294) at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.clearDirectory(Storage.java:456) at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:591) at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:613) at org.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:188) at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:1206) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1649) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1759) 2020-10-13 18:07:46,386 ERROR namenode.NameNode: Failed to start namenode. ExitCodeException exitCode=-1073741515: at org.apache.hadoop.util.Shell.runCommand(Shell.java:1008) at org.apache.hadoop.util.Shell.run(Shell.java:901) at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:1213) at org.apache.hadoop.util.Shell.execCommand(Shell.java:1307) at org.apache.hadoop.util.Shell.execCommand(Shell.java:1289) at org.apache.hadoop.fs.FileUtil.execCommand(FileUtil.java:1350) at org.apache.hadoop.fs.FileUtil.execSetPermission(FileUtil.java:1341) at org.apache.hadoop.fs.FileUtil.setPermission(FileUtil.java:1294) at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.clearDirectory(Storage.java:456) at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:591) at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:613) at org.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:188) at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:1206) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1649) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1759) 2020-10-13 18:07:46,406 INFO util.ExitUtil: Exiting with status 1: ExitCodeException exitCode=-1073741515: 2020-10-13 18:07:46,418 INFO namenode.NameNode: SHUTDOWN_MSG: /************************************************************ SHUTDOWN_MSG: Shutting down NameNode at ML-RefVm-145321/10.140.18.4 ************************************************************/VMs are stuck in starting/stopping state
Hi All, A small number of customers, when using a lab plan, are experiencing issues with virtual machines getting stuck in starting state. We are actively working on resolving the issue. If you hit the issue, please proceed to open a support ticket for it. Thank You, Fawad Khan Microsoft
Getting an error when trying to increase lab capacity?
One goal but two issues. I've created a template and published it with a VM pool of three VMs in order to test the Template before finally publishing it for the class. I am now ready to do the final publication, but I am unable to increase the capacity of the lab to 25 VMs, or even increase it by 1. I get the error message "An error occurred while updating the lab capacity." My second thought was to export it to the Azure Compute Gallery, and then just delete the old lab and create a new one with the appropriate number of VMs, but after selecting the Export option and waiting a day, I don't see where I can select the Template. It doesn't show up as an option when creating a new lab.
