Quantcast
Channel: Security forum
Viewing all articles
Browse latest Browse all 12072

How to register a custom policy module for AD CS

$
0
0

Hi

I migrated an enterprise CA from Windows Server 2003 to Windows Server 2008 R2 und migrated also from CLM 2007 to FIM 2010 CM.

We had a custom policy module running on the old server and i want to run it on the new server too. Unfortunately, I could not find any documentation, about how to register a policy module for AD CS on Windows Server 2008 R2.

The policy module was a .NET 2.0 dll and my predecessor documented, that he used RegAsm.Exe to register the dll on the server. Copying the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration\[CAName]\PolicyModules\CLM.Policy (just the key name is different from the original key) was also necessary. After restarting the certificate service, the policy module used to show up in the list of available policy modules.

I compiled the policy module with .NET 4.0, because it uses FIM DLLs, that are compiled with .NET 4.0. I could register the DLL with RegAsm.exe, and i also modified the registry according to our documentation. The policy module however still doesn't show up.

Is there any documentation available about how to correctly register a DLL as a policy module or what compile options need to be set in Visual Studio?

I've already looked up on MSDN about policy modules, but it's not much more than how policy modules work in general and a brief documentation about the interfaces, that need to be implemented.

These are the main sources, where I found info about policy modules:

http://msdn.microsoft.com/en-us/library/aa376540.aspx
http://msdn.microsoft.com/en-us/library/aa387348.aspx
http://msdn.microsoft.com/en-us/library/aa388216%28v=vs.85%29

Thanks and Regards,
Gabriel


Viewing all articles
Browse latest Browse all 12072

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>