commit d6a8bce79e491a8a245a37a9e20e6a6bec4d325b Merge: 0ab4e4e1 a7c70ad4 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 23 10:35:16 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 0ab4e4e119590e0e8cef691eee2b87180b07c5b3 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 23 10:29:48 2017 -0700 Jordan feedback commit 4454eeadbebb5fccdbfb3b1d07e87d708fefbe87 Merge: 03444e15 ef670cb5 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 23 09:26:54 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 03444e15f5b51bd1bdf1e76745f62cbbed3b529d Merge: 603408f3 660a6984 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 22 11:00:46 2017 -0700 Merge branch 'rs2' into jdrs2sh commit 603408f38ecd99e6f7fce1f61a4f199918fd67c4 Merge: 6821f22f b96e1555 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 21 13:54:33 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 6821f22f07f1864bb0a5c8eda33f7daf4f9531bc Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 21 13:41:44 2017 -0700 change ICD references commit 5804bc18db376fba16e8c863f5af8ffdd965359a Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 21 13:39:55 2017 -0700 rename file commit 9268142c9b881b0e0ad4fc2a0d4dcfddc180a1b3 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 21 13:32:31 2017 -0700 update what's new commit 503be68ec3a731434ca789df2da1f1c4783fdca7 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 21 13:30:48 2017 -0700 art commit 93914a2cf2aef9622b172c8ea97a3c1d72544c6a Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 21 13:30:43 2017 -0700 Jordan updates commit 27b1445ba4149fa78b7ec628870b19933307ba38 Merge: 9578dffe 6f0a1f7f Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 21 08:19:27 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 9578dffee198b0be16992368f571eed81f261818 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 20 09:09:56 2017 -0700 new oobe image commit 616c10e4e404574ecce7726fc76d7582c56b318e Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 20 08:23:53 2017 -0700 get bulk token warning commit 5600a6c7b320c4968686c07df90c62d8110764c9 Merge: cf29bb53 4b34636b Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 20 08:22:02 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit cf29bb53ec1c6e45e068219a796b2a5b04347b15 Merge: 695ec39f a5ec4c4d Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 17 09:42:51 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 695ec39f81b6da46b442ce8e52c9d9b28d65434a Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 16 12:25:06 2017 -0700 delete # Conflicts: # devices/surface-hub/TOC.md # devices/surface-hub/intro-to-surface-hub.md # devices/surface-hub/surface-hub-administrators-guide.md commit cc123f7aa0718efaa7cd355df4e3693afb073b9c Merge: 6b7ddf3e 3c12e864 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 16 12:23:40 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 6b7ddf3e498d541c2dbb531dd132e7ec0f45eb9d Merge: 278d14c4 032c25d4 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 16 11:34:53 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 278d14c462fa386e8979c4e998c464f2cdbf6a6c Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 15 10:26:22 2017 -0700 get bulk token commit 005f12e3939f8134143314e95e6bc9f76db8c3de Merge: 410e7508 1bff6ddd Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 15 10:25:19 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 410e750850a5037d843fe9d9c64a477d252ff10e Merge: d2f94c8f 8eed0956 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 13:51:32 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit d2f94c8f9d73868dec86e472fe5ace87b7370ac3 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 13:27:23 2017 -0700 tweak commit f629b4f1fd27fad24c258a7de903e6c18e85ec8c Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 12:44:21 2017 -0700 fix mdm enrollment commit 1dd74f9e7e353ba9ce5e71c8797cfa8cd02342a7 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 12:33:24 2017 -0700 add proxy commit c71e5af71bc866f1a5fe9abefb82b5124fb957fd Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 12:03:09 2017 -0700 add install link commit 0344deee4c68ae3c81529dc9cb602eec2af0b5c3 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 11:57:43 2017 -0700 stick commit be7ed51e1fb7b1a578c8e843b56e701bcf90be9d Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 11:56:52 2017 -0700 resize art commit 857be3cdfca07da3c5dfb470b3a3a3aee290a07c Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 11:55:09 2017 -0700 moved note to correct cell commit a91ca3943b8c0454549a1c0c5455b919ed46de8c Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 11:52:21 2017 -0700 sync commit 5bcf3c1db3c97d87ca60bfd4d688b908d4d9e518 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 11:43:25 2017 -0700 fix link commit de7d60524a2e1ba0d5e1bc1074da9bf887fa6457 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 11:42:46 2017 -0700 add apps to provisioning commit 67e14be35b30f4bfa45fb79815c25ef2317a171c Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 11:37:27 2017 -0700 sync to switch branches commit c6b9d8dae5d29f441ea262323baaad5e41b2bc9f Merge: 3260248b 4b13310a Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Mar 14 08:35:04 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 3260248b8a0511c081a5547419109f9380ea9b26 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 13 08:56:25 2017 -0700 fix table for non-IE browsers # Conflicts: # windows/whats-new/images/wcd-options.png commit a3ece5c8d4a6c37645f4aa5b39b582be855b98b9 Merge: 4ed80574 759b4a41 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 13 08:53:34 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 4ed80574020c1291ba4e853553330a7b84f21657 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 12:00:27 2017 -0800 fix typo commit 7541a4507508822dcd51da773536b89a5a49f305 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 11:53:38 2017 -0800 fix table commit 37254f098396342dd23115ea10885f121f5b9371 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 11:51:48 2017 -0800 resize art commit a936a6c4768729fec66775528a31c64132fa4f8e Merge: a217a9ae 9786c53a Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 11:50:43 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit a217a9ae8e48af3b533eb421a716b5a580daecba Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 11:45:55 2017 -0800 sync commit f09e8ae9e87db16b7ee6982864a1c4c2fc8ebcdc Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 11:39:34 2017 -0800 add image to index commit 80a133370000b2b7ff8c9e1383aca7eb1769258a Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 11:30:34 2017 -0800 fix link commit d8aa55211a62fecf56e6404146917b8e84b3c296 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 11:25:33 2017 -0800 tweak TOC, get rid of intro commit 6415e3739e13f47f2d3a6355066015d0bcd4cc7a Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 11:16:33 2017 -0800 remove admin guide level from toc commit 0d016720488e8aa1e3e0621b50596a66db8d232f Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 07:53:03 2017 -0800 release in change history commit 67a8f585dd788db1a18247827b1f9d22378d5b9f Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 07:50:20 2017 -0800 add what's new commit be5e195fc41d9ce94cd1b6189f0da25e9e50b9f2 Merge: e3e75663 8e80f0e1 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Mar 8 07:40:34 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit e3e756632b462d8a110b0538782bc22487e96d4b Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 28 13:46:55 2017 -0800 end session # Conflicts: # windows/configure/windows-10-start-layout-options-and-policies.md commit 0a9b86a2f6b69e5883fcdab48bb22f19cf1e6c32 Merge: 13e94977 4530d39f Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 28 13:42:38 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 13e9497711b34daab936735edcfa87f13c89d006 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Feb 27 11:29:01 2017 -0800 resize art commit 17d830dfde1174c95cb2bde7018fa1c85b8dcacc Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Feb 27 10:59:56 2017 -0800 delete file from images commit 395946c6c9b54516461e79a232525e965632686d Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Feb 27 10:50:39 2017 -0800 fix link commit c328942818f6e4b5d2bd2062724a90687b85926e Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Feb 27 10:40:29 2017 -0800 set up wizard table commit 942af3c56e6e6f7736e1ea03d6801633237a9311 Merge: 6ce5c31d 819ba842 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Feb 27 10:03:16 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 6ce5c31d127662010841791aa6498cd1606ed31e Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Feb 27 09:55:32 2017 -0800 change branches commit a3c28ae9e83bde3c97dd2d9232ad430e08ae972b Merge: b794a681 0a914cf9 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Feb 27 08:31:41 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/jdrs2icd' into jdrs2sh commit b794a6819b1a3ad9deb834986a184f6b488497fa Merge: af38dabf 2d1267b5 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Feb 27 07:37:48 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit af38dabf79f6b51971fbf3891d72be73f0f9035a Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Feb 24 11:25:09 2017 -0800 changed all to End Session # Conflicts: # devices/surface-hub/index.md commit 4e124566f0a01017232d6c2c6be95db15abf5db3 Merge: d07431ae 4b1663d8 Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Feb 24 11:18:06 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit d07431ae706af0af4c6c44909c4e08b16b904ccc Merge: 237cb29c 8bfa038e Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 14 13:48:31 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh commit 237cb29ce337e73ab6d707c1c06eaa89f5b49f3b Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 7 15:06:27 2017 -0800 undo all commit 5461ccb226a5ee079f07c59d719c52f3fefe2343 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 7 07:53:02 2017 -0800 sync commit 1e56393ac1a33ff3d1b5eb2183e1ece4e776a9a6 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 7 07:41:45 2017 -0800 sync commit 25ad8424a8f0dff551367cebedad18563e9d1081 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 7 07:32:18 2017 -0800 iframe commit 114cccfb75b3f27f46b67b5577d05a5de55662c1 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 7 07:22:49 2017 -0800 try span commit 03c4b1bb5aad5871b6808c2b7c48e0e71b6c10c7 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 7 07:10:29 2017 -0800 remove test commit 8a55ced11b6e8d4117d940ec73e2b045a0d7cf24 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 7 06:59:19 2017 -0800 test compass video commit f4ae742993fa9892f4d7c411fa87683697849cf7 Merge: dd9a3df0 94b855cd Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Feb 7 06:55:10 2017 -0800 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh
13 KiB
title, description, ms.assetid, keywords, ms.prod, ms.mktglfcycl, ms.sitesec, ms.pagetype, author, localizationpriority
title | description | ms.assetid | keywords | ms.prod | ms.mktglfcycl | ms.sitesec | ms.pagetype | author | localizationpriority |
---|---|---|---|---|---|---|---|---|---|
Install apps on your Microsoft Surface Hub | Admins can install apps can from either the Windows Store or the Windows Store for Business. | 3885CB45-D496-4424-8533-C9E3D0EDFD94 | install apps, Windows Store, Windows Store for Business | w10 | deploy | library | surfacehub, store | jdeckerMS | medium |
Install apps on your Microsoft Surface Hub
You can install additional apps on your Surface Hub to fit your team or organization's needs. There are different methods for installing apps depending on whether you are developing and testing an app, or deploying a released app. This topic describes methods for installing apps for either scenario.
A few things to know about apps on Surface Hub:
- Surface Hub only runs Universal Windows Platform (UWP) apps. See a list of apps that work with Surface Hub.
- Apps must be targeted for the Universal device family.
- By default, apps must be Store-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.- When submitting an app to the Windows Store, developers need to set Device family availability and Organizational licensing options to make sure an app will be available to run on Surface Hub.
- You need admin credentials to install apps on your Surface Hub. Since the device is designed to be used in communal spaces like meeting rooms, people can't access the Windows Store to download and install apps.
Develop and test apps
While you're developing your own app, there are a few options for testing apps on Surface Hub.
Developer Mode
By default, Surface Hub only runs UWP apps that have been published to and signed by the Windows Store. Apps submitted to the Windows 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.
To turn on developer mode
- 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.
Visual Studio
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.
Provisioning package
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.
Submit apps to the Windows Store
Once an app is ready for release, developers need to submit and publish it to the Windows Store. For more information, see Publish Windows apps.
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.
To set device family availability
- On the Windows Dev Center, navigate to your app submission page.
- Select Packages.
- Under Device family availability, select these options:
- Windows 10 Desktop (other device families are optional)
- Let Microsoft decide whether to make the app available to any future device families
For more information, see Device family availability.
To set organizational licensing
- 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.
Note
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.
Deploy released apps
There are several options for installing apps that have been released to the Windows 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 the app using the Windows Store app, or
- Download the app package from the Windows Store for Business, and distribute it using a provisioning package or a supported MDM provider.
Windows Store app
To evaluate apps released on the Windows Store, use the Windows Store app on the Surface Hub to browse and download apps.
Note
Using the Windows Store app is not the recommended method of deploying apps at scale to your organization:
- To download apps, you must sign in to the Windows 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 Windows Store app on each Surface Hub you own.
To browse the Windows Store on Surface Hub
- From your Surface Hub, start Settings.
- Type the device admin credentials when prompted.
- Navigate to This device > Apps & features.
- Select Open Store.
Download app packages from Windows Store for Business
To download the app package you need to install apps on your Surface Hub, visit the Windows Store for Business. The Store for Business is where you can find, acquire, and manage apps for the Windows 10 devices in your organization, including Surface Hub.
Note
Currently, Surface Hub only supports offline-licensed apps available through the Store for Business. App developers set offline-license availability when they submit apps.
Find and acquire the app you want, then download:
- The offline-licensed app package (either an .appx or an .appxbundle)
- The unencoded license file (if you're using provisioning packages to install the app)
- The encoded license file (if you're using MDM to distribute the app)
- Any necessary dependency files
For more information, see Download an offline-licensed app.
Provisioning package
You can manually install the offline-licensed apps that you downloaded from the Store for Business on a few 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 from the Store for Business. For more information, see Create provisioning packages.
Supported MDM provider
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 System Center Configuration Manager (beginning in version 1602) | Yes |
Hybrid MDM with System Center Configuration Manager and Microsoft Intune | Yes |
Microsoft Intune standalone | No |
Third-party MDM provider | Check to make sure your MDM provider supports deploying offline-licensed app packages. |
To deploy apps remotely using System Center Configuration Manager (either on-prem MDM or hybrid MDM)
Note
These instructions are based on the current branch of System Center Configuration Manager.
- Enroll your Surface Hubs to System Center Configuration Manager. For more information, see Enroll a Surface Hub into MDM.
- Download the offline-licensed app package, the encoded license file, and any necessary dependency files from the Store for Business. For more information, see Download an offline-licensed app. Place the downloaded files in the same folder on a network share.
- In the Software Library workspace of the Configuration Manager console, click Overview > Application Management > Applications.
- On the Home tab, in the Create group, click Create Application.
- On the General page of the Create Application Wizard, select the Automatically detect information about this application from installation files check box.
- In the Type drop-down list, select Windows app package (*.appx, *.appxbundle).
- In the Location field, specify the UNC path in the form \server\share\filename for the offline-licensed app package that you downloaded from the Store for Business. Alternatively, click Browse to browse to the app package.
- On the Import Information page, review the information that was imported, and then click Next. If necessary, you can click Previous to go back and correct any errors.
- On the General Information page, complete additional details about the app. Some of this information might already be populated if it was automatically obtained from the app package.
- Click Next, review the application information on the Summary page, and then complete the Create Application Wizard.
- Create a deployment type for the application. For more information, see Create deployment types for the application.
- Deploy the application to your Surface Hubs. For more information, see Deploy applications with System Center Configuration Manager.
- As needed, update the app by downloading a new package from the Store for Business, and publishing an application revision in Configuration Manager. For more information, see Update and retire applications with System Center Configuration Manager.
Note
If you are using System Center Configuration Manager (current branch), you can bypass the above steps by connecting the Store for Business to System Center Configuration Manager. By doing so, you can synchronize the list of apps you've purchased with System Center Configuration Manager, view these in the Configuration Manager console, and deploy them like you would any other app. For more information, see Manage apps from the Windows Store for Business with System Center Configuration Manager.
Summary
There are a few different ways to install apps on your Surface Hub depending on whether you are developing apps, evaluating apps on a small number of devices, or deploying apps broadly to your oganization. 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 | |
Windows Store app | X | ||
Supported MDM provider | X |
Related topics
Microsoft Surface Hub administrator's guide