The Preference Manifests node lists applications and settings that you can manage using preference manifests. Policy items contained in this node are specific to the Macintosh operating system. A preference manifest is a file that describes application settings and makes them manageable. Application developers create preference manifest files to make their application’s settings available for management through the Preference Manifests node.
When you install Group Policy console extensions, it creates preference manifests in sysvol at the following location:
Policies\Quest Software\Preference Manifest
In order to reduce GPO size, Preference Manifest files are stored in the GPT under the Policies\Quest Software\Preference Manifest folder. All of the Preference Manifest files found there are displayed in the Preference Manifests node. If the folder does not exist in the GPT, Preference Manifest files are loaded from the local installation directory.
Apple provides preference manifests for many built-in applications and systems. Group Policy includes preference manifests for Microsoft Office applications and other common third-party applications. You can also import custom preference manifests for policy configuration. The Safeguard Authentication Services installation process adds macOS, Workgroup Manager, and Preference Manifest Settings nodes to both the Computer Configuration and User Configuration nodes and stores all the Safeguard Authentication Services for macOS Desktop policies there.
Adding a preference manifest
You can add a preference manifest file to the Preference Manifests node in Group Policy Object Editor (GPOE)
To add a preference manifest
- Right-click on the Preference Manifests node and select Add/Remove Preference Manifests from the menu.
The Add/Remove Preference Manifest dialog is displayed.
- Click Add to browse for the preference manifest file that you want to load.
- Click Load Defaults to reset the list to the default set of preference manifests.
- Click Remove to remove the selected preference manifests.
- Click OK to save changes and close the Add/Remove Preference Manifest dialog.
The Preference Manifest view is updated to reflect the changes.
Certificate Autoenrollment is a feature of Safeguard Authentication Services based on Microsoft Open Specifications. Certificate Autoenrollment allows macOS/macOS® clients to take advantage of existing Microsoft infrastructure to automatically enroll for and install certificates. Certificate policy controls which certificates are enrolled and what properties those certificates will have.
With Certificate Autoenrollment, a public/private key pair is automatically generated according to certificate template parameters defined in Group Policy. The public key is sent to the Certification Authority (CA), and the CA responds with a new certificate corresponding to the public key, which is installed along with the private key into the appropriate system or user keychain on the Mac client.
You can use Group Policy to automatically configure which certificate enrollment policy servers to use for Certificate Autoenrollment and to periodically run Certificate Autoenrollment.
This section explains the system requirements for Certificate Autoenrollment and walks you through policy setup as well as client-side usage and troubleshooting.
Most of the Certificate Autoenrollment code is implemented in Java. After this code has successfully requested a certificate from a CA, it invokes platform-specific code to store the private key and certificate in a suitable way for the operating system or for particular applications. This platform-specific code is implemented as a shell script, certstore.sh, in the /var/opt/quest/vascert/script directory.
The certstore.sh script is a platform-agnostic front end that chooses and loads a platform-specific back end script. For macOS, the back end script is certstore-mac.sh. This script provides a fully functional implementation that uses the /usr/bin/security tool to integrate with macOS keychains.