How to Deploy PrintPilot via Active Directory GPO: Silent Installation & setup.ini Guide
Learn how to silently deploy PrintPilot virtual printer across enterprise workstations using Active Directory Group Policy (GPO) and automate provisioning via setup.ini.
Instead of manually installing PrintPilot and logging in on dozens or hundreds of client PCs, you can deploy it across your entire Windows domain using Active Directory Group Policy (GPO) and a simple 'setup.ini' configuration file. By placing 'setup.ini' in the same folder as the installer (EXE or MSI), administrator credentials and directory settings are provisioned automatically during silent setup.
Auto Print to PDF & Send Email with PrintPilot
Stop wasting time on manual document printing. Start your free trial.
1setup.ini File Structure & Template
When the PrintPilot installer or MSI executes, it automatically checks its current directory for a 'setup.ini' file. If found, it reads the administrator email, password, and target directory to automatically register and link the client machine without user interaction.\n\nSave the following configuration as 'setup.ini' next to your installer:
[PrintPilot]
; PrintPilot Setup Configuration File
; Rename this file to setup.ini and place it next to PrintPilot-Setup.exe or the MSI
; to automatically provision these settings during silent installation.
; Administrator Email (Used for login / identification)
Email=admin@example.com
; Administrator Password
Password=secretpassword123
; Optional Referral Code
ReferralCode=
; Optional Custom Installation Directory
; Note: If deploying via MSI, the MSI INSTALLDIR property takes precedence.
InstallDir=C:\Program Files\PrintPilot2Step 1: Place Installer & setup.ini on Network Share
Copy `PrintPilot-Setup.exe` (or `PrintPilot.msi`) along with `setup.ini` to a central network folder accessible by all domain workstations (SYSVOL or an SMB share).\n\nExample Share Path:\n`\\\\yourdomain.local\\SYSVOL\\yourdomain.local\\Deploy\\PrintPilot\\`\nor\n`\\\\fileserver.yourdomain.local\\SoftwareDeploy$\\PrintPilot\\`\n\nEnsure 'Domain Computers' has Read & Execute permissions.
3Step 2: Create Silent Installation Startup Script
Create a batch script (`install-printpilot.bat`) that verifies whether PrintPilot is already installed before initiating the silent install:
@echo off
:: ===================================================================
:: PrintPilot GPO Silent Installation Script
:: ===================================================================
setlocal
set DEPLOY_SHARE=\\sirketiniz.local\SYSVOL\sirketiniz.local\Deploy\PrintPilot
set LOG_FILE=%TEMP%\printpilot_gpo_install.log
:: 1. Check if PrintPilot is already installed on the machine
if exist "C:\Program Files\PrintPilot\PrintPilot.exe" (
goto :ALREADY_INSTALLED
)
echo [%DATE% %TIME%] Starting PrintPilot silent installation... >> "%LOG_FILE%"
:: 2. Silent install with EXE (setup.ini in same directory is detected automatically)
"%DEPLOY_SHARE%\PrintPilot-Setup.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART >> "%LOG_FILE%" 2>&1
:: Alternative: Silent install with MSI:
:: msiexec.exe /i "%DEPLOY_SHARE%\PrintPilot.msi" /qn /norestart >> "%LOG_FILE%" 2>&1
if %ERRORLEVEL% EQU 0 (
echo [%DATE% %TIME%] PrintPilot installed and provisioned successfully. >> "%LOG_FILE%"
) else (
echo [%DATE% %TIME%] ERROR: Installation failed with exit code %ERRORLEVEL% >> "%LOG_FILE%"
)
:ALREADY_INSTALLED
endlocal
exit /b 04Step 3: Configure GPO in Group Policy Management Console
Open Group Policy Management (`gpmc.msc`) on your Domain Controller:\n\n1. Right-click the targeted Organizational Unit (OU) and select 'Create a GPO in this domain, and Link it here...'.\n2. Name the GPO: `Deploy-PrintPilot-Workstations`.\n3. Right-click the GPO and click 'Edit'.\n4. Navigate to:\n `Computer Configuration -> Policies -> Windows Settings -> Scripts (Startup/Shutdown) -> Startup`.\n5. Click 'Add' and enter the UNC path to `install-printpilot.bat`.
5Step 4: Update Policy & Verify on Client PC
To verify the deployment on a client machine:\n\n1. Run policy update in elevated CMD or PowerShell:\n `gpupdate /force`\n2. Reboot the workstation.\n3. Verify virtual printer presence in PowerShell:
# 1. Verify PrintPilot virtual printer status
Get-Printer -Name "PrintPilot" | Select-Object Name, DriverName, PortName
# 2. Inspect installation log
Get-Content "$env:TEMP\printpilot_gpo_install.log" -Tail 20Frequently Asked Questions (FAQ)
Do I need to pass setup.ini as a command-line argument?
No. As long as setup.ini is in the same directory as PrintPilot-Setup.exe or PrintPilot.msi, the installer automatically detects and reads it.
Do client users need local administrator rights?
No. GPO Computer Startup Scripts execute under the Windows SYSTEM account, ensuring the virtual printer driver installs seamlessly for standard users.
How do I specify a custom directory when deploying via MSI?
When using MSI, the 'INSTALLDIR' property takes precedence, e.g.: msiexec /i PrintPilot.msi INSTALLDIR="C:\\Program Files\\PrintPilot" /qn /norestart.
Can I deploy via Microsoft Intune or SCCM?
Yes. Package PrintPilot-Setup.exe and setup.ini into a single Intune Win32 App (.intunewin) and run it silently using `/VERYSILENT /SUPPRESSMSGBOXES /NORESTART`.
Start Automating Your Workflows Today
With Active Directory GPO and setup.ini, you can deploy and provision PrintPilot across your organization in minutes with zero manual intervention.
Download PrintPilot Free Trial