Skip to content
  • There are no suggestions because the search field is empty.

Deploy Foxit PDF Editor with Microsoft Intune

Walks IT admins through deploying the Foxit PDF Editor ZIP distribution package using Microsoft Intune.

Answer

This guide explains how to deploy Foxit PDF Editor to managed Windows devices using Microsoft Intune's Win32 app management capabilities.

Applicable Versions

This deployment guide is specifically designed for Foxit PDF Editor v2025.3 or later distributed in ZIP package format. The procedures outlined below are optimized for this version and packaging type.

Prerequisites

Before you begin, ensure that:

  • End-user computers run Windows 10 version 1607 or later (Enterprise, Pro, or Education editions)
  • You have administrative access to Microsoft Intune
  • You have downloaded the Foxit PDF Editor v2025.3 or later ZIP installation package
  • You have extracted the ZIP package to access the installation files

After extracting the ZIP file, users will find:

File Name Description
FoxitPDFEditor.msi Base installer for version 2025.3.0 or later
FoxitPDFEditorUpd20253.msp Patch package for the latest version
Transforms Language-specific MST files
Setup.exe Installer launcher
setup.ini Configuration file for Setup.exe

For complete system requirements, refer to Microsoft's Win32 app management in Microsoft Intune.

Step 1: Prepare the Intune Package

1.1 Download Required Tools

First, download the Microsoft Win32 Content Prep Tool (Download link: IntuneWinAppUtil.exe ).

1.2 Extract the Editor Package

Download and extract the ZIP package (such as: Foxit PDF Editor v2025.3) to a local folder on your computer. This will provide access to the setup files and configuration files (including the .ini file containing the application GUID).

1.3. Generate the FoxitPDFEditor.intunewin File

You can create the deployment package using either an interactive or command-line approach:

1.3.1 Interactive Method:

Run IntuneWinAppUtil.exe without parameters. The tool will prompt you to enter:

  • Source folder containing all installer files
  • Setup file name (e.g., Setup.exe or setup.msi)
  • Output folder for the generated file
  • Whether to run in quiet mode

1.3.2 Command-Line Method:

Use the following command structure:

IntuneWinAppUtil.exe -c <setup_folder> -s <setup_file> -o <output_folder> -q

Parameters:

  • -c : Folder containing all installer files. All files within this folder will be compressed into the .intunewin file.
  • -s : Installer file (Setup.exe or setup.msi)
  • -o : Output folder for the .intunewin file
  • -q : Silent mode (optional)
  • -h : Display help. For example: IntuneWinAppUtil.exe -h

Example:

IntuneWinAppUtil.exe -c c:\testapp\v1.0 -s c:\testapp\v1.0\setup.exe -o c:\testappoutput\v1.0 -q

This command generates the .intunewin file from the specified source folder. For MSI installers, the tool automatically retrieves necessary metadata for Intune. If the output folder doesn't exist, it will be created automatically.

Step 2: Publish the output Intune file on Microsoft Intune

2.1 Add New Application

  • Select Windows app (Win32) as the app type

  • Click Select and choose the FoxitPDFEditor.intunewin file you created

2.2 Configure App Information

For detailed reference, please see Microsoft's Add a Win32 app to Intune .

Provide the following required details:

  • Name: Enter a unique name for the application in Intune (e.g., "Foxit PDF Editor 2025.3")
  • Description: Add a description of the application
  • Publisher: Enter the publisher name (e.g., Foxit Software)
  • App version: Specify the version number (2025.3)
  • Additional optional fields as needed

2.3 Configure Program Settings

Specify the installation and uninstallation commands:

Install Command:

  • For Setup.exe files: Setup.exe /quiet

Uninstall Command: Use the application GUID found in the extracted ZIP package's .ini file:

msiexec /x {GUID} /qn

Install Behavior: Select "System" to install for all users.

2.4 Set Requirements

Define the minimum system requirements:

  • Operating System Architecture: Choose 32-bit, 64-bit, or ARM
  • Minimum Operating System: Select the minimum Windows 10 version required

2.5 Configure Detection Rules

You can keep the default detection rules, which use the MSI product code to verify installation.

  • Rule Type: Choose “MSI”
  • MSI product code: View the GUID value in the INI file extracted from the ZIP package.
  • MSI product version check: Yes
  • Operator: Greater than or equal to
  • Value: The version number of the Editor to be deployed.

For more information on custom detection rules, refer to Microsoft's Detection rules.

2.6 Set Dependencies (Optional)

If Foxit PDF Editor requires other applications to be installed first, configure dependencies here. Otherwise, you can skip this section. See Microsoft's dependencies for details.

2.7 Configure Supersedence (Optional)

If this package replaces an older version, configure supersedence settings. For most deployments, default values are sufficient. See Microsoft's Supersedence for details.

2.8 Assign to Groups

Select the deployment type and target groups:

Assignment Types:

  • Required: Automatically installs on devices in the selected groups
  • Available for enrolled devices: Users can install from the Company Portal
  • Uninstall: Removes the application from selected devices

Click Add group and select the Azure AD groups that should receive this deployment.

For more information on managing assignments, see:

2.9 Review and Create

Review all settings and click Create to publish the application to Intune.

Step 3: Verify Deployment

3.1 Client-Side Verification

Users may need to restart their computers or log out and back in for the deployment to take effect. Once applied, the application will install according to the assignment type configured.

3.2 Monitor Installation Status

To check deployment status:

  1. In the Microsoft Endpoint Manager admin center, navigate to Apps > All apps
  2. Select the Foxit PDF Editor application
  3. Click Device install status or User install status
  4. Review the installation progress and any error messages

You can view detailed installation status for each device, including success, failure, or in-progress states.

4 Troubleshooting

If installation fails:

  • Check that devices meet the system requirements
  • Verify the install command syntax is correct
  • Review the device logs in Intune for specific error messages
  • Ensure the GUID in the uninstall command matches the package (found in the .ini file from the extracted ZIP)
  • Confirm that target devices have network connectivity to Intune
  • Verify that the ZIP package was fully extracted before creating the .intunewin file

For additional support, consult Microsoft's Intune troubleshooting documentation or contact Foxit support.