David Andé

I had the same Issue on 2019 servers. I included this code to delete passive screens: ``` $delpassiveshares= Get-FsrmFileScreen | Select Active, Path, Template | Where-Object { ($_.active -like 'False')...

maybe an issue should be select only shares with type 0. Not 0 and 2147483648 as it is actually. $drivesContainingShares = Get-WmiObject Win32_Share | Select Name,Path,Type | Where-Object { $_.Type...

FRSM role now makes no errors in GPO. no incompatibility anymore.

ok with Nexxai: extension needs to be approved but I also like the idea to manually include even if it needs a real close management

I also don't know how to. just post it here :-)

maybe be adding simply -ErrorAction Stop at the end of cmdlet: $jsonStr = Invoke-WebRequest -Uri https://fsrm.experiant.ca/api/v1/get -ErrorAction Stop

So in this case, to stop the script we have to use Try and Catch. This way if an error occurs, the cmdlet is stopped and It exit the script...

ok so i tried using Catch ``` Try { # Verifying if new crypto extensions available # Invoke-WebRequest https://fsrm.experiant.ca/api/v1/combined -OutFile $wkdir\extensions.txt } Catch { Write-Host Remote extension list Offline -...

works also on 2008 R2

We meet the same problem on our Exchange servers. Impossible to update and we look for a trick to make it works. any idea?