Hi All,
I've had some issues getting the ADFS 2.0 Management pack to work at all within my estate.
I have followed the directions from the ADFS 2.0 management pack documentation, as well as the known issues when deploying this management pack as detailed here and have performed these "fixes",
http://scug.be/christopher/2012/03/07/opsmgr-scom-adfs-2-0-mp-discovery-issue/
Which indicates installing the IIS 6 compatibilty components as well as disabling IPv6 on both the RMS and client servers, both of which I have done.
Referencing here for more information. http://blogs.msdn.com/b/card/archive/2010/08/06/announcing-active-directory-federation-services-2-0-management-pack-for-microsoft-system-center-operations-manager-2007.aspx
I have uninstalled the management pack and reinstalled. Stopped/Restarted HealthService on Client and RMS after deleting the "Health Service State"
Updated my client from 2007 R2 CU4 to CU6. My server estate is at 2007 R3 CU4 Level. ADFS artifact DB and configuration DB is SQL, although there doesn't appear to be any options fo r
The clients are showing up as Healthy and the ADFS discovery process appears to execute on the client, with the following two messages.
Microsoft.ActiveDirectoryFederationServices.2.0: Beginning FederationServer discovery : servername.somedomain.com
Microsoft.ActiveDirectoryFederationServices.2.0: End of FederationServer discovery :
There appears to only be a single .ps1 ADFS health script on the client, when compared to the RMS server's Management Pack.
I can't see any of the ADFS classes when using health Explorer, so I believe the issue is related to the client configuration. Could someone please advise what I could try next to validate that these classes are enumerating. I have looked at using the SCOM TraceConfig, however haven't found which would be the relevant components to start tracing.
This is happening for a number of different ADFS servers both proxy and regular federation servers throughout my estate.
At this stage I am looking to create customised ADFS service rules to at least get up/down monitoring, however it is frustrating, as there are a whole other bunch of useful monitoring tools in this "native" management pack.