Create a Custom Detection Script for Microsoft Office 2003 Web Components (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 Microsoft Office 2003 Web Components using PowerShell.

How to Create a Custom Detection Script for Microsoft Office 2003 Web Components

Microsoft Office 2003 Web Components (Registry Detection Method)

• Install the version of Microsoft Office 2003 Web Components you want to deploy on a test box or VM
  • Check out the following posts for further details
    • Microsoft Office 2003 Web Components Silent Install (How-To Guide)
    • Microsoft Office 2003 Web Components 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 Microsoft Office 2003 Web Components (Registry Detection Method)
$OWC = Get-ChildItem -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall","HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall" | Get-ItemProperty | Where-Object {$_.DisplayName -match 'Microsoft Office 2003 Web Components' } | Select-Object -Property DisplayName, DisplayVersion, UninstallString
$OWC.DisplayVersion
$GUID = $OWC.UninstallString -replace 'MsiExec.exe /I', '' -replace 'MsiExec.exe /X', ''

## Create Text File with Microsoft Office 2003 Web Components Registry Detection Method
$FilePath = "C:\Windows\Temp\Office_2003_Web_Components_Detection_Method.txt"
New-Item -Path "$FilePath" -Force
Set-Content -Path "$FilePath" -Value "If([Version](Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$($GUID)','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$($GUID)' -Name DisplayVersion -ea SilentlyContinue) -ge '$($OWC.DisplayVersion)') {"
Add-Content -Path "$FilePath" -Value "Write-Host `"Installed`""
Add-Content -Path "$FilePath" -Value "}"
Invoke-Item $FilePath

• Click Run Script (F5)
• A text file will open with the Microsoft Office 2003 Web Components Detection Method script required to detect the current version of Microsoft Office 2003 Web Components that is installed on the device you are running the script from.

Example:

If([Version](Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-00A4-0409-0000-0000000FF1CE}','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-00A4-0409-0000-0000000FF1CE}' -Name DisplayVersion -ea SilentlyContinue) -ge '12.0.4518.1014') {
Write-Host "Installed"
}

• Copy the Microsoft Office 2003 Web Components 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.