Return to contents
This article originates from the Security Forum discussion from 2008 R2 CA not using static DCOM port
Kurt L Hudson MSFT edited Revision 7. Comment: Reworked the article based on Senior Developer comments and PFE questions
Ed Price MSFT edited Revision 6. Comment: Updated title to cap standards.
Kurt Hudson MSFT edited Revision 5. Comment: Expanded tags
Kurt Hudson MSFT edited Revision 3. Comment: changed command font to tahoma, marked UI interfaces appropriately bolded UI text
Kurt Hudson MSFT edited Revision 2. Comment: Updated navigation with TOC and links to subsections.
Kurt Hudson MSFT edited Revision 1. Comment: Continuing with updates - mostly formatting
Kurt Hudson MSFT edited Original. Comment: further updates
Some details were not included here from the original thread:
1) You may not be able to edit the properties of "CertSrv Request" by default, since the registry key may be owned by "Trusted Installer". In this case, you need to take ownership of HKLM\SOFTWARE\Classes\AppID\{D99E6E74-FC88-11D0-B498-00A0C90312F3} and grant Administrators full control to the registry key
2) After making these changes, the specified port will not be open on the certificate server until the RPC is requested by a client
Revision: edited tags