Installation of fonts without admin rights

[Guest MD5T]

You can do this through sccm if you use it.

 

I can dig out batch script if so

[Jewel11]

If it is a very tight security environment I doubt you will be able to run a random script. You'd be better off looking at implementing web fonts (can't remember the exact term) so you don't need to install the fonts.

 

I do need the downloaded files to be able to create prototypes in Photoshop. But I see what you're saying, I probably would not be able to do it myself. I was hoping to understand more about the script to relay to IT, they can be quite hard to deal with.

[Arthur]

Is there a way to allow staff to install fonts without admin rights?

Give them all Macs?

 

It's a shame Microsoft didn't copy OS X and create a user-specific font folder like ~/Library/Fonts where they don't need admin rights.

[Jewel11]

Give them all Macs?

 

It's a shame Microsoft didn't copy OS X and create a user-specific font folder like ~/Library/Fonts where they don't need admin rights.

 

Ahh I wish so badly this was the case. I've tried to make the case for a Mac but am constantly thwarted by IT because they don't want to support it

[Arthur]

I'm not having much luck with the script at the moment... It copies the file over but doesn't do the install. I'll keep playing.

I'm not sure if you eventually discovered this, but when installing fonts under the local SYSTEM account with 'Shell.Application', the file extension gets removed preventing Windows from installing the font.

 

More details on why this happens: https://beingwinsysadmin.blogspot.com/2017/11/powershell-installing-fonts-hard-way.html (it's a feature, not a bug! )

 

Here's a working PowerShell script (based on the script in the linked article)...

 

$Shell = New-Object -ComObject Shell.Application
ForEach ($Font in $Shell.Namespace($PSScriptRoot).Items()) {

   $FileName = [iO.Path]::GetFileName($Font.Path)

   if ($FileName -match '\.(ttf|otf|pfm|fon)$') {

       if (-not(Test-Path ($env:windir + "\Fonts\" + $FileName) -ErrorAction SilentlyContinue)) {

           $Font.InvokeVerbEx("Install")

       }

   }

}

Edited November 27, 2017 by Arthur

[mavhc]

Is the bug that you're using Shell.Items, not get-childitem?

[Arthur]

Is the bug that you're using Shell.Items, not get-childitem?

How would you do the "InvokeVerbEx" bit with Get-ChildItem?

 

Just copying the fonts into the Windows fonts folder isn't the correct way of installing fonts.

[mavhc]

Good point, I guess you'd have to call GetFolderItem with the path from get-childitem, at which point the parsing of the path is about as easy

[internetuser]

Does this still work with 1809 after MS change things for fonts ?

[mavhc]

What changed in 1809? In 1903 you can drag and drop fonts into Settings to install them, I think for standard users

[Arthur]

What changed in 1809?

www.edugeek.net/forums/windows-10/197576-non-admin-font-installation-windows-10-new-feature-v1809.html