IT deployment guide

1. Install the Enterprise MSIX

Use the Enterprise MSIX from TechXperts, not the Microsoft Store version. It is signed by TechXperts with a certificate that chains to a public Microsoft root, so PCs trust it with no certificate to import.

Many PCs, with Intune

In the Intune admin center go to Apps, Windows, Add, choose "Line-of-business app", and upload the .msix. Assign it to the device group, as Required.

A small business, with automatic updates

Download Snapper.appinstaller from TechXperts and open it (click it twice). Windows' App Installer shows Snapper and an Install button. After that, Windows checks for a new version about once a day, and the update applies the next time Snapper starts after Windows has found it.

Microsoft has turned off web links that open App Installer in one click, so the file must be downloaded and opened. Companies that manage PCs with Intune should keep deploying the plain MSIX. Do not mix the two on one PC.

One PC, by hand

In an elevated PowerShell:

Add-AppxPackage -Path .\Snapper-Enterprise.msix

No certificate import is needed. Only a test signed package from TechXperts needs its certificate added with Import-Certificate first.

Snapper starts from the Start menu and runs from the tray. It starts at sign in only if the person turns on Open at Login in Settings.

2. Install the Group Policy templates

1. On a domain controller, or on the PC where you edit policy, copy Snapper.admx into the PolicyDefinitions store, and the en-US folder's Snapper.adml into the store's en-US folder.
   • Central store: \\<domain>\SYSVOL\<domain>\Policies\PolicyDefinitions\ and its en-US folder.
   • A single PC: C:\Windows\PolicyDefinitions\ and C:\Windows\PolicyDefinitions\en-US\.
2. Open the Group Policy Management Editor for a GPO linked to the PCs.
3. Go to Computer Configuration, Administrative Templates, TechXperts, Snapper. The settings are machine scope, so they apply to everyone who uses the PC.
4. Set what you need (the table below), then run gpupdate /force on a test PC.

Snapper reads the policy at startup, every hour, when the PC wakes and when its settings change. A changed setting reaches a running Snapper within the hour, or at once on a restart.

3. The settings

All values live under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\TechXperts\Snapper. A value that is missing, of the wrong type or out of range counts as not set.

Not configured, or the value removed, means people choose for themselves. Their own choices are kept on disk, so removing a lock gives them back what they had.

4. The same settings with Intune or any registry tool

Group Policy is not required. Intune can set the same registry values with a PowerShell script, a Win32 app or a remediation script. No OMA-URI setting is needed. A sample .reg file with every value:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\TechXperts\Snapper]
"LicenseKey"="SNAP-CO-paste-your-whole-key-here"
"ForceEphemeralMode"=dword:00000001
"DisableRecording"=dword:00000003
"DisableAudio"=dword:00000001
"SaveFolder"="D:\\Captures"
"HideSubscribe"=dword:00000001

Keep only the lines you want. The same in PowerShell, run as administrator, or as SYSTEM from Intune.

Run it in 64 bit PowerShell. In Intune, set "Run script in 64 bit PowerShell Host" to Yes. Intune runs scripts in 32 bit PowerShell by default, and there HKLM:\SOFTWARE\Policies is redirected to HKLM\SOFTWARE\WOW6432Node\Policies.

$key = 'HKLM:\SOFTWARE\Policies\TechXperts\Snapper'
New-Item -Path $key -Force | Out-Null
Set-ItemProperty -Path $key -Name LicenseKey -Value 'SNAP-CO-paste-your-whole-key-here' -Type String
Set-ItemProperty -Path $key -Name DisableRecording -Value 3 -Type DWord

From a 32 bit host you can still write the 64 bit key with reg.exe and /reg:64:

reg add "HKLM\SOFTWARE\Policies\TechXperts\Snapper" /v DisableRecording /t REG_DWORD /d 3 /f /reg:64

Snapper reads the 64 bit key first. If that key doesn't exist at all, it reads the 32 bit one (HKLM\SOFTWARE\WOW6432Node\Policies\TechXperts\Snapper) instead, so a policy already written from 32 bit PowerShell still applies. Both keys can only be changed by administrators. Use one of the two, not both: when the 64 bit key exists, the 32 bit one is ignored.

To lift a setting, delete its value.

5. Renewing

Your key has a start and an end date. Push the new key before the end date: change the Company license key setting (or the LicenseKey value) and let it reach the PCs. A running Snapper picks it up within the hour. There is nothing to reinstall.

• For the last 30 days before the end date, Snapper shows a reminder (see below).
• After the end date there are 14 days of grace: Snapper Pro keeps working, with a notice that the license has ended.
• After that, Snapper Pro is off on those PCs, and Snapper goes back to its usual trial and Store rules.

A new key whose start date is still in the future is ignored until that day, so you can push next year's key early.

A key pasted into Settings by a person is kept as a fallback. When the policy sets a key, the policy's key is the one used. That stays true after your key has ended: while the policy's key is expired, a key a person pastes does not take over. So renew by pushing the new key through the policy.

6. What people see

Settings, Snapper Pro tab

• Company key set by policy: the company name with "Set by your organization", and the status line. There is no Subscribe button, and no Enter company key button.
• Company key in force: "Licensed to {Company} until {date}".
• In the last 30 days: the same line, then "Ends on {date}. Ask your IT team to renew."
• In the 14 days after: "Your company license has ended. Ask your IT team to renew."
• With no policy key, the tab has "Enter company key…" (paste the key and choose Use Key), and "Remove company key" once one is in. A key pasted wrong gives "That key isn't valid". A pasted key that has not started yet shows "Starts on {date}" in muted text.

Reminder toast

Once, when the key enters its last 30 days: "Your company's Snapper license ends on {date}" with "Ask your IT team to renew."

Locked controls

A setting you lock is shown disabled in Settings with "Set by your organization" under it: Ephemeral Mode (on), the audio choices (off), the Save Folder (your folder).

Recording turned off

Starting a turned off recording from a shortcut, the panel, the tray menu or the taskbar jump list shows the toast "Recording is turned off by your organization". Screenshots still work.

Hide Subscribe

Where Snapper Pro would be offered, people see the toast "Snapper Pro isn't set up on this PC" with "Ask your IT team.", and the Snapper Pro tab says the same instead of offering Subscribe.

7. Updates

Updates for the Enterprise package come from TechXperts.

PCs installed from Snapper.appinstaller (section 1) update themselves. Windows checks for a new version about once a day, and the update applies the next time Snapper starts after that check. Snapper runs in the tray and may stay open for days, so a PC can take longer than a day. Windows does the checking, not Snapper.

PCs installed from the plain MSIX, including Intune deployments, do not update themselves. Deploy the new MSIX the same way as the first.

8. Troubleshooting

• The Diagnostic Log (Settings, General) says which company key is in use, why a key was ignored (not valid, or starts later) and what the policy set. Its lines never contain the key itself.
• A setting not taking effect: check gpresult /r or the registry path in section 3, and that the value type matches the table.
• Snapper Pro still shows Subscribe: the key may be for another product, mistyped, or not started yet. Check the log.