Deployment Archives - MARKSWINKELS.NL

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: …..’

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

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

Now you’re good to go!!

SCCM 2012 R2 SP1 CU1….Why are my task sequences not visible?

This week I’ve upgraded a SCCM 2012 R2 environment to Service Pack 1 with update CU1. After the upgrade, I noticed that not all my task sequences (deployment) where available after PXE boot. Why is that? Is this a ‘new feature’ or just a ‘bug’? After some Troubleshooting I’ve figured out that there’s a strange thing in my deployments!

As you can see in my example I’ve created a collection with 3 deployments active. After PXE boot a virtual machine, only the first deployment is available?!?! :S The other two deployments are also active, but not available…

When we go to the properties of the other two deployments, and change the schedule 1 day back in the time, the deployment became available!! Very strange behavior, but this is the only ‘solution’ I’ve figured out!

How to: Install ConfigMgr 2012 R2 hotfix KB2910552 during OSD

A few weeks ago Microsoft has released a update KB2910552 for ConfigMgr 2012 R2. This update fixes a lot of issues, but also speed up the OSD within ConfigMgr 2012 R2. I should highly recommend to install this hotfix in your environment. The hotfix is updating the site system automatically, but the client not. This blogpost will discribe how to install this hotfix during a OS deployment (OSD).

1.) First install the hotfix KKB2910552. The hotfix is vissible in the installation folder of ConfigMgr. In my example E:\Program Files\Microsoft Configuration Manager\hotfix\KB2910552\Client
2.) Copy the content in this folder to your source directory.
In my example \\CM01\Sources\OSD\Hotfix\KB2910552\Client
3.) Add a new package and configure the source location to the right directory.
In my example \\CM01\Sources\OSD\Hotfix\KB2910552\Client
4.) Select “Do not create a program”
5.) Distribute the package to your distribution point(s)
6.) Open the task sequence and add a new step “Run Command Line”
7.) Select the right package and configure the command line
cmd.exe /c xcopy x64\*.* “C:\Hotfix” /E /H /C /I /Q /Y
This is for x64 systems only! Change x64 to x86 for deployment to x86 systems
8.) In the “Setup Windows and Configuration Manager” step, add the following installation properties
PATCH=”C:\Hotfix\configmgr2012ac-r2-kb2910552-x64.msp”
This is for x64 systems only! Change x64 to x86 for deployment to x86 systems
9.) Start the deployment of a x64 system
10.) After the deployment has finished, navigat to the control panel and Configuration Manager
11.) On the general tab you’ll see the new version number 5.00.7958.1104

WIM image has deployed to wrong partition using SCCM 2012

When you’re deploying an WIM image using System Center Configuration Manager 2012, by default the installation is done on the D:\ partition of your system. Huh….D:\ partition?? But my task sequence say C:\?? Yes indead!! During the task sequence you’ll see “applying image 1 to C:\”, but after rebooting the system, there is no C:\ drive!! Only a D:\ drive!!

To fix this problem, you’ll need to add a new task within the task sequence.

1.) Open the System Center Configuration Manager 2012 Console
2.) Navigate to the task sequence and click Edit
3.) After the partition task, add a new task named Set Task Sequence Variable
4.) The name of the Task Sequence Variable is: Disable Disk Drive Letter (this can be anything you want!)
5.) The Task Sequence Variable will be: OSDPreserveDriveLetter
6.) The value will be: False
7.) Just PXE boot the machine again and watch te result!