Skip to content

Commit 2e8704d

Browse files
authored
Merge pull request #263145 from rpsqrd/esu-certs
Updating ESU docs for additional intermediate CAs
2 parents 7e2a2f4 + 263f355 commit 2e8704d

File tree

1 file changed

+21
-13
lines changed

1 file changed

+21
-13
lines changed

articles/azure-arc/servers/troubleshoot-extended-security-updates.md

Lines changed: 21 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -53,26 +53,35 @@ If you're unable to enable this service offering, review the resource providers
5353

5454
## ESU patches issues
5555

56-
Ensure that both the licensing package and servicing stack update (SSU) are downloaded for the Azure Arc-enabled server as documented at [KB5031043: Procedure to continue receiving security updates after extended support has ended on October 10, 2023](https://support.microsoft.com/topic/kb5031043-procedure-to-continue-receiving-security-updates-after-extended-support-has-ended-on-october-10-2023-c1a20132-e34c-402d-96ca-1e785ed51d45). Ensure you are following all of the networking prerequisites as recorded at [Prepare to deliver Extended Security Updates for Windows Server 2012](prepare-extended-security-updates.md?tabs=azure-cloud#networking).
57-
58-
If installing the Extended Security Update enabled by Azure Arc fails with errors such as "ESU: Trying to Check IMDS Again LastError=HRESULT_FROM_WIN32(12029)" or "ESU: Trying to Check IMDS Again LastError=HRESULT_FROM_WIN32(12002)", there is a known remediation approach:
56+
### ESU prerequisites
5957

60-
1. Download this [intermediate CA published by Microsoft](https://www.microsoft.com/pkiops/certs/Microsoft%20Azure%20TLS%20Issuing%20CA%2001%20-%20xsign.crt).
61-
1. Install the downloaded certificate as Local Computer under `Intermediate Certificate Authorities\Certificates`. Use the following command to install the certificate correctly:
58+
Ensure that both the licensing package and servicing stack update (SSU) are downloaded for the Azure Arc-enabled server as documented at [KB5031043: Procedure to continue receiving security updates after extended support has ended on October 10, 2023](https://support.microsoft.com/topic/kb5031043-procedure-to-continue-receiving-security-updates-after-extended-support-has-ended-on-october-10-2023-c1a20132-e34c-402d-96ca-1e785ed51d45). Ensure you are following all of the networking prerequisites as recorded at [Prepare to deliver Extended Security Updates for Windows Server 2012](prepare-extended-security-updates.md?tabs=azure-cloud#networking).
6259

63-
`certutil -addstore CA 'Microsoft Azure TLS Issuing CA 01 - xsign.crt'`
6460

65-
1. Install security updates. If it fails, reboot the machine and install security updates again.
61+
### Error: Trying to check IMDS again (HRESULT 12002)
6662

67-
If you're working with Azure Government Cloud, use the following instructions instead of those above:
63+
If installing the Extended Security Update enabled by Azure Arc fails with errors such as "ESU: Trying to Check IMDS Again LastError=HRESULT_FROM_WIN32(12029)" or "ESU: Trying to Check IMDS Again LastError=HRESULT_FROM_WIN32(12002)", you may need to update the intermediate certificate authorities trusted by your computer using one of the following two methods:
6864

69-
1. Download this [intermediate CA published by Microsoft](https://www.microsoft.com/pkiops/certs/Microsoft%20Azure%20TLS%20Issuing%20CA%2002%20-%20xsign.crt).
65+
1. Configure your network firewall and/or proxy server to allow access from the Windows Server 2012 (R2) machines to `https://microsoft.com/pkiops/certs`. This will allow the machine to automatically retrieve updated intermediate certificates as required and is Microsoft's preferred approach.
66+
1. Download all intermediate CAs from a machine with internet access, copy them to each Windows Server 2012 (R2) machine, and import them to the machine's intermediate certificate authority store:
67+
1. Download the 4 intermediate CA certificates:
68+
1. [Microsoft Azure TLS Issuing CA 01](https://www.microsoft.com/pkiops/certs/Microsoft%20Azure%20TLS%20Issuing%20CA%2001%20-%20xsign.crt)
69+
1. [Microsoft Azure TLS Issuing CA 02](https://www.microsoft.com/pkiops/certs/Microsoft%20Azure%20TLS%20Issuing%20CA%2002%20-%20xsign.crt)
70+
1. [Microsoft Azure TLS Issuing CA 05](https://www.microsoft.com/pkiops/certs/Microsoft%20Azure%20TLS%20Issuing%20CA%2005%20-%20xsign.crt)
71+
1. [Microsoft Azure TLS Issuing CA 06](https://www.microsoft.com/pkiops/certs/Microsoft%20Azure%20TLS%20Issuing%20CA%2006%20-%20xsign.crt)
72+
1. Copy the certificate files to your Windows Server 2012 (R2) machine.
73+
1. Run the following commands in an elevated command prompt or PowerShell session to add the certificates to the "Intermediate Certificate Authorities" store for the local computer. The command should be run from the same directory as the certificate files. The commands are idempotent and won't make any changes if you've already imported the certificate:
7074

71-
1. Install the downloaded certificate as Local Computer under `Intermediate Certificate Authorities\Certificates`. Use the following command to install the certificate correctly:
75+
```powershell
76+
certstore -addstore CA "Microsoft Azure TLS Issuing CA 01 - xsign.crt"
77+
certstore -addstore CA "Microsoft Azure TLS Issuing CA 02 - xsign.crt"
78+
certstore -addstore CA "Microsoft Azure TLS Issuing CA 05 - xsign.crt"
79+
certstore -addstore CA "Microsoft Azure TLS Issuing CA 06 - xsign.crt"
80+
```
7281
73-
`certutil -addstore CA 'Microsoft Azure TLS Issuing CA 02 - xsign.crt'`
82+
After allowing the servers to reach the PKI URL or manually importing the intermediate certificates, try installing the Extended Security Updates again using Windows Update or your preferred patch management software. You may need to reboot your computer for the changes to take effect.
7483
75-
1. Install security updates. If it fails, reboot the machine and install security updates again.
84+
### Error: Not eligible (HRESULT 1633)
7685
7786
If you encounter the error "ESU: not eligible HRESULT_FROM_WIN32(1633)", follow these steps:
7887
@@ -81,4 +90,3 @@ If you encounter the error "ESU: not eligible HRESULT_FROM_WIN32(1633)", follow
8190
`Restart-Service himds`
8291
8392
If you have other issues receiving ESUs after successfully enrolling the server through Arc-enabled servers, or you need additional information related to issues affecting ESU deployment, see [Troubleshoot issues in ESU](/troubleshoot/windows-client/windows-7-eos-faq/troubleshoot-extended-security-updates-issues).
84-

0 commit comments

Comments
 (0)