title | description | ms.assetid | ms.reviewer | manager | ms.service | author | ms.author | ms.topic | ms.date | ms.localizationpriority | appliesto | |||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Install apps on Surface Hub |
Learn how to install and manage apps on Surface Hub devices using WinGet, the Microsoft Store, and other deployment methods. |
3885CB45-D496-4424-8533-C9E3D0EDFD94 |
dpandre |
frankbu |
surface-hub |
coveminer |
chauncel |
how-to |
08/15/2024 |
medium |
|
You can install more apps on your Surface Hub to fit your team or organization's needs. There are different methods for installing apps depending on whether you're developing and testing an app, or deploying a released app.
- Surface Hub only runs UWP apps. Apps created using the MSIX Packaging Tool do not run on Surface Hub.
- Surface Hub only supports offline-licensed apps.
- Apps must be targeted for the Universal device family or Windows Team device family.
- By default, apps must be signed to be installed. During testing and development, you can also choose to run developer-signed UWP apps by placing the device in developer mode.
- You need admin credentials to install apps on your Surface Hub.
There are several options for installing apps that have been released to the Microsoft Store, depending on whether you want to evaluate them on a few devices, or deploy them broadly to your organization.
To install released apps:
- Download apps using the Microsoft Store app, or
- Download app packages from the Microsoft Store via the WinGet command-line package manager and distribute them using a provisioning package or supported MDM provider.
To evaluate apps on an individual Surface Hub, you can use the Microsoft Store app on Surface Hub to browse and download apps.
Note
Using the Microsoft Store app is not the recommended method of deploying apps at scale to your organization. In an enterprise enviroment with multiple Surface Hubs, deploy apps with a provisioning package or via an MDM provider, such as Microsoft Intune.
- To download apps, you must sign in to the Microsoft Store app with a Microsoft account or organizational account. However, you can only connect an account to a maximum of 10 devices at once. If you have more than 10 Surface Hubs, you will need to create multiple accounts or remove devices from your account between app installations.
- To install apps, you will need to manually sign in to the Microsoft Store app on each Surface Hub you own.
- From your Surface Hub, open Settings.
- Enter device admin credentials when prompted.
- Navigate to Surface Hub > Apps & features.
- Select Open Store and search for the app you're looking for.
With the retirement of the Microsoft Store for Business, organizations need a robust alternative for managing and deploying applications across multiple Surface Hub devices. WinGet, Microsoft's command-line package manager, fills this gap by offering IT pros a powerful and flexible tool for discovering, downloading, and installing applications. This transition to WinGet ensures that organizations can maintain control over their app deployment processes while benefiting from improved automation and consistency across devices. By adopting WinGet, you can streamline application management and ensure a smooth transition away from the now-deprecated Store for Business.
- By default, WinGet is preinstalled on Windows 10 (version 1809 and later) and Windows 11. To confirm you have WinGet installed, open a command prompt and enter winget.
- Ensure you're running WinGet 1.8 or later.
- If WinGet isn't present or you need the latest version, follow these instructions: Install WinGet.
In this scenario, use WinGet to download an app package for Surface Hub.
-
Enter the following command:
Replace
<app-id>
with the specific ID of the app you want to download.winget download <app-id> --platform windows.universal -a x64 --skip-license
Example command:
winget download 9WZDNCRFHVJL --platform windows.universal -a x64 --skip-license
-
Agree to the terms:
If prompted, agree to the terms as part of the download process.
:::image type="content" alt-text="Screenshot of app download via WinGet." source="images/download-app-winget-example.png":::
-
View the downloaded files:
After the download completes, the files are saved in a new subdirectory within your Downloads folder. This folder contains the app package and any necessary dependency files.
-
Deploy the app via a provisioning package or your MDM provider.
- 9WZDNCRFHVJL: The Microsoft Store app ID; in this example, Microsoft OneNote.
- platform windows.universal: Refers to the Universal Windows Platform (UWP), which means the package is designed to run on multiple Windows devices, including Surface Hub, PCs, tablets, and other devices that support UWP.
- -a x64: Specifies the architecture of the package, compatible with 64-bit Windows systems.
- --skip-license: Bypasses the requirement to accept the license agreement before downloading the package. By using this flag, you're automatically accepting the license terms without being prompted during the download process.
Find compatible apps with keywords related to Surface Hub or by filtering for Universal Windows Platform (UWP) apps.
Use the following command in the command prompt:
winget search --tag "Surface Hub"
This command searches for apps tagged with "Surface Hub," indicating they're optimized for Surface Hub devices.
If you're looking for UWP apps that are compatible with Surface Hub, you can filter your search with a command like this:
winget search --source msstore --query uwp
This shows UWP apps from the Microsoft Store, many of which can run on Surface Hub.
If you have an idea of the type of app you're looking for, such as collaboration tools or specific software by name, you can search more directly:
winget search "collaboration"
Or
winget search "Microsoft Whiteboard"
Once you find an app that interests you, you can view more details to confirm compatibility or learn more about the app:
winget show <app-id>
For example:
winget show Microsoft.Whiteboard
This command provides detailed information about the app, including its description, version, and whether it’s compatible with devices like Surface Hub.
You can manually install offline-licensed apps on Surface Hubs using provisioning packages. Use Windows Imaging and Configuration Designer (ICD) to create a provisioning package containing the app package and unencoded license file that you downloaded via WinGet. For more information, see Create provisioning packages for Surface Hub.
To deploy apps to a large number of Surface Hubs in your organization, use a supported MDM provider. The table below shows which MDM providers support deploying offline-licensed app packages.
MDM provider | Supports offline-licensed app packages |
---|---|
On-premises MDM with Configuration Manager (beginning in version 1602) | Yes |
Third-party MDM provider | Check to make sure your MDM provider supports deploying offline-licensed app packages. |
Note
To deploy offline apps remotely using Intune, refer to Add a Windows line-of-business app to Microsoft Intune. Surface Hub app deployment only supports offline apps that are assigned to a Device group and use the Device license type.
This section provides information for app developers for testing apps on Surface Hub.
By default, Surface Hub only runs UWP apps published to and signed by the Microsoft Store. Apps submitted to the Microsoft Store go through security and compliance tests as part of the app certification process, so this helps safeguard your Surface Hub against malicious apps. By enabling developer mode, you can also install developer-signed UWP apps.
Important
After developer mode has been enabled, you will need to reset the Surface Hub to disable it. Resetting the device removes all local user files and configurations and then reinstalls Windows.
- From your Surface Hub, start Settings.
- Type the device admin credentials when prompted.
- Navigate to Update & security > For developers.
- Select Developer mode and accept the warning prompt.
During development, the easiest way to test your app on a Surface Hub is using Visual Studio. Visual Studio's remote debugging feature helps you discover issues in your app before deploying it broadly. For more information, see Test Surface Hub apps using Visual Studio.
Use Visual Studio to create an app package for your UWP app, signed using a test certificate. Then use Windows Imaging and Configuration Designer (ICD) to create a provisioning package containing the app package. For more information, see Create provisioning packages for Surface Hub.
Once an app is ready for release, developers need to submit and publish it to the Microsoft Store. For more information, see Publish Windows apps and games.
During app submission, developers need to set Device family availability and Organizational licensing options to make sure the app will be available to run on Surface Hub.
-
On the Windows Dev Center, navigate to your app submission page.
-
Select Packages.
-
Under Device family availability, select these options:
- Windows 10 Team
- Let Microsoft decide whether to make the app available to any future device families
For more information, see Device family availability.
-
On the Windows Dev Center, navigate to your app submission page.
-
Select Pricing and availability.
-
Under Organizational licensing, select Allow disconnected (offline) licensing for organizations.
[!NOTE] Make my app available to organizations with Store-managed (online) licensing and distribution is selected by default.
[!TIP] Developers can also publish line-of-business apps directly to enterprises without making them broadly available in the Store. For more information, see Distribute LOB apps to enterprises.
For more information, see Organizational licensing options.
There are a few different ways to install apps on your Surface Hub depending on whether you're developing apps, evaluating apps on a few devices, or deploying apps broadly to your organization. This table summarizes the supported methods:
Install method | Developing apps | Evaluating apps on a few devices | Deploying apps broadly to your organization |
---|---|---|---|
Visual Studio | X | ||
Provisioning package | X | X | |
Microsoft Store app | X | ||
Supported MDM provider | X |