VediramVediramSupport

Policy Reference

Every Vediram Deck Group Policy setting: registry value, type, scope, default, and effect

This is the complete reference for all 12 Deck policies. To install the templates and understand scope and precedence, start with Group Policy Setup.

Registry location

Every policy is a value under the Deck policy key:

  • Machine: HKLM\SOFTWARE\Policies\Vediram\Deck
  • User: HKCU\SOFTWARE\Policies\Vediram\Deck

Type mapping used by the ADMX templates:

Policy typeRegistry typeEncoding
BooleanREG_DWORD1 = enabled, 0/absent = disabled
IntegerREG_DWORDthe number
String / EnumREG_SZthe text value

You normally set these through the Group Policy editor; the registry details are given so you can verify applied policy or configure managed devices that ingest ADMX-backed settings.

Summary

PolicyCategoryScopeTypeDefault
ProfileManagementModeProfilesMachine + UserEnumFull
ManagedProfilesPathProfilesMachine + UserString (path)(none)
AllowedOfficeAppsFeaturesMachine + UserString (list)(all apps)
DisableLiveToggleFeaturesMachine + UserBoolean0 (off)
DisableCrashAnalysisFeaturesMachine + UserBoolean0 (off)
DisableTelemetryFeaturesMachine + UserBoolean0 (off)
DatabaseFolderFoldersMachine + UserString (folder)%LOCALAPPDATA%\Vediram\Deck
LogsFolderFoldersMachine + UserString (folder)%LOCALAPPDATA%\Vediram\Deck
CrashDumpsFolderFoldersMachine + UserString (folder)%LOCALAPPDATA%\CrashDumps
AutoStartGeneralUser onlyBoolean(user choice)
PollingIntervalGeneralMachine + UserInteger (1-120)(user choice; 5 min)
ManagementModeManagementMachine onlyEnumStandalone

The Excel OPENorder / ForceOn / ForceOff settings live under a separate Managed Extensions subkey and are documented in Managing Excel XLL Extensions.


Profiles

ProfileManagementMode

Controls what users can do with profiles.

  • Value: ProfileManagementMode (REG_SZ)
  • Scope: Machine + User · Default: Full
  • Allowed values:
    • Full - users can create, edit, delete, and activate any profile, including their own.
    • AdminOnly - users may only activate IT-managed profiles; they cannot create or edit profiles.
    • Disabled - profile management UI is unavailable.

Pair AdminOnly with ManagedProfilesPath to give users a fixed set of approved profiles to switch between. See Managing Profiles Centrally.

ManagedProfilesPath

Points Deck at a JSON file of IT-defined profiles.

  • Value: ManagedProfilesPath (REG_SZ)
  • Scope: Machine + User · Default: none
  • Format: a local or UNC path, e.g. \\fileserver\deck$\profiles.json
  • Effect: when set, Deck loads the managed profiles from that file at startup and presents them as read-only profiles. If unset, no managed profiles are loaded. File schema and behavior: Managing Profiles Centrally.

Features

AllowedOfficeApps

Restricts which Office applications Deck manages.

  • Value: AllowedOfficeApps (REG_SZ)
  • Scope: Machine + User · Default: all apps
  • Format: semicolon-delimited app names from Excel, Outlook, Word, PowerPoint - e.g. Excel;Outlook
  • Effect: add-ins belonging to apps not in the list are hidden from the UI and left unmanaged. If unset, all four apps are managed.

DisableLiveToggle

  • Value: DisableLiveToggle (REG_DWORD)
  • Scope: Machine + User · Default: 0
  • Effect: when 1, activating a profile only writes LoadBehavior registry values; Deck does not toggle add-ins in running Office processes. Changes take effect the next time the Office app starts. Use this where COM automation of running Office is undesirable.

DisableCrashAnalysis

  • Value: DisableCrashAnalysis (REG_DWORD)
  • Scope: Machine + User · Default: 0
  • Effect: when 1, Deck performs no crash analysis and the Crashes page is unavailable.

DisableTelemetry

  • Value: DisableTelemetry (REG_DWORD)
  • Scope: Machine + User · Default: 0
  • Effect: when 1, Deck collects no telemetry or crash-analytics data. (Deck makes no outbound network calls regardless; this policy governs local collection.)

Folders

All three folder policies accept a local or UNC path and override where Deck stores the corresponding data. Ensure the target exists and the user (per-user install) or SYSTEM (per-machine) can write to it.

DatabaseFolder

  • Value: DatabaseFolder (REG_SZ)
  • Scope: Machine + User · Default: %LOCALAPPDATA%\Vediram\Deck
  • Effect: relocates deck.db.

LogsFolder

  • Value: LogsFolder (REG_SZ)
  • Scope: Machine + User · Default: %LOCALAPPDATA%\Vediram\Deck
  • Effect: relocates core.log and core-error.log. Useful for redirecting logs to a collected location.

CrashDumpsFolder

  • Value: CrashDumpsFolder (REG_SZ)
  • Scope: Machine + User · Default: %LOCALAPPDATA%\CrashDumps
  • Effect: the folder Deck monitors for Office crash dumps. Change this if your organization redirects Windows Error Reporting local dumps elsewhere.

General

AutoStart

  • Value: AutoStart (REG_DWORD)
  • Scope: User only · Default: user choice
  • Effect: forces Deck's start-with-Windows behavior. 1 forces auto-start on; 0 forces it off. When configured, the user cannot change the setting. Deck's auto-start entry is HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\VediramDeck, which launches Vediram.Deck.Core.exe.

PollingInterval

  • Value: PollingInterval (REG_DWORD)
  • Scope: Machine + User · Default: user choice (5 minutes)
  • Allowed values: 1-120 (minutes)
  • Effect: forces the metrics polling interval and locks the control in Settings. Lower values give finer metrics resolution at slightly higher background cost.

Management

ManagementMode

  • Value: ManagementMode (REG_SZ)
  • Scope: Machine only · Default: Standalone
  • Allowed values:
    • Standalone - Deck operates entirely locally.
    • PortalManaged - records intent for future central-portal management. Setting it today shows a portal-managed indicator in the UI but does not change Deck's behavior; there is no portal connection in this release.

Leave this at Standalone unless directed otherwise.