Interim guidance on 2022 time zone updates for Chile

For those who has MECM (SCCM), you can do this with a compliance rule (CI and CB). Since this change involves binary values, It requires some PowerShell scripting to get it working. Please configure these as discovery and remediation script and test it:

#DiscoveryScript

$RegistryPath   = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Pacific SA Standard Time\Dynamic DST'
$AttributeName  = "2019"
$binvalue = "f0,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,04,00,06,00,02,00,17,00,3b,00,3b,00,e7,03,00,00,09,00,06,00,02,00,17,00,3b,00,3b,00,e7,03"
$hexvalue = $binvalue.Split(',') | % { "0x$_"}

#Check_registry_value
$AttributeValue = @(Get-ItemProperty -Path $registrypath -Name $attributename).2019

if ((!$AttributeValue)) {
    return $false
}

if ($AttributeValue) {
    #convert_value_to_comparable_data
    [byte[]]$comparablevalue = $hexvalue
    #compare_object._if_null_then_values_match
    $compareresult = Compare-Object $AttributeValue $comparablevalue

    if ($compareresult -eq $null) {
        #values_match_then_return_true
        return $true
    }
    else {
    return $false
    }
}

Then, you may run a remediation powershell script that forces the correct value.

#RemediationScript
$RegistryPath   = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Pacific SA Standard Time\Dynamic DST'
$AttributeName  = "2019"
$binvalue = "f0,00,00,00,00,00,00,00,c4,ff,ff,ff,00,00,04,00,06,00,02,00,17,00,3b,00,3b,00,e7,03,00,00,09,00,06,00,02,00,17,00,3b,00,3b,00,e7,03"
$hexvalue = $binvalue.Split(',') | % { "0x$_"}

Set-ItemProperty -Path $RegistryPath -Name $AttributeName -Value ([byte[]]$hexvalue) -Force

Finally just set a compliance rule so that the value returned by the discovery script is Equals "True"

From MEM (Intune), simply create a Script from the Device Menu and use the #RemediationScript below to assign it to a group for testing. It should also work just fine.

Regards,

Mariano