Deploy Onplana Schedule and Onplana Tasks with Intune

This guide is for the IT administrator who installs Onplana Schedule and Onplana Tasks on company devices with Microsoft Intune or another device management (MDM) tool. You install the apps the way you install any other desktop app, and you can push three settings so every seat opens a sign-in that is already pointed at your workspace.

The settings are read from the next Onplana Tasks desktop release and from Onplana Schedule 0.5.2. An older version ignores them and behaves as a hand install does.

If you only want the apps on your own computer, see Install Onplana Tasks for Windows or Open Microsoft Project files with Onplana Schedule instead.

What your users get

• Their workspace, already named. With WorkspaceSlug set, Sign in opens the Onplana sign-in page with your workspace filled in. Onplana Tasks also says on its sign-in screen: “Your organization set up this app for the <slug> workspace.”
• Sign in with Microsoft, preselected. With SignInProvider set to microsoft, Sign in goes straight to Sign in with Microsoft, with no Onplana sign-in page in between. Onplana Tasks labels its button Sign in with Microsoft.
• Sign-in at first launch. With ConnectAtFirstLaunch on, the first launch of Onplana Tasks on a device opens the sign-in by itself, once. A person who cancels is not asked again on the next launch.

Create an account is never changed by these settings.

Caution

Company single sign-on (SAML or OIDC) does not finish sign-in from the desktop apps yet. Set SignInProvider to microsoft as well as WorkspaceSlug, or have people use Sign in with Microsoft or their password on the sign-in page.

Install the apps

From the Microsoft Store (Windows)

In Intune, go to Apps then Windows, add a Microsoft Store app (new), and search for the app by its Store id.

App	Microsoft Store id
Onplana Schedule	9PF2FKJNGTLG
Onplana Tasks	9N2XMV176WMT

A Store install updates through the Microsoft Store.

From the direct download (Windows)

Both apps also ship an NSIS installer (.exe) and an MSI from onplana.com/download. These are the switches the apps’ own updater uses:

Installer	Silent	With progress, no questions
NSIS .exe	<installer>.exe /S	<installer>.exe /P
MSI	msiexec /i <installer>.msi /quiet	msiexec /i <installer>.msi /passive

The NSIS installer installs for the signed-in user only, without Administrator rights. For a device-wide push, use the Store app, or confirm the MSI’s install scope on a pilot device before you roll it out.

On a Mac

Install from the Mac App Store, or from the DMG on onplana.com/download.

The three settings

Every setting is optional. Set one, two or all three.

Setting	Type	What it does
WorkspaceSlug	String (REG_SZ; plist <string>)	Your organization’s slug, the short name in your Onplana web address and in organization settings. Lowercase letters, digits and hyphens. Spaces around it are trimmed and capitals are lowercased; any other value is ignored.
SignInProvider	String (REG_SZ; plist <string>)	microsoft sends Sign in straight to Sign in with Microsoft. Any other value is ignored. When both this and WorkspaceSlug are set, this one decides the page Sign in opens.
ConnectAtFirstLaunch	DWORD 0 or 1 (plist <true/>, <false/> or <integer>)	Onplana Tasks opens the sign-in by itself at the first launch on a device. Onplana Schedule reads this setting but does not act on it yet.

Onplana Schedule presets the page Sign in opens, as Onplana Tasks does. Its sign-in screen does not name the workspace yet.

Windows: policy registry keys

Each app reads its own key, so you can configure one without the other.

App	Key
Onplana Tasks	HKLM\SOFTWARE\Policies\Onplana\Tasks
Onplana Schedule	HKLM\SOFTWARE\Policies\Onplana\Schedule

The same paths under HKCU are read too, for a user-scoped profile. For each value, HKLM wins, and HKCU only fills a value HKLM does not set. A normal user cannot write under SOFTWARE\Policies, so people cannot set or clear these values themselves.

Onplana ships no ADMX file, so the simplest way to write the key in Intune is a platform script or a Remediation, run as SYSTEM:

$k = 'HKLM:\SOFTWARE\Policies\Onplana\Schedule'
New-Item -Path $k -Force | Out-Null
New-ItemProperty -Path $k -Name WorkspaceSlug -Value 'acme-corp' -PropertyType String -Force
New-ItemProperty -Path $k -Name SignInProvider -Value 'microsoft' -PropertyType String -Force
New-ItemProperty -Path $k -Name ConnectAtFirstLaunch -Value 1 -PropertyType DWord -Force

Use Tasks in place of Schedule in the first line for Onplana Tasks. The same values as a .reg file, for both apps:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Onplana\Tasks]
"WorkspaceSlug"="acme-corp"
"SignInProvider"="microsoft"
"ConnectAtFirstLaunch"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Onplana\Schedule]
"WorkspaceSlug"="acme-corp"
"SignInProvider"="microsoft"
"ConnectAtFirstLaunch"=dword:00000001

Replace acme-corp with your organization’s slug.

macOS: a configuration profile

Each app reads its own preference domain, its bundle id.

App	Preference domain
Onplana Tasks	com.onplana.tasks
Onplana Schedule	com.onplana.schedule

Only managed (forced) values are read: a configuration profile with a Custom Settings or Preference file payload for the domain, or a file at /Library/Managed Preferences/<domain>.plist. A value someone writes with defaults write is ignored.

The payload for one domain:

<dict>
  <key>WorkspaceSlug</key><string>acme-corp</string>
  <key>SignInProvider</key><string>microsoft</string>
  <key>ConnectAtFirstLaunch</key><true/>
</dict>

Add one payload for com.onplana.tasks and one for com.onplana.schedule if you deploy both apps.

When no setting is pushed

Nothing is required. With no settings, or with values the app cannot use, both apps behave exactly as a hand install does: Sign in opens the usual Onplana sign-in page. A missing key or a value of the wrong type never stops an app from launching.

Check it on a seat

1. On a test device, confirm the values arrived. On Windows, open the key in Registry Editor. On a Mac, run defaults read com.onplana.tasks (or com.onplana.schedule) and look for your three values.

2. Install the app and launch it for the first time. With ConnectAtFirstLaunch on, Onplana Tasks opens the sign-in by itself.

3. On the Onplana Tasks sign-in screen, check for “Your organization set up this app for the <slug> workspace.” and a Sign in with Microsoft button.

4. Click Sign in. With SignInProvider set to microsoft, Microsoft’s sign-in opens directly. With only WorkspaceSlug, the Onplana sign-in page opens with your workspace filled in.

If nothing changed, check the app’s version first, then the key path or the preference domain, and that WorkspaceSlug holds only lowercase letters, digits and hyphens.

FAQs

Do the apps cost anything? No. Onplana Schedule and Onplana Tasks are free to install, and people sign in to the workspace your organization already has.

Can I configure only one of the apps? Yes. Each app has its own registry key and its own preference domain.

Can a user change the settings? No. On Windows the key sits under SOFTWARE\Policies, which only an administrator can write. On a Mac only managed values are read.