mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into sh-7573357
This commit is contained in:
Trudy Hakala
@ -2,7 +2,11 @@
|
||||
title: Accessibility (Surface Hub)
|
||||
description: Accessibility settings for the Microsoft Surface Hub can be changed by using the Settings app. You'll find them under Ease of Access. Your Surface Hub has the same accessibility options as Windows 10.
|
||||
ms.assetid: 1D44723B-1162-4DF6-99A2-8A3F24443442
|
||||
keywords: ["Accessibility settings", "Settings app", "Ease of Access"]
|
||||
keywords: Accessibility settings, Settings app, Ease of Access
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surfacehub
|
||||
ms.sitesec: library
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Admin group management (Surface Hub)
|
||||
description: Every Microsoft Surface Hub can be configured individually by opening the Settings app on the device.
|
||||
ms.assetid: FA67209E-B355-4333-B903-482C4A3BDCCE
|
||||
keywords: ["admin group management", "Settings app", "configure Surface Hub"]
|
||||
keywords: admin group management, Settings app, configure Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -31,11 +35,11 @@ Note that the local admin account information is not backed by any directory ser
|
||||
|
||||
You can set a security group from your domain as local administrators on the Surface Hub after you domain join the device to AD. You will need to provide credentials that are capable of joining the domain of your choice. After you domain join successfully, you will be asked to pick an existing security group to be set as the local admins. Anyone who is a member of that security group can enter their credentials and unlock Settings.
|
||||
|
||||
**Note** Surface Hubs domain join for the single purpose of using a security group as local admins. Group policies are not applied after the device is domain joined.
|
||||
>**Note** Surface Hubs domain join for the single purpose of using a security group as local admins. Group policies are not applied after the device is domain joined.
|
||||
|
||||
|
||||
|
||||
**Note** If your Surface Hub loses trust with the domain (for example, if you remove the Surface Hub from the domain after it is domain joined), you won't be able to authenticate into the device and open up Settings. If you decide to remove the trust relationship of the Surface Hub with your domain, reset the device first.
|
||||
>**Note** If your Surface Hub loses trust with the domain (for example, if you remove the Surface Hub from the domain after it is domain joined), you won't be able to authenticate into the device and open up Settings. If you decide to remove the trust relationship of the Surface Hub with your domain, reset the device first.
|
||||
|
||||
|
||||
|
||||
@ -43,7 +47,7 @@ You can set a security group from your domain as local administrators on the Sur
|
||||
|
||||
You can set up IT pros from your Azure AD organization as local administrators on the Surface Hub after you join the device. The people that are provisioned as local admins on your device depend on what Azure AD subscription you have. You will need to provide credentials that are capable of joining the Azure AD organization of your choice. After you successfully join Azure AD, the appropriate people will be set as local admins on the device. Any user who was set up as a local admin as a result of this process can enter their credentials and unlock the Settings app.
|
||||
|
||||
**Note** If your Azure AD organization is configured with mobile device management (MDM) enrollment, Surface Hubs will be enrolled into MDM as a result of joining Azure AD. Surface Hubs that have joined Azure AD are subject to receiving MDM policies, and can be managed using the MDM solution that your organization uses.
|
||||
>**Note** If your Azure AD organization is configured with mobile device management (MDM) enrollment, Surface Hubs will be enrolled into MDM as a result of joining Azure AD. Surface Hubs that have joined Azure AD are subject to receiving MDM policies, and can be managed using the MDM solution that your organization uses.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
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"]
|
||||
keywords: PowerShell, set up Surface Hub, manage Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -38,7 +42,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.
|
||||
|
||||
|
||||
|
||||
@ -1669,7 +1673,7 @@ Set-CalendarProcessing $ strRoomUpn -AutomateProcessing AutoAccept
|
||||
|
||||
For a device account to accept external meeting requests (a meeting request from an account not in the same tenant/domain), the device account must be set to allow processing of external meeting requests. Once set, the device account will automatically accept or decline meeting requests from external accounts as well as local accounts.
|
||||
|
||||
**Note** If the **AutomateProcessing** attribute is not set to **AutoAccept**, then setting this will have no effect.
|
||||
>**Note** If the **AutomateProcessing** attribute is not set to **AutoAccept**, then setting this will have no effect.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Applying ActiveSync policies to device accounts (Surface Hub)
|
||||
description: The Microsoft Surface Hub's device account uses ActiveSync to sync mail and calendar. This allows people to join and start scheduled meetings from the Surface Hub, and allows them to email any whiteboards they have made during their meeting.
|
||||
ms.assetid: FAABBA74-3088-4275-B58E-EC1070F4D110
|
||||
keywords: ["Surface Hub", "ActiveSync policies"]
|
||||
keywords: Surface Hub, ActiveSync policies
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Change the Microsoft Surface Hub device account
|
||||
description: You can change the device account in Settings to either add an account if one was not already provisioned, or to change any properties of an account that was already provisioned.
|
||||
ms.assetid: AFC43043-3319-44BC-9310-29B1F375E672
|
||||
keywords: ["change device account", "change properties", "Surface Hub"]
|
||||
keywords: change device account, change properties, Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -1,8 +1,11 @@
|
||||
---
|
||||
title: Connect other devices and display with Surface Hub
|
||||
description: You can connect other device to your Surface Hub to display content. This topic describes guest mode and replacement PC modes that is available through a wired connection.
|
||||
Robots: noindex, nofollow
|
||||
ms.assetid: 8BB80FA3-D364-4A90-B72B-65F0F0FC1F0D
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Create a device account using UI (Surface Hub)
|
||||
description: If you prefer to use a graphical user interface, you can create a device account for your Microsoft Surface Hub with either the Office 365 UI or the Exchange Admin Center.
|
||||
ms.assetid: D11BCDC4-DABA-4B9A-9ECB-58E02CC8218C
|
||||
keywords: ["create device account", "Office 365 UI", "Exchange Admin center", "Office 365 admin center", "Skype for Business", "mobile device mailbox policy"]
|
||||
keywords: create device account, Office 365 UI, Exchange Admin center, Office 365 admin center, Skype for Business, mobile device mailbox policy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -264,7 +268,7 @@ You can use the Exchange Admin Center to create a device account:
|
||||
|
||||
### <a href="" id="create-device-acct-exch-mbx-policy"></a>Create a mobile device mailbox policy from the Exchange Admin Center
|
||||
|
||||
**Note** If you want to create and assign a policy to the account you created, and are using Exchange 2010, look up the corresponding information regarding policy creation and policy assignment when using the EMC (Exchange management console).
|
||||
>**Note** If you want to create and assign a policy to the account you created, and are using Exchange 2010, look up the corresponding information regarding policy creation and policy assignment when using the EMC (Exchange management console).
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Create and test a device account (Surface Hub)
|
||||
description: This topic introduces how to create and test the device account that Microsoft Surface Hub uses to communicate with Microsoft Exchange and Skype.
|
||||
ms.assetid: C8605B5F-2178-4C3A-B4E0-CE32C70ECF67
|
||||
keywords: ["create and test device account", "device account", "Surface Hub and Microsoft Exchange", "Surface Hub and Skype"]
|
||||
keywords: create and test device account, device account, Surface Hub and Microsoft Exchange, Surface Hub and Skype
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -19,7 +23,7 @@ A "device account" is an account that the Microsoft Surface Hub uses to:
|
||||
|
||||
People can book this account by scheduling a meeting with it. The Surface Hub will be able to join that meeting and provide various features to the meeting attendees.
|
||||
|
||||
**Important** Without a device account, none of these features will work.
|
||||
>**Important** Without a device account, none of these features will work.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Device reset (Surface Hub)
|
||||
description: You may wish to reset your Microsoft Surface Hub.
|
||||
ms.assetid: 44E82EEE-1905-464B-A758-C2A1463909FF
|
||||
keywords: ["reset Surface Hub"]
|
||||
keywords: reset Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Microsoft Exchange properties (Surface Hub)
|
||||
description: Some Microsoft Exchange properties of the device account must be set to particular values to have the best meeting experience on Microsoft Surface Hub.
|
||||
ms.assetid: 3E84393B-C425-45BF-95A6-D6502BA1BF29
|
||||
keywords: ["Microsoft Exchange properties", "device account", "Surface Hub", "Windows PowerShell cmdlet"]
|
||||
keywords: Microsoft Exchange properties, device account, Surface Hub, Windows PowerShell cmdlet
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: First-run program (Surface Hub)
|
||||
description: The term \ 0034;first run \ 0034; refers to the series of steps you'll go through the first time you power up your Microsoft Surface Hub, and means the same thing as \ 0034;out-of-box experience \ 0034; (OOBE). This section will walk you through the process.
|
||||
ms.assetid: 07C9E84C-1245-4511-B3B3-75939AD57C49
|
||||
keywords: ["first run", "Surface Hub", "out-of-box experience", "OOBE"]
|
||||
keywords: first run, Surface Hub, out-of-box experience, OOBE
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -29,7 +33,7 @@ The normal procedure goes through six steps:
|
||||
|
||||
Each of these sections also contains information about paths you might take when something is different. For example, most Surface Hubs will use a wired network connection, but some of them will be set up with wireless instead. Details are described where appropriate.
|
||||
|
||||
**Note** You should have the separate keyboard that came with your Surface Hub set up and ready before beginning. See the Surface Hub Setup Guide for details.
|
||||
>**Note** You should have the separate keyboard that came with your Surface Hub set up and ready before beginning. See the Surface Hub Setup Guide for details.
|
||||
|
||||
|
||||
|
||||
@ -38,7 +42,7 @@ 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.
|
||||
|
||||
|
||||
|
||||
@ -55,7 +59,7 @@ If the default values shown are correct, then you can click **Next** to go on. O
|
||||
|
||||
### What happens?
|
||||
|
||||
**Note** Once the settings on this page are entered, you can't come back to this screen unless you reset the device (see [Device reset](device-reset-suface-hub.md)). Make sure that the settings are properly configured before proceeding.
|
||||
>**Note** Once the settings on this page are entered, you can't come back to this screen unless you reset the device (see [Device reset](device-reset-suface-hub.md)). Make sure that the settings are properly configured before proceeding.
|
||||
|
||||
|
||||
|
||||
@ -136,7 +140,7 @@ When you click **Next**, the device will attempt to connect to the proxy server.
|
||||
|
||||
You can skip connecting to a network by selecting **Skip this step**. You'll be taken to the [Set up for you page](#set-up-for-you).
|
||||
|
||||
**Note** If you skip this, the device will not have a network connection, and nothing that requires a network connection will work on your Surface Hub, including things like email and calendar synchronization. You can connect to a wireless network later using Settings (see [Wireless network managment](wireless-network-management-for-surface-hub.md)).
|
||||
>**Note** If you skip this, the device will not have a network connection, and nothing that requires a network connection will work on your Surface Hub, including things like email and calendar synchronization. You can connect to a wireless network later using Settings (see [Wireless network managment](wireless-network-management-for-surface-hub.md)).
|
||||
|
||||
|
||||
|
||||
@ -162,7 +166,7 @@ The settings shown on the page have already been made, and can't be changed unti
|
||||
|
||||
On this page, the Surface Hub will ask for credentials for the device account that you previously configured. (See [Create and test a device account](create-and-test-a-device-account-surface-hub.md).) The Surface Hub will attempt to discover various properties of the account, and may ask for more information on another page if it does not succeed.
|
||||
|
||||
**Note** This section does not cover specific errors that can happen during first run. See [Troubleshoot Surface Hub](troubleshoot-surface-hub.md) for more information on errors.
|
||||
>**Note** This section does not cover specific errors that can happen during first run. See [Troubleshoot Surface Hub](troubleshoot-surface-hub.md) for more information on errors.
|
||||
|
||||
|
||||
|
||||
@ -299,7 +303,7 @@ On this page, you will choose from several options for how you want to set up ad
|
||||
|
||||
Because every Surface Hub can be used by any number of authenticated employees, settings are locked down so that they can't change from session to session. Only admins can configure the settings on the device, and on this page, you’ll choose which type of admins have that privilege.
|
||||
|
||||
**Note** The purpose of this page is primarily to determine who can configure the device from the device’s UI; that is, who can actually visit a device, log in, open up the Settings app, and make changes to the Settings.
|
||||
>**Note** The purpose of this page is primarily to determine who can configure the device from the device’s UI; that is, who can actually visit a device, log in, open up the Settings app, and make changes to the Settings.
|
||||
|
||||
|
||||
|
||||
@ -331,7 +335,7 @@ This is what happens when you choose an option.
|
||||
|
||||
Note that a local admin must have physical access to the Surface Hub to log in.
|
||||
|
||||
**Note** After you finish this process, you won't be able to change the device's admin option unless you reset the device.
|
||||
>**Note** After you finish this process, you won't be able to change the device's admin option unless you reset the device.
|
||||
|
||||
|
||||
|
||||
@ -389,7 +393,7 @@ Using the provided domain, account credentials from the [Use Active Directory Do
|
||||
|
||||
If the join is successful, you'll see the **Enter a security group** page. When you click the **Select** button on this page, the device will search for the specified security group on your domain. If found, the group will be verified. Click **Finish** to complete the first run process.
|
||||
|
||||
**Note** If you domain join the Surface Hub, you can't unjoin the device without resetting it.
|
||||
>**Note** If you domain join the Surface Hub, you can't unjoin the device without resetting it.
|
||||
|
||||
|
||||
|
||||
@ -414,7 +418,7 @@ This page will attempt to create a new admin account using the credentials that
|
||||
## <a href="" id="update-surface-hub"></a>Update the Surface Hub
|
||||
|
||||
|
||||
**Important** Before you do the updates, make sure you read [Save your BitLocker key](save-bitlocker-key-surface-hub.md) in order to make sure you have a backup of the key.
|
||||
>**Important** Before you do the updates, make sure you read [Save your BitLocker key](save-bitlocker-key-surface-hub.md) in order to make sure you have a backup of the key.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Hybrid deployment (Surface Hub)
|
||||
description: A hybrid deployment requires special processing in order to set up a device account for your Microsoft Surface Hub.
|
||||
ms.assetid: 7BFBB7BE-F587-422E-9CE4-C9DDF829E4F1
|
||||
keywords: ["hybrid deployment", "device account for Surface Hub", "Exchange hosted on-prem", "Exchange hosted online"]
|
||||
keywords: hybrid deployment, device account for Surface Hub, Exchange hosted on-prem, Exchange hosted online
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -21,7 +25,7 @@ Use this procedure if you use Exchange on-prem.
|
||||
|
||||
- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
|
||||
|
||||
**Important**<br>Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
>**Important** Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
|
||||
|
||||
|
||||
@ -147,7 +151,7 @@ Use this procedure if you use Exchange on-prem.
|
||||
|
||||
- Click **Save**.
|
||||
|
||||
**Note**<br>You can also use the Windows Azure Active Directory Module for Windows Powershell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
>**Note** You can also use the Windows Azure Active Directory Module for Windows Powershell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
|
||||
For validation, you should be able to use any Skype for Business client (PC, Android, etc) to log in to this account.
|
||||
|
||||
@ -223,7 +227,7 @@ Use this procedure if you use Exchange online.
|
||||
|
||||
- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
|
||||
|
||||
**Important**<br>Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
>**Important** Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
|
||||
|
||||
|
||||
@ -306,6 +310,6 @@ Use this procedure if you use Exchange online.
|
||||
|
||||
- Click **Save**.
|
||||
|
||||
**Note**<br>You can also use the Windows Azure Active Directory Module for Windows PowerShell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
>**Note** You can also use the Windows Azure Active Directory Module for Windows PowerShell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
|
||||
For validation, you should be able to use any Skype for Business client (PC, Android, etc) to log in to this account.
|
||||
@ -2,6 +2,10 @@
|
||||
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
|
||||
---
|
||||
|
||||
|
||||
BIN
devices/surface-hub/images/room-control-wiring-diagram.png
Normal file
BIN
devices/surface-hub/images/room-control-wiring-diagram.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 10 KiB |
@ -2,6 +2,10 @@
|
||||
title: Microsoft Surface Hub
|
||||
description: Documents related to the Microsoft Surface Hub.
|
||||
ms.assetid: 69C99E91-1441-4318-BCAF-FE8207420555
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Install apps on your Microsoft Surface Hub
|
||||
description: Admins can install apps can from either the Windows Store or the Windows Store for Business.
|
||||
ms.assetid: 3885CB45-D496-4424-8533-C9E3D0EDFD94
|
||||
keywords: ["install apps", "Windows Store", "Windows Store for Business"]
|
||||
keywords: [install apps, Windows Store, Windows Store for Business
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, store
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
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"]
|
||||
keywords: Surface Hub, productivity, collaboration, presentations, setup
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
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
|
||||
keywords: ["local admin account", "Surface Hub", "change local admin options"]
|
||||
keywords: local admin account, Surface Hub, change local admin options
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -83,7 +87,7 @@ To create a local admin, choose to use a local admin during first run. This will
|
||||
|
||||
After you domain join the device, you can set up a security group from your domain as local administrators on the Surface Hub. You will need to provide credentials that are capable of joining the domain of your choice. After you domain join successfully, you will be asked to pick an existing security group to be set as the local admins. When the Setting app is opened, any user who is a member of that security group can enter their credentials and unlock Settings.
|
||||
|
||||
**Note** Surface Hubs domain join for the sole purpose of using a security group as local admins. Group policies are not applied after the device is domain joined.
|
||||
>**Note** Surface Hubs domain join for the sole purpose of using a security group as local admins. Group policies are not applied after the device is domain joined.
|
||||
|
||||
|
||||
|
||||
@ -96,7 +100,7 @@ Otherwise, if you don’t want to use the device account to join Azure AD, you c
|
||||
- The org account of an admin who will manage the device, or
|
||||
- A separate account that is part of your organization and used only for joining Surface Hubs.
|
||||
|
||||
**Note** If your Azure AD organization is also configured with MDM enrollment, Surface Hubs will also be enrolled into MDM as a result of joining Azure AD. Surface Hubs that have joined Azure AD are subject to receiving MDM policies, and can be widely managed using an MDM solution, which opts these devices into remote management. You may want to choose an account to join Azure AD that benefits how you manage devices—you find more info about this in the [Enroll a Surface Hub into MDM](manage-settings-with-mdm-for-surface-hub.md#enroll-into-mdm) section.
|
||||
>**Note** If your Azure AD organization is also configured with MDM enrollment, Surface Hubs will also be enrolled into MDM as a result of joining Azure AD. Surface Hubs that have joined Azure AD are subject to receiving MDM policies, and can be widely managed using an MDM solution, which opts these devices into remote management. You may want to choose an account to join Azure AD that benefits how you manage devices—you find more info about this in the [Enroll a Surface Hub into MDM](manage-settings-with-mdm-for-surface-hub.md#enroll-into-mdm) section.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Manage settings with an MDM provider (Surface Hub)
|
||||
description: Microsoft Surface Hub provides an enterprise management solution to help IT administrators manage policies and business applications on these devices using a mobile device management (MDM) solution.
|
||||
ms.assetid: 18EB8464-6E22-479D-B0C3-21C4ADD168FE
|
||||
keywords: ["mobile device managemen", "MDM", "manage policies"]
|
||||
keywords: mobile device management, MDM, manage policies
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, mobility
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Manage Microsoft Surface Hub
|
||||
description: How to manage your Surface Hub after finishing the first-run program.
|
||||
ms.assetid: FDB6182C-1211-4A92-A930-6C106BCD5DC1
|
||||
keywords: ["manage Surface Hub"]
|
||||
keywords: manage Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -25,7 +29,7 @@ For remotely-managed devices, the device must be enrolled into an MDM solution,
|
||||
|
||||
Be aware that the two management methods are not mutually exclusive—every device will have the capability to be locally managed, and devices can be remotely managed if you choose.
|
||||
|
||||
**Note** If a device is remotely managed, then any changes to local settings that are also remotely managed will only persist until the next time your Surface Hub syncs with your MDM solution. Once a sync occurs, the settings and policies defined on your MDM solution will be pushed to the device, overwriting the local changes.
|
||||
>**Note** If a device is remotely managed, then any changes to local settings that are also remotely managed will only persist until the next time your Surface Hub syncs with your MDM solution. Once a sync occurs, the settings and policies defined on your MDM solution will be pushed to the device, overwriting the local changes.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Windows updates (Surface Hub)
|
||||
description: You can manage Windows updates on your Microsoft Surface Hub by setting the maintenance window, deferring updates, or using Windows Server Update Services (WSUS).
|
||||
ms.assetid: A737BD50-2D36-4DE5-A604-55053D549045
|
||||
keywords: ["manage Windows updates", "Surface Hub", "Windows Server Update Services", "WSUS"]
|
||||
keywords: manage Windows updates, Surface Hub, Windows Server Update Services, WSUS
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -20,7 +24,7 @@ A default maintenance window is set for all new Surface Hubs:
|
||||
|
||||
Most Windows updates are downloaded and installed automatically by Surface Hub. You can change the maintenance window to limit when the device can be automatically rebooted after a Windows update installation. For those updates that require a reboot of the device, the update installation will be postponed until the maintenance window begins. If a meeting is scheduled to start during the maintenance window, or if the Surface Hub sensors detect that the device is being used, the pending installation will be postponed to the next maintenance window.
|
||||
|
||||
**Note** : If an update installation has been pending for 28 days, on the 28th day the update will be forcibly installed. The device will ignore meetings or sensor status and reboot during the maintenance window.
|
||||
>**Note**: If an update installation has been pending for 28 days, on the 28th day the update will be forcibly installed. The device will ignore meetings or sensor status and reboot during the maintenance window.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Monitor your Microsoft Surface Hub
|
||||
description: Monitoring for Microsoft Surface Hub devices is enabled through Microsoft Operations Management Suite (OMS).
|
||||
ms.assetid: 1D2ED317-DFD9-423D-B525-B16C2B9D6942
|
||||
keywords: ["monitor Surface Hub", "Microsoft Operations Management Suite", "OMS"]
|
||||
keywords: monitor Surface Hub, Microsoft Operations Management Suite, OMS
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: On-premises deployment (Surface Hub)
|
||||
description: This topic explains how you add a device account for your Microsoft Surface Hub when you have a single-forest, on-premises deployment.
|
||||
ms.assetid: 80E12195-A65B-42D1-8B84-ECC3FCBAAFC6
|
||||
keywords: ["single forest deployment", "on prem deployment", "device account", "Surface Hub"]
|
||||
keywords: single forest deployment, on prem deployment, device account, Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Online deployment with Office 365 (Surface Hub)
|
||||
description: This topic has instructions for adding a device account for your Microsoft Surface Hub when you have a pure, online deployment.
|
||||
ms.assetid: D325CA68-A03F-43DF-8520-EACF7C3EDEC1
|
||||
keywords: ["device account for Surface Hub", "online deployment"]
|
||||
keywords: device account for Surface Hub, online deployment
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -134,8 +138,7 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
|
||||
- In the **Assign licenses** section, you need to select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and what you've decided in terms of needing Enterprise Voice. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Surface Hub.
|
||||
- Click **Save** and you're done.
|
||||
|
||||
**Note**<br>
|
||||
It's also possible to use the Windows Azure Active Directory Module for Windows PowerShell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
>**Note**: It's also possible to use the Windows Azure Active Directory Module for Windows PowerShell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
|
||||
For validation, you should be able to use any Skype for Business client (PC, Android, etc) to log in to this account.
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Password management (Surface Hub)
|
||||
description: Every Microsoft Surface Hub device account requires a password to authenticate and enable features on the device.
|
||||
ms.assetid: 0FBFB546-05F0-430E-905E-87111046E4B8
|
||||
keywords: ["password", "password management", "password rotation", "device account"]
|
||||
keywords: password, password management, password rotation, device account
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Physically install Microsoft Surface Hub
|
||||
description: The Microsoft Surface Hub Readiness Guide will help make sure that your site is ready for the installation.
|
||||
ms.assetid: C764DBFB-429B-4B29-B4E8-D7F0073BC554
|
||||
keywords: ["Surface Hub", "readiness guide", "installation location", "mounting options"]
|
||||
keywords: Surface Hub, readiness guide, installation location, mounting options
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, readiness
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Prepare your environment for Microsoft Surface Hub
|
||||
description: This section contains an overview of the steps required to prepare your environment so that you can use all of the features of Microsoft Surface Hub.
|
||||
ms.assetid: 336A206C-5893-413E-A270-61BFF3DF7DA9
|
||||
keywords: ["prepare environment", "features of Surface Hub", "create and test device account", "check network availability"]
|
||||
keywords: prepare environment, features of Surface Hub, create and test device account, check network availability
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
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"]
|
||||
keywords: add certificate, provisioning package
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -34,7 +38,7 @@ Currently, you can use provisioning packages to install certificates and to inst
|
||||
|
||||
You may use provisioning packages to install certificates that will allow the device to authenticate to Microsoft Exchange or Skype for Business, or to sideload apps that don't come from the Windows Store (for example, your own in-house apps).
|
||||
|
||||
**Note** Provisioning 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, you must use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details.
|
||||
>**Note** Provisioning 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, you must use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details.
|
||||
|
||||
|
||||
|
||||
@ -54,7 +58,7 @@ In order to create and deploy provisioning packages, all of the following are re
|
||||
### <a href="" id="installing-wicd-prov-pkg"></a>Install the Windows Imaging and Configuration Designer
|
||||
|
||||
1. The Windows Imaging and Configuration Designer (ICD) is installed as part of the Windows 10 ADK. The installer for the ADK can be downloaded from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkId=718147).
|
||||
**Note** The ADK must be installed on a separate PC, not on the Surface Hub.
|
||||
>**Note** The ADK must be installed on a separate PC, not on the Surface Hub.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Save your BitLocker key (Surface Hub)
|
||||
description: Every Microsoft 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.
|
||||
ms.assetid: E11E4AB6-B13E-4ACA-BCE1-4EDC9987E4F2
|
||||
keywords: ["Surface Hub", "BitLocker", "Bitlocker recovery keys"]
|
||||
keywords: Surface Hub, BitLocker, Bitlocker recovery keys
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Set up Microsoft Surface Hub
|
||||
description: Set up instructions for Surface Hub include a setup worksheet, and a walkthrough of the first-run program.
|
||||
ms.assetid: 4D1722BC-704D-4471-BBBE-D0500B006221
|
||||
keywords: ["set up instructions", "Surface Hub", "setup worksheet", "first-run program"]
|
||||
keywords: set up instructions, Surface Hub, setup worksheet, first-run program
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Setup worksheet (Surface Hub)
|
||||
description: When you've finished pre-setup and are ready to start first-time setup for your Microsoft Surface Hub, make sure you have all the information listed in this section.
|
||||
ms.assetid: AC6F925B-BADE-48F5-8D53-8B6FFF6EE3EB
|
||||
keywords: ["Setup worksheet", "pre-setup", "first-time setup"]
|
||||
keywords: Setup worksheet, pre-setup, first-time setup
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
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"]
|
||||
keywords: Surface Hub, installation, administration, administrator's guide
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Troubleshoot Microsoft 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"]
|
||||
keywords: Troubleshoot common problems, setup issues, Exchange ActiveSync errors
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: support
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Using a room control system (Surface Hub)
|
||||
description: Room control systems can be used with your Microsoft Surface Hub.
|
||||
ms.assetid: DC365002-6B35-45C5-A2B8-3E1EB0CB8B50
|
||||
keywords: ["room control system", "Surface Hub"]
|
||||
keywords: room control system, Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -13,14 +17,9 @@ Room control systems can be used with your Microsoft Surface Hub.
|
||||
|
||||
Using a room control system with your Surface Hub involves connecting room control hardware to the Surface Hub, usually through the RJ11 serial port on the bottom of the Surface Hub.
|
||||
|
||||
## Debugging
|
||||
## Terminal settings
|
||||
|
||||
|
||||
You can use the info in this section for debugging scenarios. You shouldn't need it for a typical installation.
|
||||
|
||||
### Terminal settings
|
||||
|
||||
To connect to a room control system control panel, you don't need to connect to the Surface Hub, or to configure any terminal settings. For debugging purposes, if you want to connect a PC or laptop to your Surface Hub and send commands from the Surface Hub, you can use a terminal emulator program like Tera Term or PuTTY. These are the terminal settings you'll need:
|
||||
To connect to a room control system control panel, you don't need to configure any terminal settings on the Surface Hub. If you want to connect a PC or laptop to your Surface Hub and send serial commands from the Surface Hub, you can use a terminal emulator program like Tera Term or PuTTY.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -54,20 +53,24 @@ To connect to a room control system control panel, you don't need to connect to
|
||||
<td align="left"><p>Flow control</p></td>
|
||||
<td align="left"><p>none</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Line feed</p></td>
|
||||
<td align="left"><p>every carriage return</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Wiring diagram
|
||||
## Wiring diagram
|
||||
|
||||
You can use a standard RJ-11 (6P6C) connector to connect the Surface Hub serial port to a room control system. This is the recommended method.
|
||||
You can use a standard RJ-11 (6P6C) connector to connect the Surface Hub serial port to a room control system. This is the recommended method. You can also use an RJ-11 4-conductor cable, but we do not recommend this method.
|
||||
|
||||
You can also use an RJ-11 4-conductor cable, but we do not recommend this method. You'll need to convert pin numbers to make sure it's wired correctly. The following diagram shows how to convert the pin numbers.
|
||||
This diagram shows the correct pinout used for an RJ-11 (6P6C) to DB9 cable.
|
||||
|
||||
|
||||
|
||||
|
||||
### Command sets
|
||||
## Command sets
|
||||
|
||||
Room control systems use common meeting-room scenarios for commands. Commands originate from the room control system, and are communicated over a serial connection to a Surface Hub. Commands are ASCII based, and the Surface Hub will acknowledge when state changes occur.
|
||||
|
||||
@ -106,7 +109,7 @@ The following command modifiers are available. Commands terminate with a new lin
|
||||
|
||||
|
||||
|
||||
### Power
|
||||
## Power
|
||||
|
||||
Surface Hub can be in one of these power states.
|
||||
|
||||
@ -157,9 +160,72 @@ Surface Hub can be in one of these power states.
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
In Replacement PC mode, the power states are only Ready and Off and only change the display. The management port can't be used to power on the replacement PC.
|
||||
|
||||
### Brightness
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">State</th>
|
||||
<th align="left">Energy Star state</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>0</p></td>
|
||||
<td align="left"><p>S5</p></td>
|
||||
<td align="left"><p>Off</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>5</p></td>
|
||||
<td align="left"><p>50</p></td>
|
||||
<td align="left"><p>Ready</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
For a control device, anything other than 5 / Ready should be considered off. Each PowerOn command results in two state changes and reponses.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Command</th>
|
||||
<th align="left">State change</th>
|
||||
<th align="left">Response</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>PowerOn</p></td>
|
||||
<td align="left"><p>Device turns on (display + PC).</p><p>PC service notifies SMC that the PC is ready.</p></td>
|
||||
<td align="left"><p>Power=0</p><p>Power=5</p></td>
|
||||
</tr>
|
||||
|
||||
<tr class="even">
|
||||
<td align="left"><p>PowerOff</p></td>
|
||||
<td align="left"><p>Device transitions to ambient state (PC on, display dim).</p></td>
|
||||
<td align="left"><p>Power=0</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Power?</p></td>
|
||||
<td align="left"><p>SMC reports the last-known power state.</p></td>
|
||||
<td align="left"><p>Power=<#></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
## Brightness
|
||||
|
||||
The current brightness level is a range from 0 to 100.
|
||||
|
||||
@ -191,18 +257,10 @@ Changes to brightness levels can be sent by a room control system, or other syst
|
||||
<p>PC service notifies SMC of new brightness level.</p></td>
|
||||
<td align="left"><p>Brightness = 50</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Brightness?</p></td>
|
||||
<td align="left"><p>SMC sends a message over the control channel to request brightness.</p>
|
||||
<p>PC service notifies SMC of new brightness level.</p></td>
|
||||
<td align="left"><p>Brightness = 50</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Volume
|
||||
## Volume
|
||||
|
||||
The current volume level is a range from 0 to 100.
|
||||
|
||||
@ -234,47 +292,14 @@ Changes to volume levels can be sent by a room control system, or other system.
|
||||
<p>PC service notifies SMC of new volume level.</p></td>
|
||||
<td align="left"><p>Volume = 50</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Volume?</p></td>
|
||||
<td align="left"><p>SMC sends a message over the control channel to request volume.</p>
|
||||
<p>PC service notifies SMC of new volume level.</p></td>
|
||||
<td align="left"><p>Volume = 50</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Mute for audio and microphone
|
||||
## Mute for audio
|
||||
|
||||
Audio and microphone can be muted.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">State</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>0</p></td>
|
||||
<td align="left"><p>Source is not muted.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>1</p></td>
|
||||
<td align="left"><p>Source is muted.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
Changes to microphone or audio can be sent by a room control system, or other system.
|
||||
Audio can be muted.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -294,32 +319,14 @@ Changes to microphone or audio can be sent by a room control system, or other sy
|
||||
<td align="left"><p>AudioMute+</p></td>
|
||||
<td align="left"><p>SMC sends the audio mute command.</p>
|
||||
<p>PC service notifies SMC that audio is muted.</p></td>
|
||||
<td align="left"><p>AudioMute=<#></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MicMute+</p></td>
|
||||
<td align="left"><p>SMC sends the microphone mute command.</p>
|
||||
<p>PC service notifies SMC that microphone is muted.</p></td>
|
||||
<td align="left"><p>MicMute=<#></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>AudioMute?</p></td>
|
||||
<td align="left"><p>SMC queries PC service for the current audio state.</p>
|
||||
<p>PC service notifies SMC that audio is muted.</p></td>
|
||||
<td align="left"><p>AudioMute=<#></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>MicMute?</p></td>
|
||||
<td align="left"><p>SMC queries PC service for the current microphone state.</p>
|
||||
<p>PC service notifies SMC that the microphone is muted.</p></td>
|
||||
<td align="left"><p>MicMute=<#></p></td>
|
||||
<td align="left"><p>none</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Video source
|
||||
## Video source
|
||||
|
||||
Several display sources can be used.
|
||||
|
||||
@ -351,10 +358,6 @@ Several display sources can be used.
|
||||
<td align="left"><p>3</p></td>
|
||||
<td align="left"><p>VGA</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>4</p></td>
|
||||
<td align="left"><p>Wireless</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -377,7 +380,7 @@ Changes to display source can be sent by a room control system, or other system.
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Source=<#></p></td>
|
||||
<td align="left"><p>Source=#</p></td>
|
||||
<td align="left"><p>SMC changes to the desired source.</p>
|
||||
<p>PC service notifies SMC that the display source has switched.</p></td>
|
||||
<td align="left"><p>Source=<#></p></td>
|
||||
@ -389,7 +392,7 @@ Changes to display source can be sent by a room control system, or other system.
|
||||
<td align="left"><p>Source=<#></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Source+</p></td>
|
||||
<td align="left"><p>Source-</p></td>
|
||||
<td align="left"><p>SMC cycles to the previous active input source.</p>
|
||||
<p>PC service notifies SMC of the current input source.</p></td>
|
||||
<td align="left"><p>Source=<#></p></td>
|
||||
@ -403,101 +406,7 @@ Changes to display source can be sent by a room control system, or other system.
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Starting apps
|
||||
|
||||
Surface Hub keyboard supports starting apps with special keys. Room control systems can invoke those keys through the management port. There is no expected response for these commands.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">State</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>0</p></td>
|
||||
<td align="left"><p>Start large-screen experience (LSX)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>1</p></td>
|
||||
<td align="left"><p>Start LSX custom app 1</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>2</p></td>
|
||||
<td align="left"><p>Start LSX custom app 2</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>3</p></td>
|
||||
<td align="left"><p>Start LSX custom app 3</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
Changes to display source can be sent by a room control system, or other system.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Command</th>
|
||||
<th align="left">State change</th>
|
||||
<th align="left">Response</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>AppKey=<#></p></td>
|
||||
<td align="left"><p>Send a command to</p>
|
||||
<p>PC service notifies SMC that the display source has switched.</p></td>
|
||||
<td align="left"><p>Source=<#></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### I'm done
|
||||
|
||||
People will be able to start the I'm done feature on a Surface Hub from a room control system. I'm done removes any work that was displayed on the Surface Hub before ending the meeting. No information or files are saved on Surface Hub.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Command</th>
|
||||
<th align="left">State change</th>
|
||||
<th align="left">Response</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>I'm done</p></td>
|
||||
<td align="left"><p>Start I'm done activity on Surface Hub.</p></td>
|
||||
<td align="left"><p>none</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Errors
|
||||
## Errors
|
||||
|
||||
Errors are returned following the format in this table.
|
||||
|
||||
|
||||
@ -2,7 +2,11 @@
|
||||
title: Wireless network management (Surface Hub)
|
||||
description: Microsoft Surface Hub offers two options for network connectivity to your corporate network and Internet wireless, and wired. While both provide network access, we recommend you use a wired connection.
|
||||
ms.assetid: D2CFB90B-FBAA-4532-B658-9AA33CAEA31D
|
||||
keywords: ["network connectivity", "wired connection"]
|
||||
keywords: network connectivity, wired connection
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, networking
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
@ -11,7 +15,7 @@ author: TrudyHa
|
||||
|
||||
Microsoft Surface Hub offers two options for network connectivity to your corporate network and Internet: wireless, and wired. While both provide network access, we recommend you use a wired connection.
|
||||
|
||||
## Modifying, adding or reviewing a network connection
|
||||
## Modifying, adding, or reviewing a network connection
|
||||
|
||||
|
||||
If a wired network connection is not available, the Surface Hub can use a wireless network for internet access. A properly connected and configured Wi-Fi access point must be available and within range of the Surface Hub.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
# [Surface](index.md)
|
||||
## [Advanced UEFI security features for Surface](advanced-uefi-security-features-for-surface.md)
|
||||
## [Advanced UEFI security features for Surface Pro 3](advanced-uefi-security-features-for-surface-pro-3.md)
|
||||
## [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)
|
||||
## [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)
|
||||
## [Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices](enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md)
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Advanced UEFI security features for Surface (Surface)
|
||||
title: Advanced UEFI security features for Surface Pro 3 (Surface)
|
||||
description: This article describes how to install and configure the v3.11.760.0 UEFI update to enable additional security options for Surface Pro 3 devices.
|
||||
ms.assetid: 90F790C0-E5FC-4482-AD71-60589E3C9C93
|
||||
keywords: security, features, configure, hardware, device, custom, script, update
|
||||
@ -10,7 +10,7 @@ ms.sitesec: library
|
||||
author: miladCA
|
||||
---
|
||||
|
||||
# Advanced UEFI security features for Surface
|
||||
# Advanced UEFI security features for Surface Pro 3
|
||||
|
||||
|
||||
This article describes how to install and configure the v3.11.760.0 UEFI update to enable additional security options for Surface Pro 3 devices.
|
||||
@ -20,7 +20,9 @@ To address more granular control over the security of Surface devices, the v3.11
|
||||
## Manually install the UEFI update
|
||||
|
||||
|
||||
Before you can configure the advanced security features of your Surface device, you must first install the v3.11.760.0 UEFI update. This update is installed automatically if you receive your updates from Windows Update. For more information about how to configure Windows to update automatically using Windows Update, see [How to configure and use Automatic Updates in Windows]( http://go.microsoft.com/fwlink/p/?LinkID=618030). Otherwise, you can download the UEFI update from the Microsoft Download Center; see [SurfacePro3\_ 150326.msi (105 MB)](http://go.microsoft.com/fwlink/p/?LinkID=618033) or [SurfacePro3\_ 150326.zip (156 MB)](http://go.microsoft.com/fwlink/p/?LinkID=618035).
|
||||
Before you can configure the advanced security features of your Surface device, you must first install the v3.11.760.0 UEFI update. This update is installed automatically if you receive your updates from Windows Update. For more information about how to configure Windows to update automatically by using Windows Update, see [How to configure and use Automatic Updates in Windows]( http://go.microsoft.com/fwlink/p/?LinkID=618030).
|
||||
|
||||
To update the UEFI on Surface Pro 3, you can download and install the Surface UEFI updates as part of the Surface Pro 3 Firmware and Driver Pack. These firmware and driver packs are available from the [Surface Pro 3 page](https://www.microsoft.com/en-us/download/details.aspx?id=38826) on the Microsoft Download Center. You can find out more about the firmware and driver packs at [Download the latest firmware and drivers for Surface devices](https://technet.microsoft.com/en-us/itpro/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices). The firmware and driver packs are available as both self-contained Windows Installer (.msi) and archive (.zip) formats. You can find out more about these two formats and how you can use them to update your drivers at [Manage Surface driver and firmware updates](https://technet.microsoft.com/en-us/itpro/surface/manage-surface-pro-3-firmware-updates).
|
||||
|
||||
## Manually configure additional security settings
|
||||
|
||||
@ -35,7 +35,7 @@ For more information on planning for, deploying, and managing Surface devices in
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td><p>[Advanced UEFI security features for Surface](advanced-uefi-security-features-for-surface.md)</p></td>
|
||||
<td><p>[Advanced UEFI security features for Surface Pro 3](advanced-uefi-security-features-for-surface-pro-3.md)</p></td>
|
||||
<td><p>Find out how to install and configure the v3.11.760.0 UEFI update to enable additional security options for Surface Pro 3 devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
|
||||
@ -34,7 +34,7 @@ For details about Group Policy for client configuration of WSUS or Windows Updat
|
||||
|
||||
**Windows Installer Package**
|
||||
|
||||
The firmware and driver downloads for Surface devices now include MSI installation files for firmware and driver updates. These MSI packages can be deployed with utilities that support application deployment, including the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager. This solution allows for centralized deployment and for administrators to test and review firmware updates before they are deployed. For more information about the MSI package delivery method for firmware and driver updates, including details on what drivers are updated by the package and why certain drivers and firmware are not updated by the MSI package, see the [Surface Pro 3 MSI Now Available](http://go.microsoft.com/fwlink/p/?LinkId=618173) blog post.
|
||||
The firmware and driver downloads for Surface devices now include Windows Installer files for firmware and driver updates. These Windows Installer packages can be deployed with utilities that support application deployment, including the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager. This solution allows for centralized deployment and for administrators to test and review firmware updates before they are deployed. For more information about the Windows Installer package delivery method for firmware and driver updates, including details on what drivers are updated by the package and why certain drivers and firmware are not updated by the Windows Installer package, see the [Surface Pro 3 MSI Now Available](http://go.microsoft.com/fwlink/p/?LinkId=618173) blog post.
|
||||
|
||||
For instructions on how to deploy with System Center Configuration Manager, refer to [How to Deploy Applications in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=618175). For deployment of applications with MDT, see [Step 4: Add an application in the Deploy a Windows 8.1 Image Using MDT 2013](http://go.microsoft.com/fwlink/p/?LinkId=618176). Note that you can deploy applications separately from an operating system deployment through MDT by using a Post OS Installation task sequence.
|
||||
|
||||
|
||||
@ -125,7 +125,9 @@ If a Surface Type Cover is not detected, the test prompts you to connect the Typ
|
||||
|
||||
>**Note:** This test is only applicable to Surface Book and requires that the Surface Book be docked to the keyboard.
|
||||
|
||||
This test is essentially the same as the Type Cover test, except the integrated keyboard in the Surface Book base is tested rather than the Type Cover. Move the cursor and use the Windows key to bring up the Start menu to confirm that the touchpad and keyboard are operating successfully. This test will display the status of cursor movement and keyboard input for you to verify. Press **ESC** to complete the test.
|
||||
This test is essentially the same as the Type Cover test, except the integrated keyboard in the Surface Book base is tested rather than the Type Cover. During the first stage of this test a diagram of the keyboard is displayed. When you press a key, the corresponding key will be marked on the diagram. The test will proceed when every key in the diagram is marked. In the second stage of this test, you are prompted to make several gestures on the keypad. As you perform each gesture (for example, a three finger tap), the gesture will be marked on the screen. When you have performed all gestures, the test will automatically complete.
|
||||
|
||||
>**Note:** The F-keys on the diagram require that you press the Function (FN) key simultaneously to activate them. By default, these keys perform other actions. For the Home and End keys, you must press the same keys as F8 and F9, but without the Function (FN) key pressed.
|
||||
|
||||
#### Canvas mode battery test
|
||||
|
||||
|
||||
Reference in New Issue
Block a user