Automated Deployment Guide
Command line reference and mass deployment strategies for enterprise environments.
Overview
RescuePC Repairs is designed as a portable application — no installation required. This guide covers strategies for deploying the toolkit across hundreds or thousands of machines using enterprise deployment tools (SCCM, Intune, PDQ Deploy) or network shares.
1. Deployment Models
Model A: Network Share (Recommended)
Best for: Environments where technicians need access from any workstation.
# Create network share
\\\\fileserver\\IT-Tools\\RescuePC\\
# Contents
├── RescuePC Repairs.exe
├── RescuePC.Runner.exe
├── scripts\\
└── license.key (optional pre-activation)
Advantages:
- • Single point of update — update once, all technicians get new version
- • No local disk space required on client machines
- • Centralized license management
- • Audit trail via file server logs
Model B: Local Deployment (SCCM/Intune)
Best for: Air-gapped environments or machines without reliable network access.
# Target directory
C:\\Program Files\\RescuePC\\
# Or portable location
C:\\IT-Tools\\RescuePC\\
Deployment Package Contents:
- • Full ZIP contents extracted to target directory
- • Optional: Desktop shortcut for technicians
- • Optional: Start Menu entry
Model C: USB Technician Kit
Best for: Walk-in support centers, field technicians, student help desks.
# USB drive structure
E:\\
├── RescuePC Repairs.exe
├── RescuePC.Runner.exe
├── scripts\\
└── logs\\ (created automatically)
Notes:
- • License binds to USB drive, not client PC
- • Run on unlimited client machines from single USB
- • Logs stored on USB for later review
2. Command Line Reference
Launcher (GUI)
The main application is GUI-only. Launch it directly — no command line arguments are supported.
"RescuePC Repairs.exe"
# For pre-activation, place a license.key file in the same directory (see Section 4)
Runner (Admin Helper)
The Runner executes repairs with elevated privileges. It accepts repair IDs from the manifest. This is called internally by the GUI but can be used for scripted automation.
| Command | Description |
|---|---|
| RescuePC.Runner.exe <RepairId> <LogPath> | Run single repair (requires elevation) |
| RescuePC.Runner.exe fix_network C:\logs\net.log | Example: Run network repair |
| RescuePC.Runner.exe --batch id1,id2 <LogPath> | Run multiple repairs (one UAC prompt) |
| RescuePC.Runner.exe --check | Verify Runner is working (returns 0) |
Optional Flags:
-NoPrompt— Skip confirmation prompts (enables silent enterprise deployment)
Security: The Runner only executes repairs defined in its signed manifest. Arbitrary script paths are rejected. The RepairId must match a valid manifest entry.
3. SCCM / Intune Deployment
SCCM Application Package
# Installation Command (xcopy deployment)
xcopy "\\\\source\\RescuePC\\*" "C:\\Program Files\\RescuePC\\" /E /I /Y
# Uninstall Command
rmdir /S /Q "C:\\Program Files\\RescuePC"
# Detection Method (File exists)
C:\\Program Files\\RescuePC\\RescuePC Repairs.exe
Intune Win32 App
# Package the ZIP as .intunewin using IntuneWinAppUtil
IntuneWinAppUtil.exe -c "C:\\Source" -s "RescuePC.zip" -o "C:\\Output"
# Install Command
powershell -ExecutionPolicy Bypass -Command "Expand-Archive -Path RescuePC.zip -DestinationPath 'C:\\Program Files\\RescuePC' -Force"
# Uninstall Command
powershell -Command "Remove-Item 'C:\\Program Files\\RescuePC' -Recurse -Force"
PDQ Deploy
# Step 1: Copy files
Command: xcopy "$(Repository)\\RescuePC\\*" "C:\\IT-Tools\\RescuePC\\" /E /I /Y
# Step 2: Create shortcut (optional)
PowerShell: $ws = New-Object -ComObject WScript.Shell; $s = $ws.CreateShortcut("C:\\Users\\Public\\Desktop\\RescuePC.lnk"); $s.TargetPath = "C:\\IT-Tools\\RescuePC\\RescuePC Repairs.exe"; $s.Save()
4. Pre-Activation (License Embedding)
To deploy with a pre-activated license, create a license.key file in the application directory containing only the license key.
# license.key contents (single line, no quotes)
YOUR-LICENSE-KEY-HERE
On first launch, the application will read this file and attempt activation automatically. The file is deleted after successful activation for security.
5. Group Policy Considerations
AppLocker / WDAC Whitelisting
For environments with application control policies, whitelist by publisher certificate:
# Publisher Rule
Publisher: O=RESCUEPC SOFTWARE, C=US
# Or by file hash (get from signed EXE)
Get-AppLockerFileInformation -Path "RescuePC Repairs.exe" | Select -ExpandProperty Hash
PowerShell Execution Policy
RescuePC repairs scripts require PowerShell execution. Ensure the following policy is set for the SYSTEM account:
# Minimum required policy
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine
Questions? Contact [email protected]