Task 1: Deploy a pair of Azure VMs running highly available Active Directory domain controllers by using an Azure Resource Manager template

While I'm deploying the template it's failing with below error

can you please check on this..?

Module: M02-Unit 2A

Lab/Demo: Unit 2A

Exercise 01. 03

Task: 01, 02

Step: 00

Description of issue
Instructions are different from Azure portal. Instructions docs needs some updating.

Repro steps:

1. Exercise 1, Task 1, Create a Virtual Machine, Disks, Step 1 -> "Encryption type" from instructions should change to "Key management"
2. Exercise 1, Task 1, Create a Virtual Machine, Networking, Step 2 -> "Address space" from instructions is not in Azure Portal
3. Exercise 1, Task 1, Create a Virtual Machine, Management, Step 1 -> "Boot diagnostics" from instructions is not in Azure Portal
4. Exercise 1, Task 1, Create a Virtual Machine, Management, Step 1 -> "OS guest diagnostics" from instructions is not in Azure Portal
5. Exercise 3, Task 2, Load Balancers, Add backend pool, Step 2 -> Instructions are different from Azure portal.
6. Exercise 3, Task 2, Load Balancers, Inbound rules, Step 3 -> Instructions are different from Azure portal.

Lab

Lab 2a: Implement Linux clustering on Azure VMs

Relevant screenshots

1. Exercise 1, Task 1, Create a Virtual Machine, Disks, Step 1, Screenshots
   

2. Exercise 1, Task 1, Create a Virtual Machine, Networking, Step 2, Screenshots
   

3. Exercise 1, Task 1, Create a Virtual Machine, Management, Step 1

4. Exercise 1, Task 1, Create a Virtual Machine, Management, Step ,1 Screenshots
   

5. Exercise 3, Task 2, Load Balancers, Add backend pool, Step 2, Screenshots
   

6. Exercise 3, Task 2, Load Balancers, Inbound rules, Step 3, Screenshots
   

Hello, when I try to connect to i20-db-1 VM from i20-db-0 using ssh root@i20-db-1 it always asks me for a password even after I have pasted the key in authorized keys see the attached screenshot. Can anyone tell me what I might be doing wrong?

Although I was able to successfully connect to i20-db-0 from i20-db-1.

Relevant screenshots

Lab 3b: Implement SAP architecture on Azure VMs running Windows

In Exercise 1: Provision Azure resources necessary to support highly available SAP NetWeaver deployments

Task 5: Deploy the Scale-Out File Server (SOFS) cluster

Here the deployment prolonged as not expected and also the deployment got failed

Can you please look into it.

Thanks & Regards

Hi,

In the Lab 03a, named HANA HA Infrastructure Deployment, I deployed some virtual machines, including i20-db-0 and
i20-db-1 (They are both configured with pacemaker configuration). I used this guide:

https://github.com/MicrosoftLearning/AZ-120-Planning-and-Administering-Microsoft-Azure-for-SAP-Workloads/blob/master/Instructions/AZ-120_Lab03a-HANA_HA_Infrastructure_Deployment.md

All the steps ran good and without any error. However, when I try to see the Suse HA Management Web Page, It prompts me the followings error message:

Any idea what happened? Did I forgot something? What do I do to fix it?

Let me know any news

Regards,
Leopoldo Morales

Are yous sure this is actually required: "A lab computer running Windows 10, Windows Server 2016, or Windows Server 2019 with access to Azure". For example, the Cloud Shell works for example on macOS Chrome browser just fine.

In Lab 3a: Exercise 1 Task 2 Step 6, this is currently given as the _artifacts Location: https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/sap-3-tier-marketplace-image-md/

I have tried several times testing yesterday and today from fresh lab instances and if I use the value for artifacts location currently given I consistently get all 6 of the /CustomScript resources all failing:

They all have this error, which seems to basically boil down to a '404' - really making me suspicious the URL for artifacts is not pointing to a correct location, and the steps in the 'Note: if the deployment fails' are of no use:

On the other hand, if I use _artifacts Location: https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/sap/sap-3-tier-marketplace-image-md/ -- a coworker recommended that one - and when using it deploy mostly succeed. I say mostly, because I have had some unexpectedly random results when trying multiple iterations of testing from fresh lab start using that URL.

In some cases the resources all deploy error free. In other cases one, or sometimes 2 (usually i20-db-0, and/or i20-db-1) /CustomScript will fail with nasty errors that appear like so:

In the case where I get those nasty errors - often (but not always) the steps in the 'Note: if the deployment fails' will be sufficient to recover, redeploy, and get a success.

In any case, to sum up: I think there is an issue w/the current URL given, and I am not 100% certain what the URL should be....just that there seems to be at least one that mostly succeeds.

In this lab in exercise 3 Task 4 and step 2 we are instructed to set Availability options to No infrastructure redundancy required, however in the next step we must select an Availability set, this option does not show up unless we set Availability options to Availability set.

Relevant screenshots

Module: M01-Unit 1B

Lab/Demo: Unit 1B

Exercise 03

Task: 02

Step: 04

Description of issue
Instructions are different from Azure portal. Instructions docs needs some updating.

Repro steps:

1. Exercise 3, Task 2, Load balancers, Add backend pools, Step 4 -> "Backend pool configuration" is not in the Instructions.
   and "IP addresses" part need update in the Instructions.

Lab

Lab 1b: Implement Windows clustering on Azure VMs

Relevant screenshots

1. Exercise 3, Task 2, Load balancers, Add backend pools, Step 4, Screenshots
   

page number 16:
Frontend IP address:
Wrong**192.168.0.240 (In linux lab used)
correct: **10.0.1.240 ( In windows lab need to use)

Page number 20:
wrong:

1. Within the RDP session to az12001b-vm2, ensure that you can establish SSH session to both az12001b-cl-vm0 and az12001b-cl-vm1 via their private IP addresses (10.0.1.4 and 10.0.1.5, respectively).

correct:

1. Within the RDP session to az12001b-vm2, ensure that you can establish RDP session to both az12001b-cl-vm0 and az12001b-cl-vm1 via their private IP addresses (10.0.1.4 and 10.0.1.5, respectively).

Below is a listing from a recent QA run where some items have changed in Azure, are no longer available, or typos:

• Exercise 1, Task 1, Step 4: 'Pdc RDP Port' & 'Bdc RDP Port' do not appear as fields to populate.

• Exercise 1, Task 2, Steps 2 + 4: There is no option anymore for 'Enable basic plan for free' nor 'Enable backup'.

• Exercise 2, Task 3, Step 3: Instead of 'Replication' it is now titled 'Redundancy'.

• Exercise 3, Task 1, Steps 7-10 & 12-15: Looks like typo where the VM name(s) are listed as 'az12001a-vm0' (or in 12-15, 'az12001a-vm1') where they are actually 'az12001b-cl-vm0' and 'az12001b-cl-vm1', respectively.

• Exercise 3, Task 2, Step 5: There is no longer an 'Unhealthy threshhold' field to populate here.

• Exercise 3, Task 2, Step 6: Frontend IP address was listed as 'frontend-ip1 (10.0.1.240)' and not '192.168.0.240 (LoadBalancerFrontEnd)'

• Exercise 3, Task 3, Step 11: There is no longer an 'Unhealthy threshhold' field to populate here.

• Exercise 3, Task 4, Step 3: No longer an option for 'Enable backup' anywhere I could find.

In this lab, Exercise 1, Task 1, Step 6, I have run multiple tests last week and the week previous where the deploy would fail every time, and the process documented to workaround the issue (removing extensions on the DCs) didn't succeed in getting me past the failure.

Unlike earlier labs with a similar failure, in this lab the failure occurred once for the PDC (and the workaround of removing the extension allowed an attempt at a redeploy) however this time I always received a second failure - this time on the BDC. This time, the recovery process could not be implemented because the redeploy insisted on the '_artifacts location Sas token' field be populated before proceeding, and I found no place to identify a value for that field.

I believe it was mentioned that this course may be getting some deploy instructions updates at some point in the future using bicep (at which point this issue may become moot) but at least for now - literally the only way I was able to proceed past this issue in this lab was to implement the following workaround:

-In place of the stock Quickstart template referenced in Exer 1/Task 1, I instead used the https://aka.ms/az120-1bdeployzone link referenced in earlier labs.

-Using that template, I also used the given values for Exer 1/Task 1/Step 6 as-written, with the exception of '_artifacts location', in which I used: https://raw.githubusercontent.com/polichtm/azure-quickstart-templates/master/application-workloads/active-directory/active-directory-new-domain-ha-2-dc-zones/

While this deploy still had a consistent single deploy failure, the currently-noted recovery process of uninstalling the extension and then redeploying succeeded - consistently - without the dual-failure.

May be worth investigating this workaround and potentially validating/adding to the current Instructions (unless a more reliable bicep-based install process is going to be incorporated in the very near future) as otherwise I found no way to proceed past this first task in repeated testing attempts, thus making the balance of the lab untestable/unusable.

While doing Task 3: Deploy Azure Resource Manager template provisioning Azure VMs running Windows Server 2016 that will host a highly available SAP NetWeaver deployment Step 5:Back on the SAP NetWeaver 3-tier (managed disk) blade, initiate deployment with the following settings:

we're getting the extension failed issue

Can you please check into this

In Exercise 3 Task 2 step 6 Frontend IP address should be updated to frontend-ip1 (10.0.1.240) instead of 192.168.0.240 (LoadBalancerFrontEnd) as we created frontend-ip1 (10.0.1.240) in step 2.

Relevant screenshots

Exercise 1: Provision Azure compute resources necessary to support highly available SAP NetWeaver deployments
Task 1: Deploy a pair of Azure VMs running highly available Active Directory domain controllers by using a Bicep template

Azure Quickstart Template fails during post-deployment configuration. Have tried multiple times (with complex passwords), but get an error stating: "Either the target name is incorrect or the server has rejected the client credentials."

Exercise 1 Task 2 link is incorrect please update it https://github.com/Azure/azure-quickstart-templates/tree/master/sap-3-tier-marketplace-image-md

Here is the correct link
https://github.com/chagarw/azure-quickstart-templates/tree/master/sap-3-tier-marketplace-image

In lab 3b(Implement SAP architecture on Azure VMs running Windows)

In Exercise 1, Task 3, Step 2
On the page titled SAP NetWeaver 3-tier compatible template using a Marketplace image - MD, When I click “Deploy to Azure” it is not redirecting the page to the Azure portal.
Link: https://github.com/Azure/azure-quickstart-templates/tree/master/sap-3-tier-marketplace-image-md

In Exercise 1, Task 5
Faced an error while deploying the template ” 301-storage-spaces-direct-md”
"The DSC Extension failed to execute: Error downloading https://raw.githubusercontent.com/robotechredmond/301-storage-spaces-direct-md/master/dsc/prep-s2d.ps1.zip

I'm unable to complete the deployment successfully at Exercise 1, Task 2 Whenever I delete the Custom script and redeploy the template the Custom script always gets created again (see 3rd Screenshot). Any suggestions?

Relevant screenshots

In Exercise 2> Task 2> step 5> Not able to connect via SSH for i20-db-0 and i20-db-1 from the RDP session to az12003a-vm0.

Dear concern,
I am getting error while using lab : - AZ-120_Lab01b-Azure_VM_Windows_Clustering at below step.Its giving error while pasting below link into the _artifacts Location

_artifacts Location: **https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/active-directory-new-domain-ha-2-dc

Module/Lab: AZ 120 Module 4: Deploy SAP on Azure

Exercise: Exercise 3: Configure clustering on Azure VMs running Linux to support a highly available SAP NetWeaver deployment

Task: 07: Review clustering configuration on Azure VMs running Linux by using Hawk

Step: 03

Description of issue
The lab guide mentions "cluster status is healthy". If you are seeing a message indicating that one of two cluster nodes is unclean, restart that node from the Azure portal. we did this part but still cluster status is not healthy.

Relevant screenshots

https://github.com/MicrosoftLearning/AZ-120-Planning-and-Administering-Microsoft-Azure-for-SAP-Workloads/blob/master/Instructions/AZ-120_Lab01a-Azure_VM_Linux_Clustering.md#task-2-create-and-configure-azure-vms-disks

hi @polichtm ,

The ARM template deployment on Exercise 1 Task 4 is still failing for Scale-Out File Server (SOFS) cluster deployment, with below error message.

Can you please check on it
{
"status": "Failed",
"error": {
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 's2dPrep'. Error message: "DSC Configuration 'PrepS2D' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_xWaitForADDomain failed to execute Set-TargetResource functionality with error message: Domain 'adatum.com' NOT found after 20 attempts. The SendConfigurationApply function did not succeed."\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "
}
}

In Exercise 1 Task 1 we are asked to type a password on step 9. Moving on in Task 2 step 2 we are asked to enter the same password we used in Task 1.

In my case, I used the password Pa55w.rd which is not accepted when provisioning a windows server VM due to password length requirements. Can this be updated to a specific password or clearly mentioned like the password should fulfill the complexity requirement?

Not a blocking issue but a frustrating one as after we wait for the deployment to complete the next task requires the same password as before and we cannot use the same password.

Relevant screenshots

The following items were noted in a recent QA as places where Azure UI/click throughs have changed and may need to be updated to match:

-Exercise 1, Task 1, Step 10: Should say select Next: Monitoring > and then select Next: Advanced >. Also, there was no option to not Enable basic plan for free.

-Exercise 1, Task 1, Step 17: Should say select Next: Monitoring > and then select Next: Advanced >. Also, there was no option to not Enable basic plan for free.

-Exercise 3, Task 2, Step 3: This step "Click Next: Frontend IP Configuration. On the Frontend IP configuration screen, click Add a frontend IP configuration and then click Add."
should be "Click Next: Frontend IP Configuration. On the Frontend IP configuration screen, click Add a frontend IP configuration, specify the following settings and then click Add."

-Exercise 3, Task 4, Step 5: Should say select Next: Monitoring > and then select Next: Advanced >. Also, there was no option to not Enable basic plan for free nor Enable backup nor Guest OS updates.

Also, in md header/title it says 'Lab 2a: Implement Linux clustering on Azure VMs' although the document is indicating 'Lab01a'. Probably as a result of evolving naming conventions as course has grown and changed...slight chance it might confuse someone who may think there were labs missing?

In Exercise 2 Task 4 step 11, Advanced Security Settings for Computers should be updated to Advanced Security Settings for Clusters

Relevant screenshots

Step 8, adVMSize should be : "adVMSize": "Standard_D4s_v3"

Hi All,

While working on Lab 3a: Implement SAP architecture on Azure VMs running Linux,
In Exercise 1, Task 2
The template deployment is failing and the corresponding image showing the error is attached.

Can u please look into this.
Thanks & Regards

Hi Team

we get this deployment error 👎 every time in this lab when we do the testing:

Please resolve or give correct instructions

We had an issue with lab 1B where it appears some changes to the template is causing the DC deployment to fail. Also, it seems the _artifacts Location url looks to be incomplete. Below is what I added to our published labs to aid the student:

Please note: On step 7 and 8 below, the template you are using has changed slightly. You will need to serarch for "defaultValue": "Standard_DS2_v2" and replace it with "defaultValue": "Standard_D4s_v3,"

On step 9, the _artifacts Location: should be entered as https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/active-directory-new-domain-ha-2-dc/azuredeploy.json

Also on step 9, Please update Ad VM Size to be Standard_D4s_v3

Exercise 1: Provision Azure compute resources necessary to support highly available SAP NetWeaver deployments
Task 3: Create and configure Azure VMs disks
Steps 7-13

After creating disks via cloud shell in steps 1-6, when I get to step 7 the disks do not show up in the Azure UI under Attach Existing Disks. (I can, however, Create and attach a new disk.)

After much trial and error, I discovered that the disks would appear in the Attach existing disks list if during the vm0 and vm1 creation process I chose No Infrastructure redundancy required for the Availability options.

I'm guessing that having the Availability options set to No Infrastructure redundancy required will have a negative impact on further tasks in this lab.

Module/Lab: 1B

Exercise: 01

Task: 01

Step: 11

Description of issue

Multiple attempts (from fresh lab start) trying to deploy the 2 DCs for this lab are failing, apparently on extension 'PepareBDC', (sic) which I have not seen before in this course.

Repro steps:

1. Take lab as written
2. Received error last night in EastUS, multiple times this morning in EastUS2 & CentralUS (does not seem to be region specific)
3. Tried workaround referenced in this steps 'note', however removing the 'PepareBDC' extension fro the BDC VM and rerunning from step 10/11 does not help. (in this case, if you attempt to redploy you have to start from the beginning, apparenlty)
4. Have not been able to figure out anything useful whilst troubleshooting it as to why it would be failing, nor do I know how long it has been since it stopped working.

Relevant screenshots

I could easily be missing something, but when I run the command in Exercise 2, Task 3, Step 1, (after earlier logging in to the VMs literally as 'student') the command runs successfully on VM0, however it fails with error when trying to auth to VM1 and run the same command.

I didn't get a screenshot of the error just now, however it is exactly the sort of error one would assume you would get if you were logged on to [machinename]\student as opposed to an account such as [domainname]\student that has perms on both VMs and thus can connect back and forth. The command/reboot does work on VM0, but in order to get it to work whilst logged in as plain 'student' account...one has to then connect separately to the VM1 VM and re-run the powershell commands.

However, since the instructions seem to assume this command will be only run once on VM0 to install to both VMs/reboot both VMs, I think that the earlier steps that reference logins should not be like so:

1. From the az12001b-cl-vm0 blade, connect to the virtual machine guest operating system by using Remote Desktop. When prompted to authenticate, provide the following credentials:

   • User name: Student

   • Password: Pa55w.rd1234

But instead be like so:

1. From the az12001b-cl-vm0 blade, connect to the virtual machine guest operating system by using Remote Desktop. When prompted to authenticate, provide the following credentials:

   • User name: Adatum\Student

   • Password: Pa55w.rd1234

Lab 3b: Implement SAP architecture on Azure VMs running Windows

In Exercise 1: Provision Azure resources necessary to support highly available SAP NetWeaver deployments

Task 5: Deploy the Scale-Out File Server (SOFS) cluster

Here the deployment prolonged as not expected and also the deployment got failed

I tried performing the below step as @polichtm Marcin suggested this in one of the closed issues

steps:

review the deployment details and identify the VM(s) where the installation of the CustomScriptExtension failed (according to the screenshot, that's i20-s2d-0 in your case)
in the Azure portal, navigate to the blade of the VM(s) you identified in the previous step, select Extensions, and from the Extensions blade, remove the CustomScript extension
in the Azure portal, navigate to the AZ12003B-SAP-RG resource group blade, select Deployments, select the link to the failed deployment, and select Redeploy
to redeploy, you will need to select the target resource group (AZ12003B-SAP-RG) and provide the password for the root account (Pa55w.rd1234).

But still, I'm facing the same issue

Can you please look into it.?

Thanks & Regards
Sathish Neelam

In Exercise 1> Task 4> step 5, The deployment is failing with the following error mentioned below:

ERROR MESSAGE:
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
"details": [
{
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 's2dPrep'. Error message: "DSC Configuration 'PrepS2D' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_xWaitForADDomain failed to execute Set-TargetResource functionality with error message: Domain 'adatum.com' NOT found after 20 attempts. The SendConfigurationApply function did not succeed."\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "
}
]
}

Kindly check on this issue.

Module/Lab:AZ-120_Lab06b-ACSS_One_Day

Exercise: 03

Task: 02

Step: 18

Description of issue:
When I attempt to enable replication, I encounter an error. The screenshot below illustrates the errors that occurred during the processing. Because of these errors, I am unable to successfully complete the task.

Relevant screenshots

Pls provide the logs of the most recent deployment you tried
rgds
Marcin

Originally posted by @polichtm in #14 (comment)

Hello, the VNet is not showing up during the creation of the VM (see 1st screenshot), if I try to create another VNet with the same name it gives an error this already exists (see 3rd screenshot). Can the steps be updated to create a VM in Azure Cloud shell instead? I believe this can be resolved if we create VMs through Cloud Shell.

Relevant screenshots

Module/Lab: 04a

Exercise: 01

Task: 02

Step: 00

Description of issue

Deploy failing, appears as if some of the parameters specified are no longer valid.

Repro steps:

Take course instructions as specified, whatif deploy (and attempting to deploy it for real) yields errors:

whatif:

real deploy is same:

I tried converting the main.bicep to a json, used it and the 3a parameters file to attempt a manual deploy/see more detailed errors in that scenario, as expected basically the same:

After running through twice, established should NOT need prompt for password and still does after creation of keys and prompting for empty password - after supposed login, instructed to use the 'passwd' command to change the empty password.

Because of repeated attempts, do not believe this to be a user error but an error within the course.

Module: M01-Unit 1B

Lab/Demo: Unit 1B

Exercise 01

Task: 01

Step: 04

Description of issue
An Error found "Deployment to resource group az12001b-ad-RG failed".

Repro steps:

1. Exercise 1, Task 1, Custom Deployment, Step 4 -> Deployment to resource group az12001b-ad-RG failed.

Lab

Lab 1b: Implement Windows clustering on Azure VMs

Relevant screenshots

1. Exercise 1, Task 1, Custom Deployment, Step 4, Screenshots