About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Autoenrollment never shows a prompt, so a failure looks like a certificate that simply does not appear. Three layers have to line up: the "Certificate Services Client - Auto-Enrollment" policy must reach the machine, the certificate template must give that machine's account Enroll and Autoenroll and be issued by a CA, and the machine must be able to make a remote procedure call (RPC) and DCOM call to the CA.
When the third layer breaks, Microsoft documents the error as 0x800706ba, "The RPC server is unavailable", and says Event ID 82 is logged in the Application log when autoenrollment fails with the same error. Check the policy and the template first, because they are quick to read.
What the error means
Autoenrollment is driven by Group Policy. Microsoft's steps set Configuration Model to Enabled under Computer Configuration, Policies, Windows Settings, Security Settings, Public Key Policies, and tick both Renew expired certificates, update pending certificates, and remove revoked certificates and Update certificates that use certificate templates. User certificates use the same setting under User Configuration. Computers apply the policy the next time Group Policy refreshes.
On the template, Microsoft's server-template steps select the group on the Security tab, make sure Enroll is allowed, and tick Autoenroll. The template must also be added to the CA through New, then Certificate Template to Issue.
The 0x800706ba page describes what the network trace looks like when the RPC layer is the problem. The LDAP queries to the configuration partition succeed and the templates are listed. The requesting server then tries an RPC call to the CA and gets "ACCESS DENIED". Microsoft explains that when the enrolling account fails Kerberos authentication, the authentication is downgraded to anonymous logon and the logon fails at the DCOM level.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Policy not applied to the machine | No attempt at all | gpresult /h shows the Auto-Enrollment setting is missing, or not Enabled |
| Template lacks Enroll and Autoenroll for the machine's group | The template is not offered to the machine | Template Security tab |
| Template not issued by the CA | Same as above | certutil -TemplateCAs lists the CAs for the template |
| User right on the CA blocks the account | 0x800706ba; DCOM event 10027 on the CA | gpresult /h on the CA, user rights Access this computer from the network and Deny access to this computer from the network |
| Local groups on the CA missing members | 0x800706ba | Users lacks Authenticated Users, Domain Users or INTERACTIVE; Certificate Service DCOM Access lacks Authenticated Users |
| EnableDCOM not Y on client and CA | 0x800706ba | Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\OLE, EnableDCOM |
| RPC restriction policy applied | 0x800706ba | Restrictions for Unauthenticated RPC Client should read Not Configured |
| COM Security limits lack the DCOM group | 0x800706ba | Component Services, My Computer, COM Security tab, Edit Limits |
The 0x800706ba rows come from Microsoft's enrolment page. The "What you see" entries for the first three rows are the pattern to expect from the settings involved, not statements from Microsoft.
Prove the cause before changing anything
These checks only read.
1. Is the policy on the machine? On the client, from an elevated prompt, produce the Group Policy report. Microsoft's page uses this form:
gpresult /h appliedgpo.html
Open the file and look for Certificate Services Client - Auto-Enrollment under Public Key Policies, and note the winning GPO.
2. Does the CA offer the template? certutil -TemplateCAs TemplateName "Displays the certification authorities (CAs) for a certificate template." certutil -config "ca01.contoso.com\Contoso Issuing CA" -CATemplates displays the templates for a CA. The reference does not print sample output, so read the list for your template's name.
3. Can the machine talk to the CA? certutil -ping "Attempts to contact the Active Directory Certificate Services Request interface."
certutil -config "ca01.contoso.com\Contoso Issuing CA" -ping
A reply means the request interface answered. A failure with 0x800706ba points to the RPC and DCOM causes in the table.
4. Find Event ID 82. Microsoft names it, without naming a source, as the Application-log event that appears when autoenrollment fails with 0x800706ba. PowerShell 5.1 documents these hashtable keys:
$Date = (Get-Date).AddDays(-2)
Get-WinEvent -FilterHashtable @{ LogName='Application'; StartTime=$Date; Id=82 }
Read each message's source column before drawing conclusions, since an ID alone can be shared by different sources. On the CA, check the System log for DistributedCOM event 10027, which Microsoft shows as "The machine wide limit settings do not grant Remote Activation permission for COM Server applications to the user NT AUTHORITY\ANONYMOUS LOGON SID (S-1-5-7)".
5. Read EnableDCOM on the client and the CA:
reg query HKLM\Software\Microsoft\OLE /v EnableDCOM
6. Check the local groups on the CA in Local Users and Groups: Users and Certificate Service DCOM Access. Microsoft lists the defaults of Users as Contoso\Domain Users, NT AUTHORITY\Authenticated Users and NT AUTHORITY\INTERACTIVE.
Fix
Policy. Enable the setting in a GPO linked to the right scope, tick both boxes, and refresh with gpupdate /force. Risk: the policy applies to every computer or user in the scope, and each one then tries to enroll for every template it qualifies for. Test in a small organisational unit first. To back out, return the setting to its previous model; certificates already issued stay in the store.
Template rights. Grant the target group Enroll and Autoenroll. Risk: every member of the group begins to receive certificates, which adds database rows on the CA. To back out, clear Autoenroll; issued certificates stay valid until revoked or expired.
Template not issued. In the Certification Authority console choose Certificate Template to Issue and add it. Risk: the CA now issues that template to anyone who holds Enroll. To back out, remove it from the list of issued templates.
User rights on the CA. Microsoft says the account used to enroll must not be denied network access, and warns that "The settings configured on the Group Policy Objects (GPOs) are for a reason, so you should talk to your security team before making any changes." Disruptive step: adding groups to Access this computer from the network or removing them from Deny access to this computer from the network changes the CA's logon surface. To back out, restore the previous list recorded from gpresult.
Local groups. Add the missing groups to Users and add NT AUTHORITY\Authenticated Users to Certificate Service DCOM Access. Risk: this widens who can reach the CA's DCOM interface. To back out, remove the added entry.
EnableDCOM. If it is N, Microsoft says change it to Y and restart. Disruptive step: a registry edit that needs a restart; on a CA that interrupts issuance. To back out, restore the earlier value and restart again.
COM Security limits. The page says the local Certificate Service DCOM Access group should hold Local Access and Remote Access under Access Permissions, and Local Activation and Remote Activation under Launch and Activation Permissions. Risk: these limits apply machine-wide; record the dialog before editing. To back out, restore the recorded entries.
RPC restriction policy. Microsoft's check is that Restrictions for Unauthenticated RPC Client is Not Configured in the winning GPO. Agree any change with whoever owns that policy.
Confirm the fix
On a test client, refresh and trigger the engine:
gpupdate /force
certutil -pulse
certutil -pulse "Pulses an autoenrollment event or NGC task." Risk: it starts enrollment now, so the CA issues certificates for every template the machine qualifies for. To back out, revoke or remove any certificate you did not mean to issue. Then list the machine store:
Get-ChildItem -Path Cert:\LocalMachine\My
Look for the certificate from the template. To check that it carries a key, pipe the item to Format-List Subject, Thumbprint, HasPrivateKey. For NPS servers, Microsoft adds that if Group Policy did not refresh properly, restarting the server refreshes it.
Example (illustrative): a hosting team runs 40 servers in the CONTOSO domain. The template Contoso Server grants Autoenroll to the group Server Certs, which holds 28 of the 40 servers. After gpupdate /force and certutil -pulse, 28 servers hold the certificate and 12 do not. The 12 are the ones missing from the group (40 minus 28). No 0x800706ba appears on them, because they never request. Adding them to the group, then refreshing policy, brings the count to 40.
What to watch afterwards
- Keep a list of templates, the groups with Autoenroll, and the CA that issues each. Compare it with the real list each quarter.
- After changing user rights on the CA, run
certutil -pingfrom a client. - Watch for Application-log Event ID 82 and for DCOM event 10027 on the CA.
- Count issued certificates per template against the count of machines in scope.
Read next
Related articles you may want next.
- Backup & RecoveryBacking up and restoring a certification authority: the key, the database and the namePlan certification-authority recovery with key generations, CA database, configuration, HSM dependencies, templates and revocation availability.Read article
- TroubleshootingLDAPS on port 636 not working: how a domain controller picks its certificateAn application cannot connect to Active Directory over LDAPS, LDP fails on port 636, or a renewed certificate is ignored. Check the certificate against the five requirements, see which store the domain controller reads first, and confirm with LDP.Read article
- HostingExpiring certificates and secrets that silently break hosted applicationsHow to inventory TLS certificates, client credentials and application secrets before they lapse in steady-state hosted production—not only after an outage.Read article
Risks and limits
These commands have not been run or lab-tested.
The Microsoft page on 0x800706ba does not name a source for event 82, so filter by ID and read the source column. The Windows Server 2012 policy page is archived. Group, user-right and registry changes apply to the whole CA or the whole organisational unit, and a restart interrupts issuance on a CA. This topic does not cover certificates enrolled through a Certificate Enrollment Web Service or by Intune.
Sources
- Error 0x800706ba during certificate enrollment — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
- Configure Certificate Auto-Enrollment for Network Policy Server — Microsoft Learn, page dated 2025-05-30, accessed 18 November 2026
- Configure the Server Certificate Template for Network Remote Access — Microsoft Learn, page dated 2025-06-17, accessed 18 November 2026
- Configure Group Policy to Autoenroll and Deploy Certificates — Microsoft Learn, page dated 2016-08-31, accessed 18 November 2026
- certutil — Microsoft Learn, page dated 2025-05-01, accessed 18 November 2026
- Get-WinEvent (Microsoft.PowerShell.Diagnostics), PowerShell 5.1 — Microsoft Learn, date not shown, accessed 18 November 2026
- Manage Certificate Stores in Windows Server — Microsoft Learn, page dated 2026-10-02, accessed 18 November 2026
This article was originally published on .