I am curious about this as well.
Stuart, Mpeller ..
I think you will periodically encounter this line in the log file when you come accross a server which has other cryptography settings turned on outside of the standard defualt windows install. This is the RSCD agent checking to see if windows has been told via its local security policy (LocalPolices>Security Options>System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing) to use FIPS compliant algorithums for encrytion.
Now when this option is set to "Enabled" in the local policy it basically tells certain applications on the OS that they must use a minimal encryption type to conform to FIPS standards (Like TLS 1.0).
Becuase the RSCD agent is in effect an application i guess its pre-programmed to check for this setting, and i would assume if it detects its enabled i guess it would change the way it works or just fail. hence why we are seeing it in a log and it states "Not Enabeld".
We have to remember that FIPS is an american standard, and that i guess the RSCD agent has been devleoped to meet those standards so that log file entry may not apply to our UK application of the RSCD agent.
Hope this spreads some light, be intersted to see the log file when FIPS is enabeld!.
Thanks very much for the information. I'll check the local policy settings of these servers which are failing so see what the System Cryptography options are set to and go from there.