Get Live Help
The Wireless Profiles tab settings control user options associated with wireless networks.
To add wireless profiles
Click the Up or Down buttons to reorder the wireless profiles.
Wireless profiles are added to the user profiles list on Mac OS X systems in the order listed in the policy.
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 Authentication Services installation process adds Mac OS X, Workgroup Manager, and Preference Manifest Settings nodes to both the Computer Configuration and User Configuration nodes and stores all the Authentication Services for Mac OS X Desktop policies there.
You can add a preference manifest file to the Preference Manifests node in Group Policy Object Editor (GPOE)
To add a preference manifest
The Add/Remove Preference Manifest dialog is displayed.
The Preference Manifest view is updated to reflect the changes.
Certificate Autoenrollment on Mac OS X/macOS
Certificate Autoenrollment requirements and setup
Java requirement: Unlimited Strength Jurisdiction Policy Files
Installing certificate enrollment web services
Configuring Certificate Services Client - Certificate Enrollment Policy
Configuring Certificate Services Client - Auto-Enrollment Group Policy
Configuring Certificate Templates for Auto-enrollment
Using Certificate Autoenrollment
Configuring Certificate Autoenrollment manually
Trigger machine-based Certificate Autoenrollment
Troubleshooting Certificate Auto-Enrollment
Enable debug logging on Windows
Pulse Certificate Autoenrollment processing
Certificate Autoenrollment is a feature of Authentication Services 4.1 based on Microsoft Open Specifications. Certificate Autoenrollment allows Mac OS X/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.