Hello Arya Abdul Azis,
The problem likely lies in one of three areas: the template was not added to the CA, the client lacks the exact permissions, or there is an Active Directory replication delay.
First, verify the template is truly published to the CA. On the CA server, open the Certification Authority console, expand your server, and right-click Certificate Templates. Select New > Certificate Template to Issue. Your template should appear in this list. If it's not there, you have only created the template object in Active Directory but have not authorized the CA to issue it. Add it now.
Next, examine the template's security with precision. Merely adding "Domain Computers" is insufficient if the template has specific requirements. Open Certificate Templates console (run certtmpl.msc), double-click your template, and go to the Security tab. Ensure the client computer's specific machine account (e.g., CLIENT-SERVER$) or a group containing it has both Read and Enroll permissions. Avoid using "Autoenroll" unless required. Also, check the Issuance Requirements tab; if CA certificate manager approval is checked, the request will pend and not issue immediately.
Then, confirm the template's compatibility. In the same properties window, go to the General tab. If the Template display name shows a version like "Windows Server 2016" or later, your client server's OS must meet that minimum. A template configured for a newer OS version will not appear on an older client. Additionally, for an ADFS service certificate, the template must be of type Computer (or custom) and should include the Subject Alternative Name extension, often critical for ADFS.
If the above checks pass, force Active Directory replication. The template information is stored in the Configuration partition and may not have replicated to the domain controller your client is using. On the CA server, open an administrative command prompt and run: repadmin /syncall /A /e
Wait a few minutes, then restart the Certificate Services service on the CA with net stop certsvc and net start certsvc.
On the client server, clear its certificate enrollment cache. Open an elevated command prompt and run: certutil -pulse
Then, attempt to request the certificate again using the Certificates MMC snap-in for the Computer account (not the user account). If the template still does not appear, query the CA directly from the client to list available templates: certutil -template -config "CA_SERVER_NAME\CA_NAME"
Replace with your CA's details. This command will show all templates the CA is authorized to issue to this client based on its permissions.
For ADFS, after obtaining the certificate, you must bind it to the ADFS service using the Set-AdfsSslCertificate PowerShell cmdlet. Ensure the certificate's subject or SAN matches the ADFS service name.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to ACCEPT ANSWER then. Should you have more questions, feel free to leave a message. Have a nice day!
VPHAN