Merge remote-tracking branch 'refs/remotes/origin/jdshrs2'
@ -56,31 +56,6 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md",
|
||||
"redirect_url": "/itpro/surface-hub/finishing-your-surface-hub-meeting",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "devices/surface-hub/provisioning-packages-for-certificates-surface-hub.md",
|
||||
"redirect_url": "/itpro/surface-hub/provisioning-packages-for-surface-hub",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "devices/surface-hub/manage-settings-with-local-admin-account-surface-hub.md",
|
||||
"redirect_url": "/itpro/surface-hub/admin-group-management-for-surface-hub",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "devices/surface-hub/surface-hub-administrators-guide.md",
|
||||
"redirect_url": "/itpro/surface-hub/index",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "devices/surface-hub/intro-to-surface-hub.md",
|
||||
"redirect_url": "/itpro/surface-hub/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/manage/waas-quick-start.md",
|
||||
"redirect_url": "/itpro/windows/update/waas-quick-start",
|
||||
"redirect_document_id": true
|
||||
|
@ -1,41 +1,42 @@
|
||||
# [Microsoft Surface Hub](index.md)
|
||||
## [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md)
|
||||
## [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
## [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
|
||||
### [Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md)
|
||||
### [Create and test a device account](create-and-test-a-device-account-surface-hub.md)
|
||||
#### [Online deployment](online-deployment-surface-hub-device-accounts.md)
|
||||
#### [On-premises deployment (single forest)](on-premises-deployment-surface-hub-device-accounts.md)
|
||||
#### [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md)
|
||||
#### [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md)
|
||||
#### [Create a device account using UI](create-a-device-account-using-office-365.md)
|
||||
#### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md)
|
||||
#### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md)
|
||||
#### [Password management](password-management-for-surface-hub-device-accounts.md)
|
||||
### [Create provisioning packages](provisioning-packages-for-surface-hub.md)
|
||||
### [Admin group management](admin-group-management-for-surface-hub.md)
|
||||
## [Set up Microsoft Surface Hub](set-up-your-surface-hub.md)
|
||||
### [Setup worksheet](setup-worksheet-surface-hub.md)
|
||||
### [First-run program](first-run-program-surface-hub.md)
|
||||
## [Manage Microsoft Surface Hub](manage-surface-hub.md)
|
||||
### [Remote Surface Hub management](remote-surface-hub-management.md)
|
||||
#### [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md)
|
||||
#### [Monitor your Surface Hub](monitor-surface-hub.md)
|
||||
#### [Windows updates](manage-windows-updates-for-surface-hub.md)
|
||||
### [Manage Surface Hub settings](manage-surface-hub-settings.md)
|
||||
#### [Local management for Surface Hub settings](local-management-surface-hub-settings.md)
|
||||
#### [Accessibility](accessibility-surface-hub.md)
|
||||
#### [Change the Surface Hub device account](change-surface-hub-device-account.md)
|
||||
#### [Device reset](device-reset-surface-hub.md)
|
||||
#### [Use fully qualified domain name with Surface Hub](use-fully-qualified-domain-name-surface-hub.md)
|
||||
#### [Wireless network management](wireless-network-management-for-surface-hub.md)
|
||||
### [Install apps on your Surface Hub](install-apps-on-surface-hub.md)
|
||||
### [End a Surface Hub meeting with End session](i-am-done-finishing-your-surface-hub-meeting.md)
|
||||
### [Save your BitLocker key](save-bitlocker-key-surface-hub.md)
|
||||
### [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md)
|
||||
### [Using a room control system](use-room-control-system-with-surface-hub.md)
|
||||
## [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md)
|
||||
## [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md)
|
||||
## [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
|
||||
## [Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
|
||||
### [Intro to Microsoft Surface Hub](intro-to-surface-hub.md)
|
||||
### [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
|
||||
#### [Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md)
|
||||
#### [Create and test a device account](create-and-test-a-device-account-surface-hub.md)
|
||||
##### [Online deployment](online-deployment-surface-hub-device-accounts.md)
|
||||
##### [On-premises deployment (single forest)](on-premises-deployment-surface-hub-device-accounts.md)
|
||||
##### [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md)
|
||||
##### [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md)
|
||||
##### [Create a device account using UI](create-a-device-account-using-office-365.md)
|
||||
##### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md)
|
||||
##### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md)
|
||||
##### [Password management](password-management-for-surface-hub-device-accounts.md)
|
||||
#### [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md)
|
||||
#### [Admin group management](admin-group-management-for-surface-hub.md)
|
||||
### [Set up Microsoft Surface Hub](set-up-your-surface-hub.md)
|
||||
#### [Setup worksheet](setup-worksheet-surface-hub.md)
|
||||
#### [First-run program](first-run-program-surface-hub.md)
|
||||
### [Manage Microsoft Surface Hub](manage-surface-hub.md)
|
||||
#### [Remote Surface Hub management](remote-surface-hub-management.md)
|
||||
##### [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md)
|
||||
##### [Monitor your Surface Hub](monitor-surface-hub.md)
|
||||
##### [Windows updates](manage-windows-updates-for-surface-hub.md)
|
||||
#### [Manage Surface Hub settings](manage-surface-hub-settings.md)
|
||||
##### [Local management for Surface Hub settings](local-management-surface-hub-settings.md)
|
||||
##### [Accessibility](accessibility-surface-hub.md)
|
||||
##### [Change the Surface Hub device account](change-surface-hub-device-account.md)
|
||||
##### [Device reset](device-reset-surface-hub.md)
|
||||
##### [Use fully qualified domain name with Surface Hub](use-fully-qualified-domain-name-surface-hub.md)
|
||||
##### [Wireless network management](wireless-network-management-for-surface-hub.md)
|
||||
#### [Install apps on your Surface Hub](install-apps-on-surface-hub.md)
|
||||
#### [End a Surface Hub meeting with I'm Done](i-am-done-finishing-your-surface-hub-meeting.md)
|
||||
#### [Save your BitLocker key](save-bitlocker-key-surface-hub.md)
|
||||
#### [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md)
|
||||
#### [Using a room control system](use-room-control-system-with-surface-hub.md)
|
||||
### [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
|
||||
### [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)
|
||||
## [Useful downloads for Surface Hub administrators](surface-hub-downloads.md)
|
||||
## [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
## [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md)
|
||||
## [Change history for Surface Hub](change-history-surface-hub.md)
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surfacehub
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -30,7 +30,7 @@ The full list of accessibility settings are available to IT admins in the **Sett
|
||||
| Mouse | Defaults selected for **Pointer size**, **Pointer color** and **Mouse keys**. |
|
||||
| Other options | Defaults selected for **Visual options** and **Touch feedback**. |
|
||||
|
||||
Additionally, these accessibility features and apps are returned to default settings when users press [End session](finishing-your-surface-hub-meeting.md):
|
||||
Additionally, these accessibility features and apps are returned to default settings when users press [I'm Done](i-am-done-finishing-your-surface-hub-meeting.md):
|
||||
- Narrator
|
||||
- Magnifier
|
||||
- High contrast
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: PowerShell for Surface Hub (Surface Hub)
|
||||
title: Appendix PowerShell (Surface Hub)
|
||||
description: PowerShell scripts to help set up and manage your Microsoft Surface Hub .
|
||||
ms.assetid: 3EF48F63-8E4C-4D74-ACD5-461F1C653784
|
||||
keywords: PowerShell, set up Surface Hub, manage Surface Hub
|
||||
@ -7,11 +7,11 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# PowerShell for Surface Hub
|
||||
# Appendix: PowerShell (Surface Hub)
|
||||
|
||||
|
||||
PowerShell scripts to help set up and manage your Microsoft Surface Hub .
|
||||
@ -43,8 +43,7 @@ What do you need in order to run the scripts?
|
||||
- Remote PowerShell access to your organization's domain or tenant, Exchange servers, and Skype for Business servers.
|
||||
- Admin credentials for your organization's domain or tenant, Exchange servers, and Skype for Business servers.
|
||||
|
||||
>[!NOTE]
|
||||
>Whether you’re creating a new account or modifying an already-existing account, the validation script will verify that your device account is configured correctly. You should always run the validation script before adding a device account to Surface Hub.
|
||||
>**Note** Whether you’re creating a new account or modifying an already-existing account, the validation script will verify that your device account is configured correctly. You should always run the validation script before adding a device account to Surface Hub.
|
||||
|
||||
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -6,7 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -14,10 +14,6 @@ localizationpriority: medium
|
||||
|
||||
This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md).
|
||||
|
||||
## RELEASE: Windows 10, version 1703
|
||||
|
||||
The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update).
|
||||
|
||||
## February 2017
|
||||
|
||||
| New or changed topic | Description |
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -49,49 +49,21 @@ If you see a blank screen for long periods of time during the **Reset device** p
|
||||
|
||||

|
||||
|
||||
3. Click **Recovery**, and then, under **Reset device**, click **Get started**.
|
||||
3. Click **Recovery**, and then click **Get started**.
|
||||
|
||||

|
||||
|
||||
<span id="cloud-recovery" />
|
||||
## Recover a Surface Hub from the cloud
|
||||
## Reset a Surface Hub from Windows Recovery Environment
|
||||
|
||||
In the Windows Recovery Environment (Windows RE), you can recover your device by downloading a factory build from the cloud and installing it on the Surface Hub. This allows devices in an unusable state to recover without requiring assistance from Microsoft Support.
|
||||
On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device will automatically reboot and try again. But if this operation fails repeatedly, the device will be automatically locked to protect user data. To unlock it, you must reset the device from [Windows Recovery Environment](https://technet.microsoft.com/library/cc765966.aspx) (Windows RE).
|
||||
|
||||
### Recover a Surface Hub in a bad state
|
||||
|
||||
If the device account gets into an unstable state or the Admin account is running into issues, you can use cloud recovery in **Settings**. You should only use cloud recovery when [reset](#reset-a-surface-hub-from-settings) doesn't fix the problem.
|
||||
|
||||
1. On your Surface Hub, go to **Settings** > **Update & security** > **Recovery**.
|
||||
|
||||
2. Under **Recover from the cloud**, click **Restart now**.
|
||||
|
||||

|
||||
|
||||
### Recover a locked Surface Hub
|
||||
|
||||
On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device will automatically reboot and try again. But if this operation fails repeatedly, the device will be automatically locked to protect user data. To unlock it, you must reset or recover the device from [Windows RE](https://technet.microsoft.com/library/cc765966.aspx).
|
||||
**To reset a Surface Hub from Windows Recovery Environment**
|
||||
|
||||
1. From the welcome screen, toggle the Surface Hub's power switch 3 times. Wait a few seconds between each toggle. See the [Surface Hub Site Readiness Guide](https://www.microsoft.com/surface/support/surface-hub/surface-hub-site-readiness-guide) for help with locating the power switch.
|
||||
2. The device should automatically boot into Windows RE.
|
||||
3. After the Surface Hub enters Windows RE, select **Recover from the cloud**. (Optionally, you can choose **Reset**, however **Recover from the cloud** is the recommended approach.)
|
||||
>[!NOTE]
|
||||
>When using **Recover from the cloud**, an ethernet connection is recommended.
|
||||
2. The device should automatically boot into Windows RE. Select **Advanced Repair**.
|
||||
3. Select **Reset**.
|
||||
4. If prompted, enter your device's BitLocker key.
|
||||
|
||||

|
||||
|
||||
4. Enter the Bitlocker key (if prompted).
|
||||
5. When prompted, select **Reinstall**.
|
||||
|
||||

|
||||
|
||||
6. Select **Yes** to repartition the disk.
|
||||
|
||||

|
||||
|
||||
Reset will begin after the image is downloaded from the cloud. You will see progress indicators.
|
||||
|
||||

|
||||
|
||||
## Related topics
|
||||
|
||||
|
@ -33,7 +33,7 @@ Surface Hub doesn't have a lock screen or a screen saver, but it has a similar f
|
||||
Surface Hub is designed to be used in communal spaces, such as meeting rooms. Unlike Windows PCs, anyone can walk up and use a Surface Hub without logging on. The system always runs as a local, auto logged-in, low-privilege user. It doesn't support logging in any additional users - including admin users.
|
||||
|
||||
> [!NOTE]
|
||||
> Surface Hub supports signing in to Microsoft Edge and other apps. However, these credentials are deleted when users press **End session**.
|
||||
> Surface Hub supports signing in to Microsoft Edge and other apps. However, these credentials are deleted when users press **I'm done**.
|
||||
|
||||
*Organization policies that this may affect:* <br> Generally, Surface Hub uses lockdown features rather than user access control to enforce security. Policies related to password requirements, interactive logon, user accounts, and access control don't apply for Surface Hub.
|
||||
|
||||
@ -46,7 +46,7 @@ Users have access to a limited set of directories on the Surface Hub:
|
||||
- Pictures
|
||||
- Downloads
|
||||
|
||||
Files saved locally in these directories are deleted when users press **End session**. To save content created during a meeting, users should save files to a USB drive or to OneDrive.
|
||||
Files saved locally in these directories are deleted when users press **I'm done**. To save content created during a meeting, users should save files to a USB drive or to OneDrive.
|
||||
|
||||
*Organization policies that this may affect:* <br> Policies related to access permissions and ownership of files and folders don't apply for Surface Hub. Users can't browse and save files to system directories and network folders.
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -1,92 +0,0 @@
|
||||
---
|
||||
title: End session - ending a Surface Hub meeting
|
||||
description: To end a Surface Hub meeting, tap End session. Surface Hub cleans up the application state, operating system state, and the user interface so that Surface Hub is ready for the next meeting.
|
||||
keywords: I am Done, end Surface Hub meeting, finish Surface Hub meeting, clean up Surface Hub meeting
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# End a Surface Hub meeting with End session
|
||||
Surface Hub is a collaboration device designed to be used in meeting spaces by different groups of people. At the end of a meeting, users can tap **End session** to clean up any sensitive data and prepare the device for the next meeting. Surface Hub will clean up, or reset, the following states:
|
||||
- Applications
|
||||
- Operating system
|
||||
- User interface
|
||||
|
||||
This topic explains what **End session** resets for each of these states.
|
||||
|
||||
## Applications
|
||||
When you start apps on Surface Hub, they are stored in memory and data is stored at the application level. Data is available to all users during that session (or meeting) until date is removed or overwritten. When **End session** is selected, Surface Hub application state is cleared out by closing applications, deleting browser history, resetting applications, and removing Skype logs.
|
||||
|
||||
### Close applications
|
||||
Surface Hub closes all visible windows, including Win32 and Universal Windows Platform (UWP) applications. The application close stage uses the multitasking view to query the visible windows. Win32 windows that do not close within a certain timeframe are closed using **TerminateProcess**.
|
||||
|
||||
### Delete browser history
|
||||
Surface Hub uses Delete Browser History (DBH) in Edge to clear Edge history and cached data. This is similar to how a user can clear out their browser history manually, but **End session** also ensures that application states are cleared and data is removed before the next session, or meeting, starts.
|
||||
|
||||
### Reset applications
|
||||
**End session** resets the state of each application that is installed on the Surface Hub. Resetting an application clears all background tasks, application data, notifications, and user consent dialogs. Applications are returned to their first-run state for the next people that use Surface Hub.
|
||||
|
||||
### Remove Skype logs
|
||||
Skype does not store personally-identifiable information on Surface Hub. Information is stored in the Skype service to meet existing Skype for Business guidance. Local Skype logging information is the only data removed when **End session** is selected. This includes Unified Communications Client Platform (UCCP) logs and media logs.
|
||||
|
||||
## Operating System
|
||||
The operating system hosts a variety of information about the state of the sessions that needs to be cleared after each Surface Hub meeting.
|
||||
|
||||
### File System
|
||||
Meeting attendees have access to a limited set of directories on the Surface Hub. When **End session** is selected, Surface Hub clears these directories:<br>
|
||||
- Music
|
||||
- Videos
|
||||
- Documents
|
||||
- Pictures
|
||||
- Downloads
|
||||
|
||||
Surface Hub also clears these directories, since many applications often write to them:
|
||||
- Desktop
|
||||
- Favorites
|
||||
- Recent
|
||||
- Public Documents
|
||||
- Public Music
|
||||
- Public Videos
|
||||
- Public Downloads
|
||||
|
||||
### Credentials
|
||||
User credentials that are stored in **TokenBroker**, **PasswordVault**, or **Credential Manager** are cleared when you tap **End session**.
|
||||
|
||||
## User interface
|
||||
User interface (UI) settings are returned to their default values when **End session** is selected.
|
||||
|
||||
### UI items
|
||||
- Reset Quick Actions to default state
|
||||
- Clear Toast notifications
|
||||
- Reset volume levels
|
||||
- Reset sidebar width
|
||||
- Reset tablet mode layout
|
||||
- Sign user out of Office 365 meetings and files
|
||||
|
||||
### Accessibility
|
||||
Accessibility features and apps are returned to default settings when **End session** is selected.
|
||||
- Filter keys
|
||||
- High contrast
|
||||
- Sticky keys
|
||||
- Toggle keys
|
||||
- Mouse keys
|
||||
- Magnifier
|
||||
- Narrator
|
||||
|
||||
### Clipboard
|
||||
The clipboard is cleared to remove data that was copied to the clipboard during the session.
|
||||
|
||||
## Frequently asked questions
|
||||
**What happens if I forget to tap End session at the end of a meeting, and someone else uses the Surface Hub later?**<br>
|
||||
Surface Hub only cleans up meeting content when users tap **End session**. If you leave the meeting without tapping **End session**, the device will return to the welcome screen after some time. From the welcome screen, users have the option to resume the previous session or start a new one. You can also disable the ability to resume a session if **End session** is not pressed.
|
||||
|
||||
**Are documents recoverable?**<br>
|
||||
Removing files from the hard drive when **End session** is selected is just like any other file deletion from a hard disk drive. Third-party software might be able to recover data from the hard disk drive, but file recovery is not a supported feature on Surface Hub. To prevent data loss, always save the data you need before leaving a meeting.
|
||||
|
||||
**Do the clean-up actions from End session comply with the US Department of Defense clearing and sanitizing standard: DoD 5220.22-M?**<br>
|
||||
No. Currently, the clean-up actions from **End session** do not comply with this standard.
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -43,10 +43,9 @@ Each of these sections also contains information about paths you might take when
|
||||
|
||||
This is the first screen you'll see when you power up the Surface Hub for the first time. It's where you input localization information for your device.
|
||||
|
||||
>[!NOTE]
|
||||
>This is also where you begin the optional process of deploying a provisioning package. See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) if that's what you're doing.
|
||||
>**Note** This is also where you begin the optional process of deploying a provisioning package. See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) if that's what you're doing.
|
||||
|
||||
Select a language and the initial setup options are displayed.
|
||||
|
||||
|
||||

|
||||
|
||||
@ -328,9 +327,6 @@ This is what happens when you choose an option.
|
||||
|
||||
Clicking this option allows you to join the device to Azure AD. Once you click **Next**, the device will restart to apply some settings, and then you’ll be taken to the [Use Microsoft Azure Active Directory](#use-microsoft-azure) page and asked to enter credentials that can allow you to join Azure AD. After joining, admins from the joined organization will be able to use the Settings app. The specific people that will be allowed depends on your Azure AD subscription and how you’ve configured the settings for your Azure AD organization.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you join Surface Hub to Azure AD during first-run setup, single sign-on (SSO) for Office apps will not work properly. Users will have to sign in to each Office app individually.
|
||||
|
||||
- **Use Active Directory Domain Services**
|
||||
|
||||
Click this option to join the device to AD. Once you click **Next**, you’ll be taken to the [Use Active Directory Domain Services](#use-active-directory) page and asked to enter credentials that allow you to join the specified domain. After joining, you can pick a security group from the joined domain, and people from that security group will be able to use the Settings app.
|
||||
@ -386,7 +382,7 @@ Once the device has been domain joined, you must specify a security group from t
|
||||
The following input is required:
|
||||
|
||||
- **Domain:** This is the fully qualified domain name (FQDN) of the domain that you want to join. A security group from this domain can be used to manage the device.
|
||||
- **User name:** The user name of an account that has sufficient permission to join the specified domain. This account must be a computer object.
|
||||
- **User name:** The user name of an account that has sufficient permission to join the specified domain.
|
||||
- **Password:** The password for the account.
|
||||
|
||||
After the credentials are verified, you will be asked to type a security group name. This input is required.
|
||||
|
@ -0,0 +1,91 @@
|
||||
---
|
||||
title: I am done - ending a Surface Hub meeting
|
||||
description: To end a Surface Hub meeting, tap I am Done. Surface Hub cleans up the application state, operating system state, and the user interface so that Surface Hub is ready for the next meeting.
|
||||
keywords: I am Done, end Surface Hub meeting, finish Surface Hub meeting, clean up Surface Hub meeting
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# End a Surface Hub meeting with I'm Done
|
||||
Surface Hub is a collaboration device designed to be used in meeting spaces by different groups of people. At the end of a meeting, users can tap **I'm Done** to clean up any sensitive data and prepare the device for the next meeting. Surface Hub will clean up, or reset, the following states:
|
||||
- Applications
|
||||
- Operating system
|
||||
- User interface
|
||||
|
||||
This topic explains what **I'm Done** resets for each of these states.
|
||||
|
||||
## Applications
|
||||
When you start apps on Surface Hub, they are stored in memory and data is stored at the application level. Data is available to all users during that session (or meeting) until date is removed or overwritten. When **I'm done** is selected, Surface Hub application state is cleared out by closing applications, deleting browser history, resetting applications, and removing Skype logs.
|
||||
|
||||
### Close applications
|
||||
Surface Hub closes all visible windows, including Win32 and Universal Windows Platform (UWP) applications. The application close stage uses the multitasking view to query the visible windows. Win32 windows that do not close within a certain timeframe are closed using **TerminateProcess**.
|
||||
|
||||
### Delete browser history
|
||||
Surface Hub uses Delete Browser History (DBH) in Edge to clear Edge history and cached data. This is similar to how a user can clear out their browser history manually, but **I'm Done** also ensures that application states are cleared and data is removed before the next session, or meeting, starts.
|
||||
|
||||
### Reset applications
|
||||
**I'm Done** resets the state of each application that is installed on the Surface Hub. Resetting an application clears all background tasks, application data, notifications, and user consent dialogs. Applications are returned to their first-run state for the next people that use Surface Hub.
|
||||
|
||||
### Remove Skype logs
|
||||
Skype does not store personally-identifiable information on Surface Hub. Information is stored in the Skype service to meet existing Skype for Business guidance. Local Skype logging information is the only data removed when **I'm Done** is selected. This includes Unified Communications Client Platform (UCCP) logs and media logs.
|
||||
|
||||
## Operating System
|
||||
The operating system hosts a variety of information about the state of the sessions that needs to be cleared after each Surface Hub meeting.
|
||||
|
||||
### File System
|
||||
Meeting attendees have access to a limited set of directories on the Surface Hub. When **I'm Done** is selected, Surface Hub clears these directories:<br>
|
||||
- Music
|
||||
- Videos
|
||||
- Documents
|
||||
- Pictures
|
||||
- Downloads
|
||||
|
||||
Surface Hub also clears these directories, since many applications often write to them:
|
||||
- Desktop
|
||||
- Favorites
|
||||
- Recent
|
||||
- Public Documents
|
||||
- Public Music
|
||||
- Public Videos
|
||||
- Public Downloads
|
||||
|
||||
### Credentials
|
||||
User credentials that are stored in **TokenBroker**, **PasswordVault**, or **Credential Manager** are cleared when you tap **I’m done**.
|
||||
|
||||
## User interface
|
||||
User interface (UI) settings are returned to their default values when **I'm Done** is selected.
|
||||
|
||||
### UI items
|
||||
- Reset Quick Actions to default state
|
||||
- Clear Toast notifications
|
||||
- Reset volume levels
|
||||
- Reset sidebar width
|
||||
- Reset tablet mode layout
|
||||
|
||||
### Accessibility
|
||||
Accessibility features and apps are returned to default settings when **I'm Done** is selected.
|
||||
- Filter keys
|
||||
- High contrast
|
||||
- Sticky keys
|
||||
- Toggle keys
|
||||
- Mouse keys
|
||||
- Magnifier
|
||||
- Narrator
|
||||
|
||||
### Clipboard
|
||||
The clipboard is cleared to remove data that was copied to the clipboard during the session.
|
||||
|
||||
## Frequently asked questions
|
||||
**What happens if I forget to tap I'm Done at the end of a meeting, and someone else uses the Surface Hub later?**<br>
|
||||
Surface Hub only cleans up meeting content when users tap **I'm Done**. If you leave the meeting without tapping **I'm Done**, the device will return to the welcome screen after some time. From the welcome screen, users have the option to resume the previous session or start a new one.
|
||||
|
||||
**Are documents recoverable?**<br>
|
||||
Removing files from the hard drive when **I'm Done** is selected is just like any other file deletion from a hard disk drive. Third-party software might be able to recover data from the hard disk drive, but file recovery is not a supported feature on Surface Hub. To prevent data loss, always save the data you need before leaving a meeting.
|
||||
|
||||
**Do the clean-up actions from I'm Done comply with the US Department of Defense clearing and sanitizing standard: DoD 5220.22-M?**<br>
|
||||
No. Currently, the clean-up actions from **I'm Done** do not comply with this standard.
|
||||
|
Before Width: | Height: | Size: 78 KiB |
Before Width: | Height: | Size: 18 KiB |
Before Width: | Height: | Size: 2.0 KiB |
Before Width: | Height: | Size: 6.8 KiB |
Before Width: | Height: | Size: 1.4 KiB |
Before Width: | Height: | Size: 6.8 KiB |
Before Width: | Height: | Size: 2.1 KiB |
Before Width: | Height: | Size: 29 KiB |
Before Width: | Height: | Size: 2.3 KiB |
Before Width: | Height: | Size: 91 KiB |
Before Width: | Height: | Size: 1.8 KiB |
Before Width: | Height: | Size: 77 KiB |
Before Width: | Height: | Size: 26 KiB |
Before Width: | Height: | Size: 2.1 KiB |
Before Width: | Height: | Size: 7.9 KiB |
Before Width: | Height: | Size: 1.0 KiB |
Before Width: | Height: | Size: 429 B |
Before Width: | Height: | Size: 470 B |
Before Width: | Height: | Size: 28 KiB |
Before Width: | Height: | Size: 450 B |
Before Width: | Height: | Size: 36 KiB |
Before Width: | Height: | Size: 22 KiB |
Before Width: | Height: | Size: 14 KiB |
Before Width: | Height: | Size: 2.4 KiB |
Before Width: | Height: | Size: 32 KiB |
Before Width: | Height: | Size: 101 KiB |
Before Width: | Height: | Size: 50 KiB |
Before Width: | Height: | Size: 141 KiB |
Before Width: | Height: | Size: 90 KiB |
Before Width: | Height: | Size: 66 KiB |
Before Width: | Height: | Size: 2.0 KiB |
Before Width: | Height: | Size: 22 KiB |
Before Width: | Height: | Size: 1.5 KiB |
Before Width: | Height: | Size: 7.8 KiB |
Before Width: | Height: | Size: 1.8 KiB |
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 32 KiB |
Before Width: | Height: | Size: 101 KiB After Width: | Height: | Size: 29 KiB |
Before Width: | Height: | Size: 105 KiB After Width: | Height: | Size: 17 KiB |
Before Width: | Height: | Size: 87 KiB After Width: | Height: | Size: 23 KiB |
Before Width: | Height: | Size: 535 B |
Before Width: | Height: | Size: 156 KiB |
Before Width: | Height: | Size: 458 B |
Before Width: | Height: | Size: 443 B |
Before Width: | Height: | Size: 12 KiB |
@ -12,36 +12,19 @@ localizationpriority: medium
|
||||
|
||||
# Microsoft Surface Hub
|
||||
|
||||
>[Looking for the user's guide for Surface Hub?](http://download.microsoft.com/download/3/6/B/36B6331E-0C63-4E71-A05D-EE88D05081F8/surface-hub-user-guide-en-us.pdf)
|
||||
|
||||
<table><tr><td style="border: 0px;width: 75%;valign= top">Microsoft Surface Hub is an all-in-one productivity device that is intended for brainstorming, collaboration, and presentations. In order to get the maximum benefit from Surface Hub, your organization’s infrastructure and the Surface Hub itself must be properly set up and integrated. The documentation in this library describes what needs to be done both before and during setup in order to help you optimize your use of the device.</td><td align="left" style="border: 0px"> </td></tr></table>
|
||||
|
||||
|
||||
## Surface Hub setup process
|
||||
|
||||
In some ways, adding your new Surface Hub is just like adding any other Microsoft Windows-based device to your network. However, in order to get your Surface Hub up and running at its full capacity, there are some very specific requirements. Here are the next topics you'll need:
|
||||
|
||||
1. [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md)
|
||||
2. [Gather the information listed in the Setup worksheet](setup-worksheet-surface-hub.md)
|
||||
2. [Physically install your Surface Hub device](physically-install-your-surface-hub-device.md)
|
||||
3. [Run the Surface Hub first-run setup program (OOBE)](first-run-program-surface-hub.md)
|
||||
|
||||
Documents related to deploying and managing the Microsoft Surface Hub in your organization.
|
||||
|
||||
>[Looking for the user's guide for Surface Hub?](https://www.microsoft.com/surface/support/surface-hub)
|
||||
|
||||
## In this section
|
||||
|
||||
| Topic | Description |
|
||||
| --- | --- |
|
||||
| [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md) | Discover the changes and improvements for Microsoft Surface Hub in the Windows 10, version 1703 release (also known as Creators Update). |
|
||||
| [Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md) | This guide covers the installation and administration of devices running Surface Hub, and is intended for use by anyone responsible for these tasks, including IT administrators and developers.|
|
||||
| [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) | This topic explains the differences between the operating system on Surface Hub and Windows 10 Enterprise. |
|
||||
| [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md) | This section contains an overview of the steps required to prepare your environment so that you can use all of the features of Surface Hub. See [Intro to Surface Hub](intro-to-surface-hub.md) for a description of how the device and its features interact with your IT environment. |
|
||||
| [Set up Microsoft Surface Hub](set-up-your-surface-hub.md) | Set up instructions for Surface Hub include a setup worksheet, and a walkthrough of the first-run program. |
|
||||
| [Manage Microsoft Surface Hub](manage-surface-hub.md) | How to manage your Surface Hub after finishing the first-run program. |
|
||||
| [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) |
|
||||
| [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) | This topic provides guidance on Wi-Fi Direct security risks, how the Surface Hub has addressed those risks, and how Surface Hub administrators can configure the device for the highest level of security. | PowerShell scripts to help set up and manage your Surface Hub. |
|
||||
| [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md) | Troubleshoot common problems, including setup issues, Exchange ActiveSync errors. |
|
||||
| [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) | This topic provides guidance on Wi-Fi Direct security risks, how the Surface Hub has addressed those risks, and how Surface Hub administrators can configure the device for the highest level of security. |
|
||||
| [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) | This topic provides links to useful Surface Hub documents, such as product datasheets, the site readiness guide, and user's guide. |
|
||||
| [Change history for Surface Hub](change-history-surface-hub.md) | This topic lists new and updated topics in the Surface Hub documentation library. |
|
||||
|
||||
| [Change history for Surface Hub](change-history-surface-hub.md) | This topic lists new and updated topics in the Surface Hub documentation. |
|
||||
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, store
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -16,7 +16,7 @@ localizationpriority: medium
|
||||
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](https://msdn.microsoft.com/windows/uwp/get-started/whats-a-uwp). Apps created using the [Desktop App Converter](https://docs.microsoft.com/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter) will not run on Surface Hub. See a [list of apps that work with Surface Hub](https://www.microsoft.com/surface/support/surface-hub/surface-hub-apps).
|
||||
- Surface Hub only runs [Universal Windows Platform (UWP) apps](https://msdn.microsoft.com/windows/uwp/get-started/whats-a-uwp). See a [list of apps that work with Surface Hub](https://www.microsoft.com/surface/support/surface-hub/surface-hub-apps).
|
||||
- Apps must be targeted for the [Universal device family](https://msdn.microsoft.com/library/windows/apps/dn894631).
|
||||
- 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.
|
||||
|
28
devices/surface-hub/intro-to-surface-hub.md
Normal file
@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Intro to Microsoft Surface Hub
|
||||
description: Microsoft Surface Hub is an all-in-one productivity device that is intended for brainstorming, collaboration, and presentations.
|
||||
ms.assetid: 5DAD4489-81CF-47ED-9567-A798B90C7E76
|
||||
keywords: Surface Hub, productivity, collaboration, presentations, setup
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Intro to Microsoft Surface Hub
|
||||
|
||||
|
||||
Microsoft Surface Hub is an all-in-one productivity device that is intended for brainstorming, collaboration, and presentations. In order to get the maximum benefit from Surface Hub, your organization’s infrastructure and the Surface Hub itself must be properly set up and integrated. This guide describes what needs to be done both before and during setup in order to help you optimize your use of the device.
|
||||
|
||||
You’ll need to understand how each of these services interacts with Surface Hub. See [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md) for details.
|
||||
|
||||
## Surface Hub setup process
|
||||
|
||||
In some ways, adding your new Surface Hub is just like adding any other Microsoft Windows-based device to your network. However, in order to get your Surface Hub up and running at its full capacity, there are some very specific requirements. Here are the next topics you'll need:
|
||||
|
||||
1. [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md)
|
||||
2. [Physically install your Surface Hub device](physically-install-your-surface-hub-device.md)
|
||||
3. [Run the Surface Hub first-run setup program (OOBE)](first-run-program-surface-hub.md)
|
||||
|
@ -6,7 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -16,38 +16,29 @@ After initial setup of Microsoft Surface Hub, the device’s settings can be loc
|
||||
|
||||
## Surface Hub settings
|
||||
|
||||
Surface Hubs have many settings that are common to other Windows devices, but also have settings which are only configurable on Surface Hubs. This table lists settings only configurable on Surface Hubs.
|
||||
Surface Hubs have many settings that are common to other Windows devices, but also have settings which are only configurable on Surface Hubs. This table lists settings only cofigurable on Surface Hubs.
|
||||
|
||||
| Setting | Location | Description |
|
||||
| ------- | -------- | ----------- |
|
||||
| Device account | Surface Hub > Accounts | Set or change the Surface Hub's device account. |
|
||||
| Device account sync status | Surface Hub > Accounts | Check the sync status of the device account’s mail and calendar on the Surface Hub. |
|
||||
| Password rotation | Surface Hub > Accounts | Choose whether to let the Surface Hub automatically rotate the device account's password. |
|
||||
| Change admin account password | Surface Hub > Accounts | Change the password for the local admin account. This is only available if you configured the device to use a local admin during first run. |
|
||||
| Device Management | Surface Hub > Device management | Manage policies and business applications using mobile device management (MDM). |
|
||||
| Provisioning packages | Surface Hub > Device management | Set or change provisioning packages installed on the Surface Hub. |
|
||||
| Configure Operations Management Suite (OMS) | Surface Hub > Device management | Set up monitoring for your Surface Hub using OMS. |
|
||||
| Open the Windows Store app | Surface Hub > Apps & features | The Windows Store app is only available to admins through the Settings app. |
|
||||
| Skype for Business domain name | Surface Hub > Calling & Audio | Configure a domain name for your Skype for Business server. |
|
||||
| Default Speaker volume | Surface Hub > Calling & Audio | Configure the default speaker volume for the Surface Hub when it starts a session. |
|
||||
| Default microphone and speaker settings | Surface Hub > Calling & Audio | Configure a default microphone and speaker for calls, and a default speaker for media playback. |
|
||||
| Enable Dolby Audio X2 | Surface Hub > Calling & Audio | Configure the Dolby Audio X2 speaker enhancements. |
|
||||
| Open Connect App automatically | Surface Hub > Projection | Choose whether projection will automatically open the Connect app or wait for user input before opening. |
|
||||
| Turn off wireless projection using Miracast | Surface Hub > Projection | Choose whether presenters can wirelessly project to the Surface Hub using Miracast. |
|
||||
| Require a PIN for wireless projection | Surface Hub > Projection | Choose whether people are required to enter a PIN before they use wireless projection. |
|
||||
| Wireless projection (Miracast) channel | Surface Hub > Projection | Set the channel for Miracast projection. |
|
||||
| Meeting info shown on the welcome screen | Surface Hub > Welcome screen | Choose whether meeting organizer, time, and subject show up on the welcome screen. |
|
||||
| Welcome screen background | Surface Hub > Welcome screen | Choose a background image for the welcome screen. |
|
||||
| Idle timeout to Welcome screen | Surface Hub > Session & Power | Choose how long until the Surface Hub returns to the welcome screen after no motion is detected. |
|
||||
| Resume session | Surface Hub > Session & Power | Choose to allow users to resume a session after no motion is detected or to automatically clean up a session. |
|
||||
| Access to Office 365 meetings and files | Surface Hub > Session & Power | Choose whether a user can sign in to Office 365 to get access to their meetings and files. |
|
||||
| Turn on screen with motion sensors | Surface Hub > Session & clean up | Choose whether the screen turns on when motion is detected. |
|
||||
| Session time out | Surface Hub > Session & clean up | Choose how long the device needs to be inactive before returning to the welcome screen. |
|
||||
| Sleep time out | Surface Hub > Session & clean up | Choose how long the device needs to be inactive before going to sleep mode. |
|
||||
| Friendly name | Surface Hub > About | Set the Surface Hub name that people will see when connecting wirelessly. |
|
||||
| Device account | This device > Accounts | Set or change the Surface Hub's device account. |
|
||||
| Device account sync status | This device > Accounts | Check the sync status of the device account’s mail and calendar on the Surface Hub. |
|
||||
| Password rotation | This device > Accounts | Choose whether to let the Surface Hub automatically rotate the device account's password. |
|
||||
| Change admin account password | This device > Accounts | Change the password for the local admin account. This is only available if you configured the device to use a local admin during first run. |
|
||||
| Configure Operations Management Suite (OMS) | This device > Device management | Set up monitoring for your Surface Hub using OMS. |
|
||||
| Open the Windows Store app | This device > Apps & features | The Windows Store app is only available to admins through the Settings app. |
|
||||
| Skype for Business domain name | This device > Calling | Configure a domain name for your Skype for Business server. |
|
||||
| Default microphone and speaker settings | This device > Calling | Configure a default microphone and speaker for calls, and a default speaker for media playback. |
|
||||
| Turn off wireless projection using Miracast | This device > Wireless projection | Choose whether presenters can wirelessly project to the Surface Hub using Miracast. |
|
||||
| Require a PIN for wireless projection | This device > Wireless projection | Choose whether people are required to enter a PIN before they use wireless projection. |
|
||||
| Wireless projection (Miracast) channel | This device > Wireless projection | Set the channel for Miracast projection. |
|
||||
| Meeting info shown on the welcome screen | This device > Welcome screen | Choose whether meeting organizer, time, and subject show up on the welcome screen. |
|
||||
| Welcome screen background | This device > Welcome screen | Choose a background image for the welcome screen. |
|
||||
| Turn on screen with motion sensors | This device > Session & clean up | Choose whether the screen turns on when motion is detected. |
|
||||
| Session time out | This device > Session & clean up | Choose how long the device needs to be inactive before returning to the welcome screen. |
|
||||
| Sleep time out | This device > Session & clean up | Choose how long the device needs to be inactive before going to sleep mode. |
|
||||
| Friendly name | This device > About | Set the Surface Hub name that people will see when connecting wirelessly. |
|
||||
| Maintenance hours | Update & security > Windows Update > Advanced options | Configure when updates can be installed. |
|
||||
| Configure Windows Server Update Services (WSUS) server | Update & security > Windows Update > Advanced options | Change whether Surface Hub receives updates from a WSUS server instead of Windows Update. |
|
||||
| Recover from the cloud | Update & security > Recovery | Reinstall the operating system on Surface Hub to a manufacturer build from the cloud. |
|
||||
| Save BitLocker key | Update & security > Recovery | Backup your Surface Hub's BitLocker key to a USB drive. |
|
||||
| Collect logs | Update & security > Recovery | Save logs to a USB drive to send to Microsoft later. |
|
||||
|
||||
|
@ -0,0 +1,13 @@
|
||||
---
|
||||
title: Manage settings with a local admin account (Surface Hub)
|
||||
description: A local admin account will be set up on every Microsoft Surface Hub as part of the first run program. The only way to change the local admin options that you chose at that time is to reset the device.
|
||||
ms.assetid: B4B3668B-985D-427E-8495-E30ABEECA679
|
||||
redirect_url: https://technet.microsoft.com/itpro/surface-hub/admin-group-management-for-surface-hub
|
||||
keywords: local admin account, Surface Hub, change local admin options
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
@ -65,23 +65,13 @@ For more information, see [SurfaceHub configuration service provider](https://ms
|
||||
| Automatically turn on the screen using motion sensors | InBoxApps/Welcome/AutoWakeScreen | Yes | Yes | Yes |
|
||||
| Require a pin for wireless projection | InBoxApps/WirelessProjection/PINRequired | Yes | Yes | Yes |
|
||||
| Enable wireless projection | InBoxApps/WirelessProjection/Enabled | Yes | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Miracast channel to use for wireless projection | InBoxApps/WirelessProjection/Channel | Yes | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Miracast channel to use for wireless projection | InBoxApps/WirelessProjection/Channel | Yes | Yes.<br> Use a custom setting. | Yes |
|
||||
| Connect to your Operations Management Suite workspace | MOMAgent/WorkspaceID <br> MOMAgent/WorkspaceKey | Yes | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Welcome screen background image | InBoxApps/Welcome/CurrentBackgroundPath | Yes | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Meeting information displayed on the welcome screen | InBoxApps/Welcome/MeetingInfoOption | Yes | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Friendly name for wireless projection | Properties/FriendlyName | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Friendly name for wireless projection | Properties/FriendlyName | Yes. <br> [Use a custom policy.](#example-intune)) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Device account, including password rotation | DeviceAccount/*`<name_of_policy>`* <br> See [SurfaceHub CSP](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx). | No | No | Yes |
|
||||
| Specify Skype domain | InBoxApps/SkypeForBusiness/DomainName | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Auto launch Connect App when projection is initiated | InBoxApps/Connect/AutoLaunch | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Set default volume | Properties/DefaultVolume | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Set screen timeout | Properties/ScreenTimeout | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Set session timeout | Properties/SessionTimeout | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Set sleep timeout | Properties/SleepTimeout | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow session to resume after screen is idle | Properties/AllowSessionResume | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow device account to be used for proxy authentication | Properties/AllowAutoProxyAuth | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Disable auto-populating the sign-in dialog with invitees from scheduled meetings | Properties/DisableSignInSuggestions | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Disable "My meetings and files" feature in Start menu | Properties/DoNotShowMyMeetingsAndFiles | Yes </br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
|
||||
|
||||
### Supported Windows 10 settings
|
||||
|
||||
@ -92,58 +82,57 @@ The following tables include info on Windows 10 settings that have been validate
|
||||
#### Security settings
|
||||
| Setting | Details | CSP reference | Supported with<br>Intune? | Supported with<br>Configuration Manager? | Supported with<br>SyncML\*? |
|
||||
| -------- | -------- | ------------- |-------------------------- | ---------------------------------------- | ------------------------- |
|
||||
| Allow Bluetooth | Keep this enabled to support Bluetooth peripherals. | [Connectivity/AllowBluetooth](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Connectivity_AllowBluetooth) | Yes. <br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Bluetooth policies | Use to set the Bluetooth device name, and block advertising, discovery, and automatic pairing. | Bluetooth/*`<name of policy>`* <br> See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes. <br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow camera | Keep this enabled for Skype for Business. | [Camera/AllowCamera](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Camera_AllowCamera) | Yes. <br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow location | Keep this enabled to support apps such as Maps. | [System/AllowLocation](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowLocation) | Yes. <br> . | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow telemetry | Keep this enabled to help Microsoft improve Surface Hub. | [System/AllowTelemetry](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowTelemetry) | Yes. <br> | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow USB Drives | Keep this enabled to support USB drives on Surface Hub | [System/AllowStorageCard](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#system-allowstoragecard) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
| Allow Bluetooth | Keep this enabled to support Bluetooth peripherals. | [Connectivity/AllowBluetooth](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Connectivity_AllowBluetooth) | Yes. <br> Use a custom policy. | Yes.<br> Use a custom setting. | Yes |
|
||||
| Bluetooth policies | Use to set the Bluetooth device name, and block advertising, discovery, and automatic pairing. | Bluetooth/*`<name of policy>`* <br> See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes. <br> Use a custom policy. | Yes.<br> Use a custom setting. | Yes |
|
||||
| Allow camera | Keep this enabled for Skype for Business. | [Camera/AllowCamera](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Camera_AllowCamera) | Yes. <br> Use a custom policy. | Yes.<br> Use a custom setting. | Yes |
|
||||
| Allow location | Keep this enabled to support apps such as Maps. | [System/AllowLocation](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowLocation) | Yes. <br> Use a custom policy. | Yes.<br> Use a custom setting. | Yes |
|
||||
| Allow telemetry | Keep this enabled to help Microsoft improve Surface Hub. | [System/AllowTelemetry](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowTelemetry) | Yes. <br> Use a custom policy. | Yes.<br> Use a custom setting. | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
|
||||
|
||||
#### Browser settings
|
||||
|
||||
| Setting | Details | CSP reference | Supported with<br>Intune? | Supported with<br>Configuration Manager? | Supported with<br>SyncML\*? |
|
||||
| -------- | ---------------- | ------------- |-------------------------- | ---------------------------------------- | ------------------------- |
|
||||
| Homepages | Use to configure the default homepages in Microsoft Edge. | [Browser/Homepages](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_Homepages) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow cookies | Surface Hub automatically deletes cookies at the end of a session. Use this to block cookies within a session. | [Browser/AllowCookies](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowCookies) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow developer tools | Use to stop users from using F12 Developer Tools. | [Browser/AllowDeveloperTools](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowDeveloperTools) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow Do Not Track | Use to enable Do Not Track headers. | [Browser/AllowDoNotTrack](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowDoNotTrack) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow pop-ups | Use to block pop-up browser windows. | [Browser/AllowPopups](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowPopups) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow search suggestions | Use to block search suggestions in the address bar. | [Browser/AllowSearchSuggestionsinAddressBar](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSearchSuggestionsinAddressBar) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow SmartScreen | Keep this enabled to turn on SmartScreen. | [Browser/AllowSmartScreen](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSmartScreen) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Prevent ignoring SmartScreen Filter warnings for websites | For extra security, use to stop users from ignoring SmartScreen Filter warnings and block them from accessing potentially malicious websites. | [Browser/PreventSmartScreenPromptOverride](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverride) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Prevent ignoring SmartScreen Filter warnings for files | For extra security, use to stop users from ignoring SmartScreen Filter warnings and block them from downloading unverified files from Microsoft Edge. | [Browser/PreventSmartScreenPromptOverrideForFiles](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverrideForFiles) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
| Homepages | Use to configure the default homepages in Microsoft Edge. | [Browser/Homepages](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_Homepages) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Allow cookies | Surface Hub automatically deletes cookies at the end of a session. Use this to block cookies within a session. | [Browser/AllowCookies](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowCookies) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Allow developer tools | Use to stop users from using F12 Developer Tools. | [Browser/AllowDeveloperTools](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowDeveloperTools) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Allow Do Not Track | Use to enable Do Not Track headers. | [Browser/AllowDoNotTrack](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowDoNotTrack) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Allow pop-ups | Use to block pop-up browser windows. | [Browser/AllowPopups](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowPopups) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Allow search suggestions | Use to block search suggestions in the address bar. | [Browser/AllowSearchSuggestionsinAddressBar](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSearchSuggestionsinAddressBar) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Allow SmartScreen | Keep this enabled to turn on SmartScreen. | [Browser/AllowSmartScreen](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSmartScreen) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Prevent ignoring SmartScreen Filter warnings for websites | For extra security, use to stop users from ignoring SmartScreen Filter warnings and block them from accessing potentially malicious websites. | [Browser/PreventSmartScreenPromptOverride](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverride) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Prevent ignoring SmartScreen Filter warnings for files | For extra security, use to stop users from ignoring SmartScreen Filter warnings and block them from downloading unverified files from Microsoft Edge. | [Browser/PreventSmartScreenPromptOverrideForFiles](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverrideForFiles) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
|
||||
|
||||
#### Windows Update settings
|
||||
|
||||
| Setting | Details | CSP reference | Supported with<br>Intune? | Supported with<br>Configuration Manager? | Supported with<br>SyncML*? |
|
||||
| ----------- | ---------------- | ------------- |-------------------------- | ---------------------------------------- | ------------------------- |
|
||||
| Use Current Branch or Current Branch for Business | Use to configure Windows Update for Business – see [Windows updates](manage-windows-updates-for-surface-hub.md). | [Update/BranchReadinessLevel](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_BranchReadinessLevel) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Defer feature updates| See above. | [Update/ DeferFeatureUpdatesPeriodInDays](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_DeferFeatureUpdatesPeriodInDays) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Defer quality updates | See above. | [Update/DeferQualityUpdatesPeriodInDays](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_DeferQualityUpdatesPeriodInDays) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Pause feature updates | See above. | [Update/PauseFeatureUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseFeatureUpdates) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Pause quality updates | See above. | [Update/PauseQualityUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseQualityUpdates) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes|
|
||||
| Configure device to use WSUS| Use to connect your Surface Hub to WSUS instead of Windows Update – see [Windows updates](manage-windows-updates-for-surface-hub.md). | [Update/UpdateServiceUrl](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_UpdateServiceUrl) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Delivery optimization | Use peer-to-peer content sharing to reduce bandwidth issues during updates. See [Configure Delivery Optimization for Windows 10](https://technet.microsoft.com/itpro/windows/manage/waas-delivery-optimization) for details. | DeliveryOptimization/*`<name of policy>`* <br> See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
| Use Current Branch or Current Branch for Business | Use to configure Windows Update for Business – see [Windows updates](manage-windows-updates-for-surface-hub.md). | [Update/BranchReadinessLevel](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_BranchReadinessLevel) | Yes. Use a custom policy. | Yes. Use a custom setting. | Yes |
|
||||
| Defer feature updates| See above. | [Update/ DeferFeatureUpdatesPeriodInDays](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_DeferFeatureUpdatesPeriodInDays) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Defer quality updates | See above. | [Update/DeferQualityUpdatesPeriodInDays](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_DeferQualityUpdatesPeriodInDays) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Pause feature updates | See above. | [Update/PauseFeatureUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseFeatureUpdates) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Pause quality updates | See above. | [Update/PauseQualityUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseQualityUpdates) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes|
|
||||
| Configure device to use WSUS| Use to connect your Surface Hub to WSUS instead of Windows Update – see [Windows updates](manage-windows-updates-for-surface-hub.md). | [Update/UpdateServiceUrl](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_UpdateServiceUrl) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Delivery optimization | Use peer-to-peer content sharing to reduce bandwidth issues during updates. See [Configure Delivery Optimization for Windows 10](https://technet.microsoft.com/itpro/windows/manage/waas-delivery-optimization) for details. | DeliveryOptimization/*`<name of policy>`* <br> See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
|
||||
|
||||
#### Windows Defender settings
|
||||
|
||||
| Setting | Details | CSP reference | Supported with<br>Intune? | Supported with<br>Configuration Manager? | Supported with<br>SyncML\*? |
|
||||
| ----------- | ---------------- | ------------- |-------------------------- | ---------------------------------------- | ------------------------- |
|
||||
| Defender policies | Use to configure various Defender settings, including a scheduled scan time. | Defender/*`<name of policy>`* <br> See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Defender policies | Use to configure various Defender settings, including a scheduled scan time. | Defender/*`<name of policy>`* <br> See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Defender status | Use to initiate a Defender scan, force a signature update, query any threats detected. | [Defender CSP](https://msdn.microsoft.com/library/windows/hardware/mt187856.aspx) | No. | No. | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
|
||||
|
||||
#### Remote reboot
|
||||
|
||||
| Setting | Details | CSP reference | Supported with<br>Intune? | Supported with<br>Configuration Manager? | Supported with<br>SyncML\*? |
|
||||
| ----------- | ---------------- | ------------- |-------------------------- | ---------------------------------------- | ------------------------- |
|
||||
| Reboot the device immediately | Use in conjunction with OMS to minimize support costs – see [Monitor your Microsoft Surface Hub](monitor-surface-hub.md). | ./Vendor/MSFT/Reboot/RebootNow <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | No | No | Yes |
|
||||
| Reboot the device at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/Single <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Reboot the device daily at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/DailyRecurrent <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
| Reboot the device at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/Single <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
| Reboot the device daily at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/DailyRecurrent <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
|
||||
|
||||
#### Install certificates
|
||||
|
||||
@ -153,7 +142,7 @@ The following tables include info on Windows 10 settings that have been validate
|
||||
<!--
|
||||
| Install client certificates | Use to deploy Personal Information Exchange (.pfx, .p12) certificates. | [ClientCertificateInstall CSP](https://msdn.microsoft.com/library/windows/hardware/dn920023.aspx) | Yes. <br> See [How to Create and Deploy PFX Certificate Profiles in Intune Standalone](https://blogs.technet.microsoft.com/karanrustagi/2016/03/16/want-to-push-a-certificate-to-device-but-cant-use-ndes-continue-reading/). | Yes. <br> See [How to create PFX certificate profiles in System Center Configuration Manager](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/create-pfx-certificate-profiles). | Yes |
|
||||
-->
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
|
||||
|
||||
#### Collect logs
|
||||
|
||||
@ -162,7 +151,7 @@ The following tables include info on Windows 10 settings that have been validate
|
||||
| Collect ETW logs | Use to remotely collect ETW logs from Surface Hub. | [DiagnosticLog CSP](https://msdn.microsoft.com/library/windows/hardware/mt219118.aspx) | No | No | Yes |
|
||||
<!--
|
||||
| Collect security auditing logs | Use to remotely collect security auditing logs from Surface Hub. | SecurityAuditing node in [Reporting CSP](https://msdn.microsoft.com/en-us/library/windows/hardware/mt608321.aspx) | No | No | Yes |-->
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
|
||||
|
||||
### Generate OMA URIs for settings
|
||||
You need to use a setting’s OMA URI to create a custom policy in Intune, or a custom setting in System Center Configuration Manager.
|
||||
@ -263,7 +252,7 @@ For more information, see [Create configuration items for Windows 8.1 and Window
|
||||
|
||||
[Manage Microsoft Surface Hub](manage-surface-hub.md)
|
||||
|
||||
|
||||
[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
|
||||
|
||||
|
||||
|
||||
|
@ -6,7 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -30,7 +30,7 @@ Learn about managing and updating Surface Hub.
|
||||
| [Remote Surface Hub management](remote-surface-hub-management.md) |Topics related to managing your Surface Hub remotely. Include install apps, managing settings with MDM and monitoring with Operations Management Suite. |
|
||||
| [Manage Surface Hub settings](manage-surface-hub-settings.md) |Topics related to managing Surface Hub settings: accessibility, device account, device reset, fully qualified domain name, Windows Update settings, and wireless network |
|
||||
| [Install apps on your Surface Hub]( https://technet.microsoft.com/itpro/surface-hub/install-apps-on-surface-hub) | Admins can install apps can from either the Windows Store or the Windows Store for Business.|
|
||||
| [End a meeting with End session](https://technet.microsoft.com/itpro/surface-hub/i-am-done-finishing-your-surface-hub-meeting) | At the end of a meeting, users can tap **End session** to clean up any sensitive data and prepare the device for the next meeting.|
|
||||
| [End a meeting with I’m done](https://technet.microsoft.com/itpro/surface-hub/i-am-done-finishing-your-surface-hub-meeting) | At the end of a meeting, users can tap I'm Done to clean up any sensitive data and prepare the device for the next meeting.|
|
||||
| [Save your BitLocker key](https://technet.microsoft.com/itpro/surface-hub/save-bitlocker-key-surface-hub) | Every Surface Hub is automatically set up with BitLocker drive encryption software. Microsoft strongly recommends that you make sure you back up your BitLocker recovery keys.|
|
||||
| [Connect other devices and display with Surface Hub](https://technet.microsoft.com/itpro/surface-hub/connect-and-display-with-surface-hub) | You can connect other device to your Surface Hub to display content.|
|
||||
| [Using a room control system]( https://technet.microsoft.com/itpro/surface-hub/use-room-control-system-with-surface-hub) | Room control systems can be used with your Microsoft Surface Hub.|
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, readiness
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -27,12 +27,11 @@ Review these dependencies to make sure Surface Hub features will work in your IT
|
||||
| Skype for Business (Lync Server 2013 or later, or Skype for Business Online) | Skype for Business is used for various conferencing features, like video calls, instant messaging, and screen sharing.</br></br>If screen sharing on a Surface Hub fails and the error message **An error occurred during the screen presentation** is displayed, see [Video Based Screen Sharing not working on Surface Hub](https://support.microsoft.com/help/3179272/video-based-screen-sharing-not-working-on-surface-hub) for help. |
|
||||
| Mobile device management (MDM) solution (Microsoft Intune, System Center Configuration Manager, or supported third-party MDM provider) | If you want to apply settings and install apps remotely, and to multiple devices at a time, you must set up a MDM solution and enroll the device to that solution. See [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) for details. |
|
||||
| Microsoft Operations Managmement Suite (OMS) | OMS is used to monitor the health of Surface Hub devices. See [Monitor your Surface Hub](monitor-surface-hub.md) for details. |
|
||||
| Network and Internet access | <p>In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred. 802.1x Authentication is supported for both wired and wireless connections.</p><p>**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.</p>**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. Proxy credentials are stored across Surface Hub sessions and only need to be set once. |
|
||||
| Network and Internet access | <p>In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred.</p><p>**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.</p>**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. |
|
||||
|
||||
Additionally, note that Surface Hub requires the following open ports:
|
||||
- HTTPS: 443
|
||||
- HTTP: 80
|
||||
- NTP: 123
|
||||
|
||||
Depending on your environment, access to additional ports may be needed:
|
||||
- For online environments, see [Office 365 IP URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US).
|
||||
@ -42,20 +41,6 @@ Microsoft collects telemetry to help improve your Surface Hub experience. Add th
|
||||
- Telemetry client endpoint: `https://vortex.data.microsoft.com/`
|
||||
- Telemetry settings endpoint: `https://settings.data.microsoft.com/`
|
||||
|
||||
### Proxy configuration
|
||||
|
||||
If your organization restricts computers on your network from connecting to the Internet, there is a set of URLs that need to be available for devices to use Store for Business. Some of the Store for Business features use Windows Store app and Windows Store services. Devices using Store for Business – either to acquire, install, or update apps – will need access to these URLs. If you use a proxy server to block traffic, your configuration needs to allow these URLs:
|
||||
|
||||
- login.live.com
|
||||
- login.windows.net
|
||||
- account.live.com
|
||||
- clientconfig.passport.net
|
||||
- windowsphone.com
|
||||
- *.wns.windows.com
|
||||
- *.microsoft.com
|
||||
- www.msftncsi.com (prior to Windows 10, version 1607)
|
||||
- www.msftconnecttest.com/connecttest.txt (replaces www.msftncsi.com starting with Windows 10, version 1607)
|
||||
|
||||
|
||||
## Work with other admins
|
||||
|
||||
@ -64,7 +49,7 @@ Surface Hub interacts with a few different products and services. Depending on t
|
||||
|
||||
## Create and verify device account
|
||||
|
||||
A device account is an Exchange resource account that Surface Hub uses to display its meeting calendar, join Skype for Business calls, send email, and (optionally) to authenticate to Exchange. See [Create and test a device account](create-and-test-a-device-account-surface-hub.md) for details.
|
||||
A device account is an Exchange resource account that Surface Hub uses to display its meeting calendar, join Skype for Business calls, and send email. See [Create and test a device account](create-and-test-a-device-account-surface-hub.md) for details.
|
||||
|
||||
After you've created your device account, there are a couple of ways to verify that it's setup correctly.
|
||||
- Run Surface Hub device account validation PowerShell scripts. For more information, see [Surface Hub device account scripts](https://gallery.technet.microsoft.com/scriptcenter/Surface-Hub-device-account-6db77696) in Script Center, or [PowerShell scripts for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) later in this guide.
|
||||
|
@ -0,0 +1,221 @@
|
||||
---
|
||||
title: Create provisioning packages (Surface Hub)
|
||||
description: For Windows 10, settings that use the registry or a content services platform (CSP) can be configured using provisioning packages. You can also add certificates during first run using provisioning.
|
||||
ms.assetid: 8AA25BD4-8A8F-4B95-9268-504A49BA5345
|
||||
keywords: add certificate, provisioning package
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Create provisioning packages (Surface Hub)
|
||||
|
||||
This topic explains how to create a provisioning package using the Windows Imaging and Configuration Designer (ICD), and apply it to Surface Hub devices. For Surface Hub, you can use provisioning packages to add certificates, install Universal Windows Platform (UWP) apps, and customize policies and settings.
|
||||
|
||||
You can apply a provisioning package using a USB during first run, or through the **Settings** app.
|
||||
|
||||
|
||||
## Advantages
|
||||
- Quickly configure devices without using a MDM provider.
|
||||
|
||||
- No network connectivity required.
|
||||
|
||||
- Simple to apply.
|
||||
|
||||
[Learn more about the benefits and uses of provisioning packages.](https://technet.microsoft.com/itpro/windows/whats-new/new-provisioning-packages)
|
||||
|
||||
|
||||
## Requirements
|
||||
|
||||
To create and apply a provisioning package to a Surface Hub, you'll need the following:
|
||||
|
||||
- Windows Imaging and Configuration Designer (ICD), which is installed as a part of the [Windows 10 Assessment and Deployment Kit (ADK)](http://go.microsoft.com/fwlink/p/?LinkId=526740).
|
||||
- A PC running Windows 10.
|
||||
- A USB flash drive.
|
||||
- If you apply the package using the **Settings** app, you'll need device admin credentials.
|
||||
|
||||
You'll create the provisioning package on a PC running Windows 10, save the package to a USB drive, and then deploy it to your Surface Hub.
|
||||
|
||||
|
||||
## Supported items for Surface Hub provisioning packages
|
||||
|
||||
Currently, you can add these items to provisioning packages for Surface Hub:
|
||||
- **Certificates** - You can add certificates, if needed, to authenticate to Microsoft Exchange.
|
||||
- **Universal Windows Platform (UWP) apps** - You can install UWP apps. This can be an offline-licensed app from the Windows Store for Business, or an app created by an in-house dev.
|
||||
- **Policies** - Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD.
|
||||
- **Settings** - You can configure any setting in the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx).
|
||||
|
||||
|
||||
## Create the provisioning package
|
||||
|
||||
Use the Windows Imaging and Configuration Designer (ICD) tool included in the Windows Assessment and Deployment Kit (ADK) for Windows 10 to create a provisioning package. When you install the ADK, you can choose to install only the Imaging and Configuration Designer (ICD). [Install the ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740)
|
||||
|
||||
1. Open Windows ICD (by default, `%windir%\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe`).
|
||||
|
||||
2. Click **Advanced provisioning**.
|
||||
|
||||

|
||||
|
||||
3. Name your project and click **Next**.
|
||||
|
||||
4. Select **Common to Windows 10 Team edition**, click **Next**, and then click **Finish**.
|
||||
|
||||

|
||||
|
||||
5. In the project, under **Available customizations**, select **Common Team edition settings**.
|
||||
|
||||

|
||||
|
||||
|
||||
### Add a certificate to your package
|
||||
You can use provisioning packages to install certificates that will allow the device to authenticate to Microsoft Exchange.
|
||||
|
||||
> [!NOTE]
|
||||
> Provisioning packages can only install certificates to the device (local machine) store, and not to the user store. If your organization requires that certificates must be installed to the user store, use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **Certificates** > **ClientCertificates**.
|
||||
|
||||
2. Enter a **CertificateName** and then click **Add**.
|
||||
|
||||
2. Enter the **CertificatePassword**.
|
||||
|
||||
3. For **CertificatePath**, browse and select the certificate.
|
||||
|
||||
4. Set **ExportCertificate** to **False**.
|
||||
|
||||
5. For **KeyLocation**, select **Software only**.
|
||||
|
||||
|
||||
### Add a Universal Windows Platform (UWP) app to your package
|
||||
Before adding a UWP app to a provisioning package, you need the app package (either an .appx, or .appxbundle) and any dependency files. If you acquired the app from the Windows Store for Business, you will also need the *unencoded* app license. See [Distribute offline apps](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app) to learn how to download these items from the Windows Store for Business.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextApp**.
|
||||
|
||||
2. Enter a **PackageFamilyName** for the app and then click **Add**. For consistency, use the app's package family name. If you acquired the app from the Windows Store for Business, you can find the package family name in the app license. Open the license file using a text editor, and use the value between the \<PFM\>...\</PFM\> tags.
|
||||
|
||||
3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle).
|
||||
|
||||
4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. For Surface Hub, you will only need the x64 versions of these dependencies.
|
||||
|
||||
If you acquired the app from the Windows Store for Business, you will also need to add the app license to your provisioning package.
|
||||
|
||||
1. Make a copy of the app license, and rename it to use a **.ms-windows-store-license** extension. For example, "example.xml" becomes "example.ms-windows-store-license".
|
||||
|
||||
2. In ICD, in the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextAppLicense**.
|
||||
|
||||
3. Enter a **LicenseProductId** and then click **Add**. For consistency, use the app's license ID from the app license. Open the license file using a text editor. Then, in the \<License\> tag, use the value in the **LicenseID** attribute.
|
||||
|
||||
4. Select the new **LicenseProductId** node. For **LicenseInstall**, click **Browse** to find and select the license file that you renamed in Step 1.
|
||||
|
||||
|
||||
### Add a policy to your package
|
||||
Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **Policies**.
|
||||
|
||||
2. Select one of the available policy areas.
|
||||
|
||||
3. Select and set the policy you want to add to your provisioning package.
|
||||
|
||||
|
||||
### Add Surface Hub settings to your package
|
||||
|
||||
You can add settings from the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx) to your provisioning package.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **WindowsTeamSettings**.
|
||||
|
||||
2. Select one of the available setting areas.
|
||||
|
||||
3. Select and set the setting you want to add to your provisioning package.
|
||||
|
||||
|
||||
## Build your package
|
||||
|
||||
1. When you are done configuring the provisioning package, on the **File** menu, click **Save**.
|
||||
|
||||
2. Read the warning that project files may contain sensitive information, and click **OK**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
|
||||
|
||||
3. On the **Export** menu, click **Provisioning package**.
|
||||
|
||||
4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources.
|
||||
|
||||
5. Set a value for **Package Version**, and then select **Next.**
|
||||
|
||||
> [!TIP]
|
||||
> You can make changes to existing packages and change the version number to update previously applied packages.
|
||||
|
||||
6. Optional: You can choose to encrypt the package and enable package signing.
|
||||
|
||||
- **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
|
||||
|
||||
- **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse...** and choosing the certificate you want to use to sign the package.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently.
|
||||
|
||||
7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.<p>
|
||||
Optionally, you can click **Browse** to change the default output location.
|
||||
|
||||
8. Click **Next**.
|
||||
|
||||
9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.<p>
|
||||
If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
|
||||
|
||||
10. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.<p>
|
||||
If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
|
||||
|
||||
- If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build.
|
||||
|
||||
- If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
|
||||
|
||||
11. Select the **output location** link to go to the location of the package. Copy the .ppkg to an empty USB flash drive.
|
||||
|
||||
|
||||
## Apply a provisioning package to Surface Hub
|
||||
|
||||
There are two options for deploying provisioning packages to a Surface Hub. You can apply a provisioning packing [during the first run wizard](#apply-a-provisioning-package-during-first-run), or using [Settings](#apply-a-package-using-settings).
|
||||
|
||||
|
||||
### Apply a provisioning package during first run
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Only use provisioning packages to install certificates during first run. Use the **Settings** app to install apps and apply other settings.
|
||||
|
||||
1. When you turn on the Surface Hub for the first time, the first-run program will display the [**Hi there page**](first-run-program-surface-hub.md#first-page). Make sure that the settings are properly configured before proceeding.
|
||||
|
||||
2. Insert the USB flash drive containing the .ppkg file into the Surface Hub. If the package is in the root directory of the drive, the first-run program will recognize it and ask if you want to set up the device. Select **Set up**.
|
||||
|
||||

|
||||
|
||||
3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**. Note that you can only install one package during first run.
|
||||
|
||||

|
||||
|
||||
5. The first-run program will show you a summary of the changes that the provisioning package will apply. Select **Yes, add it**. The package will be applied, and you'll be taken to the next page in the first-run program.
|
||||
|
||||

|
||||
|
||||
|
||||
### Apply a package using Settings
|
||||
|
||||
1. Insert the USB flash drive containing the .ppkg file into the Surface Hub.
|
||||
|
||||
2. From the Surface Hub, start **Settings** and enter the admin credentials when prompted.
|
||||
|
||||
3. Navigate to **This device** > **Device management**. Under **Provisioning packages**, select **Add or remove a provisioning package**.
|
||||
|
||||
4. Select **Add a package**.
|
||||
|
||||
5. Choose your provisioning package and select **Add**. You may have to re-enter the admin credentials if prompted.
|
||||
|
||||
6. You'll see a summary of the changes that the provisioning package will apply. Select **Yes, add it**.
|
@ -1,319 +0,0 @@
|
||||
---
|
||||
title: Create provisioning packages (Surface Hub)
|
||||
description: For Windows 10, settings that use the registry or a configuration service provider (CSP) can be configured using provisioning packages.
|
||||
ms.assetid: 8AA25BD4-8A8F-4B95-9268-504A49BA5345
|
||||
keywords: add certificate, provisioning package
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Create provisioning packages (Surface Hub)
|
||||
|
||||
This topic explains how to create a provisioning package using the Windows Configuration Designer, and apply it to Surface Hub devices. For Surface Hub, you can use provisioning packages to add certificates, install Universal Windows Platform (UWP) apps, and customize policies and settings.
|
||||
|
||||
You can apply a provisioning package using a USB stick during first-run setup, or through the **Settings** app.
|
||||
|
||||
|
||||
## Advantages
|
||||
- Quickly configure devices without using a mobile device management (MDM) provider.
|
||||
|
||||
- No network connectivity required.
|
||||
|
||||
- Simple to apply.
|
||||
|
||||
[Learn more about the benefits and uses of provisioning packages.](https://technet.microsoft.com/itpro/windows/configure/provisioning-packages)
|
||||
|
||||
|
||||
## Requirements
|
||||
|
||||
To create and apply a provisioning package to a Surface Hub, you'll need the following:
|
||||
|
||||
- Windows Configuration Designer, which can be installed from Windows Store or from the Windows 10 Assessment and Deployment Kit (ADK). [Learn how to install Windows Configuration Designer.](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd)
|
||||
- A USB stick.
|
||||
- If you apply the package using the **Settings** app, you'll need device admin credentials.
|
||||
|
||||
You create the provisioning package on a PC running Windows 10, save the package to a USB drive, and then deploy it to your Surface Hub.
|
||||
|
||||
|
||||
## Supported items for Surface Hub provisioning packages
|
||||
|
||||
Using the **Provision Surface Hub devices** wizard, you can:
|
||||
|
||||
- Enroll in Active Directory, Azure Active Directory, or MDM
|
||||
- Create an device administrator account
|
||||
- Add applications and certificates
|
||||
- Configure proxy settings
|
||||
- Add a Surface Hub configuration file
|
||||
|
||||
>[!WARNING]
|
||||
>You must run Windows Configuration Designer on Windows 10 to configure Azure Active Directory enrollment using the wizard.
|
||||
|
||||
Using the advanced provisioning editor, you can add these items to provisioning packages for Surface Hub:
|
||||
|
||||
- **Policies** - Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#surfacehubpolicies).
|
||||
- **Settings** - You can configure any setting in the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx).
|
||||
|
||||
>[!TIP]
|
||||
> Use the wizard to create a package with the common settings, then switch to the advanced editor to add other settings.
|
||||
>
|
||||
>
|
||||
|
||||
## Use the Surface Hub provisioning wizard
|
||||
|
||||
After you [install Windows Configuration Designer](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd), you can create a provisioning package.
|
||||
|
||||
### Create the provisioning package
|
||||
|
||||
1. Open Windows Configuration Designer:
|
||||
- From either the Start screen or Start menu search, type 'Windows Configuration Designer' and click on the Windows Configuration Designer shortcut,
|
||||
|
||||
or
|
||||
|
||||
- If you installed Windows Configuration Designer from the ADK, navigate to `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86` (on an x64 computer) or `C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe` (on an x86 computer), and then double-click **ICD.exe**.
|
||||
|
||||
2. Click **Provision Surface Hub devices**.
|
||||
|
||||
3. Name your project and click **Next**.
|
||||
|
||||
### Configure settings
|
||||
|
||||
<table>
|
||||
<tr><td style="width:45%" valign="top"> </br></br>To provision the device with a certificate, click **Add a certificate**. Enter a name for the certificate, and then browse to and select the certificate to be used.</td><td></td></tr>
|
||||
<tr><td style="width:45%" valign="top"> </br></br>Toggle **Yes** or **No** for proxy settings. The default configuration for Surface Hub is to automatically detect proxy settings, so you can select **No** if that is the setting that you want. However, if your infrastructure previously required using a proxy server and has changed to not require a proxy server, you can use a provisioning package to revert your Surface Hub devices to the default settings by selecting **Yes** and **Automatically detect settings**. </br></br>If you toggle **Yes**, you can select to automatically detect proxy settings, or you can manually configure the settings by entering a URL to a setup script, or a static proxy server address. You can also identify whether to use the proxy server for local addresses, and enter exceptions (addresses that Surface Hub should connect to directly without using the proxy server). </td><td></td></tr>
|
||||
<tr><td style="width:45%" valign="top"> </br></br>You can enroll the device in Active Directory and specify a security group to use the Settings app, enroll in Azure Active Directory to allow global admins to use the Settings app, or create a local administrator account on the device.</br></br>To enroll the device in Active Directory, enter the credentials for a least-privileged user account to join the device to the domain, and specify the security group to have admin credentials on Surface Hub. If a provisioning package that enrolls a device in Active Directory is going to be applied to a Surface Hub that was reset, the same domain account can only be used if the account listed is a domain administrator or is the same account that set up the Surface Hub initially. Otherwise, a different domain account must be used in the provisioning package.</br></br>Before you use a Windows Configuration Designer wizard to configure bulk Azure AD enrollment, [set up Azure AD join in your organization](https://docs.microsoft.com/azure/active-directory/active-directory-azureadjoin-setup). The **maximum number of devices per user** setting in your Azure AD tenant determines how many times the bulk token that you get in the wizard can be used. To enroll the device in Azure AD, select that option and enter a friendly name for the bulk token you will get using the wizard. Set an expiration date for the token (maximum is 30 days from the date you get the token). Click **Get bulk token**. In the **Let's get you signed in** window, enter an account that has permissions to join a device to Azure AD, and then the password. Click **Accept** to give Windows Configuration Designer the necessary permissions.</br></br>To create a local administrator account, select that option and enter a user name and password. </br></br>**Important:** If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. </td><td></td></tr>
|
||||
<tr><td style="width:45%" valign="top"> </br></br>Toggle **Yes** or **No** for enrollment in MDM. </br></br>If you toggle **Yes**, you must provide a service account and password or certificate thumbprint that is authorized to enroll the device, and also specify the authentication type. If required by your MDM provider, also enter the URLs for the discovery service, enrollment service, and policy service. [Learn more about managing Surface Hub with MDM.](manage-settings-with-mdm-for-surface-hub.md)</td><td></td></tr>
|
||||
<tr><td style="width:45%" valign="top"> </br></br>You can install multiple Universal Windows Platform (UWP) apps in a provisioning package. For help with the settings, see [Provision PCs with apps](https://technet.microsoft.com/itpro/windows/configure/provision-pcs-with-apps). </br></br>**Important:** Although the wizard interface allows you to select a Classic Win32 app, only include UWP apps in a provisioning package that will be applied to Surface Hub. If you include a Classic Win32 app, provisioning will fail. </td><td></td></tr>
|
||||
<tr><td style="width:45%" valign="top"> </br></br>You don't configure any settings in this step. It provides instructions for including a configuration file that contains a list of device accounts. The configuration file must not contain column headers. When you apply the provisioning package to Surface Hub, if a Surface Hub configuration file is included on the USB drive, you can select the account and friendly name for the device from the file. See [Sample configuration file](#sample-configuration-file) for an example.</br></br>**Important:** The configuration file can only be applied during the out-of-box setup experience (OOBE) and can only be used with provisioning packages created using the Windows Configuration Designer released with Windows 10, version 1703. </td><td></td></tr>
|
||||
<tr><td style="width:45%" valign="top"> </br></br>You can set a password to protect your provisioning package. You must enter this password when you apply the provisioning package to a device.</td><td></td></tr>
|
||||
</table>
|
||||
|
||||
After you're done, click **Create**. It only takes a few seconds. When the package is built, the location where the package is stored is displayed as a hyperlink at the bottom of the page.
|
||||
|
||||
## Sample configuration file
|
||||
|
||||
A Surface Hub configuration file contains a list of device accounts that your device can use to connect to Exchange and Skype for Business. When you apply a provisioning package to Surface Hub, you can include a configuration file in the root directory of the USB flash drive, and then select the desired account to apply to that device. The configuration file can only be applied during the out-of-box setup experience (OOBE) and can only be used with provisioning packages created using the Windows Configuration Designer released with Windows 10, version 1703.
|
||||
|
||||
Use Microsoft Excel or other CSV editor to create a CSV file named `SurfaceHubConfiguration.csv`. In the file, enter a list of device accounts and friendly names in this format:
|
||||
|
||||
```
|
||||
<DeviceAccountName>,<DeviceAccountPassword>,<FriendlyName>
|
||||
```
|
||||
>[!IMPORTANT]
|
||||
>Because the configuration file stores the device account passwords in plaintext, we recommend that you update the passwords after you've applied the provisioning package to your devices. You can use the [DeviceAccount node](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp#deviceaccount) in the [Surface Hub configuration service provider (CSP)](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp) to update the passwords via MDM.
|
||||
|
||||
|
||||
The following is an example of `SurfaceHubConfiguration.csv`.
|
||||
|
||||
```
|
||||
Rainier@contoso.com,password,Rainier Surface Hub
|
||||
Adams@contoso.com,password,Adams Surface Hub
|
||||
Baker@contoso.com,password,Baker Surface Hub
|
||||
Glacier@constoso.com,password,Glacier Surface Hub
|
||||
Stuart@contoso.com,password,Stuart Surface Hub
|
||||
Fernow@contoso.com,password,Fernow Surface Hub
|
||||
Goode@contoso.com,password,Goode Surface Hub
|
||||
Shuksan@contoso.com,password,Shuksan Surface Hub
|
||||
Buckner@contoso.com,password,Buckner Surface Hub
|
||||
Logan@contoso.com,password,Logan Surface Hub
|
||||
Maude@consoto.com,password,Maude Surface hub
|
||||
Spickard@contoso.com,password,Spickard Surface Hub
|
||||
Redoubt@contoso.com,password,Redoubt Surface Hub
|
||||
Dome@contoso.com,password,Dome Surface Hub
|
||||
Eldorado@contoso.com,password,Eldorado Surface Hub
|
||||
Dragontail@contoso.com,password,Dragontail Surface Hub
|
||||
Forbidden@contoso.com,password,Forbidden Surface Hub
|
||||
Oval@contoso.com,password,Oval Surface Hub
|
||||
StHelens@contoso.com,password,St Helens Surface Hub
|
||||
Rushmore@contoso.com,password,Rushmore Surface Hub
|
||||
```
|
||||
|
||||
## Use advanced provisioning
|
||||
|
||||
After you [install Windows Configuration Designer](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd), you can create a provisioning package.
|
||||
|
||||
### Create the provisioning package (advanced)
|
||||
|
||||
1. Open Windows Configuration Designer:
|
||||
- From either the Start screen or Start menu search, type 'Windows Configuration Designer' and click on the Windows Configuration Designer shortcut,
|
||||
|
||||
or
|
||||
|
||||
- If you installed Windows Configuration Designer from the ADK, navigate to `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86` (on an x64 computer) or `C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe` (on an x86 computer), and then double-click **ICD.exe**.
|
||||
|
||||
2. Click **Advanced provisioning**.
|
||||
|
||||
3. Name your project and click **Next**.
|
||||
|
||||
4. Select **Common to Windows 10 Team edition**, click **Next**, and then click **Finish**.
|
||||
|
||||

|
||||
|
||||
5. In the project, under **Available customizations**, select **Common Team edition settings**.
|
||||
|
||||

|
||||
|
||||
|
||||
### Add a certificate to your package
|
||||
You can use provisioning packages to install certificates that will allow the device to authenticate to Microsoft Exchange.
|
||||
|
||||
> [!NOTE]
|
||||
> Provisioning packages can only install certificates to the device (local machine) store, and not to the user store. If your organization requires that certificates must be installed to the user store, use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **Certificates** > **ClientCertificates**.
|
||||
|
||||
2. Enter a **CertificateName** and then click **Add**.
|
||||
|
||||
2. Enter the **CertificatePassword**.
|
||||
|
||||
3. For **CertificatePath**, browse and select the certificate.
|
||||
|
||||
4. Set **ExportCertificate** to **False**.
|
||||
|
||||
5. For **KeyLocation**, select **Software only**.
|
||||
|
||||
|
||||
### Add a Universal Windows Platform (UWP) app to your package
|
||||
Before adding a UWP app to a provisioning package, you need the app package (either an .appx, or .appxbundle) and any dependency files. If you acquired the app from the Windows Store for Business, you will also need the *unencoded* app license. See [Distribute offline apps](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app) to learn how to download these items from the Windows Store for Business.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextApp**.
|
||||
|
||||
2. Enter a **PackageFamilyName** for the app and then click **Add**. For consistency, use the app's package family name. If you acquired the app from the Windows Store for Business, you can find the package family name in the app license. Open the license file using a text editor, and use the value between the \<PFM\>...\</PFM\> tags.
|
||||
|
||||
3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle).
|
||||
|
||||
4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. For Surface Hub, you will only need the x64 versions of these dependencies.
|
||||
|
||||
If you acquired the app from the Windows Store for Business, you will also need to add the app license to your provisioning package.
|
||||
|
||||
1. Make a copy of the app license, and rename it to use a **.ms-windows-store-license** extension. For example, "example.xml" becomes "example.ms-windows-store-license".
|
||||
|
||||
2. In ICD, in the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextAppLicense**.
|
||||
|
||||
3. Enter a **LicenseProductId** and then click **Add**. For consistency, use the app's license ID from the app license. Open the license file using a text editor. Then, in the \<License\> tag, use the value in the **LicenseID** attribute.
|
||||
|
||||
4. Select the new **LicenseProductId** node. For **LicenseInstall**, click **Browse** to find and select the license file that you renamed in Step 1.
|
||||
|
||||
|
||||
### Add a policy to your package
|
||||
Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **Policies**.
|
||||
|
||||
2. Select one of the available policy areas.
|
||||
|
||||
3. Select and set the policy you want to add to your provisioning package.
|
||||
|
||||
|
||||
### Add Surface Hub settings to your package
|
||||
|
||||
You can add settings from the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx) to your provisioning package.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **WindowsTeamSettings**.
|
||||
|
||||
2. Select one of the available setting areas.
|
||||
|
||||
3. Select and set the setting you want to add to your provisioning package.
|
||||
|
||||
|
||||
## Build your package
|
||||
|
||||
1. When you are done configuring the provisioning package, on the **File** menu, click **Save**.
|
||||
|
||||
2. Read the warning that project files may contain sensitive information, and click **OK**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
|
||||
|
||||
3. On the **Export** menu, click **Provisioning package**.
|
||||
|
||||
4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources.
|
||||
|
||||
5. Set a value for **Package Version**, and then select **Next.**
|
||||
|
||||
> [!TIP]
|
||||
> You can make changes to existing packages and change the version number to update previously applied packages.
|
||||
|
||||
6. Optional: You can choose to encrypt the package and enable package signing.
|
||||
|
||||
- **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
|
||||
|
||||
- **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse...** and choosing the certificate you want to use to sign the package.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently.
|
||||
|
||||
7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.<p>
|
||||
Optionally, you can click **Browse** to change the default output location.
|
||||
|
||||
8. Click **Next**.
|
||||
|
||||
9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.<p>
|
||||
If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
|
||||
|
||||
10. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.<p>
|
||||
If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
|
||||
|
||||
- If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build.
|
||||
|
||||
- If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
|
||||
|
||||
11. Select the **output location** link to go to the location of the package. Copy the .ppkg to an empty USB flash drive.
|
||||
|
||||
|
||||
## Apply a provisioning package to Surface Hub
|
||||
|
||||
There are two options for deploying provisioning packages to a Surface Hub. You can apply a provisioning packing [during the first run wizard](#apply-a-provisioning-package-during-first-run), or using [Settings](#apply-a-package-using-settings).
|
||||
|
||||
|
||||
### Apply a provisioning package during first run
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Only use provisioning packages to install certificates during first run. Use the **Settings** app to install apps and apply other settings.
|
||||
|
||||
1. When you turn on the Surface Hub for the first time, the first-run program will display the [**Hi there page**](first-run-program-surface-hub.md#first-page). Make sure that the settings are properly configured before proceeding.
|
||||
|
||||
2. Insert the USB flash drive containing the .ppkg file into the Surface Hub. If the package is in the root directory of the drive, the first-run program will recognize it and ask if you want to set up the device. Select **Set up**.
|
||||
|
||||

|
||||
|
||||
3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**. Note that you can only install one package during first run.
|
||||
|
||||

|
||||
|
||||
5. The first-run program will show you a summary of the changes that the provisioning package will apply. Select **Yes, add it**.
|
||||
|
||||

|
||||
|
||||
6. If a configuration file is included in the root directory of the USB flash drive, you will see **Select a configuration**. The first device account in the configuration file will be shown with a summary of the account information that will be applied to the Surface Hub.
|
||||
|
||||

|
||||
|
||||
7. In **Select a configuration**, select the device name to apply, and then click **Next**.
|
||||
|
||||

|
||||
|
||||
The settings from the provisioning package will be applied to the device and OOBE will be complete. After the device restarts, you can remove the USB flash drive.
|
||||
|
||||
### Apply a package using Settings
|
||||
|
||||
1. Insert the USB flash drive containing the .ppkg file into the Surface Hub.
|
||||
|
||||
2. From the Surface Hub, start **Settings** and enter the admin credentials when prompted.
|
||||
|
||||
3. Navigate to **Surface Hub** > **Device management**. Under **Provisioning packages**, select **Add or remove a provisioning package**.
|
||||
|
||||
4. Select **Add a package**.
|
||||
|
||||
5. Choose your provisioning package and select **Add**. You may have to re-enter the admin credentials if prompted.
|
||||
|
||||
6. You'll see a summary of the changes that the provisioning package will apply. Select **Yes, add it**.
|
||||
|
||||
|
@ -6,7 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
76
devices/surface-hub/surface-hub-administrators-guide.md
Normal file
@ -0,0 +1,76 @@
|
||||
---
|
||||
title: Microsoft Surface Hub administrator's guide
|
||||
description: This guide covers the installation and administration of devices running Surface Hub, and is intended for use by anyone responsible for these tasks, including IT administrators and developers.
|
||||
ms.assetid: e618aab7-3a94-4159-954e-d455ef7b8839
|
||||
keywords: Surface Hub, installation, administration, administrator's guide
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Microsoft Surface Hub administrator's guide
|
||||
|
||||
|
||||
This guide covers the installation and administration of devices running Surface Hub, and is intended for use by anyone responsible for these tasks, including IT administrators and developers.
|
||||
|
||||
Before you power on Microsoft Surface Hub for the first time, make sure you've [completed preparation items](prepare-your-environment-for-surface-hub.md), and that you have the information listed in the [Setup worksheet](setup-worksheet-surface-hub.md). When you do power it on, the device will walk you through a series of setup screens. If you haven't properly set up your environment, or don't have the required information, you'll have to do extra work afterward making sure the settings are correct.
|
||||
|
||||
## In this section
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Topic</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Intro to Microsoft Surface Hub](intro-to-surface-hub.md)</p></td>
|
||||
<td align="left"><p>Surface Hub is an all-in-one productivity device that is intended for brainstorming, collaboration, and presentations. In order to get the maximum benefit from Surface Hub, your organization’s infrastructure and the Surface Hub itself must be properly set up and integrated. This guide describes what needs to be done both before and during setup in order to help you optimize your use of the device.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md)</p></td>
|
||||
<td align="left"><p>The Surface Hub Readiness Guide will help make sure that your site is ready for the installation. You can download the Guide from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=718144). It includes planning information for both the 55" and 84" devices, as well as info on moving the Surface Hub from receiving to the installation location, mounting options, and a list of what's in the box.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)</p></td>
|
||||
<td align="left"><p>This section contains an overview of the steps required to prepare your environment so that you can use all of the features of Surface Hub. See [Intro to Surface Hub](intro-to-surface-hub.md) for a description of how the device and its features interact with your IT environment.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Set up Microsoft Surface Hub](set-up-your-surface-hub.md)</p></td>
|
||||
<td align="left"><p>Set up instructions for Surface Hub include a setup worksheet, and a walkthrough of the first-run program.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Manage Microsoft Surface Hub](manage-surface-hub.md)</p></td>
|
||||
<td align="left"><p>How to manage your Surface Hub after finishing the first-run program.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)</p></td>
|
||||
<td align="left"><p>Troubleshoot common problems, including setup issues, Exchange ActiveSync errors.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)</p></td>
|
||||
<td align="left"><p>PowerShell scripts to help set up and manage your Surface Hub .</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -1,57 +0,0 @@
|
||||
---
|
||||
title: What's new in Windows 10, version 1703 for Surface Hub
|
||||
description: Windows 10, version 1703 (Creators Update) brings new features to Microsoft Surface Hub.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: devices
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# What's new in Windows 10, version 1703 for Microsoft Surface Hub?
|
||||
|
||||
Windows 10, version 1703 (also called the Creators Update), introduces the following changes for Microsoft Surface Hub:
|
||||
|
||||
## New settings
|
||||
|
||||
Settings have been added to mobile device management (MDM) and configuration service providers (CSPs) to expand the Surface Hub management capabilities. [New settings include](manage-settings-with-mdm-for-surface-hub.md):
|
||||
|
||||
- InBoxApps/SkypeForBusiness/DomainName
|
||||
- InBoxApps/Connect/AutoLaunch
|
||||
- Properties/DefaultVolume
|
||||
- Properties/ScreenTimeout
|
||||
- Properties/SessionTimeout
|
||||
- Properties/SleepTimeout
|
||||
- Properties/AllowSessionResume
|
||||
- Properties/AllowAutoProxyAuth
|
||||
- Properties/DisableSigninSuggestions
|
||||
- Properties/DoNotShowMyMeetingsAndFiles
|
||||
</br>
|
||||
|
||||
## Provizioning wizard
|
||||
|
||||
An easy-to-use wizard helps you quickly create provisioning packages that you can apply to multiple Surface Hub devices, and includes bulk join to Azure Active Directory. [Learn how to create a provisioning package for Surface Hub.](provisioning-packages-for-certificates-surface-hub.md)
|
||||
|
||||

|
||||
|
||||
## Cloud recovery
|
||||
|
||||
When you reset a Surface Hub device, you now have the ability to download and install a factory build of the operating system from the cloud. [Learn more about cloud recovery.](device-reset-surface-hub.md#cloud-recovery)
|
||||
|
||||
>[!NOTE]
|
||||
>Cloud recovery doesn't work if you use proxy servers.
|
||||
|
||||

|
||||
|
||||
## End session
|
||||
|
||||
**I'm done** is now **End session**. [Learn how to use End session.](i-am-done-finishing-your-surface-hub-meeting.md)
|
||||
|
||||

|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: support
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -417,7 +417,29 @@ Possible fixes for issues with Surface Hub first-run program.
|
||||
|
||||
|
||||
|
||||
### <a href="" id="settings-skype"></a>Skype for Business
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Issue</th>
|
||||
<th align="left">Causes</th>
|
||||
<th align="left">Possible fixes</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Can't call a Skype consumer from my Surface Hub.</p></td>
|
||||
<td align="left"><p>Outgoing calls aren't supported yet.</p></td>
|
||||
<td align="left"><p>None currently.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
@ -600,9 +622,7 @@ This section lists status codes, mapping, user messages, and actions an admin ca
|
||||
|
||||
|
||||
|
||||
## Related content
|
||||
|
||||
- [Troubleshooting Miracast connection to the Surface Hub](https://blogs.msdn.microsoft.com/surfacehub/2017/01/30/troubleshooting-miracast-connection-to-the-surface-hub/)
|
||||
|
||||
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Use fully qualified doman name with Surface Hub
|
||||
description: Troubleshoot common problems, including setup issues, Exchange ActiveSync errors.
|
||||
ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
|
||||
keywords: ["Troubleshoot common problems", "setup issues", "Exchange ActiveSync errors"]
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -16,7 +16,7 @@ There are a few scenarios where you need to specify the domain name of your Skyp
|
||||
|
||||
**To configure the domain name for your Skype for Business server**</br>
|
||||
1. On Surface Hub, open **Settings**.
|
||||
2. Click **Surface Hub**, and then click **Calling & Audio**.
|
||||
2. Click **This device**, and then click **Calling**.
|
||||
3. Under **Skype for Business configuration**, click **Configure domain name**.
|
||||
4. Type the domain name for your Skype for Business server, and then click **Ok**.
|
||||
> [!TIP]
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, networking
|
||||
author: jdeckerMS
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -24,7 +24,7 @@ If a wired network connection is not available, the Surface Hub can use a wirele
|
||||
### Choose a wireless access point
|
||||
|
||||
1. On the Surface Hub, open **Settings** and enter your admin credentials.
|
||||
2. Click **Network & Internet**. Under **Wi-Fi**, choose an access point. If you want Surface Hub to automatically connect to this access point, click **Connect automatically**. Click **Connect**.
|
||||
2. Click **System**, and then click **Network & Internet**. Under **Wi-Fi**, choose an access point. If you want Surface Hub to automatically connect to this access point, click **Connect automatically**. Click **Connect**.
|
||||
|
||||

|
||||
|
||||
@ -35,7 +35,7 @@ If a wired network connection is not available, the Surface Hub can use a wirele
|
||||
### Review wireless settings
|
||||
|
||||
1. On the Surface Hub, open **Settings** and enter your admin credentials.
|
||||
2. Click **Network & Internet**, then **Wi-Fi**, and then click **Advanced options**.
|
||||
2. Click **System**, click **Network & Internet**, then **Wi-Fi**, and then click **Advanced options**.
|
||||
3. Surface Hub shows you the properties for the wireless network connection.
|
||||
|
||||

|
||||
|