Robert Pearman
Latest posts by Robert Pearman (see all)
- Specops Key Recovery: Self-service for unlocking BitLocker-encrypted devices - Thu, Oct 24 2019
- Automating Remote Desktop Services certificate installation with PowerShell - Thu, Sep 5 2019
- Conditional Access in Office 365 - Wed, Jul 10 2019
Many of my clients work in creative industries, so a regular task for us is to install fonts. These fonts might be licensed on a per-machine basis or simply used for only one project and never seen again. This makes it difficult or essentially impractical to build a machine with all the required fonts already installed.
So when a new project starts, or more likely the last minute before several machines head out to give important presentations, you may need to install 50 fonts on 10 machines! But the users have no time for you to log on to their PCs and install the fonts.
Over the years, I have put together what we will generously call some "solutions" to this problem. The most recent was so labor intensive, it was probably more effort than that saved by walking to each individual computer with a pen drive containing the font files.
I speak of course of the Group Policy Preference (GPP) settings. Installing a font with a GPP is quite easy. You can set the font file to copy from a source folder to the C:\Windows\Fonts folder, and in the same GPP, set up the relevant registry key. After a reboot, the font is available for use.
However, as you can see from the two example images, managing multiple font installs using this method (having to create each registry item) is time consuming.
Then when asked to install several more fonts on several more computers, I thought again about using PowerShell. I had investigated font installs with PowerShell before, but I had never found a method that worked for me. I don't remember every example of what I tried, but I do recall one that tried to force the User Account Control (UAC) elevation prompt via PowerShell. The whole thing just seemed a bit lacking, so I put it on the back burner. However, soon I was back again, needing a quick way to install fonts without messing around.
I realized the answer was in front of me. I could use PowerShell to populate the registry section of the GPP for me! Genius.
No—wait. Why use GPP at all if PowerShell can do the registry entries for me? Goal!
So I present to you Font-Install.ps1. The script has two parameters: $pcNames and $fontFolder.
The $pcNames array will accept a list of PC Names, and $fontFolder (as the name suggests) is a string that should contain a Uniform Naming Convention (UNC) path to where the script can find the font files themselves.
The script will test a connection to each PC in turn. It will copy each font file it finds available on the network from the $fontFolder to the C:\Windows\Fonts folder on the PC using the admin $ share. It does this from the machine where the script executes to mitigate the issue of credential hopping through remote PowerShell sessions.
It then processes each font file for the font name (which is not always the same as the file name) and creates a registry entry for that font using Invoke-Command.
This is the full script:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 | param( [Parameter(Mandatory=$true,Position=0)] [ValidateNotNull()] [array]$pcNames, [Parameter(Mandatory=$true,Position=1)] [ValidateNotNull()] [string]$fontFolder ) $padVal = 20 $pcLabel = "Connecting To".PadRight($padVal," ") $installLabel = "Installing Font".PadRight($padVal," ") $errorLabel = "Computer Unavailable".PadRight($padVal," ") $openType = "(Open Type)" $regPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" $objShell = New-Object -ComObject Shell.Application if(!(Test-Path $fontFolder)) { Write-Warning "$fontFolder - Not Found" } else { $objFolder = $objShell.namespace($fontFolder) foreach ($pcName in $pcNames) { Try{ Write-Output "$pcLabel : $pcName" $null = Test-Connection $pcName -Count 1 -ErrorAction Stop $destination = "\\",$pcname,"\c$\Windows\Fonts" -join "" foreach ($file in $objFolder.items()) { $fileType = $($objFolder.getDetailsOf($file, 2)) if(($fileType -eq "OpenType font file") -or ($fileType -eq "TrueType font file")) { $fontName = $($objFolder.getDetailsOf($File, 21)) $regKeyName = $fontName,$openType -join " " $regKeyValue = $file.Name Write-Output "$installLabel : $regKeyValue" Copy-Item $file.Path $destination Invoke-Command -ComputerName $pcName -ScriptBlock { $null = New-ItemProperty -Path $args[0] -Name $args[1] -Value $args[2] -PropertyType String -Force } -ArgumentList $regPath,$regKeyname,$regKeyValue } } } catch{ Write-Warning "$errorLabel : $pcName" } } } |
Join the 4sysops PowerShell group!
Your question was not answered? Ask in the forum!
This is something I have been looking for, I had a similar experience when searching for solution. What I will do with this is first test this in my environment, but then once I know my environment doesn't break it, I will modify it to be used with SCCM. this will overcome the inherent limitation` of targeting workstations with Invoke-command, because the user has shutdown their workstation. With SCCM the job will just wait for the user to come on line and optionally require a reboot. Great work!
Will it do postscript fonts as well?
Only tested True Type and Open Type, both of which appeared as True Type. If you manually install one, go into the fonts folder and open it up what does it show as the title in the menu bar?
It just shows the font name. i.e. Akzidenz Grotesk BE Cn
File properties shows:
GFBC___.PFM
Type 1 Font file (.PFM)
Not sure if that helps or not. ;P
We currently use the following solution
set MyDir=\\YourShare\YourFonts
set MyFonts=*.otf [or *.ttf]
set LocalFontDir=%SystemRoot%\Fonts
for /f %%i in ('dir /b %MyDir%\%MyFonts%') do (
if not exist %LocalFontDir%\%%i cscript.exe %~dp0CopyFont.vbs %MyDir%\%%i
)
We are looking for a PowerShell-replacement.
Sorry, obviously the vbs part was missing in my first post:
Dim MyFont
If WScript.Arguments.Count > 0 Then MyFont = WScript.Arguments(0) Else WScript.Quit
'Debugging MsgBox "Now Copying " & MyFont & " to " & FONTS
Const FONTS = &H14&
Set objShell = CreateObject("Shell.Application")
Set objFolder = objShell.Namespace(FONTS)
objFolder.CopyHere MyFont
Set objFolder = nothing
Set objShell = nothing
Broken in W10 1809; Will only install for the Admin user that performs the install, not for all users.
Did you logoff or restart after the font install? That seems to be necessary in my Windows 10 testing, before the font will show itself to all users.
I use the following code to install Fonts on remote PCs, no need to logoff or reboot. Tested on 1909.
Incredible help as part of a larger install script I wrote today, thanks so much!
Ian Manning, would you be willing to share your script with us?
Thx a lot for your help with this script. I just have one question.
Why he stop processing at the "conneting to" and don't go to "Installing Font"
Hi Rob, any solution for Windows 10 1809 ? Not sure if you have any working script for install fonts on Windows 10 1809.
Thanks in advance.
Has anyone managed to make this work through Powershell since 1809 was released? The copyhere method I used to use is not working through Intune.
Just to mention, in the end I wrote a basic script that used 'copy-item' for each font straight into the system fonts folder and added a registry key into the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts. I put this in a for loop to install any .ttf fonts found in a certain folder and it worked when deployed through Intune in a cloud only environment.
Hi, when running the script I keep receive the error " Computer unavailable" but I able to ping the computer