Pidgin Silent Install with SCCM Guide

To silently install Pidgin with SCCM, you use the command pidgin.exe /S (or /silent) and deploy it as an application with a detection method. This guide explains the exact command, how to package it in SCCM, and how to handle common issues like missing dependencies and 64-bit detection.

Why Pidgin Needs a Silent Install

Pidgin is a free, open-source instant messaging client that supports multiple protocols (XMPP, IRC, etc.). Its installer is built with NSIS (Nullsoft Scriptable Install System), which supports the standard /S flag for silent installation. Without this flag, the installer shows a GUI wizard, which blocks automated deployment. SCCM (Microsoft Endpoint Configuration Manager) requires silent installation commands so it can push software to many machines without user interaction. The /S flag tells the NSIS installer to run without any prompts, using default settings.

The Exact SCCM Command and Parameters

In your SCCM application deployment type, set the Installation program to:

pidgin.exe /S

That is the core command. You may add /D= to specify a custom install directory, but it must be the last parameter and must not contain quotes. For example:

pidgin.exe /S /D=C:\Program Files\Pidgin

Note: The /D parameter is case-sensitive and must be the last argument. If you need to install for the current user only (not recommended for enterprise), you might use /S with the per-user installer, but the standard installer installs per-machine by default when run with admin rights.

Packaging the Application in SCCM

To deploy Pidgin via SCCM, follow these steps:

1. Download the Pidgin installer (e.g., pidgin-2.14.12.exe) and place it in your source folder, e.g., \\Server\Share\Pidgin.
2. In the SCCM console, create a new Application. Choose “Manually specify the application information”.
3. Create a Deployment Type. For the installation command, enter pidgin.exe /S.
4. For the detection method, use “File System” to detect the file pidgin.exe in %ProgramFiles%\Pidgin (or %ProgramFiles(x86)%\Pidgin on 64-bit systems, since Pidgin is 32-bit).
5. Set the deployment type to “Install for system” if you want it to install for all users (requires admin rights).
6. Distribute content to your distribution points and deploy the application to a device collection.

For uninstallation, the command is msiexec /x {GUID} if you use the MSI wrapper, or you can use pidgin.exe /S again with the uninstaller, but the standard uninstaller is uninstall.exe located in the install directory. In SCCM, you can specify an uninstall command like "C:\Program Files\Pidgin\uninstall.exe" /S.

Detection Methods and 64-Bit Considerations

Pidgin is a 32-bit application, so on 64-bit Windows, it installs to C:\Program Files (x86)\Pidgin by default. When creating a detection rule in SCCM, you must check both possible locations or use a registry detection. The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Pidgin contains the uninstall string. Better yet, use the file pidgin.exe in the appropriate path. If you use a generic path like %ProgramFiles%\Pidgin, it will fail on 64-bit systems because the environment variable points to the 64-bit folder. Use %ProgramFiles(x86)%\Pidgin for 64-bit systems, or better, use a detection method that checks for the registry key under both WOW6432Node and normal hive. A robust approach: use a PowerShell detection script that checks if the file exists in either location.

Common Issues and Troubleshooting

Here are frequent problems and how to fix them:

• Installation fails with error 1603 – This usually means the installer could not write to the target directory. Ensure the SCCM agent runs as SYSTEM, which has admin rights. Also, check that no previous version is running.
• Pidgin installs but does not appear in Start Menu – The NSIS installer may not create shortcuts when running silently. To fix, add a post-install script that creates shortcuts, or use a custom script to copy .lnk files.
• Detection method says not installed – Verify the actual install path. Use the registry uninstall key to get the InstallLocation. Adjust your detection rule accordingly.
• Silent install hangs – The installer might be waiting for a reboot or user input. Ensure no other NSIS installers are running. Also, check that the command line is exactly /S (capital S).
• Dependencies missing – Pidgin requires some Visual C++ runtime libraries. The installer usually bundles them, but if you are deploying via SCCM, you might need to deploy the runtime separately. Check the Pidgin documentation for required runtimes.

Alternatives to a Raw EXE: MSI and Third-Party Tools

If you prefer an MSI for easier deployment, you can wrap the EXE with tools like Advanced Installer or use the /S flag with a script. Another approach is to use Chocolatey, which has a Pidgin package that handles silent installs. However, in SCCM, you can also use a PowerShell script as the deployment type. For example, you could download the installer and run it with Start-Process -Wait -ArgumentList '/S'. This gives you more control over logging and error handling. If you need to install Pidgin for multiple users, consider using the per-machine installer and ensure the SCCM deployment runs in the SYSTEM context.

Frequently Asked Questions

What is the exact silent install switch for Pidgin?

The switch is /S (case-sensitive). For example: pidgin.exe /S. This is the NSIS standard silent flag.

How do I uninstall Pidgin silently with SCCM?

Use the uninstaller located in the install directory. The command is "C:\Program Files (x86)\Pidgin\uninstall.exe" /S. In SCCM, set this as the uninstall program for the deployment type.

Why does the SCCM detection method fail even though Pidgin is installed?

Most likely because the detection path is wrong. On 64-bit systems, Pidgin installs to Program Files (x86). Use a registry detection or check both paths. Also, ensure you are checking for the file pidgin.exe and not a folder.

Can I install Pidgin for a specific user via SCCM?

Yes, but it is not recommended. You can run the installer in the user context, but this requires the user to be logged on. The standard SCCM application model installs per-machine. For per-user, you would need to use a script that runs in the user session, which is complex.

Does Pidgin require any prerequisites like .NET?

No, Pidgin does not require .NET, but it does require the Visual C++ runtime libraries. The installer usually includes them, but if you are deploying to a clean system, you might need to install them separately.

How can I verify that Pidgin installed correctly after SCCM deployment?

Check the SCCM console for the deployment status. On the client, you can look for the file pidgin.exe in the install directory, or run pidgin.exe --version from a command prompt. Also, check the SCCM log files (AppEnforce.log) for the detection result.

Related

• Line Wish List: What It Is & How to Use It
• Why Concord Can’t Get Players: Key Reasons
• VPS DDoS Protection: How It Works & 4 Hosts Compared