Last updated at 2016-12-20 14:32:11 by oucs0162
Differences between revisions 2 and 5 (spanning 3 versions)
Revision 2 as of 2016-12-20 13:02:16
Size: 524
Editor: oucs0162
Comment:
Revision 5 as of 2016-12-20 14:32:11
Size: 816
Editor: oucs0162
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= How to deploy fonts using Orchard = ## page was renamed from ITSS/Fonts
= How we package fonts for Orchard using AutoPkg =
Line 5: Line 6:
== Packaging fonts using AutoPkg == In order to install additional fonts on Orchard Macs we use AutoPkg to generate a package of
Line 11: Line 12:
== Allocating fonts using munki manifests == == Step 2: Allocate fonts using munki manifests ==
Line 17: Line 18:
=== What to do if Sites need different versions of the same font == === What to do if Sites need different versions of the same font ===
Line 22: Line 23:


Orchard administrators may be interested in how manifests are used to deploy licensed fonts to different sites. As this contains some back-end information it is protected.

How we package fonts for Orchard using AutoPkg

In order to install additional fonts on Orchard Macs we use AutoPkg to generate a package of

Payload dirs .pkg.recipe Check package (Suspicious Package)

Step 2: Allocate fonts using munki manifests

** Currently not available to Orchard Tools For ITSS customers ** manifests manana

What to do if Sites need different versions of the same font

Limitations

Fonts not removed if device moves Site (probably due to human error) Potentially use autoremove or managed_uninstalls keys

Orchard administrators may be interested in how manifests are used to deploy licensed fonts to different sites. As this contains some back-end information it is protected.


Orchard is a close co-operation of