Skip to content

Enterprise Deployment

GitWyrm can be installed silently and deployed through Intune, Configuration Manager, Group Policy, or any scripted automation.

How GitWyrm installs

GitWyrm installs per-user into %LOCALAPPDATA%\GitWyrm. It never requires administrator rights and never writes outside the user's profile.

This matters for deployment: GitWyrm must run in a user context, not as SYSTEM. Installing as SYSTEM appears to succeed but places the app in the system profile, where no real user can launch it.

The file you deploy, GitWyrm-Setup.exe, is a small bootstrapper. It downloads the current release from https://cdn.gitwyrm.com and installs it.

Installer switches

GitWyrm-Setup.exe [options]
SwitchEffect
/S, /silentInstall with no user interface and no prompts. Required for automated deployment.
/log <path>Write the setup log to <path> instead of %TEMP%. /log=<path> also works.
/norestartAccepted and ignored. GitWyrm setup never reboots the machine.
/?Show usage.

Switches are case-insensitive, and the --silent / --log long forms are accepted as well.

Exit codes

The bootstrapper returns a status your deployment tool can act on.

CodeMeaning
0Success
1Bad command line
2Download failed - check network access to cdn.gitwyrm.com
3The installer ran but failed

Logging

Setup writes a log to %TEMP%\GitWyrm-Setup.log unless /log overrides it. Collect this file when reporting a failed deployment.

GitWyrm-Setup.exe /S /log "C:\Logs\GitWyrm-Setup.log"

Deploying with Intune

1. Package the installer

Put GitWyrm-Setup.exe in an otherwise empty folder and wrap it with the Microsoft Win32 Content Prep Tool:

IntuneWinAppUtil.exe -c C:\package -s GitWyrm-Setup.exe -o C:\output

2. Create the app

In Intune, create a Windows app (Win32) and upload the resulting .intunewin file.

SettingValue
Install commandGitWyrm-Setup.exe /S /log "%TEMP%\GitWyrm-Setup.log"
Uninstall command"%LOCALAPPDATA%\GitWyrm\uninstall.exe" /S
Install behaviorUser
Device restart behaviorNo specific action

Install behavior must be User

GitWyrm is a per-user application. Leaving this set to System installs into the system profile and users will not see the app.

3. Detection rule

Use a file rule:

  • Rule type: File
  • Path: %LOCALAPPDATA%\GitWyrm
  • File or folder: GitWyrm.exe
  • Detection method: File or folder exists

To require a minimum version instead, use detection method String (version) with the operator Greater than or equal to and the version you are deploying.

Deploying with a script

The bootstrapper is a normal executable, so any automation that can run a command works. Check the exit code rather than assuming success.

powershell
$setup = "\\server\share\GitWyrm-Setup.exe"
$log = "$env:TEMP\GitWyrm-Setup.log"

$proc = Start-Process $setup -ArgumentList '/S', "/log=$log" -PassThru
$proc.WaitForExit()

if ($proc.ExitCode -ne 0) {
  Write-Error "GitWyrm install failed with exit code $($proc.ExitCode). See $log"
  exit $proc.ExitCode
}

Wait on the bootstrapper, not the process tree

The installer launches GitWyrm when it finishes. The bootstrapper still exits immediately with its own status, so Intune records the result correctly. In scripts, wait on the bootstrapper process itself as shown above. Start-Process -Wait waits on the whole process tree and will block until the user closes GitWyrm.

Network requirements

Setup downloads over HTTPS from cdn.gitwyrm.com. Allow egress to that host.

Proxies

If the machine reaches the internet through a proxy, set HTTPS_PROXY (or ALL_PROXY) in the environment setup runs in:

powershell
$env:HTTPS_PROXY = 'http://proxy.corp.example:8080'
GitWyrm-Setup.exe /S

Setup does not read Windows' system-wide proxy configuration, so the environment variable is required.

Proxies requiring authentication are supported with the usual http://user:password@host:port form. Credentials are redacted from the setup log.

Installing without internet access

There is no separate offline installer. If the target machines cannot reach the CDN at install time, download the full installer for the version you are deploying - GitWyrm_<version>_x64-setup.exe (or arm64) from the releases page, or the version-pinned copy at https://cdn.gitwyrm.com/releases/<version>/GitWyrm-Setup.exe - and deploy that directly instead of the bootstrapper. It accepts the same /S switch.

Uninstalling

"%LOCALAPPDATA%\GitWyrm\uninstall.exe" /S

This removes the application. It runs in the user's context and returns 0 on success.