Create a Custom Detection Script for PDF-XChange 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 PDF-XChange Editor using PowerShell.

How to Create a Custom Detection Script for PDF-XChange Editor

PDF-XChange Editor (File Detection Method)

Install the version of PDF-XChange Editor you want to deploy on a test box or VM
- Check out the following posts for further details
  - PDF-XChange Editor Silent Install (How-To Guide)
  - PDF-XChange Editor Install and Uninstall (PowerShell)
Open Windows PowerShell ISE by Right-Clicking on Windows PowerShell ISE and selecting Run as Administrator
Copy the following code into the Windows PowerShell ISE

## Check for PDF-XChange Editor (File Detection Method)
$PDFXEditExe = (Get-ChildItem -Path "C:\Program Files\Tracker Software\PDF Editor\PDFXEdit.exe","C:\Program Files (x86)\Tracker Software\PDF Editor\PDFXEdit.exe" -ErrorAction SilentlyContinue)
$PDFXEditExe.FullName
$PDFXEditPath = $($PDFXEditExe.FullName).Replace("C:\Program Files\","").Replace("C:\Program Files (x86)\","")
$FileVersion = (Get-Item -Path "$($PDFXEditExe.FullName)" -ErrorAction SilentlyContinue).VersionInfo.FileVersion

## Create Text File with PDF-XChange Editor File Detection Method
$FilePath = "C:\Windows\Temp\PDF-XChange_Editor_Detection_Method.txt"
New-Item -Path "$FilePath" -Force
Set-Content -Path "$FilePath" -Value "If([String](Get-Item -Path `"`$Env:ProgramFiles\$PDFXEditPath`",`"`${Env:ProgramFiles(x86)}\$PDFXEditPath`" -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 PDF-XChange Editor Detection Method script required to detect the current version of PDF-XChange Editor that is installed on the device you are running the script from.

Example:

If([String](Get-Item -Path "$Env:ProgramFiles\Tracker Software\PDF Editor\PDFXEdit.exe","${Env:ProgramFiles(x86)}\Tracker Software\PDF Editor\PDFXEdit.exe" -ErrorAction SilentlyContinue).VersionInfo.FileVersion -ge "9.4.362.0"){
Write-Host "Installed"
Exit 0
}
else {
Exit 1
}

Copy the PDF-XChange Editor Detection Method script content into the Custom Detection Rules (Script)
Microsoft Endpoint Manager Configuration Manager (MEMCM / SCCM)
- https://docs.microsoft.com/en-us/mem/configmgr/apps/deploy-use/create-applications#bkmk_detect-script
Microsoft Intune
- https://docs.microsoft.com/en-us/mem/intune/apps/apps-win32-add

PDF-XChange Editor (Registry Detection Method)

Install the version of PDF-XChange Editor you want to deploy on a test box or VM
- Check out the following posts for further details
  - PDF-XChange Editor Silent Install (How-To Guide)
  - PDF-XChange Editor Install and Uninstall (PowerShell)
Open Windows PowerShell ISE by Right-Clicking on Windows PowerShell ISE and selecting Run as Administrator
Copy the following code into the Windows PowerShell ISE

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

## Create Text File with PDF-XChange Editor Registry Detection Method
$FilePath = "C:\Windows\Temp\PDF-XChange_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\$($PDFXEdit.PSChildName)','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$($PDFXEdit.PSChildName)' -Name DisplayVersion -ea SilentlyContinue) -ge '$($PDFXEdit.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 PDF-XChange Editor Detection Method script required to detect the current version of PDF-XChange 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\{6ED73499-76FE-435D-A62F-A2BF9566EBD6}','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{6ED73499-76FE-435D-A62F-A2BF9566EBD6}' -Name DisplayVersion -ea SilentlyContinue) -ge '9.4.362.0') {
Write-Host "Installed"
Exit 0
}
else {
Exit 1
}

Copy the PDF-XChange Editor Detection Method script content into the Custom Detection Rules (Script)
Microsoft Endpoint Manager Configuration Manager (MEMCM / SCCM)
- https://docs.microsoft.com/en-us/mem/configmgr/apps/deploy-use/create-applications#bkmk_detect-script
Microsoft Intune
- https://docs.microsoft.com/en-us/mem/intune/apps/apps-win32-add

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.