diff --git a/devices/surface-hub/change-history-surface-hub.md b/devices/surface-hub/change-history-surface-hub.md index a753773f2f..b8837a0545 100644 --- a/devices/surface-hub/change-history-surface-hub.md +++ b/devices/surface-hub/change-history-surface-hub.md @@ -19,6 +19,9 @@ This topic lists new and updated topics in the [Surface Hub Admin Guide]( surfac | New or changed topic | Description | | --- | --- | | [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) | New | +| [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md) | Added information for Video Out and a table to help select a display method. | +| [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Added instructions for creating accounts for Surface Hub in a Skype for Business hybrid environment. | + ## RELEASE: Windows Anniversary Update for Surface Hub (Windows 10, version 1607) The topics in this library have been updated for Windows 10, version 1607 (also known as Windows Anniversary Update for Surface Hub). These topics had significant updates for this release: diff --git a/devices/surface-hub/connect-and-display-with-surface-hub.md b/devices/surface-hub/connect-and-display-with-surface-hub.md index 3d1a589760..28001227cc 100644 --- a/devices/surface-hub/connect-and-display-with-surface-hub.md +++ b/devices/surface-hub/connect-and-display-with-surface-hub.md @@ -1,28 +1,42 @@ --- 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. +description: You can connect other device to your Surface Hub to display content. ms.assetid: 8BB80FA3-D364-4A90-B72B-65F0F0FC1F0D ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- # Connect other devices and display with Surface Hub -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. +You can connect other devices to your Microsoft Surface Hub to display content. This topic describes the Guest Mode, Replacement PC Mode, and Video Out functionality available through wired connections. -## Guest mode +## Which method should I choose? + +When connecting external devices and displays to a Surface Hub, there are several available options. The method you use will depend upon your scenario and needs. + +| When you want to: | Use this method: | +| --- | --- | +| Mirror the Surface Hub's display on another device. | [Video Out](#video-out) | +| Present another device's display on the Surface Hub screen and interact with both the device's content and the built-in Surface Hub experience. | [Guest Mode](#guest-mode) | +| Power the Surface Hub from an external Windows 10 PC, turning off the embedded computer of the Surface Hub. Cameras, microphones, speakers, and other peripherals, are sent to the external PC, in addition to pen and touch. | [Replacement PC Mode](#replacement-pc-mode) | -Guest mode uses a wired connection, so people can display content from their devices to the Surface Hub. If the source device is Windows based, that device can also provide Touchback and Inkback. Surface Hub's internal PC takes video and audio from the connected device and displays them on the Surface Hub. If Surface Hub encounters an HDCP signal, the source will be re-routed through an alternate path, allowing the source to be displayed full-screen without violating HDCP requirements. +## Guest Mode + + +Guest Mode uses a wired connection, so people can display content from their devices to the Surface Hub. If the source device is Windows-based, that device can also provide Touchback and Inkback. Surface Hub's internal PC takes video and audio from the connected device and presents them on the Surface Hub. If Surface Hub encounters a High-Bandwidth Digital Content Protection (HDCP) signal, the source will be re-routed through an alternate path, allowing the source to be displayed full-screen without violating HDCP requirements. + +>[!NOTE] +>When an HDCP source is connected, use the side keypad to change source inputs. ### Ports -Use these ports on the Surface Hub for the guest mode. +Use these ports on the Surface Hub for Guest Mode. @@ -93,7 +107,7 @@ Use these ports on the Surface Hub for the guest mode. ### Port locations -These are the port connections used for guest mode on the 55" and 84" Surface Hubs. +These are the port connections used for Guest Mode on the 55" and 84" Surface Hubs. ![image showing guest ports on 55" surface hub. ](images/sh-55-guest-ports.png) @@ -105,7 +119,7 @@ Wired port connections on 84" Surface Hub ### Port enumeration -When a Surface hub is connected to guest computer with the wired connect USB port, a number of USB devices are discovered and configured. These peripheral devices are created for touchback and inkback. The peripheral devices can viewed in Device Manager. Device Manager will show duplicate names for some devices. +When a Surface hub is connected to a guest computer with the wired connect USB port, a number of USB devices are discovered and configured. These peripheral devices are created for Touchback and Inkback. The peripheral devices can be viewed in Device Manager. Device Manager will show duplicate names for some devices. **Human interface devices** @@ -137,9 +151,9 @@ When a Surface hub is connected to guest computer with the wired connect USB por - USB composite device -### Guest mode connectivity +### Guest Mode connectivity -Your choice of video cable will be determined by what is available from your source input. The Surface Hub has three choices of video input, DisplayPort, HDMI and VGA. Please refer to the below chart for available resolutions. +Your choice of video cable will be determined by what is available from your source input. The Surface Hub has three choices of video input: DisplayPort, HDMI, and VGA. See the following chart for available resolutions.
@@ -206,9 +220,9 @@ Your choice of video cable will be determined by what is available from your sou   -Source audio is provided by DisplayPort and HDMI cables. If you must use VGA, Surface Hub has an audio input port that uses a 3.5 mm plug. Surface Hub also uses a USB cable that provides touch and inkback from the Surface Hub to compatible Windows 10 devices. The USB cable can be used with any video input that is already connected with a cable. +Source audio is provided by DisplayPort and HDMI cables. If you must use VGA, Surface Hub has an audio input port that uses a 3.5 mm plug. Surface Hub also uses a USB cable that provides Touchback and Inkback from the Surface Hub to compatible Windows 10 devices. The USB cable can be used with any video input that is already connected with a cable. -Someone using guest mode to connect a PC would use one of these options: +Someone using Guest Mode to connect a PC would use one of these options: **DisplayPort** -- DisplayPort cable and USB 2.0 cable @@ -216,16 +230,16 @@ Someone using guest mode to connect a PC would use one of these options: **VGA** -- VGA cable, 3.5 mm audio cable, and USB 2.0 cable -If the computer you are using for guest mode is not compatible with Touch and Inkback, then you won't need the USB cable. +If the computer you are using for Guest Mode is not compatible with Touchback and Inkback, then you won't need the USB cable. -## Replacement PC mode +## Replacement PC Mode -In replacement PC mode, the embedded computer of the Surface Hub is turned off and an external PC is connected to the Surface Hub. Connections to replacement PC ports give access to key peripherals on the Surface Hub, including the screen, pen, and touch features. This does mean that your Surface Hub won’t have the benefit of the Windows Team experience, but you will have the flexibility offered by providing and managing your own Windows computer. +In Replacement PC Mode, the embedded computer of the Surface Hub is turned off and an external PC is connected to the Surface Hub. Connections to replacement PC ports give access to key peripherals on the Surface Hub, including the screen, pen, and touch features. This does mean that your Surface Hub won’t have the benefit of the Windows Team experience, but you will have the flexibility offered by providing and managing your own Windows computer. ### Software requirements -You can run Surface Hub in replacement PC mode with 64-bit versions of Windows 10 Home, Windows 10 Pro and Windows 10 Enterprise. You can download the [Surface Hub Replacement PC driver package](https://www.microsoft.com/download/details.aspx?id=52210) from the Microsoft download center. We recommend that you install these drivers on any computer you plan to use as a replacement PC. +You can run Surface Hub in Replacement PC Mode with 64-bit versions of Windows 10 Home, Windows 10 Pro, and Windows 10 Enterprise. You can download the [Surface Hub Replacement PC driver package](https://www.microsoft.com/download/details.aspx?id=52210) from the Microsoft Download Center. We recommend that you install these drivers on any computer you plan to use as a replacement PC. ### Hardware requirements @@ -233,7 +247,7 @@ Surface Hub is compatible with a range of hardware. Choose the processor and mem ### Graphics adapter -In replacement PC mode, Surface Hub supports any graphics adapter that can produce a DisplayPort signal. You'll improve your experience with a graphics adapter that can match Surface Hub's resolution and refresh rate. For example, the best and recommended replacement PC experience on the Surface Hub is with a 120Hz video signal. +In Replacement PC Mode, Surface Hub supports any graphics adapter that can produce a DisplayPort signal. You'll improve your experience with a graphics adapter that can match Surface Hub's resolution and refresh rate. For example, the best and recommended replacement PC experience on the Surface Hub is with a 120Hz video signal. **55" Surface Hubs** - For best experience, use a graphics card capable of 1080p resolution at 120Hz. @@ -272,7 +286,7 @@ Check directly with graphics card vendors for the latest drivers. ### Ports -Replacement PC ports on 55" Surface Hub. +Replacement PC ports on 55" Surface Hub ![image showing replacement pc ports on 55" surface hub. ](images/sh-55-rpc-ports.png) @@ -329,7 +343,7 @@ Replacement PC ports on 55" Surface Hub.   -Replacement PC ports on 84" Surface Hub. +Replacement PC ports on 84" Surface Hub ![image showing replacement pc ports on 84" surface hub. ](images/sh-84-rpc-ports.png) @@ -388,13 +402,12 @@ Replacement PC ports on 84" Surface Hub. ### Replacement PC setup instructions -**To use replacement PC mode** +**To use Replacement PC Mode** 1. Download and install the [Surface Hub Replacement PC driver package](https://www.microsoft.com/download/details.aspx?id=52210) on the replacement PC. - **Note**  We recommend that you set sleep or hibernation on the replacement PC so the Surface Hub will turn off the display when it isn't being used. - -   + >[!NOTE] + >We recommend that you set sleep or hibernation on the replacement PC so the Surface Hub will turn off the display when it isn't being used. 2. Turn off the Surface Hub using the power switch next to the power cable. @@ -421,10 +434,39 @@ You can switch the Surface Hub to use the internal PC. 3. Turn on the Surface Hub using the power switch next to the power cable.   - +## Video Out   +The Surface Hub includes a Video Out port for mirroring visual content from the Surface Hub to another display. +### Ports +Video Out port on the 55" Surface Hub +![Illustration of video output port](images/video-out-55.png) +Video Out port on the 84" Surface Hub + +![Illustration of video output port](images/video-out-84.png) + +
+ + + + + + + + + + + + + + + + +
DescriptionTypeInterfaceCapabilities

Video Output Mirror

Video Output

Video Output

    +

  • Supports connection to a standard DisplayPort monitor (only supports an x4 Link displaying 1080p60 resolution at 24bpp)

    • +

  • Supports use with HDMI monitors (supporting 1080p60) by using a DisplayPort-to-HDMI adaptor

    • +
diff --git a/devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md b/devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md index 798952d528..ceb0a4bc73 100644 --- a/devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md +++ b/devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md @@ -1,18 +1,18 @@ --- 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. +description: A hybrid deployment requires special processing 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 ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- # Hybrid deployment (Surface Hub) -A hybrid deployment requires special processing in order to set up a device account for your Microsoft Surface Hub. If you’re using a hybrid deployment, in which your organization has a mix of services, with some hosted on-premises and some hosted online, then your configuration will depend on where each service is hosted. This topic covers hybrid deployments for [Exchange hosted on-prem](#exchange-on-prem), and [Exchange hosted online](#exchange-online). Because there are so many different variations in this type of deployment, it's not possible to provide detailed instructions for all of them. The following process will work for many configurations. If the process isn't right for your setup, we recommend that you use PowerShell (see [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)) to achieve the same end result as documented here, and for other deployment options. You should then use the provided Powershell script to verify your Surface Hub setup. (See [Account Verification Script](appendix-a-powershell-scripts-for-surface-hub.md#acct-verification-ps-scripts).) +A hybrid deployment requires special processing to set up a device account for your Microsoft Surface Hub. If you’re using a hybrid deployment, in which your organization has a mix of services, with some hosted on-premises and some hosted online, then your configuration will depend on where each service is hosted. This topic covers hybrid deployments for [Exchange hosted on-prem](#exchange-on-prem), [Exchange hosted online](#exchange-online), Skype for Business on-prem, Skype for Business online, and Skype for Business hybrid. Because there are so many different variations in this type of deployment, it's not possible to provide detailed instructions for all of them. The following process will work for many configurations. If the process isn't right for your setup, we recommend that you use PowerShell (see [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)) to achieve the same end result as documented here, and for other deployment options. You should then use the provided Powershell script to verify your Surface Hub setup. (See [Account Verification Script](appendix-a-powershell-scripts-for-surface-hub.md#acct-verification-ps-scripts).) ## Exchange on-prem Use this procedure if you use Exchange on-prem. @@ -52,26 +52,31 @@ Use this procedure if you use Exchange on-prem. ```ps1 Set-ExecutionPolicy Unrestricted - $org='contoso.com' - $cred=Get-Credential $admin@$org + $cred=Get-Credential -Message "Please use your Office 365 admin credentials" $sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri 'https://outlook.office365.com/ps1-liveid/' -Credential $cred -Authentication Basic -AllowRedirection Import-PSSession $sess ``` 5. Create a new Exchange ActiveSync policy, or use a compatible existing policy. + After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy or use a compatible existing policy. + Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled. - If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts. + If you haven’t created a compatible policy yet, use the following cmdlet—-this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts. ```ps1 $easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false ``` - Once you have a compatible policy, then you will need to apply the policy to the device account. + Once you have a compatible policy, then you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not to resource mailboxes. You'll need to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox; you may need to re-enable it and set the password again too. ```ps1 - Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy + Set-Mailbox 'HUB01@contoso.com' -Type Regular + Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id + Set-Mailbox 'HUB01@contoso.com' -Type Room + $credNewAccount = Get-Credential -Message “Please provide the Surface Hub username and password” + Set-Mailbox 'HUB01@contoso.com' -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true ``` 6. Set Exchange properties. @@ -105,18 +110,21 @@ Use this procedure if you use Exchange on-prem. Set-MsolUserLicense -UserPrincipalName 'HUB01@contoso.com' -AddLicenses $strLicense ``` -9. Enable the device account with Skype for Business. +Next, you enable the device account with [Skype for Business Online](#skype-for-business-online), [Skype for Business on-prem](#skype-for-business-on-prem), or [Skype for Business hybrid](#skype-for-business-hybrid). - In order to enable Skype for Business, your environment will need to meet the following prerequisites: - - You'll need to have Lync Online (Plan 2) or higher in your O365 plan. The plan needs to support conferencing capability. - - - If you need Enterprise Voice (PSTN telephony) using telephony service providers for the Surface Hub, you need Lync Online (Plan 3). - - - Your tenant users must have Exchange mailboxes. - - - Your Surface Hub account does require a Lync Online (Plan 2) or Lync Online (Plan 3) license, but it does not require an Exchange Online license. +### Skype for Business Online - - Start by creating a remote PowerShell session from a PC. +To enable Skype for Business online, your environment will need to meet the following prerequisites: + +- You need to have Lync Online (Plan 2) or higher in your O365 plan. The plan needs to support conferencing capability. + +- If you need Enterprise Voice (PSTN telephony) using telephony service providers for the Surface Hub, you need Lync Online (Plan 3). + +- Your tenant users must have Exchange mailboxes (at least one Exchange mailbox in the tenant is required). + +- Your Surface Hub account does require a Lync Online (Plan 2) or Lync Online (Plan 3) license, but it does not require an Exchange Online license. + +1. Start by creating a remote PowerShell session from a PC to the Skype for Business online environment. ```ps1 Import-Module LyncOnlineConnector @@ -124,22 +132,22 @@ Use this procedure if you use Exchange on-prem. Import-PSSession $cssess -AllowClobber ``` - - To enable your Surface Hub account for Skype for Business Server, run this cmdlet: +2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet: ```ps1 - Enable-CsMeetingRoom -Identity $rm -RegistrarPool - 'sippoolbl20a04.infra.lync.com&' -SipAddressType EmailAddress + Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool 'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName ``` - If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet: + If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet: ```ps1 - Get-CsOnlineUser -Identity ‘alice@contoso.com’| fl *registrarpool* + Get-CsOnlineUser -Identity ‘HUB01@contoso.com’| fl *registrarpool* ``` -10. Assign Skype for Business license to your Surface Hub account. +2. Assign Skype for Business license to your Surface Hub account. Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) to the device. + - Login as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app. - Click on **Users and Groups** and then **Add users, reset passwords, and more**. @@ -152,9 +160,35 @@ Use this procedure if you use Exchange on-prem. - Click **Save**. - >**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. + >[!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 sign in to this account. + +### Skype for Business on-prem + +To run this cmdlet, you will need to connect to one of the Skype front-ends. Open the Skype PowerShell and run: + +``` +Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool registrarpoolfqdn -SipAddressType UserPrincipalName +``` + +### Skype for Business hybrid + +If your organization has set up [hybrid connectivity between Skype for Business Server and Skype for Business Online](https://technet.microsoft.com/library/jj205403.aspx), the guidance for creating accounts differs from a standard Surface Hub deployment. + +The Surface Hub requires a Skype account of the type `meetingroom`, while a normal user would use a user type account in Skype. If your Skype server is set up for hybrid where you might have users on the local Skype server as well as users hosted in Office 365, you might run into a few issues when trying to create a Surface Hub account. + +In a hybrid Skype environment, you have to create the user on-prem first, then move the user to the cloud. This means that your user is present in both environments (which makes SIP routing possible). The move from on-prem to online is done via the [Move-CsUser](https://technet.microsoft.com/library/gg398528.aspx) cmdlet which can only be used against user type accounts, not meetingroom type accounts. Because of this, you will not be able to move a Surface Hub account that has a meetingroom type of account. You might think of using the [Move-CsMeetingRoom](https://technet.microsoft.com/library/jj204889.aspx?f=255&mspperror=-2147217396) cmdlet, unfortunately this will not work between the on-prem Skype server and Office 365 - it only works across on-prem Skype pools. + +To have a functional Surface Hub account in a Skype hybrid configuration, create the Skype account as a normal user type account, instead of creating the account as a meetingroom. Enable the account on the on-prem Skype server first: + +``` +Enable-CsUser -Identity 'HUB01@contoso.com' -RegistrarPool "registrarpoolfqdn" -SipAddressType UserPrincipalName +``` + +After the Surface Hub account is enabled for Skype for Business on-premises, you can keep the account on-premises or you can move the Surface Hub account to Office 365, using the Move-CsUser cmdlet. [Learn more about moving a Skype user to Office 365.](https://technet.microsoft.com/library/jj204969.aspx) -For validation, you should be able to use any Skype for Business client (PC, Android, etc) to log in to this account. ## Exchange online Use this procedure if you use Exchange online. @@ -165,8 +199,7 @@ Use this procedure if you use Exchange online. ```ps1 Set-ExecutionPolicy Unrestricted - $org='contoso.microsoft.com' - $cred=Get-Credential $admin@$org + $cred=Get-Credential -Message "Please use your Office 365 admin credentials" $sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/ps1-liveid/ -Credential $cred -Authentication Basic -AllowRedirection Import-PSSession $sess ``` @@ -202,9 +235,10 @@ Use this procedure if you use Exchange online. Once you have a compatible policy, then you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not resource mailboxes. You need to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox—you may need to re-enable it and set the password again too. ```ps1 - Set-Mailbox $acctUpn -Type Regular - Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy + Set-Mailbox 'HUB01@contoso.com' -Type Regular + Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id Set-Mailbox 'HUB01@contoso.com' -Type Room + $credNewAccount = Get-Credential -Message "Please provide the Surface Hub username and password" Set-Mailbox 'HUB01@contoso.com' -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true ``` @@ -236,7 +270,7 @@ Use this procedure if you use Exchange online. ![Image with account name, logon name, and password options for new user.](images/hybriddeployment-03a.png) -6. Directory synchronization. +6. Run directory synchronization. After you've created the account, run a directory synchronization. When it's complete, go to the users page and verify that the two accounts created in the previous steps have merged. @@ -262,44 +296,47 @@ Use this procedure if you use Exchange online. Set-MsolUserLicense -UserPrincipalName 'HUB01@contoso.com' -AddLicenses $strLicense ``` -9. Enable the device account with Skype for Business. +Next, you enable the device account with [Skype for Business Online](#sfb-online), [Skype for Business on-prem](#sfb-onprem), or [Skype for Business hybrid](#sfb-hybrid). - In order to enable Skype for Business, your environment will need to meet the following prerequisites: - - - You'll need to have Lync Online (Plan 2) or higher in your O365 plan. The plan needs to support conferencing capability. + +### Skype for Business Online - - If you need Enterprise Voice (PSTN telephony) using telephony service providers for the Surface Hub, you need Lync Online (Plan 3). +In order to enable Skype for Business, your environment will need to meet the following prerequisites: + +- You'll need to have Lync Online (Plan 2) or higher in your O365 plan. The plan needs to support conferencing capability. - - Your tenant users must have Exchange mailboxes. +- If you need Enterprise Voice (PSTN telephony) using telephony service providers for the Surface Hub, you need Lync Online (Plan 3). - - Your Surface Hub account does require a Lync Online (Plan 2) or Lync Online (Plan 3) license, but it does not require an Exchange Online license. +- Your tenant users must have Exchange mailboxes (at least one Exchange mailbox in the tenant is required). + +- Your Surface Hub account does require a Lync Online (Plan 2) or Lync Online (Plan 3) license, but it does not require an Exchange Online license. - Start by creating a remote PowerShell session from a PC. +1. Start by creating a remote PowerShell session to the Skype for Business online environment from a PC. - ```ps1 - Import-Module LyncOnlineConnector - $cssess=New-CsOnlineSession -Credential $cred - Import-PSSession $cssess -AllowClobber - ``` + ``` + Import-Module LyncOnlineConnector + $cssess=New-CsOnlineSession -Credential $cred + Import-PSSession $cssess -AllowClobber + ``` - To enable your Surface Hub account for Skype for Business Server, run this cmdlet: +2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet: - ```ps1 - Enable-CsMeetingRoom -Identity $rm -RegistrarPool - 'sippoolbl20a04.infra.lync.com' -SipAddressType EmailAddress - ``` + ``` + Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool + 'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName + ``` - If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet: + If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet: - ```ps1 - Get-CsOnlineUser -Identity ‘alice@contoso.com’| fl *registrarpool* - ``` + ``` + Get-CsOnlineUser -Identity 'HUB01@contoso.com'| fl *registrarpool* + ``` 10. Assign Skype for Business license to your Surface Hub account Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) to the device. - - Login as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app. + - Sign in as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app. - Click on **Users and Groups** and then **Add users, reset passwords, and more**. @@ -311,6 +348,34 @@ Use this procedure if you use Exchange online. - Click **Save**. - >**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. + >[!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 sign in to this account. + + +### Skype for Business on-prem + +To run this cmdlet, you will need to connect to one of the Skype front-ends. Open the Skype PowerShell and run: + +``` +Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool registrarpoolfqdn -SipAddressType UserPrincipalName +``` + + +### Skype for Business hybrid + +If your organization has set up [hybrid connectivity between Skype for Business Server and Skype for Business Online](https://technet.microsoft.com/library/jj205403.aspx), the guidance for creating accounts differs from a standard Surface Hub deployment. + +The Surface Hub requires a Skype account of the type *meetingroom*, while a normal user would use a *user* type account in Skype. If your Skype server is set up for hybrid where you might have users on the local Skype server as well as users hosted in Office 365, you might run into a few issues when trying to create a Surface Hub account. + +In a hybrid Skype environment, you have to create the user on-prem first, then move the user to the cloud. This means that your user is present in both environments (which makes SIP routing possible). The move from on-prem to online is done via the [Move-CsUser](https://technet.microsoft.com/library/gg398528.aspx) cmdlet which can only be used against user type accounts, not meetingroom type accounts. Because of this, you will not be able to move a Surface Hub account that has a meetingroom type of account. You might think of using the [Move-CsMeetingRoom](https://technet.microsoft.com/library/jj204889.aspx?f=255&MSPPError=-2147217396) cmdlet, unfortunately this will not work between the on-prem Skype server and Office 365 - it only works across on-prem Skype pools. + +In order to have a functional Surface Hub account in a Skype hybrid configuration, create the Skype account as a normal user type account, instead of creating the account as a meetingroom. First follow the Exchange steps - either [online](#exchange-online) or [on-prem](#exchange-on-prem) - and, instead of enabling the user for Skype for Business Online as described, [enable the account](https://technet.microsoft.com/library/gg398711.aspx) on the on-prem Skype server: + +``` +Enable-CsUser -Identity 'HUB01@contoso.com' -RegistrarPool "registrarpoolfqdn" -SipAddressType UserPrincipalName +``` + +After the Surface Hub account is enabled for Skype for Business on-premises, you can keep the account on-premises or you can move the Surface Hub account to Office 365, using the Move-CsUser cmdlet. [Learn more about moving a Skype user to Office 365](https://technet.microsoft.com/library/jj204969.aspx). -For validation, you should be able to use any Skype for Business client (PC, Android, etc) to log in to this account. \ No newline at end of file diff --git a/devices/surface-hub/images/video-out-55.png b/devices/surface-hub/images/video-out-55.png new file mode 100644 index 0000000000..e386b7f3d9 Binary files /dev/null and b/devices/surface-hub/images/video-out-55.png differ diff --git a/devices/surface-hub/images/video-out-84.png b/devices/surface-hub/images/video-out-84.png new file mode 100644 index 0000000000..672ae78556 Binary files /dev/null and b/devices/surface-hub/images/video-out-84.png differ diff --git a/devices/surface-hub/manage-windows-updates-for-surface-hub.md b/devices/surface-hub/manage-windows-updates-for-surface-hub.md index e41075f908..2d077cb622 100644 --- a/devices/surface-hub/manage-windows-updates-for-surface-hub.md +++ b/devices/surface-hub/manage-windows-updates-for-surface-hub.md @@ -19,7 +19,7 @@ New releases of the Surface Hub operating system are published through Windows U You can also configure Surface Hub to receive updates from both Windows Update for Business and WSUS. See [Integrate Windows Update for Business with Windows Server Update Services](https://technet.microsoft.com/en-us/itpro/windows/manage/waas-integrate-wufb#integrate-windows-update-for-business-with-windows-server-update-services) for details. -| Capabilities | Windows Update for Business | Windows server Update Services (WSUS) | +| Capabilities | Windows Update for Business | Windows Server Update Services (WSUS) | | ------------ | --------------------------- | ------------------------------------- | | Receive updates directly from Microsoft's Windows Update service, with no additional infrastructure required. | Yes | No | | Defer updates to provide additional time for testing and evaluation. | Yes | Yes | diff --git a/windows/keep-secure/trusted-platform-module-overview.md b/windows/keep-secure/trusted-platform-module-overview.md index 8b0098f582..a1b3a32c2d 100644 --- a/windows/keep-secure/trusted-platform-module-overview.md +++ b/windows/keep-secure/trusted-platform-module-overview.md @@ -45,7 +45,7 @@ The TPM has several Group Policy settings that can be used to manage how it is u ## New and changed functionality -For more info on new and changed functionality for Trusted Platform Module in Windows 10, see [What's new in Trusted Platform Module?](../whats-new/trusted-platform-module.md). +For more info on new and changed functionality for Trusted Platform Module in Windows 10, see [What's new in Trusted Platform Module?](../whats-new/whats-new-windows-10-version-1507-and-1511.md#trusted-platform-module). ## Device health attestation diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index cf1b406e61..50f89c5dea 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -16,6 +16,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in | New or changed topic | Description | | --- | --- | +| [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Added guidance for switching devices between servicing branches | | [Manage updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md) | Added Windows 10 IoT Mobile | ## October 2016 diff --git a/windows/manage/guidelines-for-assigned-access-app.md b/windows/manage/guidelines-for-assigned-access-app.md index 2d776f2cf5..0552f8af1a 100644 --- a/windows/manage/guidelines-for-assigned-access-app.md +++ b/windows/manage/guidelines-for-assigned-access-app.md @@ -54,8 +54,8 @@ If you use a web browser as your assigned access app, consider the following tip 2. Press **Enter** or click the gpedit icon to launch the group policy editor. 3. In the group policy editor, navigate to **User Configuration** > **Administrative Templates** > **Start Menu and Taskbar**. 4. Select **Remove Run menu from Start Menu**, select **Disabled**, and click **Apply**. Disabling this policy prevents users from entering the following into the Internet Explorer Address Bar: - - A UNC path (\\\) - - A local drive (C:\) + - A UNC path (\\\\*server*\\\\*share*) + - A local drive (C:\\) - A local folder (\temp) diff --git a/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md index ca86b2cd46..08bc3dd3db 100644 --- a/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md +++ b/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md @@ -23,7 +23,7 @@ Learn about the network connections that Windows components make to Microsoft an If you want to minimize connections from Windows to Microsoft services, or configure particular privacy settings, this article covers the settings that you could consider. You can configure telemetry at the lowest level for your edition of Windows, and also evaluate which other connections Windows makes to Microsoft services you want to turn off in your environment from the list in this article. -You can configure telemetry at the Security level, turn off Windows Defender telemetry and MSRT reporting, and turn off all other connections to Microsoft network endpoints as described in this article to help prevent Windows from sending any data to Microsoft. There are many reason why these communications are enabled by default, such as updating malware definitions and maintain current certificate revocation lists, which is why we strongly recommend against this. This data helps us deliver a secure, reliable, and more delightful personalized experience. +You can configure telemetry at the Security level, turn off Windows Defender telemetry and MSRT reporting, and turn off all other connections to Microsoft network endpoints as described in this article to help prevent Windows from sending any data to Microsoft. There are many reasons why these communications are enabled by default, such as updating malware definitions and maintain current certificate revocation lists, which is why we strongly recommend against this. This data helps us deliver a secure, reliable, and more delightful personalized experience. We are always striving to improve our documentation and welcome your feedback. You can provide feedback by contacting telmhelp@microsoft.com. diff --git a/windows/manage/waas-servicing-branches-windows-10-updates.md b/windows/manage/waas-servicing-branches-windows-10-updates.md index 65180b5cba..64dd552067 100644 --- a/windows/manage/waas-servicing-branches-windows-10-updates.md +++ b/windows/manage/waas-servicing-branches-windows-10-updates.md @@ -100,6 +100,80 @@ To prevent devices in your enterprise from being enrolled in the Insider Program - Group Policy: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\\**Toggle user control over Insider builds** - MDM: Policy CSP - [System/AllowBuildPreview](https://msdn.microsoft.com/library/windows/hardware/dn904962%28v=vs.85%29.aspx#System_AllowBuildPreview) +## Switching branches + +During the life of a device, it may be necessary or desirable to switch between the available branches. Depending on the branch you are using, the exact mechanism for doing this can be different; some will be simple, others more involved. + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
From this branchTo this branchYou need to
Windows Insider ProgramCurrent BranchWait for the final Current Branch release.
Current Branch for BusinessNot directly possible, because Windows Insider Program machines are automatically upgraded to the Current Branch release at the end of the development cycle.
Long-Term Servicing BranchNot directly possible (requires wipe-and-load).
Current BranchInsiderUse the Settings app to enroll the device in the Windows Insider Program.
Current Branch for BusinessSelect the Defer upgrade setting, or move the PC to a target group or flight that will not receive the next upgrade until it is business ready. Note that this change will not have any immediate impact; it only prevents the installation of the next Current Branch release.
Long-Term Servicing BranchNot directly possible (requires wipe-and-load).
Current Branch for BusinessInsiderUse the Settings app to enroll the device in the Windows Insider Program.
Current BranchDisable the Defer upgrade setting, or move the PC to a target group or flight that will receive the latest Current Branch release.
Long-Term Servicing BranchNot directly possible (requires wipe-and-load).
Long-Term Servicing BranchInsiderUse media to upgrade to the latest Windows Insider Program build.
Current BranchUse media to upgrade to a later Current Branch build. (Note that the Current Branch build must be a later build.)
Current Branch for BusinessUse media to upgrade to a later Current Branch for Business build (Current Branch build plus fixes). Note that it must be a later build.
+ + ## Steps to manage updates for Windows 10 diff --git a/windows/whats-new/security.md b/windows/whats-new/security.md index a17f84be19..5cf158fc99 100644 --- a/windows/whats-new/security.md +++ b/windows/whats-new/security.md @@ -188,9 +188,8 @@ Table 1. Windows 10 hardware requirements | Windows Hello | R | N | N | N | N | N | | VBS | N | Y | Y | Y | N | Y | | UEFI Secure Boot | R | N | N | N | Y | N | -| Device health attestation through Measured Boot | Y\* | N | N | N | Y | Y | +| Device health attestation through Measured Boot | Y | N | N | N | Y | Y |   -\* Requires use of TPM 2.0. **Note**
In this table, **R** stands for *recommended*, **Y** means that the hardware component is *required* for that Windows 10 feature, and **N** means that the hardware component is *not used* with that Windows 10 feature.