$objFolder = $objShell.namespace($fontFolder) $objShell = New-Object -ComObject Shell.Application $regPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" $errorLabel = "Computer Unavailable".PadRight($padVal," ") $installLabel = "Installing Font".PadRight($padVal," ") $pcLabel = "Connecting To".PadRight($padVal," ") 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.
It does this from the machine where the script executes to mitigate the issue of credential hopping through remote PowerShell sessions. 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. The script will test a connection to each PC in turn. 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 has two parameters: $pcNames and $fontFolder. Why use GPP at all if PowerShell can do the registry entries for me? Goal! I could use PowerShell to populate the registry section of the GPP for me! Genius. I realized the answer was in front of me.
BEST FONT MANAGER WITH PHOTOSHOP INSTALL
However, soon I was back again, needing a quick way to install fonts without messing around.
The whole thing just seemed a bit lacking, so I put it on the back burner. 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.
I had investigated font installs with PowerShell before, but I had never found a method that worked for me. Then when asked to install several more fonts on several more computers, I thought again about using PowerShell. 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.
0 kommentar(er)
