Category filter

Add custom fonts on macOS devices using a configuration profile

The administrator can include newly available fonts and modify the font style of the devices to match their taste. For Mac users, adding custom fonts can be a simple process using a configuration profile. Use Hexnode’s Deploy Custom Configuration feature to remotely push this profile to macOS devices.

Disclaimer:

The sample configuration profiles provided below are created using various profile creator applications.

Note:

This configuration profile is supported on Mac devices running macOS 10.9 and above.

Add custom fonts

To add new fonts on your macOS devices, provide the required content of the font file to the <key>Font</key> key in the below .plist file before pushing it to devices.

The <key>Name</key> key is the font’s name that is visible to the user. However, upon installation, the actual font name will replace it. Only one font file in either TrueType (.ttf) or OpenType (.otf) format can be included in each payload. It’s important to note that collection formats like (.ttc or .otc) are not supported.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>PayloadContent</key>
	<array>
		<dict>
			<key>Font</key>
			<data>base64encodeddata</data>
			<key>Name</key>
			<string>Font.ttf</string>
			<key>PayloadDescription</key>
			<string>Configures Font settings</string>
			<key>PayloadDisplayName</key>
			<string>Fonts</string>
			<key>PayloadIdentifier</key>
			<string>com.apple.font.99659c06-bbbf-45aa-9674-06b378ec2cd5</string>
			<key>PayloadType</key>
			<string>com.apple.font</string>
			<key>PayloadUUID</key>
			<string>99659c06-bbbf-45aa-9674-06b378ec2cd5</string>
			<key>PayloadVersion</key>
			<integer>1</integer>
		</dict>
	</array>
	<key>PayloadDisplayName</key>
	<string>Fonts</string>
	<key>PayloadIdentifier</key>
	<string>macOS.FC6A36B6-9895-459E-AA19-CFCB210773EB</string>
	<key>PayloadType</key>
	<string>Configuration</string>
	<key>PayloadUUID</key>
	<string>0719760D-FC25-4C26-877A-0D994DE92512</string>
	<key>PayloadVersion</key>
	<integer>1</integer>
</dict>
</plist>

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>PayloadContent</key>

<array>

<dict>

<data>base64encodeddata</data>

<key>PayloadDescription</key>

<string>Configures Font settings</string>

<key>PayloadDisplayName</key>

<string>Fonts</string>

<key>PayloadIdentifier</key>

<string>com.apple.font.99659c06-bbbf-45aa-9674-06b378ec2cd5</string>

<key>PayloadType</key>

<string>com.apple.font</string>

<key>PayloadUUID</key>

<key>PayloadVersion</key>

</dict>

</array>

<key>PayloadDisplayName</key>

<string>Fonts</string>

<key>PayloadIdentifier</key>

<string>macOS.FC6A36B6-9895-459E-AA19-CFCB210773EB</string>

<key>PayloadType</key>

<string>Configuration</string>

<key>PayloadUUID</key>

<key>PayloadVersion</key>

</dict>

</plist>

Notes:

To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
Ensure that you do not associate conflicting configurations with the devices.
Use wildcards to fetch key values from the portal.
It is recommended to manually validate the configuration profile on a system before executing it in bulk.
Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

Need more help?

Raise a Ticket

Ask Community

Chat With us