A handful of devices that sit outside Active Directory domain membership still need certificates: Wi-Fi laptops joined by user credential, VPN clients, mobile devices enrolled through Intune, and network gear that speaks SCEP and nothing else. NDES is the Microsoft service that bridges those devices into an internal certification authority using the SCEP protocol, and it exists because the CA itself does not speak SCEP.
Setting it up is a two-part job. Part one is issuing the NDES service a certificate that proves its identity to the CA, which is fiddly. Part two is the NDES Policy Module, which decides which requests get approved and how. Most failures occur in part one, and they produce generic SCEP errors that point nowhere useful.
What NDES actually does
The Network Device Enrollment Service is a role service of Active Directory Certificate Services. It listens for SCEP requests over HTTP, validates the one-time password a device presents, signs the request with its own enrollment certificate, and forwards it to the CA. It then returns the issued certificate to the device as a PKCS#7 response.
Critically, NDES does not have its own CA logic. It is a proxy. Anything the CA does not allow, such as a template that does not grant enrol permission to the NDES account, fails at the CA and appears at the device as a vague “invalid request” or “transaction failed”. The device never sees the real error code.
Prerequisites that get skipped
You need an Enterprise or Standalone CA with Web Enrollment enabled, a dedicated service account, and the CA’s root certificate distributed to the devices before enrolment starts. That last item is the most common omission. A device that does not trust the issuing root cannot validate the NDES response, so it discards a perfectly valid certificate.
The service account must be a domain user with no interactive logon rights and must be granted Read and Enroll on the NDES template. It also needs to be able to read the CA’s certificate. Allocate two hours to the prerequisite checklist before you touch the NDES installer, because finding a gap afterwards means uninstalling and starting over.
Certificate templates you will need
Two templates matter. The first is the enrollment agent certificate for the NDES service, which must permit “Enrollment Agent” application policy and have the account listed with Enroll permission. The second is the certificate the devices receive, which typically permits Client Authentication and has the subject built from the request.
Set the device template to issue the subject from the request rather than from AD, since these devices have no AD object. Set the validity period to match your device lifecycle, usually one year. If you set the enrollment agent template to auto-enrol it will not work; the CA needs to issue it through an explicit request so the application policy is applied.
Registration authority is the real key
SCEP requires an RA certificate bound to the NDES certificate on the CA. Generate it with certreq -new using a policy inf file that carries the RA application policy, then submit it to the CA through the web enrollment page and install the issued certificate locally. Only then does the NDES service see a valid RA binding.
If the RA certificate has the wrong application policy, NDES starts and reports healthy in the console while every request fails. The symptom is a correct service state, correct IIS binding, and complete silence from the device. Check the application policies on the RA certificate with certutil -v before blaming anything else.
URLs, challenge passwords and device config
Devices need three endpoints: the SCEP service at /CertSrv/mscep/mscep.dll, the CA certificate endpoint, and the password endpoint. The password flow gives a device a challenge valid for a limited window, typically eight hours, and it can only be used once. Generate passwords on demand rather than in bulk.
Confirm the URL is reachable from outside the network without authentication and without an interactive prompt. A captive portal or a redirect will break SCEP silently, because the device has no browser and no way to report what it saw. Test with a plain HTTP client from a device outside the firewall before enrolling anything real.
Monitoring and failure modes
The NDES logs live under the CA and in the IIS logs. Watch for HTTP 200 responses carrying a SCEP failure code, since the transport looks fine and the payload is the problem. A recurring pattern of failed requests from one device usually means an untrusted root or a clock skew of more than five minutes.
Clock skew deserves its own paragraph. Devices without reliable time will fail their SCEP request and their later certificate validation. On a Windows Server that syncs to a hypervisor host with a drifting clock, every request from that subnet fails. Point devices at a reachable NTP source before you debug anything else.
Sizing the NDES host
NDES is not CPU heavy. Two cores and 4 GB of RAM handle a few thousand devices comfortably, and the bottleneck is IIS request latency and disk for logs. The real constraint is availability: if the NDES server is down, no device can renew, and certificate expiry is a quiet cliff that arrives at the worst moment.
Our Windows VPS plans give you a dedicated machine for NDES with its own public IP and a firewall you control, which is the important part. Put NDES on a host that trusts the CA and is trusted by the devices, keep it off the same box as the CA, and check that the plan allows the inbound HTTP port SCEP needs. A second NDES node is worth considering once device count passes a thousand, since the role is stateless apart from the challenge table.
One more operational note: document the RA certificate expiry date prominently. It is usually issued for two years and nothing reminds you to renew it. When it lapses, NDES keeps running, the console stays green, and every device enrolment across the estate stops working with the same unhelpful SCEP error. A calendar entry and a monthly check of the certificate store on the NDES box costs almost nothing and prevents an outage that takes a full day to diagnose from scratch. For the broader architecture around this service, our Windows hosting overview explains how a CA, NDES and file server can be split across separate small VPS instances without breaking domain trust.



