A couple weeks ago I played with the FSLogix Java Rule Editor beta and posted a review (FSLogix Delivers Simple Java Version Management).
I wanted to go back and take a look at the font management piece, but instead of just doing a review I thought I’d do a quick guide to setting up font management rules.
One great application of this would be for licensed fonts, so that you can make sure that you are not exceeding your license count. You would use the “Manage Assignments” function in the RuleEditor to configure a policy for the font and deploy the font to everyone and use the rule to only allow a certain subset of users to be able to see the font.
Just as an example, you could pay anywhere from $25 to $100 per font, per user or more. You can purchase fonts on many different sites, and get licenses that are from 1 user per font to 5 users or more, but in either case it can get very expensive.
The font functionality is part of the main FSLogix Apps RuleEditor. I had not installed this previously as the Java piece is standalone, so I went ahead and ran through this quickly. The install only takes about 15 seconds. Have to love something that provides very useful functionality in such a small footprint.
Here is what you need to do to setup a rule for a font.
For this walkthrough, I am going to hide the Consolas font. If you are following this guide, you can simply replace any font file references with the font you want to hide.
1. Click File → New.
- This will open a save dialog in the “FSLogix Rule Sets” folder
- Type in a name for your rule and click save. I called mine “Hide Consolas Font”
2. Another window will open with some choices. Just select “Blank Rule Set” and click “Ok”.
3. The Rule Editor should now contain the new entry on the left.
4. In the toolbar, click the plus sign on the right side.
5. This will open the “Add Rule” dialog.
6. From the drop-down select “Hiding Rule” and click the folder icon on the right, and click “File”.
7. In the window that opens, browse to the font file.
- Fonts are located in “C:\Windows\Fonts”
- The Consolas font has 4 files.
- You need to add a hide entry for each of them.
- Repeat step 4-7 for each file associated with the font
Note: Due to how Windows handles security with the Fonts folder, you may run into a situation where adding the font file will give you a permissions error while trying to access “C:\Windows\Fonts”. The FSLogix team is working on finding the best way to handle this, but for now, if you do run into this error you can still complete the configuration by opening “C:\Windows\Fonts” using Windows Explorer, note the name(s) of the font file(s) (including file extension) and manually enter the path for each file in the “Object Name:” field of the “Add Rule” dialog box, step 5 above. Example: C:\Windows\Fonts\FontName.ttf ← Replace “FontName.ttf” with the name of the font file.
8. When you’re done the RuleEditor window should look like this.
9. Click File → Save.
10. Now I can test it by clicking the check mark icon in the toolbar.
- This option enables the rule for all users on the local machine. After testing, you can just toggle it to disable the rule again.
11. The rule is applied and I can open the fonts window in Notepad and check to verify. You can see in the screenshot below, that the “Consolas” font is no longer available.
That’s all there is to it. At this point you can take the rule and deploy it per your organizational requirements.