Enterprise Deployment

Deploy Deck with Microsoft Intune, Configuration Manager, or Group Policy Software Installation

All three channels below install the same MSI. The recurring theme: because Deck's MSI is authored per-user, device/computer-context deployments must pass ALLUSERS=1 to install per-machine. Review Deployment Overview for the reasoning.

Microsoft Intune (Win32 app)

Intune's .intunewin Win32 packaging gives you the most control.

Package the MSI with the Microsoft Win32 Content Prep Tool:

IntuneWinAppUtil.exe -c <source folder> -s VediramDeckSetup-1.8.0-x64.msi -o <output folder>

Create the Win32 app in Intune and set the commands:
- Install: msiexec /i VediramDeckSetup-1.8.0-x64.msi ALLUSERS=1 /qn
- Uninstall: msiexec /x {ProductCode} /qn (Intune auto-detects the code from the MSI)
Install behavior: System (device context). Pairs with ALLUSERS=1.
Detection rule - prefer a file rule over an MSI rule for speed:
- File exists: C:\Program Files\Vediram\Deck\Vediram.Deck.Core.exe
- Or MSI product code detection (Intune reads it from the package).
Return codes: map 3010 to "soft reboot" if you standardize on it; Deck normally returns 0.

For user-context assignment instead (per-user install to each user's profile), drop ALLUSERS=1, set install behavior to User, and use a detection file path of %LOCALAPPDATA%\Programs\Vediram\Deck\Vediram.Deck.Core.exe.

Configuration Manager (SCCM)

Create an Application with a Windows Installer deployment type:

Content: the MSI (and, if you script it, a wrapper).
Installation program: msiexec /i "VediramDeckSetup-1.8.0-x64.msi" ALLUSERS=1 /qn
Uninstall program: msiexec /x {ProductCode} /qn
Install for system / Install for system if resource is device, with whether or not a user is logged on.
Detection method: the MSI product code (imported automatically), or a file rule on Vediram.Deck.Core.exe.

Deploy to a device collection for per-machine, or a user collection with the per-user command line (no ALLUSERS).

Group Policy Software Installation

GPO Software Installation can only consume the MSI directly (no command line), so it cannot pass ALLUSERS. Use the natural scope of each assignment:

Assigned to Computer (Computer Configuration → Policies → Software Settings → Software Installation): installs at next boot in the SYSTEM context. Because the package is per-user by design, prefer Intune/ConfigMgr with ALLUSERS=1 when you need a per-machine install. If you must use GPO for a per-machine install, repackage or use a transform (.mst) that sets ALLUSERS=1.
Published/Assigned to User (User Configuration → …): installs the default per-user package for the targeted users. This matches the MSI's native scope and is the more reliable GPO path for Deck.

Steps:

Copy the MSI to a UNC share readable by the target computers/users (e.g. \\server\software$\Deck\VediramDeckSetup-1.8.0-x64.msi).
Edit the GPO → Software Installation → New → Package, select the MSI via its UNC path (never a local path).
Choose Assigned.
Link the GPO to the target OU.

GPO Software Installation is the least flexible channel (no properties, no logging, upgrade handling is coarse). If you have Intune or Configuration Manager, prefer those. Use GPO Software Installation only where it is your sole option; use Group Policy for configuration regardless - see Group Policy Setup.

PDQ Deploy and generic scripts

Any tool that can run msiexec works. Use the command lines from Silent & Command-Line Install, install in the SYSTEM context with ALLUSERS=1, and capture /l*v logs.

After deployment

Deploy the ADMX templates and configure policy next - see Group Policy Setup. Policy and client install are independent; apply them in either order.

Silent & Command-Line Install Updates & Uninstall