Create a Custom Detection Script for Flameshot (PowerShell)


Microsoft Endpoint Manager Configuration Manager (MEMCM / SCCM) and Microsoft Intune use Detection Rules to determine the presence of Applications & Win32 Apps. The detection rules ensure that application installations only begin to run if the application is not already installed on the device. This article will serve as an informative guide and give you a clear understanding of how to create an updated custom detection script for each new version of Flameshot using PowerShell.

How to Create a Custom Detection Script for Flameshot

Flameshot (File Detection Method)

## Check for Flameshot (File Detection Method)
$FlameshotExe = (Get-ChildItem -Path "C:\Program Files\Flameshot\bin\flameshot.exe","C:\Program Files (x86)\Flameshot\bin\flameshot.exe" -ErrorAction SilentlyContinue)
$FlameshotExe.FullName
$FlameshotPath = $($FlameshotExe.FullName).Replace("C:\Program Files\","").Replace("C:\Program Files (x86)\","")
$FileVersion = (Get-Item -Path "$($FlameshotExe.FullName)" -ErrorAction SilentlyContinue).VersionInfo.FileVersion

## Create Text File with Flameshot File Detection Method
$FilePath = "C:\Windows\Temp\Flameshot_Detection_Method.txt"
New-Item -Path "$FilePath" -Force
Set-Content -Path "$FilePath" -Value "If([String](Get-Item -Path `"`$Env:ProgramFiles\$FlameshotPath`",`"`${Env:ProgramFiles(x86)}\$FlameshotPath`" -ErrorAction SilentlyContinue).VersionInfo.FileVersion -ge `"$FileVersion`"){"
Add-Content -Path "$FilePath" -Value "Write-Host `"Installed`""
Add-Content -Path "$FilePath" -Value "Exit 0"
Add-Content -Path "$FilePath" -Value "}"
Add-Content -Path "$FilePath" -Value "else {"
Add-Content -Path "$FilePath" -Value "Exit 1"
Add-Content -Path "$FilePath" -Value "}"
Invoke-Item $FilePath

Example:

If([String](Get-Item -Path "$Env:ProgramFiles\Flameshot\bin\flameshot.exe","${Env:ProgramFiles(x86)}\Flameshot\bin\flameshot.exe" -ErrorAction SilentlyContinue).VersionInfo.FileVersion -ge "12.1.0"){
Write-Host "Installed"
Exit 0
}
else {
Exit 1
}

Flameshot (Registry Detection Method)

## Check for Flameshot (Registry Detection Method)
$Flameshot = Get-ChildItem -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall","HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall" | Get-ItemProperty | Where-Object {$_.DisplayName -like 'Flameshot*' } | Select-Object -Property DisplayName, DisplayVersion, PSChildName
$Flameshot.DisplayVersion
$Flameshot.PSChildName

## Create Text File with Flameshot Registry Detection Method
$FilePath = "C:\Windows\Temp\Flameshot_Detection_Method.txt"
New-Item -Path "$FilePath" -Force
Set-Content -Path "$FilePath" -Value "If([Version](Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$($Flameshot.PSChildName)','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$($Flameshot.PSChildName)' -Name DisplayVersion -ea SilentlyContinue) -ge '$($Flameshot.DisplayVersion)') {"
Add-Content -Path "$FilePath" -Value "Write-Host `"Installed`""
Add-Content -Path "$FilePath" -Value "Exit 0"
Add-Content -Path "$FilePath" -Value "}"
Add-Content -Path "$FilePath" -Value "else {"
Add-Content -Path "$FilePath" -Value "Exit 1"
Add-Content -Path "$FilePath" -Value "}"
Invoke-Item $FilePath
  • Click Run Script (F5)
  • A text file will open with the Flameshot Detection Method script required to detect the current version of Flameshot that is installed on the device you are running the script from.

Example:

If([Version](Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EBC7D3FB-4ED6-4EF4-ADD0-5695E6716C8B}','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{EBC7D3FB-4ED6-4EF4-ADD0-5695E6716C8B}' -Name DisplayVersion -ea SilentlyContinue) -ge '12.1.0') {
Write-Host "Installed"
Exit 0
}
else {
Exit 1
}

Always make sure to test everything in a development environment prior to implementing anything into production. The information in this article is provided “As Is” without warranty of any kind.

Recent Posts