


The basis of this protocol is the client/server model, which means data is packaged and distributed through this communication technology to other processes that do not exist on the same process (computer). It’s basically a technology that utilises a communication technique called inter-processing, which is used for enabling a server and client PC to communication with one another over a network. RPC is an abbreviation of the words Remote Procedure Call. Here is a screenshot of part of the log: Īny help/suggestions would be greatly appreciated.This article presents an overview of the RPC server as well as how to effectively resolve the RPC server is unavailable error.īefore you can fully understand the function(s) of the RPC server, you will first need to know what an RPC is, such as its attributes and importance. There is still a lot of data and I'm not seeing anything obvious that shows failure to enroll. 6-.7 seconds worth of data in procmon during reproducing this error and have filtered out the success messages. The response has a ReturnValue of ERROR_ACCESS_DENIED which leads me to believe it's permissions but I cannot narrow this down. I used wireshark to capture a packet of the certification wizard request and I can see that there is a DCOM:RemoteCreateInstance Request and then a DCOM:RemoteCreateInstance Response. I have followed the instructions on setting up permissions properly for DCOM from links such as:

I am able to run certutil -ping PRD-ROOT-CA successfully. This same error occurs even when I try to request a certificate on the Root CA itself. Here is the more specific error from eventvwr: Certificate enrollment for Local system failed to enroll for a SCCMClient certificate with request ID N/A from \Enterprise-Root (The RPC server is unavailable. When trying to manually enroll or auto enroll, I get an error saying the RPC server is unavailable. The enterprise root CA is Windows 2008 R2 for my server. I have a Windows 7 test machine for my client.
