ANAVEM
Languagefr
How to Deploy HP Support Assistant Using Microsoft Intune

How to Deploy HP Support Assistant Using Microsoft Intune

Learn to package and deploy HP Support Assistant as a Win32 app through Microsoft Intune, including installer preparation, IntuneWin packaging, and enterprise deployment configuration.

March 30, 2026 15 min
mediumintune 8 steps 15 min

Why Deploy HP Support Assistant Through Microsoft Intune?

HP Support Assistant provides automated driver updates, system diagnostics, and hardware support for HP devices in enterprise environments. However, manually installing and maintaining this software across hundreds or thousands of HP devices becomes a significant administrative burden. Microsoft Intune solves this challenge by enabling centralized deployment and management of HP Support Assistant as a Win32 application.

What Makes This Deployment Method Effective?

Unlike consumer-focused installation methods, enterprise deployment through Intune requires specific packaging and configuration steps. The process involves converting the HP Support Assistant installer into an IntuneWin package, configuring silent installation parameters, and setting up detection rules that ensure successful deployment verification. This approach provides complete control over when, where, and how the application deploys across your HP device fleet.

What Will You Accomplish With This Tutorial?

By following this guide, you'll create a fully automated deployment pipeline for HP Support Assistant that targets only HP devices in your organization. The deployment will run silently without user intervention, include proper detection rules for installation verification, and provide comprehensive monitoring capabilities through the Intune admin center. This enterprise-grade approach ensures consistent HP Support Assistant availability across your organization while minimizing administrative overhead and user disruption.

Implementation Guide

Full Procedure

01

Download and Prepare HP Support Assistant Enterprise Installer

Navigate to the HP Support website and download the enterprise version of HP Support Assistant. This is crucial because the web installer won't work for enterprise deployment scenarios.

Create a working directory and verify the installer integrity:

New-Item -Path "C:\HPSAPackaging" -ItemType Directory -Force
Set-Location "C:\HPSAPackaging"

# Verify the downloaded installer
$installerPath = "C:\HPSAPackaging\HPSupportAssistantInstaller.exe"
if (Test-Path $installerPath) {
    $fileVersion = (Get-ItemProperty $installerPath).VersionInfo.FileVersion
    $fileSize = (Get-Item $installerPath).Length / 1MB
    Write-Output "HP Support Assistant version: $fileVersion"
    Write-Output "File size: $([math]::Round($fileSize, 2)) MB"
} else {
    Write-Error "Installer not found. Download the enterprise version from HP Support website."
}
Warning: Never use the web installer for enterprise deployment. It requires internet connectivity during installation and won't work in offline scenarios.

Verification: The installer should be at least 100MB in size. Web installers are typically under 5MB.

02

Extract and Prepare the Microsoft Win32 Content Prep Tool

Download the Microsoft Win32 Content Prep Tool from the official Microsoft documentation. Extract it to your packaging directory and verify it's working correctly.

# Create tools directory
New-Item -Path "C:\HPSAPackaging\Tools" -ItemType Directory -Force

# Extract Win32 Content Prep Tool to Tools directory
# Download from: https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool

# Verify the tool is ready
Set-Location "C:\HPSAPackaging\Tools"
if (Test-Path "IntuneWinAppUtil.exe") {
    .\IntuneWinAppUtil.exe
    Write-Output "Win32 Content Prep Tool is ready"
} else {
    Write-Error "IntuneWinAppUtil.exe not found. Download and extract the tool first."
}

The tool will display usage information when run without parameters, confirming it's working properly.

Pro tip: Keep the Win32 Content Prep Tool in a dedicated tools folder that you can reuse for other application packaging projects.

Verification: Running IntuneWinAppUtil.exe without parameters should display help text and usage examples.

03

Create the IntuneWin Package

Use the Win32 Content Prep Tool to convert the HP Support Assistant installer into the .intunewin format required by Microsoft Intune.

# Navigate to the Win32 Content Prep Tool directory
Set-Location "C:\HPSAPackaging\Tools"

# Create source and output directories
New-Item -Path "C:\HPSAPackaging\Source" -ItemType Directory -Force
New-Item -Path "C:\HPSAPackaging\Output" -ItemType Directory -Force

# Copy the installer to the source directory
Copy-Item "C:\HPSAPackaging\HPSupportAssistantInstaller.exe" -Destination "C:\HPSAPackaging\Source\"

# Create the IntuneWin package
.\IntuneWinAppUtil.exe -c "C:\HPSAPackaging\Source" -s "HPSupportAssistantInstaller.exe" -o "C:\HPSAPackaging\Output" -q

The tool will process the installer and create the .intunewin file. This process typically takes 1-2 minutes depending on the installer size.

Verification: Check that the .intunewin file was created successfully:

$intuneWinFile = Get-ChildItem "C:\HPSAPackaging\Output" -Filter "*.intunewin"
if ($intuneWinFile) {
    Write-Output "Package created: $($intuneWinFile.Name)"
    Write-Output "Package size: $([math]::Round($intuneWinFile.Length / 1MB, 2)) MB"
} else {
    Write-Error "IntuneWin package creation failed"
}
04

Create Win32 App in Microsoft Intune Admin Center

Sign in to the Microsoft Endpoint Manager admin center and create a new Win32 application for HP Support Assistant deployment.

Navigate to Apps > All Apps > Add. Select Windows app (Win32) from the app type dropdown.

Click Select app package file and upload your .intunewin file. Fill in the application information:

  • Name: HP Support Assistant
  • Description: HP Support Assistant provides automated driver updates and system diagnostics for HP devices
  • Publisher: HP Inc.
  • Category: Productivity
Pro tip: Use a consistent naming convention for your applications. Consider adding version numbers or deployment dates to track different releases.

Configure the application logo by uploading the HP Support Assistant icon (you can extract this from the installer or download from HP's brand resources).

Verification: The app package should upload successfully and display the correct file size and metadata in the Intune admin center.

05

Configure Installation and Uninstallation Commands

Set up the installation behavior and commands for silent deployment across your organization's devices.

On the Program tab, configure these settings:

  • Install behavior: System
  • Device restart behavior: Determine based on return codes

Set the installation command for silent deployment:

HPSupportAssistantInstaller.exe /S /v"/qn ALLUSERS=1"

Configure the uninstall command. First, you'll need to identify the product GUID after installation:

# Run this on a test machine after installation to find the GUID
Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*HP Support Assistant*"} | Select-Object Name, IdentifyingNumber

Use the identified GUID in your uninstall command:

MsiExec.exe /X{GUID-FROM-ABOVE} /qn
Warning: Always test installation and uninstallation commands on a test device before deploying to production. Silent installations can fail without obvious error messages.

Verification: Test the installation command manually on a test device to ensure it works silently without user interaction.

06

Set System Requirements and Detection Rules

Configure the minimum system requirements and detection rules to ensure proper deployment targeting and installation verification.

On the Requirements page, set:

  • Operating system architecture: x64
  • Minimum operating system: Windows 11 22H2 (or your organization's minimum supported version)
  • Disk space required: 500 MB
  • Physical memory required: 4 GB

Configure detection rules on the Detection rules page. Create a custom PowerShell script for accurate detection:

# HP Support Assistant Detection Script
$hpSAService = Get-Service "HP Support Assistant Service" -ErrorAction SilentlyContinue
$hpSAPath = "${env:ProgramFiles}\HP\HP Support Assistant\bin\HPSupportAssistant.exe"

if ($hpSAService -and $hpSAService.Status -eq "Running" -and (Test-Path $hpSAPath)) {
    Write-Output "HP Support Assistant is installed and running"
    exit 0
} else {
    exit 1
}

Set the detection rule type to Use a custom detection script and upload your PowerShell script. Configure it to run as a 64-bit process.

Verification: Test your detection script manually on a device with HP Support Assistant installed to ensure it returns the correct exit codes.

07

Configure Device Group Assignments

Create targeted assignments to deploy HP Support Assistant only to HP devices in your organization.

Navigate to the Assignments tab and click Add group. Configure these assignment settings:

  • Assignment type: Required
  • Included groups: Select your HP devices group
  • Available for enrolled devices: Yes
  • Installation deadline: 7 days after assignment

Create a device filter to target only HP devices:

(device.manufacturer -eq "HP") or (device.manufacturer -eq "Hewlett-Packard")

Configure notification settings:

  • Show all toast notifications: Yes
  • Show restart required notifications: Yes
  • Restart grace period: 1440 minutes (24 hours)
Pro tip: Start with a pilot group of 10-20 HP devices before rolling out to your entire organization. This allows you to catch any deployment issues early.

Verification: Review the assignment summary to ensure the correct groups and filters are applied before saving the configuration.

08

Monitor Deployment Status and Troubleshoot Issues

Monitor the deployment progress and troubleshoot any installation failures using Intune's built-in reporting tools.

Navigate to Apps > All apps > HP Support Assistant > Device install status to view real-time deployment information.

Monitor these key metrics:

  • Installation success rate
  • Failed installations with error codes
  • Pending installations
  • Not applicable assignments

For troubleshooting failed installations, check the Intune Management Extension logs on affected devices:

# Check Intune Management Extension logs
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" | Where-Object {$_.TimeCreated -gt (Get-Date).AddHours(-24)} | Select-Object TimeCreated, LevelDisplayName, Message | Format-Table -Wrap

Verify successful installation across your environment:

# Verification script for HP Support Assistant deployment
$devices = Get-MgDevice -Filter "manufacturer eq 'HP'"
foreach ($device in $devices) {
    $hpSAStatus = Invoke-Command -ComputerName $device.DisplayName -ScriptBlock {
        $service = Get-Service "HP Support Assistant Service" -ErrorAction SilentlyContinue
        if ($service -and $service.Status -eq "Running") {
            return "Installed"
        } else {
            return "Not Installed"
        }
    } -ErrorAction SilentlyContinue
    
    Write-Output "$($device.DisplayName): $hpSAStatus"
}

Common error codes and solutions:

  • 0x80070005: Access denied - Check device permissions and ensure the app runs as System
  • 0x80070643: Fatal error during installation - Verify the installer isn't corrupted
  • 0x8007000D: Invalid data - Re-create the IntuneWin package

Verification: Successful deployment should show 95%+ success rate within 48 hours for devices that are online and checking in with Intune regularly.

Frequently Asked Questions

Can I deploy HP Support Assistant to non-HP devices through Intune?+
No, HP Support Assistant is designed specifically for HP hardware and will not function properly on devices from other manufacturers. The application includes hardware-specific drivers and diagnostic tools that require HP components. Use device filters in your Intune assignment to target only HP devices by filtering on manufacturer properties like 'HP' or 'Hewlett-Packard'.
What's the difference between the web installer and enterprise installer for HP Support Assistant?+
The web installer is a small download that requires internet connectivity during installation to fetch additional components. The enterprise installer is a complete offline package containing all necessary files for installation. For Intune deployment, you must use the enterprise installer because devices may not have internet access during the installation process, and the web installer cannot be properly packaged into an IntuneWin file.
How do I troubleshoot failed HP Support Assistant deployments in Intune?+
Check the Intune Management Extension logs on affected devices using Event Viewer or PowerShell. Common issues include incorrect silent installation parameters, insufficient permissions, or corrupted IntuneWin packages. Verify your detection script works correctly and test the installation command manually on a test device. Monitor the device install status in the Intune admin center for specific error codes and their meanings.
Can HP Support Assistant be deployed to Windows 10 devices through Intune?+
Yes, HP Support Assistant supports Windows 10 devices, but you should verify the minimum supported version with HP's current system requirements. When configuring requirements in Intune, set the minimum operating system to match your organization's supported Windows 10 version. However, HP may eventually discontinue Windows 10 support, so plan for Windows 11 migration as part of your long-term device management strategy.
How often does HP Support Assistant check for driver updates after Intune deployment?+
By default, HP Support Assistant checks for driver and software updates weekly, but this can be configured through group policy or registry settings after deployment. The application runs as a Windows service and performs background checks without user intervention. You can customize the update frequency and notification settings through HP's administrative tools or by deploying additional configuration policies through Intune to match your organization's change management requirements.

Discussion

Share your thoughts and insights

Sign in to join the discussion