As with all automated systems, many assumptions are made about the environment in which the system is operating. When these assumptions no longer hold true, the system fails to operate as expected. Compliance settings management is an automated system and therefore operates on certain assumptions. When issues arise, troubleshooting is necessary to determine which assumption or assumptions are no longer true.

Troubleshooting compliance settings, like the rest of ConfigMgr, is largely a log file review exercise. Because compliance settings evaluation is a client activity, the logs for compliance setting processing are on the client in the client logs folder (%SystemRoot%\CCM\Logs). Five log files are used by compliance settings ...

Get System Center 2012 Configuration Manager Unleashed now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.