What this lets you do
This article shows an IT administrator how to deploy the SchedEx desktop client to Windows PCs with Microsoft Intune. You add the Microsoft Store app SchedEx Desktop to Intune once. Intune then installs it on the PCs you choose, or offers it to users in Company Portal, and keeps it up to date automatically.
This works even if your organization has blocked the Microsoft Store for users. Blocking the Store app does not stop Intune from installing Store apps.
- Who it is for: IT administrators who manage Windows PCs with Microsoft Intune.
- Who can do it: a person with an Intune role that can add and assign apps, for example the built-in Application Manager role, or the Intune Administrator role in Microsoft Entra ID. No SchedEx role is needed.
Not sure this is the right article?
- You want to compare all ways to get the desktop client, or install it on your own PC: see Installing the SchedEx desktop client.
- You must deploy the installer file (
.msi) instead of the Store app, for example with Configuration Manager: see Downloading the desktop client installer from the Installation Center.
TABLE OF CONTENTS
- Before you start
- Add SchedEx Desktop to Intune
- Fill in the app information
- Assign the app — Required · Available for enrolled devices · Uninstall
- Review, create, and check the installation
- Deploy the .NET 10 Desktop Runtime
- Make SchedEx easy to find in Company Portal
- How updates work
- Keep the app information in Intune up to date
- If you must deploy the .msi instead
- Questions and answers
- Related articles
1. Before you start
At a glance
| Item | Value |
|---|---|
| App name in the Microsoft Store | SchedEx Desktop |
| Publisher | Promineo AS |
| Package identifier (Store ID) | 9P636SWQ0C8F |
| Store page | https://apps.microsoft.com/detail/9P636SWQ0C8F |
| Price | Free |
| Intune app type | Microsoft Store app (new) |
| Also needed on each PC | Microsoft .NET 10 Desktop Runtime (x64) (see chapter 6) |
Checklist
- An active Microsoft Intune subscription for your organization.
- Permission to add and assign apps in Intune. The built-in Application Manager role is enough. Intune Administrator also works. See Microsoft Intune built-in roles reference.
- PCs enrolled in Intune, running Windows 10 or Windows 11, 64-bit (x64).
- At least two processor cores on each PC. Microsoft requires this for Microsoft Store apps.
- The Intune Management Extension can run on the PCs. Intune uses it to install Microsoft Store apps.
- Network access from the PCs to the Microsoft Store and its content. See the Microsoft Store section of Network endpoints for Microsoft Intune.
- A Microsoft Entra group of the users or devices that should get SchedEx (for example "SchedEx users").
- A plan for the .NET 10 Desktop Runtime. The desktop client does not run without it.
Microsoft's own guide for this app type is Add Microsoft Store apps to Microsoft Intune.
2. Add SchedEx Desktop to Intune
- Sign in to the Microsoft Intune admin center.
- Select Apps > All Apps > Create. (You can also start from Apps > Windows.)
- In the Select app type pane, under Store app, select Microsoft Store app (new).
- Choose Select at the bottom of the pane. The app creation steps open: App information, Assignments, and Review + create.
- Select Search the Microsoft Store app. A search panel opens.
- In the search bar, type SchedEx Desktop. You can also search for the Store ID 9P636SWQ0C8F.
- In the results, check the Name (SchedEx Desktop) and the Publisher (Promineo AS). Select the app, then choose Select.
- On the App information page, check that Package Identifier shows 9P636SWQ0C8F.
Intune searches the United States Microsoft Store catalog by default. SchedEx Desktop is available there, so you do not need to change the region.
3. Fill in the app information
Intune fills in some fields from the Microsoft Store. Check each field, then select Next.
| Field | What to enter | Our advice |
|---|---|---|
| Name | Prefilled from the Store. | Keep SchedEx Desktop. This is the name users see in Company Portal. App names must be unique; if two apps have the same name, Company Portal shows only one of them. |
| Description | Prefilled from the Store. | Keep it, or add a line such as "Used to run SchedEx uploads and downloads. Sign in with your work account." |
| Publisher | Prefilled (Promineo AS). | Keep it. |
| Package Identifier | Read-only. | Must be 9P636SWQ0C8F. |
| Installer Type | Read-only. | Filled in by Intune. |
| Install behavior | System or User. | Choose System if your PCs are Microsoft Entra registered (Microsoft requires System there) or shared by several people. If the option is greyed out, the app supports only the selected behavior. Use the same behavior for all SchedEx deployments; Microsoft advises against mixing them. |
| Category | Optional. | Choose one, for example Productivity or Business, so users can browse to it. |
| Show this as a featured app in the Company Portal | Yes or No. | Yes if many users install it themselves. It then appears on the Company Portal home page. |
| Information URL | Optional. | https://exchange.help.ilap.org/support/solutions/articles/156000318223 (our installation article). Users see this link in Company Portal. |
| Privacy URL | Prefilled. | Keep it. |
| Developer / Owner / Notes | Optional. | For example, Owner: the team that supports SchedEx in your organization. |
| Logo | Optional. You upload it. | Upload a SchedEx icon so users recognize the app in Company Portal. Intune does not copy the Store icon for you. |
4. Assign the app
On the Assignments page, choose who gets the app and how. Select Add group (or Add all users / Add all devices) under one of the three assignment types.
| Assignment type | What happens | Best for |
|---|---|---|
| Required | Intune installs the app on the PCs of the selected groups. Users do nothing. | Everyone who must run SchedEx transfers. |
| Available for enrolled devices | Users install the app themselves from the Company Portal app or website. | People who need SchedEx now and then. |
| Uninstall | Intune removes the app from the PCs of the selected groups. | People who no longer need SchedEx. |
Required: install it automatically
- Under Required, select Add group and pick your SchedEx group.
- Optionally set End user notifications, Restart grace period, and Installation deadline.
- To leave out some users or devices, edit the assignment and change Filter mode from Included to Excluded. Select OK.
Available for enrolled devices: users install it from Company Portal
- Under Available for enrolled devices, select Add group (or Add all users). Pick a user group: Intune accepts Available assignments of Store apps only for user groups, not device groups.
- Tell your users where to find it. On the PC they open the Company Portal app, or the Company Portal website https://portal.manage.microsoft.com, find SchedEx Desktop, and select Install. Microsoft's user guide: Install work apps from Intune Company Portal app for Windows.
Company Portal itself is a Microsoft Store app. If your users do not have it yet, see Manually add the Windows Company Portal app.
Uninstall: remove it
Under Uninstall, select Add group and pick the users or devices that should no longer have SchedEx.
When you are done, select Next.
More about groups and assignments: Assign apps to groups with Microsoft Intune.
5. Review, create, and check the installation
- On the Review + create page, check the values you entered.
- Select Create. SchedEx Desktop now appears in Apps > All Apps.
Check the installation
- Go to Apps > All Apps and select SchedEx Desktop.
- The Overview shows how many devices and users have the app Installed, Not Installed, Failed, Install Pending, or Not Applicable.
- Under Monitor, select Device install status or User install status for details per device or user.
- For a report across apps, go to Apps > Monitor > App install status.
Microsoft Store apps assigned as Available do not report an installation status. You see status only for Required assignments.
See Monitor app information and assignments and Troubleshooting app installation issues.
6. Deploy the .NET 10 Desktop Runtime
The desktop client is built on .NET 10 and needs the Microsoft .NET 10 Desktop Runtime (x64) on each PC. The Store package does not install it. Without it, SchedEx does not start, and the user sees a message about .NET.
The runtime is installed for the whole PC and needs administrator rights, so deploy it with Intune too. Assign it as Required to the same groups as SchedEx Desktop.
Common ways to deploy it:
- As a Win32 app. Download the x64 installer for .NET Desktop Runtime 10.0.x from Download .NET 10.0. Wrap it with the Microsoft Win32 Content Prep Tool and add it as a Win32 app (Add, assign, and monitor a Win32 app). Install command:
windowsdesktop-runtime-10.0.x-win-x64.exe /install /quiet /norestart(use the real file name). Microsoft documents these switches in Install .NET on Windows. The installer returns 0 for success and 3010 when a restart is needed. - With WinGet, if you already deploy apps that way. The package ID is
Microsoft.DotNet.DesktopRuntime.10. - With your existing patching or software tool, if it already handles .NET.
Microsoft Update can keep the runtime patched after it is installed.
An Intune app dependency cannot link the runtime to SchedEx Desktop, because dependencies work only between Win32 apps. Assign both apps to the same groups instead.
7. Make SchedEx easy to find in Company Portal
This matters most for Available assignments, where users install the app themselves.
- Category. Put SchedEx Desktop in a category users browse, such as Productivity or Business.
- Featured app. Set Show this as a featured app in the Company Portal to Yes. The app then appears on the Company Portal home page.
- Logo. Upload the SchedEx icon. Users recognize an app by its icon faster than by its name.
- Information URL. Link to
https://exchange.help.ilap.org/support/solutions/articles/156000318223so users can read how to get started. - Description. Say in one sentence who needs the app and what to do after installing ("Sign in with your work account").
- Support details. Your helpdesk details appear in Company Portal under Help & support. Set them in Tenant administration > Customization. See How to configure the Intune Company Portal apps, Company Portal website, and Intune app.
You can change all of these later in Apps > All Apps > SchedEx Desktop > Properties > App information > Edit.
8. How updates work
Apps deployed from the Microsoft Store are automatically kept up to date. When we publish a new SchedEx Desktop version in the Microsoft Store, the PCs get it without any work from you.
For this to work:
- Do not enable the policy "Turn off Automatic Download and Install of updates". Microsoft states that this policy must not be enabled for Store apps to update. Recommended value: Not configured or Disabled. In Intune you find it in the Settings Catalog under Microsoft App Store > Allow apps from the Microsoft app store to auto update; in Group Policy under Administrative Templates > Windows Components > Store. (CSP: ApplicationManagement/AllowAppStoreAutoUpdate.)
- The policy "Turn off the Store application" is fine. It stops users from installing apps from the Microsoft Store themselves, but it does not affect Intune's ability to install Microsoft Store apps, and it does not stop automatic updates.
So you can block the Store for users and still deploy and update SchedEx through Intune. Microsoft explains all related Store policies in Add Microsoft Store apps to Microsoft Intune.
Keep the .NET 10 Desktop Runtime patched too (chapter 6). Store updates of SchedEx do not update the runtime.
9. Keep the app information in Intune up to date
Intune does not automatically synchronize changes to app metadata (name, description, icon) after an app has been added from the Microsoft Store. App updates still work normally: the program itself is updated as described in chapter 8.
When you add the app, Intune copies the name and description from the Store, and you upload the logo yourself. After that, these fields stay as they are in Intune, even if we change them in the Microsoft Store.
Typical trigger: SchedEx changes its name, description, or icon. For example, after the app was renamed to "SchedEx Desktop", Intune entries created before the rename kept the earlier name in Company Portal until an administrator edited them.
To update the information by hand:
- Sign in to the Microsoft Intune admin center.
- Select Apps > All apps and select the SchedEx Desktop app (it may still have its old name).
- Select Properties.
- Select Edit next to App information.
- Update Name, Description, and, if needed, upload the new Logo.
- Select Review + save, then Save.
Users see the new name, description, and icon in Company Portal after their next refresh.
References: Add Microsoft Store apps to Microsoft Intune (name and description are prefilled from the Store when you add the app and can be edited; the logo is uploaded by the admin; apps are kept up to date automatically) and Add built-in apps (the general edit path Apps > All Apps > app > Properties > Edit next to App information).
10. If you must deploy the .msi instead
Some organizations cannot use the Store app type, for example because they do not allow Store content at all. Then a SchedEx Tenant Admin downloads the installer (.msi) from the SchedEx Installation Center (see Downloading the desktop client installer from the Installation Center) and gives it to you. You deploy it as a Win32 app (recommended) or a line-of-business app.
The .msi does not update automatically. You must download and deploy every new version yourself. That is why we recommend the Store app type when you can use it.
What to know about the .msi: it installs silently with msiexec /i "Client_<version>_x64.msi" /qn, needs administrator rights, needs the .NET 10 Desktop Runtime (x64) (chapter 6), and upgrades an older SchedEx .msi installation in place.
IT tip: the installer puts its shortcut on the desktop of the account that installs it. When you deploy in system context, add
ALLUSERS=1to the install command (msiexec /i "Client_<version>_x64.msi" ALLUSERS=1 /qn) so the program is installed for all users of the PC. Test on one PC first and check that users see the SchedEx shortcut.
Intune Win32 app (recommended for the .msi)
The Win32 app type gives IT full control over the install command, detection, and updates.
- Package the
.msiwith the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe). It creates an.intunewinfile and reads the MSI information Intune needs. - In the Microsoft Intune admin center, select Apps > All Apps > Create, select the Windows platform, then Windows app (Win32), and choose Select.
- Upload the
.intunewinfile and fill in the app information. - On the Program page, set the Install command (see the IT tip above), and set Install behavior to System.
- On the Detection rules page, use the MSI rule (product code).
- Assign the app (Required or Available for enrolled devices), then Review + create.
Microsoft's guides: Win32 app management in Microsoft Intune and Add and assign Win32 apps.
Deploy the .NET 10 Desktop Runtime as a Win32 app too. Then you can add it to SchedEx as a dependency, so Intune installs the runtime first.
Intune line-of-business app
Simpler, with fewer options.
- In the Microsoft Intune admin center, select Apps > All Apps > Create.
- In the Select app type pane, select the Windows platform, then Line-of-business app, and choose Select.
- Select Select app package file, browse to the
.msi, and select OK. - Fill in the App information. App Install Context is set from the package.
- Assign the app and select Create.
Microsoft's guide: Add a Windows line-of-business app to Microsoft Intune.
Microsoft advises against mixing Win32 apps and line-of-business apps during Windows Autopilot enrollment, because both use the Trusted Installer service. Choose one app type for SchedEx.
Deploy each new version
- Ask a Tenant Admin to download the new
.msifrom the Installation Center. - Intune Win32 app: add the new version as a new Win32 app and set it to supersede the previous one. Because the
.msiupgrades itself, leave Uninstall previous version off. See Add Win32 app supersedence. Or, for a line-of-business app: go to Apps > All Apps, select the app, select Properties, select Edit next to App information, select the file next to Select file to update, and upload the new.msi. Check that App version shows the new version. See Update a line-of-business app. - Check the installation status (see chapter 5).
11. Questions and answers
Our users cannot open the Microsoft Store. Will this still work? Yes. The policy Turn off the Store application does not affect Intune's ability to install Microsoft Store apps, and Store apps still update automatically as long as Turn off Automatic Download and Install of updates is not enabled.
I cannot find SchedEx Desktop when I search in Intune. Search for the Store ID 9P636SWQ0C8F. Make sure the region is the default (United States). Microsoft lists other reasons an app may not appear: it is not available in the region, it is a paid app, or its platform is not supported. SchedEx Desktop is free.
Should I choose System or User install behavior? Choose System for Microsoft Entra registered PCs (Microsoft requires it) and for shared PCs. Otherwise either works. Do not mix both for the same app.
After assigning a System app to a PC that already had it, Intune shows error 0x87D1041C. Microsoft documents this: the app "was not detected after installation completed successfully", but it is still installed correctly. You can ignore it for PCs that already had SchedEx.
Company Portal says "Requirements Not Met" when a user selects Install. This happens when the install behavior is User, the assignment is Available, and the PC is only Microsoft Entra registered. Change the install behavior to System, or make sure the PC is Microsoft Entra joined.
SchedEx installed but does not start, and the user sees a message about .NET. The .NET 10 Desktop Runtime is missing. Deploy it as described in chapter 6.
Does Intune install SchedEx on ARM-based PCs? No. SchedEx Desktop is built for 64-bit (x64) Windows, and Microsoft Store apps with an ARM64 installer are not supported by this Intune app type.
Users still see an old name or icon in Company Portal. Intune does not copy name, description, or icon changes from the Store. Edit them by hand, see chapter 9.
Some users installed the .msi earlier. What do we do?
Remove the .msi version from those PCs (for example with an Uninstall assignment of the old line-of-business or Win32 app) and assign the Store app instead. Running both side by side can leave users on two different versions.
How do I see which SchedEx version people use? Intune does not show version numbers for Microsoft Store apps in Device install status. In SchedEx, a Tenant Admin sees each user's version, and which versions are outdated, in Tenant Admin > Clients > Desktop Client.
Do we need a SchedEx license or role to deploy the app? No. Deploying needs only Intune permissions. Each user needs a SchedEx account to sign in.
12. Related articles
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article