Error: ‘User failed validation to purchase resources’ when deploying a virtual machine

Today I’ve deployed a new virtual machine within Azure using the Windows Server 2022 Azure Edition Preview Marketplace image. After running my Powershell script, I received an error:
’User failed validation to purchase resources. Error message: ‘You have not accepted the legal terms on this subscription: …..’

image

So, let’s take a look at the legal terms, also using Powershell. I’ve used a couple of variables.

$azureVmPublisherName = "MicrosoftWindowsServer"
$azureVmOffer = "microsoftserveroperatingsystems-previews"
$azureVmSkus = "windows-server-2022-azure-edition-preview"
$Version = "latest"


Get-AzMarketplaceTerms -Publisher $azureVmPublisherName -Product $azureVmOffer -Name $azureVmSkus

image

As you can see, the legal terms are not accepted yet!! With a small Powershell command, we can accept the legal terms.

Get-AzMarketplaceTerms -Publisher $azureVmPublisherName -Product $azureVmOffer -Name $azureVmSkus | Set-AzMarketplaceTerms -Accept

image

Now you’re good to go!!

PowerCLI: An Aspiring Automator’s Guide

Getting into scripting can be daunting. It’s easier to just use existing scripts found online, but if you choose this route you’ll quickly run into limitations. If you take the time to learn how to create your scripts, trust me, you’ll never look back!

clip_image002

Automating vSphere is particularly useful for countless applications and the best way is through PowerCLI – a version of PowerShell developed specifically for VMware. Learn how to develop your own PowerCLI scripts with this free 100+ page eBook from Altaro, PowerCLI: The Aspiring Automator’s Guide.

Written by VMware vExpert Xavier Avrillier, this eBook presents a use-case approach to learning how to automate tasks in vSphere environments using PowerCLI. We start by covering the basics of installation, set up, and an overview of PowerCLI terms. From there we move into scripting logic and script building with step-by-step instructions of truly useful custom scripts, including how to retrieve data on vSphere objects; display VM performance metrics; how to build HTML reports and schedule them; the basics on building functions; and more!

Stop looking at scripts online in envy because you wish you could build your own scripts.

Get started on your path to automation greatness – Download the eBook now!

Enable Azure Accelerated Networking

Azure Accelerated Networking is a new option for Azure Infrastructure as a Service (IaaS) Virtual Machine (VM) on the NIC level providing several benefits by enabling single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the datapath, reducing latency, jitter, and CPU utilization, for use with the most demanding network workloads on supported VM types. You would typically use this feature with heavy workloads that need to send or receive data at high speed with reliable streaming and lower CPU utilization. It will enable speeds of up to 25Gbps per Virtual Machine. Best of all, it’s free!

accelerated-networking

How to Enable Accelerated Networking:

You can enable this feature during initial creation of the VM, on the networking tab, you will see “Enable Accelerated Networking”. If you are unable to enable, then it is not compatible on your chosen Azure VM size. If you need to enable this feature after VM creation you will require to do so through powershell as it is not yet supported in the portal. You can do this simply with the below commands after deallocating the Virtual Machine.


Login-AzureRmAccount
$nic = Get-AzureRmNetworkInterface -ResourceGroupName “YourResourceGroupName” -Name “YourNicName”
$nic.EnableAcceleratedNetworking = $true
$nic | Set-AzureRmNetworkInterface

Then proceed to start the Virtual Machine and Accelerated Networking will be enabled.

Altaro Dojo forums

Altaro has kicked off the Altaro Dojo forums. The forum brings fellow IT pros together, connect the community and enable members to learn and share their knowledge with one another.

Some info on how people can use the forum can be found here.

Please register on the forum and share your knowledge with other IP pros! Let’s make some community!

I want to become a ‘Ninja’. Let’s go!!!

Failover Hyper-V cluster nodes with mixed Upper & Lower case names

I’ve seen a lot of Hyper-V clusters during my daily work. Most of the time, I see a mixture of none standardised names or letters. Also a mixture of upper and lower case names.

There’s is only one option to have all your cluster nodes in Upper case names within the failover cluster manager, you’ll have to use the command line! For example:

cluster.exe /cluster:<name of the cluster> /add /node:<name of the node in UPPER case>

For this command to work, you’ve to install ‘Failover Cluster Command Interface’.

       

How to: Implementing Storage Spaces insides Azure Virtual Machines

Within an Azure Virtual Machine, you should never store your (personal) data on the C: drive or the temporary disk. You can attach new storage disks to the virtual machine, how many disks depends on the VM size you’ve choosen.

View all VM sizes in Microsoft Azure:
https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-sizes

In my example I’ve choosen the ‘DS1v2’ VM size, so I can attach two extra (premium storage) disks. Because the maximum size of an disk in Microsoft Azure is 1023 GB, I’ve created multiple disks. Both disks are attached to the virtual machine and we’re going to implement Storage Spaces within the virtual machine. Storage Spaces is software defined storage (SDS) from Windows Server 2012 R2 and above.

Storage Spaces is a built-in Windows Server Role. When combining all the data disks, you can create one, or more, big data volumes in your Windows Virtual Machine. Extremely powerful for example file servers.

1.) First of all I’ve created a new virtual machine using the Azure Portal

2017-02-27_14h41_01    2017-02-27_14h42_11    2017-02-27_14h44_48

2017-02-27_14h45_06    2017-02-27_14h57_06

2.) Next I’ve created two new disks (premium storage – SSD) with tthe size of 1023 GB.

2017-02-27_14h57_22    2017-02-27_14h58_22    2017-02-27_15h00_04

3.) Next I’ve logged in into the new created virtual machine and configured Storage Spaces.

2017-02-27_15h01_25    2017-02-27_15h02_08    2017-02-27_15h04_49

2017-02-27_15h08_16    2017-02-27_15h08_29    2017-02-27_15h09_04

2017-02-27_15h09_17    2017-02-27_15h09_27    2017-02-27_15h09_37

2017-02-27_15h09_57

4.) The next step is to create a new virtual disk

2017-02-27_15h10_03    2017-02-27_15h10_26    2017-02-27_15h10_35

2017-02-27_15h11_00    2017-02-27_15h11_08    2017-02-27_15h11_28

2017-02-27_15h11_48    2017-02-27_15h12_01    2017-02-27_15h12_10

2017-02-27_15h12_24

5.) The final step is to create the new volume for storing your data on.

2017-02-27_15h12_31    2017-02-27_15h12_43    2017-02-27_15h12_52

2017-02-27_15h13_03    2017-02-27_15h13_24    2017-02-27_15h13_36

2017-02-27_15h14_02    2017-02-27_15h14_14    2017-02-27_15h14_35

As you can see, there’s a new volume of 2 TBwithin the virtual machine. If you’re changing the size of the virtual machine, it is also possible to add some more disks to the virtual machine and extend the Storage Spaces with more terabytes!!

2017-02-27_15h14_52

 

Demo movie: Storage Spaces Direct in Windows Server 2016

The following movie shows the power of Storage Spaces Direct in Windows Server 2016. From the local disks, to storage pools and cluster, all the layers are explained!! Very useful when you want to know exactly how Storage Spaces Direct (S2D) works.

Software Defined will be the feature! So prepare yourself….. 🙂