CEM troubleshooting

When you’re having issues with Puppet Compliance Enforcement Modules (CEM) for Linux or Windows, check for common configuration and dependency issues.

Version and installation information

CEM version: Latest
OS: Linux, Windows

Solution

For both CEM for Linux and CEM for Windows

To avoid issues:

• Verify that you are using a supported OS and version for Linux or for Windows.

• If you’re using CEM for Windows, using the puppetlabs-dsc module with the autogenerated DSC module used by CEM for Windows causes issues. Check for dependency issues in your Puppetfile.

• Verify that you’ve downloaded a Forge premium content token and configured it via your Puppetfile using Hiera data.

• If you need to customize your installation, make sure that your configuration is correct. See examples for Linux and examples for Windows.

• CEM relies on files in the data directory within the module to function. Make sure you leave the files in this directory unchanged.

For CEM for Linux

To avoid issues:

• When CEM for Linux identifies an issue, remember to run tasks and plans to audit and query them so that you can investigate and fix them.

• CEM for Linux disables SSH root login and password by default. You can use the module’s reference information to either re-enable SSH root login and password or configure another SSH method.

For CEM for Windows

To avoid issues:

• CEM for Windows disables local account RDP by default. You can either domain join to use RDP or re-enable local account RDP as a top-level configuration option in Hiera.