Extended Security Updates via Azure Arc - Everything you need to know
As of October 10th, Windows Server 2012 will no longer be supported by Microsoft. This means that organizations still using this operating system will no longer receive security updates, leaving their systems vulnerable to potential threats. There are multiple paths to overcome this, purchase yearly extended security updates licenses(ESUs), retiring those workloads, upgrading to a newer supported version, migrating those workloads to the cloud, modernize to PaaS services or more recently leveraging Azure Arc to deploy extended security updates and get monthly billing so you can stop paying for those ESUs once the servers are migrated to the cloud, retired or no longer on 2012.
Azure Arc offers more than just extended security updates for Windows Server 2012. It brings a range of powerful capabilities to the table. With Azure Arc, organizations can easily manage, secure and monitor their hybrid infrastructure, including on-premises servers, multi-cloud environments, and edge devices, all from a single control plane with capabilities like Azure Monitor, Defender for Cloud , Change Tracking and Inventory , Azure Update Manager , and much more.
In this post, we will explore everything you need to know to start deploying ESUs using Azure Arc to your 2012 machines.
Requirements
- You must have Software Assurance through Volume Licensing
- onboard your 2012 machines to Azure Arc. There are different ways you can onboard Windows servers like group policy, configuration manager, Windows Admin Center, or any 3rd-party configuration management solution. Most methods are documented here.
NOTE: With GPO onboarding, you can leverage WMI filters to have the group policy only applicable to Windows Server 2012/2012R2
select * from Win32_OperatingSystem where (Version like "6.2%" or Version like "6.3%") and (ProductType="2" or ProductType="3")**
- Apply tags as you are onboarding, it will come handy later. Start with tags that can help you deploy ESUs, like owner, type, environment, department/site, migration date,…etc.
- If the machines are already onboarded to Azure Arc, update the Azure connected machine agent to 1.34 or later to support deploying ESUs. Its recommended to automate the agent upgrade process using Windows Updates for Windows by configuring the Windows Update client on the machine to check for other Microsoft products. You can also of course upgrade manually by re-deploying the latest msi for the agent.
Since the machines are onboarded to Azure Arc, you can leverage the Azure Resource Graph explorer to find the machines with older versions of the agent.
resources
| where type == 'microsoft.hybridcompute/machines'
| extend agentVersion = tostring(properties.agentVersion) , operatingSystem = tostring(properties.osSku)
| where agentVersion !startswith '1.34.'
| project name,resourceGroup,operatingSystem,agentVersion
- If you don’t have automation in-place to continuously upgrade the agent, you can leverage the same method you used for onboarding to push the new agent version. The below code snippet is using Configuration manager’s run script capability to check the agent version and only upgrade if its less than 1.34. The new agent msi is hosted on a shared folder.
try {
# Add the service principal application ID and secret here
$servicePrincipalClientId = "<App Id HERE>";
$servicePrincipalSecret = "<App SECRET HERE>";
$env:SUBSCRIPTION_ID = "<Subscription Id>";
$env:RESOURCE_GROUP = "<Resource group name>";
$env:TENANT_ID = "<Tenant Id>";
$env:LOCATION = "<Azure region>";
$uncPath = "\\<server hosting the agent>\<shared folder name>\AzureConnectedMachineAgent.msi"
$localPath = "C:\Temp\AzureConnectedMachineAgent.msi"
$agentPath = "C:\Program Files\AzureConnectedMachineAgent"
$targetVersion = "1.34.02440.1261"
if (test-path -Path $agentPath) {
Write-host "Agent is already installed....Checking the agent version"
$agentVersion = (azcmagent show agentVersion -j | ConvertFrom-Json).agentVersion
# Split the version string into an array of its components
$versionComponents = $agentVersion -split '\.'
# Split the target version into an array of its components
$targetComponents = $targetVersion -split '\.'
# Compare each component of the versions
for ($i = 0; $i -lt $versionComponents.Length; $i++) {
$versionComponent = [int]$versionComponents[$i]
$targetComponent = [int]$targetComponents[$i]
if ($versionComponent -lt $targetComponent) {
Write-Host "The version '$agentVersion' is less than '$targetVersion'."
Write-Host "Upgrading the agent"
New-Item -Path c:\temp -ItemType Directory -Force | Out-Null
Copy-Item -Path $uncPath -Destination $localPath -Force
Start-Process -FilePath msiexec.exe -ArgumentList "/i `"$localPath`" /qn" -Wait
Remove-Item -Path $localPath -Force
break
}
elseif ($versionComponent -gt $targetComponent) {
Write-Host "The version '$agentVersion' is greater than '$targetVersion'."
break
}
}
# If all components are equal or the loop completes without a break, the versions are equal
if ($i -eq $versionComponents.Length) {
Write-Host "The version '$agentVersion' is equal to '$targetVersion'."
}
}
else {
Write-Host "Installing the agent"
New-Item -Path c:\temp -ItemType Directory -Force | Out-Null
Copy-Item -Path $uncPath -Destination $localPath -Force
Start-Process -FilePath msiexec.exe -ArgumentList "/i `"$localPath`" /qn" -Wait
Remove-Item -Path $localPath -Force
# Run connect command
& "$env:ProgramW6432\AzureConnectedMachineAgent\azcmagent.exe" connect --service-principal-id "$servicePrincipalClientId" --service-principal-secret "$servicePrincipalSecret" --resource-group "$env:RESOURCE_GROUP" --tenant-id "$env:TENANT_ID" --location "$env:LOCATION" --subscription-id "$env:SUBSCRIPTION_ID";
}
}
catch {
$logBody = @{subscriptionId = "$env:SUBSCRIPTION_ID"; resourceGroup = "$env:RESOURCE_GROUP"; tenantId = "$env:TENANT_ID"; location = "$env:LOCATION"; operation = "onboarding"; messageType = $_.FullyQualifiedErrorId; message = "$_"; };
Invoke-WebRequest -UseBasicParsing -Uri "https://gbl.his.arc.azure.com/log" -Method "PUT" -Body ($logBody | ConvertTo-Json) | out-null;
Write-Host -ForegroundColor red $_.Exception;
}
Licensing
- Determine the Windows Server 2012 editions available and number of cores. You can use the following Azure resource graph query or your existing configuration management solution.
resources
| where type == 'microsoft.hybridcompute/machines'
| extend agentVersion = tostring(properties.agentVersion) , operatingSystem = tostring(properties.osSku)
| extend status = tostring(properties.status)
| extend lastConnected = todatetime(properties.lastStatusChange)
| extend cores = properties.detectedProperties.coreCount
| where operatingSystem contains "2012"
| project name,operatingSystem,cores,status,lastConnected,agentVersion
There are two editions of Windows Server 2012; Standard can be applied to up to two virtual machines (VMs) and Data center which has no limit to the number of VMs it can be applied to.
NOTE: If ESU is enabled at a later time than October 10th, it will charge back to the date of 10th of October regardless of when it was enabled (1-time charge back).
- If you have already purchased traditional Windows Server 2012 ESUs, you can switch to ESUs enabled by Azure Arc between Year one and Year two.
Physical core licensing
- Requires a minimum of 16 physical cores per license.
- It makes sense to use this type of licensing for physical servers and Windows Server virtualization hosts that host lots of virtual machines specially if the host is Data center edition where there is no limit on the VMs it can be applied to.
Virtual core licensing
- Requires a minimum of eight virtual cores per VM.
- It is advisable for VMs running on third-party hosts, 3rd-party cloud providers, or if the Windows Server was licensed on a virtualization basis.
- Usually used with Windows Server standard edition.
NOTE: You can find different example scenarios in this article to help determine what is the best mix of licenses to acquire.
Deploy the Extended security updates
- Start creating the needed licenses from the Azure Portal.
- Link the licenses to the eligible machines. Currently its manual from the portal but soon there can be an Azure Policy to do this at scale.
- At the time of this post, there is no Azure Policy to link the license at scale. The only way to do this programmatically is use the ARM API.
[Update] There are newly published Azure Policies that can help with governing and deploying the extended security updates licenses.
$location = "<Region where the ESU license is deployed>"
$subscriptionId = "<SubscriptionId for Arc-enabled servers>"
$esuSubscriptionId = "<SubscriptionId for Arc-enabled servers>"
$esuLicenceResourceGroup = "<Resource group where the ESU license is deployed>"
$licenseName = "<Name of the ESU license>"
$arcServersResourceGroup = "<Resource group where the Arc-enabled machines are deployed>"
################################################################
# Uncomment the method you will use to provide the servers list
## 1. Import using CSV
## 2. Manually create an array of servers
## 3. Directly query the Arc-enabled machines
################################################################
###############################################################################
##1. Importing servers list using a CSV file (Column name should be ServerName)
###############################################################################
<#
$serversListFile = "<Path to the CSV file containing the list of servers>"
$servers = Import-Csv $serversListFile -Header "ServerName"
#>
################################################################
## 2. Manually create an array of servers
################################################################
<#
$servers = @(
"server1",
"server2"
)
#>
################################################################
## 3. Directly query the Arc-enabled machines
################################################################
<#
Install-Module -Name Az.ConnectedMachine -Force
$servers = Get-AzConnectedMachine -ResourceGroupName $arcServersResourceGroup -SubscriptionId $subscriptionId | Select-Object -ExpandProperty Name
#>
Connect-AzAccount
$licenseId = "/subscriptions/$esuSubscriptionId/resourceGroups/$esuLicenceResourceGroup/providers/Microsoft.HybridCompute/licenses/$licenseName"
$accessToken = (Get-AzAccessToken).Token
$headers = @{
"Authorization" = "Bearer $accessToken"
"Content-Type" = "application/json"
}
foreach($server in $servers){
$Url = "https://management.azure.com/subscriptions/$subscriptionId/resourceGroups/$arcServersResourceGroup/providers/Microsoft.HybridCompute/machines/$server/licenseProfiles/default?api-version=2023-06-20-preview "
$body = @{
location = $location
properties = @{
esuProfile = @{
assignedLicense = $licenseId
}
}
} | ConvertTo-Json
Invoke-RestMethod -Method Put -Uri $url -Body $body -Headers $headers
}
- You can then use any update management solution to push the updates once available. You have to have critical and security updates classification selected in your patch management solution.
- You can use Azure Update manager with no additional cost if the machines are associated with an ESU License (you can use tags to dynamically assign them)
- Change tracking, machine configuration are offered at no additional cost as well if ESU is enabled and linked to the Arc-enabled machines.
- If you have SQL 2012 on the same VM , just Arc-enable the SQL server by installing the Azure extension for SQL Server and enable ESU to get extended security updates for this SQL instance.
- You can apply ESUs to some dev/test, DR scenarios at no additional cost via Azure Arc by using predefined tags (first you must have provisioned and activated a WS2012 Arc ESU License intended to be linked to regular Azure Arc-enabled servers running in production environments (i.e., normally billed ESU scenarios)).
You May Also Like
Jumpstart Agora - Streamlining the Software Delivery Process using CI/CD
We have recently launched Jumpstart Agora 🏛️ which is a marketplace of …
SSH into your Azure Arc-enabled servers from anywhere
A new capability has been introduced for Azure Arc-enabled servers …
Secure Azure Arc servers onboarding using Conditional Access
One of the most common methods of onboarding servers to Azure Arc is …