For administrators

Manage OneMount with Group Policy

Set application parameters centrally on every device in your organization — from the tenant address and the set of drives to the interface language and update policy. Via Active Directory (GPO) or Microsoft Intune, with familiar ADMX templates.

Download templates (ZIP) How to deploy

English · Ukrainian · Spanish · compatible with OneMount 1.0 and later

OneMount-ADMX.zip

OneMount.admx
en-US / uk-UA / es-ES
README with instructions
15 settings in 5 groups

How it works

The template describes to the administrator which settings to configure. OneMount reads them from the registry (SOFTWARE\Policies\OneMount) and only reads — so a policy always wins over the user's own settings, and a managed setting becomes disabled in the app with a "managed by your organization" note.

Add the templates

To the domain Central Store, locally, or to Intune (see below).

Configure the policies

In the "OneMount" section — computer or user scope, your choice.

Apply

gpupdate /force and restart OneMount on the devices.

Managed settings

15 policies in five groups. Each comes with a detailed description right in the policy editor.

Sign-in

SharePoint sign-in address

The tenant for automatic sign-in — users don't need to know it.
Automatic sign-in at startup

Silent Single Sign-On with the device account.
Block signing in with another account

Only the account of this device.

Drives

Configure drives to connect

The set of drives arrives by policy — letter and library address.
Prevent changing drives

The drive list becomes read-only for the user.
Restrict allowed drive letters

So network drives don't clash with other systems.

User interface

Interface language

Automatic / Ukrainian / English / Español.
Interface theme

Light / Dark / Follow Windows.
Hidden-files notifications

Controls the alerts about overly long paths.
Office hyperlink warning

Links from Outlook and Teams open in one click.

Maintenance and updates

Renewal and health-check intervals

How often the session and drives are checked in the background.
Disable automatic updates

You control the roll-out of new versions.
Custom update source

Serve updates from inside your network.

Licensing

Organization enrollment key

Every user of a managed device automatically becomes a member of your organization — no manual email list in the portal. More about deploying with the key.

How to deploy the templates

Pick the scenario that fits your infrastructure.

Domain (Active Directory)

Copy the files to the Central Store — the policies become available on every domain controller and workstation:

            \\<domain>\SYSVOL\<domain>\Policies\
PolicyDefinitions\OneMount.admx

            …\PolicyDefinitions\en-US\OneMount.adml
          

Manage in the Group Policy Management Console (GPMC), linking GPOs to the OUs you need.

Microsoft Intune

In the admin center:

Devices → Configuration → Create → Import ADMX.
Upload OneMount.admx first, then the OneMount.adml files you need.
Create a configuration profile based on the imported template and assign it to your groups.

The settings appear among the profile options.

Standalone workstation

Copy the files to the local policy store:

            C:\Windows\PolicyDefinitions\
OneMount.admx

            …\en-US\OneMount.adml
          

Manage via gpedit.msc → Administrative Templates → OneMount.

Tip. If the domain has an active Central Store, the policy editor takes templates only from there and ignores the local folder. After changing policies, run gpupdate /force on the device and restart OneMount — settings are read at startup. The full guide is in the README.md inside the archive.

Deploying with the organization key

The key removes the manual user list: everyone who signs in to OneMount on a managed machine automatically joins your organization and gets a license as soon as a seat is free.

Where to get the key

In the customer portal on the "Organization" page — the "Organization ID" block, format XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.

Keep the key secret: anyone who has it can join users to your organization and occupy paid seats. If it leaks, click "Regenerate" in the portal — the old key stops working instantly, existing members are not affected.

Option 1 — silent installer

For Intune, SCCM or a deployment script — the key is passed as a parameter and written during installation:

            OneMount-Setup.exe /VERYSILENT /SUPPRESSMSGBOXES
  /OrgKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
          

During a regular (non-silent) install the key can be entered on a dedicated wizard page. App self-updates never touch the key.

Option 2 — Group Policy

The "Organization enrollment key" policy (the "Licensing" category of these very templates), or the registry value directly:

            HKLM\SOFTWARE\Policies\OneMount
  OrgKey (REG_SZ) = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
          

The key is read live, so the policy also applies to already installed copies — nothing needs to be reinstalled. The policy takes priority over the installer key.

What happens next

The user signs in to OneMount with their Microsoft account — and immediately becomes an organization member (visible in the portal, with an event log record).
If a paid seat is free, a license is issued automatically by that same request.
If seats run out, the user works on their own trial and is marked "over seats" in the portal: buy more seats and the license follows automatically.
A member of another organization is never pulled in by the key — conflicts are excluded.