DEPLOYMENT ENGINE

Zero-Touch Mass Deployment.

Keep your software libraries uniform without the wait. Paste directly from Excel to mass-deploy applications in parallel. Features intelligent Wake-on-LAN (WoL) to catch offline targets and ensure 100% compliance.

SEE HOW IT WORKS
Mass Deployment Orchestrator ● RUNNING

[UHDC] MASS ZERO-TOUCH DEPLOYMENT

[i] Application: Corporate VPN Client v8
[i] Total Targets: 42

> [1/4] Performing rapid ping sweep...

Online: 38 | Offline: 4

> [2/4] Attempting Wake-on-LAN for offline targets...

Sending Magic Packet to PC-039 (A1-B2-C3-D4-E5-F6)...

[SUCCESS] PC-039 is now awake!

> [3/4] Dispatching parallel WinRM commands...

WinRM Success: 37 | WinRM Blocked: 2

> [4/4] Initiating PsExec fallback for blocked targets...

[UHDC SUCCESS] Mass Deployment Report Generated.

The Ultimate Quality-of-Life Upgrade

When a zero-day vulnerability drops or a new software version is released, waiting for SCCM or Intune to sync across the fleet is agonizing. This engine allows admins to force compliance instantly across hundreds of machines.

Smart Excel Parsing

Copy an entire column of computer names directly from a spreadsheet and paste it into the UI. The engine automatically sanitizes the input, strips newlines and tabs, and converts it into a clean array for bulk processing.

Wake-on-LAN (WoL)

Never miss an offline target. The engine cross-references the central telemetry database to find the MAC address of offline PCs, broadcasts a UDP Magic Packet, and waits 45 seconds for them to boot before deploying.

Detached WMI Routing

Instead of standard WinRM execution, it uses Win32_Process Create to spawn the installer. This detaches the process from the network session, preventing the console from hanging if an MSI gets stuck.

INTERACTIVE TRAINING ENGINE
⭐ 300 XP

How Junior Techs Learn This Tool:

While the UHDC uses WMI and PowerShell runspaces to deploy software asynchronously, a junior technician should know how to push an installer manually. The training engine teaches them how to utilize Sysinternals PsExec to remotely execute an installer as the SYSTEM account. This bypasses the infamous "Double-Hop" authentication issue, allowing the target machine's computer account to pull the installer directly from a network share.

psexec \\$Target -s msiexec.exe /i "\\server\share\installer.msi" /qn /norestart

The In-Person Equivalent

Walking desk to desk with a flash drive, copying the installer to the desktop, and clicking through the installation wizard. Alternatively, opening an elevated command prompt and typing the silent install command.

Technical Q&A

Q: How does the Excel pasting work?
The UI uses a smart regex parser (split(/[\n\r\t\s,]+/)) that detects newlines, tabs, and spaces. You can copy a raw column of 50 hostnames directly from a spreadsheet, paste it into the target box, and the JavaScript engine instantly converts it into a clean, comma-separated array for the PowerShell backend to process.
Q: How does it know the MAC address for Wake-on-LAN?
It queries the UserHistory.json database generated by the Global Asset Telemetry engine. Because the telemetry agent logs the active MAC address of every PC that connects to the network, the deployment engine can look up the offline PC's last known MAC address and send the UDP broadcast packet to wake it up.
Q: Why use `Win32_Process Create` instead of just running the installer directly?
If you run an installer directly over WinRM and the installer hangs (e.g., waiting for a hidden user prompt), your WinRM session will hang indefinitely. By encoding the payload into Base64 and passing it to Win32_Process Create, we instruct the remote operating system to spawn a completely detached background process. WinRM returns success instantly, and the installer finishes on its own time.
Q: What happens if WinRM is blocked by the firewall?
The script catches the WinRM failure and automatically falls back to PsExec. It deploys PsExec to the target machine to execute the installation under the NT AUTHORITY\SYSTEM context. This not only bypasses the firewall block but also solves the "Double-Hop" authentication issue, allowing the target machine to pull the installer from a secondary network share using its Computer Account.