Deploy Pidgin with Intune

Overview

Deploy Pidgin 2.14.14 from Pidgin with a structured Intune workflow that covers packaging, assignment, and post-deploy checks.

Download Installer

Create Intune Package

1. Create a working folder on your local machine (for example: D:\Intune).
2. Create two subfolders inside the working folder: Input and Output.
   • D:\Intune\Input: Folder for all setup files. All files in this folder are compressed into an .intunewin file.
   • D:\Intune\Output: Stores the generated .intunewin package.
3. Place pidgin-2.14.14-offline.exe in the Input folder.
4. Download the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe) and place it in D:\Intune.

Set up your packaging paths first; a predictable workspace reduces repackaging drift for Pidgin across future updates.

D:\Intune
├── Input
│   └── pidgin-2.14.14-offline.exe
├── Output
└── IntuneWinAppUtil.exe

5. Open Windows PowerShell or Command Prompt as Administrator.
6. Navigate to the working folder: cd D:\Intune.
7. Run the following packaging command to generate the pidgin-2.14.14-offline.intunewin package. For packaging background, see .intunewin package preparation.

IntuneWinAppUtil.exe -c .\Input -s "pidgin-2.14.14-offline.exe" -o .\Output

8. After the command finishes, the generated package should be available in the D:\Intune\Output folder.

D:\Intune
├── Input
│   └── pidgin-2.14.14-offline.exe
├── Output
│   └── pidgin-2.14.14-offline.intunewin
└── IntuneWinAppUtil.exe

Note: Windows application size is capped at 30 GB per app.

Create the Win32 App Entry

Build the Intune app entry for Pidgin with metadata, program settings, and detection prepared for pilot rollout.

1. Go to Apps → Overview, then choose the Windows platform card (or expand Platforms and select Windows).

   

2. Click Create to add a new app.

   

3. In the Select app type panel, choose Windows app (Win32).

   

4. On the App information page, click Select app package file.

   

5. Upload pidgin-2.14.14-offline.intunewin, then confirm the App package file panel.

   

Configure App Settings

6. Treat app settings for Pidgin as your deployment contract and validate each field against real endpoint outcomes.

   Name	Pidgin 2.14.14
   Description	Pidgin 2.14.14
   Publisher	Pidgin
   App version	2.14.14

   

7. Configure how Intune installs and uninstalls the app. Enter the values below in the Program tab and leave all other settings unchanged. See Intune install and uninstall commands for command guidance.

   Install/Uninstall type	Command line
   Install command	"pidgin-2.14.14-offline.exe" /S /NCRC⧉
   Uninstall command	"%ProgramFiles(x86)%Pidginpidgin-uninst.exe" /S⧉
   Install behavior	System
   Device restart behavior	App install may force a device restart
   Allow available uninstall	Yes
   Installation time required	60 minutes
   Return codes	Keep the default Intune return codes.

   

8. Define which devices are eligible to install the app. Learn more in Intune requirements explained.

   Check operating system architecture	No. Allow this app to be installed on all systems.
   Minimum operating system	Windows 10 1607
   Additional requirement rules	No requirements are specified.

   

9. On the Detection rules page, set Rules format to Manually configure detection rules. For the concept, see Intune detection rules explained.

   

10. Click Add to create a detection rule.

    

11. Select the appropriate Rule type (MSI, File, or Registry) based on the installer. Use the table below as a reference.

    #	Type	Target	Method	Value
    1	File	%ProgramFiles%\Pidginpidgin.exe	String/version comparison	equals 2.14.14.0
    2	Registry	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallPidgin → DisplayVersion	String comparison	equals 2.14.14

    Associated with a 32-bit app on 64-bit clients: Yes.

12. On the Dependencies page, click Next unless this app must install after another app.

    

13. On the Supersedence page, click Next unless this app replaces an older app.

    

Configure Assignment and Rollout

14. Deploy Pidgin through progressive rings and require clear success thresholds before each promotion.

    Assignment options

    Required

    Installs the app automatically on targeted users or devices. Use this after install, uninstall, and detection are verified.

    Available for enrolled devices

    Shows the app in Company Portal so users can install it manually. Use this for pilot users, IT validation, or optional apps.

    Uninstall

    Automatically removes the app from targeted devices. Use this when you need to retire or remove the app.

    Note: Start with a dedicated test group before broad deployment. For example, use the Required assignment option to automatically install the app on targeted devices.

    

15. Review all configuration details, then click Create to deploy the app.

    

16. Verify the app in Intune. Confirm that the upload is finished, the application is saved, and the app overview shows the expected package details.

    Note: If Intune says the app is not ready yet, wait a few minutes and refresh the page.

    

Run a Device Policy Sync

Validate device policy sync state for Pidgin so reporting delays are not mistaken for deployment faults.

End User Experience

Use pilot devices to verify the real user journey for Pidgin and adjust guidance before expansion.

Required apps install automatically. During installation, Windows may show notifications from Microsoft Intune Management Extension. Users can see the app move from installing to installed.

Note: Notification visibility depends on Windows notification settings and Intune app deployment behavior.

Tracking the App Deployment

Monitor install and detection status for Pidgin by ring to decide whether to proceed, pause, or remediate.

Click Device install status or User install status to see the list of devices or users with their installation status.

Uninstall the App from Intune

When the app is no longer needed, remove it by changing the Intune assignment to Uninstall for the target group.

1. Go to Apps → All apps, then select the app you want to remove.

   

2. Open Properties and click Edit next to Assignments.

   

3. Move the target group to the Uninstall section.

   

4. Review the assignment, then click Save. Devices will remove the app after the policy is applied.

   

After saving, the uninstall policy is applied. The device removes the app automatically.

Note: The uninstall process may take a few minutes depending on device check-in and policy sync timing.

Troubleshooting and Fixes

When deployment results drift from expected behavior, run the checks below in order to isolate scope, command, detection, and policy timing problems quickly.

For persistent failures, capture the exact return code, rerun the install command in the same context, and re-check Intune Management Extension logs.

Deployment Fit and Risks

Review these fit-and-risk checks for Pidgin before moving from pilot to broad production scope.

• Install behavior is currently set to system; confirm it matches the expected execution context.
• Restart behavior resolves to basedOnReturnCode; align this with maintenance windows and user-impact constraints.
• Validate requirements and detection against real endpoint state before widening assignment scope.
• Gate broad deployment on pilot success criteria and hold expansion when install or detection drift appears.

Post-Deployment Validation

• Validate Pidgin in a controlled pilot group before scaling to production.
• Confirm the install command executes silently in the target context: "pidgin-2.14.14-offline.exe" /S /NCRC.
• Verify detection criteria (types observed: manual/unspecified) against the actual installed footprint.
• Track early deployment signals in Intune reporting and Intune Management Extension logs for non-zero outcomes.
• Validate uninstall behavior on one pilot endpoint so rollback is ready if required.

Change Log and Rollback Guidance

• Capture the current state for Pidgin and record target version 2.14.14 before expanding assignment.
• Rollback path available via uninstall command: "%ProgramFiles(x86)%Pidginpidgin-uninst.exe" /S.
• Advance rollout in rings and require stable install plus detection results before each promotion step.
• During change windows, track both install and rollback outcomes to preserve fast recovery options.

Deeper Internal References

Use the focused guides below for deeper implementation details tied to this deployment.

• IntuneWin build workflow for deployment consistency
• Rollout intent model for required and available apps
• IME diagnostics path for install and detection failures
• Program command hardening before production rollout