After the October 13, 2026 cumulative update, our on-prem NDES started rejecting SCEP requests from Jamf Pro SCEP Proxy (Jamf Cloud). Each failure logs:
Application log, source NetworkDeviceEnrollmentService, Event ID 60 (EVENT_MSCEP_REJECTED_SID_IN_SAN_URI): “…rejected a certificate request because the Subject Alternative Name (SAN) extension contained a URI entry with a security identifier (SID). SID values must not be present in SCEP request SAN entries when no custom policy module is registered to validate them.”
Our profiles follow Jamf’s strong-mapping guidance: a URI SAN of tag:microsoft.com,2022-09-14:sid:$EXTENSIONATTRIBUTE_#, with the EA pulling objectSid. That’s exactly what NDES now refuses.
Environment: Windows Server 2019 NDES, AD CS, NPS for EAP-TLS Wi-Fi
Trigger: KB5126651 (the Server 2019 October update). Uninstalling it restored enrollment immediately.
Impact: existing certs keep working, but new enrollments and renewals fail.
Microsoft appears to accept a SID in a SCEP request only when a registered NDES policy module validates it, the way the Intune Certificate Connector does. Jamf SCEP Proxy has no equivalent, so Jamf’s documented method seems to conflict with this update.
Is anyone else seeing Event 60 on a patched NDES? Has anyone found a supported workaround or an override?
Wanted to let people here know that we also ran into this and found a temporary work-a-round that doesn’t resort to uninstall the Update, or replacing .DLL files.
On the Windows AD CS server you’re processing the requests coming from JAMF, add the following Registry Key:
After that, to be certain restart the server, or open CMD.exe with elevated permissions and run IISReset so the App Pool gets restarted.
This allowed our JAMF environment to get certificates signed again for now, and we can use the time to explore other options like the Outbound Connector.
PPS: Our environment is: JAMF Cloud SCEP → Azure/Entra ID Application Proxy → AD CS NDES Server
Hope it helps!
I just confirmed setting that key worked in my lab as well, thanks for sharing. We have a similar environment. The October mscep.dll contains the text “AllowSIDInSANURI”, which makes sense. I wonder if this workaround will continue to work after the November CU. We’re still moving to the AD CS connector in outbound mode, but this reg key will help with that transition.
Thanks for confirming, as you might’ve noticed I was being very careful how to word things.
And like you, we will only trust this for a brief period of time and move over to the Outbound connector as soon as we can, as until we hear anything official from JAMF or Microsoft regarding that key we just feel it has given us some additional days. 😂
This looks like a collision between two Microsoft requirements rather than a profile mistake. Jamf's strong-mapping guidance is to put the objectSid in the SAN URI — tag:microsoft.com,2022-09-14:sid:<SID> — because for SCEP/offline templates that tag is how the KDC gets its strong mapping. Event 60 is the updated NDES refusing that same URI at issuance time because no custom policy module is registered to validate the SID. In Microsoft's own Intune path, the Certificate Connector fills that validator role; Jamf SCEP Proxy forwards the request but registers nothing equivalent, which is why a by-the-book Jamf configuration is the one that breaks.
Before changing the profile, I'd pin down two things: (1) the exact cumulative update and Windows Server version on the NDES host, and whether an Intune Certificate Connector has ever been installed on that server — its policy module registration changes what NDES accepts; and (2) whether these certs actually face a domain controller for authentication. If they don't, the SID URI may be removable. If they do, removing it just moves the failure from issuance today to authentication at the next renewal, and the real fix has to be a policy module that validates the SID (or a Jamf/Microsoft update that ships one), with the OID 1.3.6.1.4.1.311.25.2 SID extension or explicit altSecurityIdentities mapping as the interim paths to test, depending on how the template builds its subject.
Has anyone on the thread seen an advisory from Jamf or Microsoft on a policy module for the SCEP Proxy path? That seems to be the missing piece the event log is pointing at.
NDES host is Windows Server 2019; the trigger is KB5126651. Uninstalling it restored enrollment immediately (this is a working/production environment). No Intune Certificate Connector has ever been installed, and nothing is registered under HKLM\SOFTWARE\Microsoft\Cryptography\MSCEP\Modules.
Yes, they face AD. These are per-user EAP-TLS Wi-Fi certs authenticated by NPS, which maps them to AD accounts under strong-mapping enforcement. That’s why the SID URI went in originally, so removing it isn’t an option.
I’m opening a case with Jamf asking for a supported validator for the SCEP Proxy path, a PI number other customers can attach to, and interim guidance. I’ll post the PI number here if they issue one. Until then, the interim paths I’m evaluating are a CA policy module that adds the SID extension (OID 1.3.6.1.4.1.311.25.2) after looking up the account, and post-issuance altSecurityIdentities mapping.
We are seeing the same exact issue after Oct security updates on our Windows Server 2022 NDES/SCEP server. No certificate requests are reaching the CA and we see Application Log Event ID 60 that NDES is rejecting the certificate requests from Jamf, exactly the same as OP. Meanwhile, SCEP requests from Intune have been working without interruption.
We know we need strong mapping with SIDs per Microsoft and Jamf documentation. What are these references to custom NDES policy modules I keep seeing and is that going to be the answer? We can’t simply keep the security update uninstalled and go by a registry key workaround permanently.
Thank you for the discussion so far, and to those of you who have reached out about this behavior.
We have reproduced this same failure on our end and have subsequently filed third-party Product Issue ticket PI-2741 to track it. We are working with Microsoft on a resolution and will share updates through an open Support ticket. If you have not already, please contact Jamf Support and reference PI-2741. In the meantime, please avoid leaving NDES unpatched for longer than necessary.
Beyond reverting the recent update, and until Microsoft confirms why this is happening and how to avoid it, the current workaround is to use the AD CS Connector to make these certificate requests. In our testing so far, the Connector, running as a service on an AD-bound Windows server in outbound mode, successfully makes these same requests with the SAN URI. More information on the AD CS Connector as an alternative to SCEP is available here:
I can confirm that we have the same issue. After removing KB5126655 from the server it worked. But this is only a temp solution for us, until we can find a more stable solution without messing with security
Are you guys considering AD CS Connector? Or is the plan to wait until Microsoft fixes?
I’m moving to the AD CS connector. Testing it on some iPads and Macs now and it’s working well so far.
By the way, in a lab, I was able to just restore mscep.dll on the NDES server with a copy from before the October update. That resolved the event 60 error and SIDs were accepted again. Can’t really recommend that, but technically it works if you don’t want to undo the entire KB. It shows that whatever change was made by Microsoft can probably be narrowed down to mscep.dll.
On Server 2022, from the lab:
Good: mscep.dll 10.0.20348.5622 (September update KB5122882, OS build 20348.5622). Requests with the SID were issued.
Bad: mscep.dll 10.0.20348.5756 (October update KB5126655, OS build 20348.5761). Requests with the SID were rejected with event 60.
Wanted to let people here know that we also ran into this and found a temporary work-a-round that doesn’t resort to uninstall the Update, or replacing .DLL files.
On the Windows AD CS server you’re processing the requests coming from JAMF, add the following Registry Key:
After that, to be certain restart the server, or open CMD.exe with elevated permissions and run IISReset so the App Pool gets restarted.
This allowed our JAMF environment to get certificates signed again for now, and we can use the time to explore other options like the Outbound Connector.
Wanted to let people here know that we also ran into this and found a temporary work-a-round that doesn’t resort to uninstall the Update, or replacing .DLL files.
On the Windows AD CS server you’re processing the requests coming from JAMF, add the following Registry Key:
After that, to be certain restart the server, or open CMD.exe with elevated permissions and run IISReset so the App Pool gets restarted.
This allowed our JAMF environment to get certificates signed again for now, and we can use the time to explore other options like the Outbound Connector.
PPS: Our environment is: JAMF Cloud SCEP → Azure/Entra ID Application Proxy → AD CS NDES Server
Hope it helps!
I just confirmed setting that key worked in my lab as well, thanks for sharing. We have a similar environment. The October mscep.dll contains the text “AllowSIDInSANURI”, which makes sense. I wonder if this workaround will continue to work after the November CU. We’re still moving to the AD CS connector in outbound mode, but this reg key will help with that transition.
Wanted to let people here know that we also ran into this and found a temporary work-a-round that doesn’t resort to uninstall the Update, or replacing .DLL files.
On the Windows AD CS server you’re processing the requests coming from JAMF, add the following Registry Key:
After that, to be certain restart the server, or open CMD.exe with elevated permissions and run IISReset so the App Pool gets restarted.
This allowed our JAMF environment to get certificates signed again for now, and we can use the time to explore other options like the Outbound Connector.
PPS: Our environment is: JAMF Cloud SCEP → Azure/Entra ID Application Proxy → AD CS NDES Server
Hope it helps!
I just confirmed setting that key worked in my lab as well, thanks for sharing. We have a similar environment. The October mscep.dll contains the text “AllowSIDInSANURI”, which makes sense. I wonder if this workaround will continue to work after the November CU. We’re still moving to the AD CS connector in outbound mode, but this reg key will help with that transition.
Thanks for confirming, as you might’ve noticed I was being very careful how to word things.
And like you, we will only trust this for a brief period of time and move over to the Outbound connector as soon as we can, as until we hear anything official from JAMF or Microsoft regarding that key we just feel it has given us some additional days. 😂