Create a Custom Detection Script for Zeta Resource Editor (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 Zeta Resource Editor using PowerShell.

How to Create a Custom Detection Script for Zeta Resource Editor

Zeta Resource Editor (File Detection Method)

## Check for Zeta Resource Editor (File Detection Method)
$ZetaResourceEditorExe = (Get-ChildItem -Path "C:\Program Files\Zeta Resource Editor\ZetaResourceEditor.exe" -ErrorAction SilentlyContinue)
$ZetaResourceEditorExe.FullName
$ZetaResourceEditorPath = $($ZetaResourceEditorExe.FullName).Replace("C:\Program Files\","")
$FileVersion = (Get-Item -Path "$($ZetaResourceEditorExe.FullName)" -ErrorAction SilentlyContinue).VersionInfo.FileVersion

## Create Text File with Zeta Resource Editor File Detection Method
$FilePath = "C:\Windows\Temp\Zeta_Resource_Editor_Detection_Method.txt"
New-Item -Path "$FilePath" -Force
Set-Content -Path "$FilePath" -Value "If([String](Get-Item -Path `"`$Env:ProgramFiles\$ZetaResourceEditorPath`" -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
  • Click Run Script (F5)
  • A text file will open with the Zeta Resource Editor Detection Method script required to detect the current version of Zeta Resource Editor that is installed on the device you are running the script from.

Example:

If([String](Get-Item -Path "$Env:ProgramFiles\Zeta Resource Editor\ZetaResourceEditor.exe" -ErrorAction SilentlyContinue).VersionInfo.FileVersion -ge "2.3.33.0"){
Write-Host "Installed"
Exit 0
}
else {
Exit 1
}

Zeta Resource Editor (Registry Detection Method)

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

## Create Text File with Zeta Resource Editor Registry Detection Method
$FilePath = "C:\Windows\Temp\Zeta_Resource_Editor_Detection_Method.txt"
New-Item -Path "$FilePath" -Force
Set-Content -Path "$FilePath" -Value "If([Version](Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$($ZetaResourceEditor.PSChildName)','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$($ZetaResourceEditor.PSChildName)' -Name DisplayVersion -ea SilentlyContinue) -ge '$($ZetaResourceEditor.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 Zeta Resource Editor Detection Method script required to detect the current version of Zeta Resource Editor that is installed on the device you are running the script from.

Example:

If([Version](Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ZetaResourceEditor','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ZetaResourceEditor' -Name DisplayVersion -ea SilentlyContinue) -ge '2.3.33.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.