deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 22:07:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'refs/remotes/origin/master' into live

Browse Source
This commit is contained in:
LizRoss 2016-04-21 10:57:41 -07:00
commit f700af3989
128 changed files with 6775 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
devices/surface-hub/TOC.md Normal file
View File

@ -0,0 +1,33 @@
# [Microsoft Surface Hub](index.md)
## [Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
### [Intro to Microsoft Surface Hub](intro-to-surface-hub.md)
### [Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md)
### [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
#### [Create and test a device account](create-and-test-a-device-account-surface-hub.md)
##### [Online deployment](online-deployment-surface-hub-device-accounts.md)
##### [On-premises deployment](on-premises-deployment-surface-hub-device-accounts.md)
##### [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md)
##### [Create a device account using UI](create-a-device-account-using-office-365.md)
##### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md)
##### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md)
##### [Password management](password-management-for-surface-hub-device-accounts.md)
#### [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md)
#### [Admin group management](admin-group-management-for-surface-hub.md)
### [Set up Microsoft Surface Hub](set-up-your-surface-hub.md)
#### [Setup worksheet](setup-worksheet-surface-hub.md)
#### [First-run program](first-run-program-surface-hub.md)
### [Manage Microsoft Surface Hub](manage-surface-hub.md)
#### [Accessibility](accessibility-surface-hub.md)
#### [Change the Surface Hub device account](change-surface-hub-device-account.md)
#### [Device reset](device-reset-suface-hub.md)
#### [Install apps on your Surface Hub](install-apps-on-surface-hub.md)
#### [Manage settings with a local admin account](manage-settings-with-local-admin-account-surface-hub.md)
#### [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md)
#### [Monitor your Surface Hub](monitor-surface-hub.md)
#### [Save your BitLocker key](save-bitlocker-key-surface-hub.md)
#### [Using a room control system](use-room-control-system-with-surface-hub.md)
#### [Windows updates](manage-windows-updates-for-surface-hub.md)
#### [Wireless network management](wireless-network-management-for-surface-hub.md)
### [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
### [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)

73
devices/surface-hub/accessibility-surface-hub.md Normal file
View File

@ -0,0 +1,73 @@
---
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"]
author: TrudyHa
---
# Accessibility (Surface Hub)
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.
The default accessibility settings for Surface Hub include:
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Accessibility feature</th>
<th align="left">Default setting</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>Narrator</strong></p></td>
<td align="left"><p>Off</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Magnifier</strong></p></td>
<td align="left"><p>Off</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>High contrast</strong></p></td>
<td align="left"><p>No theme selected</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Closed captions</strong></p></td>
<td align="left"><p>Defaults selected for <strong>Font</strong> and <strong>Background and window</strong>.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>Keyboard</strong></p></td>
<td align="left"><p>On-screen <strong>Keyboard</strong>, <strong>Sticky Keys</strong>, <strong>Toggle Keys</strong>, and <strong>Filter Keys</strong> are all off.</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Mouse</strong></p></td>
<td align="left"><p>Defaults selected for <strong>Pointer size</strong>, <strong>Pointer color</strong> and <strong>Mouse keys</strong>.</p></td>
</tr>
</tbody>
</table>
 
You'll find additional settings under **Ease of Access** &gt; **Other options**.
## Related topics
[Manage Microsoft Surface Hub](manage-surface-hub.md)
[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
 
 

104
devices/surface-hub/admin-group-management-for-surface-hub.md Normal file
View File

@ -0,0 +1,104 @@
---
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"]
author: TrudyHa
---
# Admin group management (Surface Hub)
Every Microsoft Surface Hub can be configured individually by opening the Settings app on the device. However, to prevent people who are not administrators from changing the settings, the Settings app requires administrator credentials to open the app and change settings.
The Settings app requires local administrator credentials to open the app.
## Admin Group Management
You can set up administrator accounts for the device in any of three ways:
- Create a local admin account.
- Domain join the device to Active Directory (AD).
- Azure Active Directory (Azure AD) join the device.
### Create a local admin account
To create a local admin, choose to use a local admin during first run. This will create a single local admin account on the Surface Hub with the username and password of your choice. These same credentials will need to be provided to open the Settings app.
Note that the local admin account information is not backed by any directory service. We recommend you only choose a local admin if the device does not have access to Active Directory (AD) or Azure Active Directory (Azure AD). If you decide to change the local admin’s password, you can do so in Settings. However, if you want to change from using the local admin account to using a group from your domain or Azure AD organization, then you’ll need to reset the device and go through first-time setup again.
### Domain join the device to Active Directory (AD)
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**  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.
 
### Azure Active Directory (Azure AD) join the device
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.
 
### Which should I choose?
If your organization is using AD or Azure AD, we recommend you either domain join or join Azure AD, primarily for security reasons. People will be able to authenticate and unlock Settings with their own credentials, and can be moved in or out of the security groups associated with you domain or organization.
We recommend that a local admin be set up only if you do not have Active Directory or Azure AD, or if you cannot connect to your Active Directory or Azure AD during first run.
### Summary
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">How is the local administrator set up?</th>
<th align="left">Requirements</th>
<th align="left">Which credentials can be used for the Settings app?</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">A local admin account is created.</td>
<td align="left">None.</td>
<td align="left">The credentials of the local admin that was created.</td>
</tr>
<tr class="even">
<td align="left">The Surface Hub is joined to a domain.</td>
<td align="left">Your organization is using Active Directory (AD).</td>
<td align="left">Credentials of any AD user from a specified security group</td>
</tr>
<tr class="odd">
<td align="left">The Surface Hub is joined to Azure Active Directory (Azure AD).</td>
<td align="left">Your organization is using Azure AD Basic.</td>
<td align="left">Tenant or device admins</td>
</tr>
<tr class="even">
<td align="left">Your organization is using Azure AD Premium.</td>
<td align="left">Tenant or device admins + additional specified people</td>
<td align="left"></td>
</tr>
</tbody>
</table>
 
 
 

1687
devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md Normal file
View File

File diff suppressed because it is too large Load Diff

36
devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md Normal file
View File

@ -0,0 +1,36 @@
---
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"]
author: TrudyHa
---
# Applying ActiveSync policies to device accounts (Surface Hub)
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.
For these features to work, the ActiveSync policies for your organization must be configured as follows:
- There can't be any global policies that block synchronization of the resource mailbox that's being used by the Surface Hub’s device account. If there is such a blocking policy, you need to whitelist the Surface Hub as an allowed device.
- You must set a mobile device mailbox policy where the **PasswordEnabled** setting is set to False. Other mobile device mailbox policy settings are not compatible with the Surface Hub.
## Whitelisting the DeviceID
Your organization may have a global policy that prevents syncing of device accounts provisioned on Surface Hubs. To configure this property, see [Allowing device IDs for ActiveSync](appendix-a-powershell-scripts-for-surface-hub.md#whitelisting-device-ids-cmdlet).
## Setting PasswordEnabled
The device account must have an ActiveSync policy where the **PasswordEnabled** attribute is set to False or 0. To configure this property, see [Creating a Surface Hub-compatible Microsoft Exchange ActiveSync policy](appendix-a-powershell-scripts-for-surface-hub.md#create-compatible-as-policy).
 
 

85
devices/surface-hub/change-surface-hub-device-account.md Normal file
View File

@ -0,0 +1,85 @@
---
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"]
author: TrudyHa
---
# Change the Microsoft Surface Hub device account
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.
## Details
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Value</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>User Principal Name</p></td>
<td align="left"><p>The user principal name (UPN) of the device account.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Password</p></td>
<td align="left"><p>The corresponding password of the device account.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Domain</p></td>
<td align="left"><p>The domain that the device account belongs to. This field does not need to be provided for Office 365 accounts.</p></td>
</tr>
<tr class="even">
<td align="left"><p>User name</p></td>
<td align="left"><p>The user name of the device account. This field does not need to be provided for Office 365 accounts.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Session Initiation Protocol (SIP) address</p></td>
<td align="left"><p>The SIP address of the device account.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft Exchange server</p></td>
<td align="left"><p>This is the Exchange server of the device account. The device account’s username and password must be able to authenticate to the specified Exchange server.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Enable Exchange services</p></td>
<td align="left"><p>When checked, all Exchange services will be enabled (for example, calendar on the welcome screen, emailing whiteboards). When not checked, all Exchange services will be disabled, and the Exchange server does not need to be provided.</p></td>
</tr>
</tbody>
</table>
 
## What happens?
The UPN and password are used to validate the account in AD or Azure AD. If the validation fails, you may need to provide the domain and user name.
Using the credentials provided, we will try to discover the SIP address. If a SIP address can't be found, then Skype for Business will use the UPN as the SIP address. If this is not the SIP address for the account, you will need to provide the SIP address.
The Exchange server address will need to be provided if the device can't find a server associated with the login credentials. Microsoft Surface Hub will use the Exchange server to talk to ActiveSync, which enables several key features on the device.
## Related topics
[Manage Microsoft Surface Hub](manage-surface-hub.md)
[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
 
 

405
devices/surface-hub/create-a-device-account-using-office-365.md Normal file
View File

@ -0,0 +1,405 @@
---
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"]
author: TrudyHa
---
# Create a device account using UI (Surface Hub)
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](#create-device-acct-o365) or the [Exchange Admin Center](#create-device-acct-eac).
## <a href="" id="create-device-acct-o365"></a>Create a device account using Office 365
1. [Create the account in the Office 365 Admin Center](#create-device-acct-o365-admin-ctr).
2. [Create a mobile device mailbox (ActiveSync) policy from the Microsoft Exchange Admin Center](#create-device-acct-o365-mbx-policy).
3. [Use PowerShell to complete device account creation](#create-device-acct-o365-complete-acct).
4. [Use PowerShell to configure Exchange properties of the account](#create-device-acct-o365-configure-exch-prop).
5. [Enable the account with Skype for Business](#create-device-acct-o365-skype-for-business).
### <a href="" id="create-device-acct-o365-admin-ctr"></a>Create the account in the Office 365 Admin Center
1. Sign in to Office 365 by visiting http://portal.office.com/admin/
2. Provide the admin credentials for your Office 365 tenant. This will take you to your Office 365 Admin Center.
![office 365 admin center. ](images/setupdeviceaccto365-02.png)
3. Once you are at the Office 365 Admin Center, navigate to **Users** in the left panel, and then click **Active Users**.
![office 365 admin center dashboard shwoing active users.](images/setupdeviceaccto365-03.png)
4. On the controls above the list of users, click **+** to create a new user. You'll need to enter a **Display name**, **User name**, **Password** and an email address for the recipient of the password. Optionally you can change the password manually, but we recommend that you use the auto-generated option. You also need to assign this account a license that gives the account access to Exchange and Skype for Business services.
![screen to create a new user account. ](images/setupdeviceaccto365-04.png)
Click **Create**.
5. Once the account has been successfully created, click **Close** on the resulting dialog box, and you will see the admin center Active Users list again.
![confirmation screen for creating a new account. ](images/setupdeviceaccto365-05.png)
6. Select the user you just created from the **Active Users** list. You need to disable the Skype for Business license, because you can’t create a Skype Meeting Room with this option.
![office 365 admin center showing properties for the new user account. ](images/setupdeviceaccto365-06.png)
In the right panel you can see the account properties and several optional actions. The process so far has created a regular Skype account for this user, which you need to disable. Click **Edit** for the **Assigned license** section, then click the dropdown arrow next to the license to expand the details.
![assign license for skype for business online.](images/setupdeviceaccto365-07.png)
From the list, uncheck **Skype for Business Online (plan 2)** (this license may vary depending on your organization), and click **SAVE**.
### <a href="" id="create-device-acct-o365-mbx-policy"></a>Create a mobile device mailbox (ActiveSync) policy from the Exchange Admin Center
1. In the Office 365 Admin Center’s left panel, click **ADMIN**, and then click **Exchange**.
![office 365 admin center, showing exchange active users. ](images/setupdeviceaccto365-08.png)
2. This will open another tab on your browser to take you to the Exchange Admin Center, where you can create and set the Mailbox Setting for Surface Hub.
![exchange admin center. ](images/setupdeviceaccto365-09.png)
3. To create a Mobile Device Mailbox Policy, click **Mobile** from the left panel and then click **Mobile device mailbox policies**. Surface Hubs require an account with a mobile device mailbox policy that does not require a password, so if you already have an existing policy that matches this requirement, you can apply that policy to the account. Otherwise use the following steps to create a new one to be used only for Surface Hub device accounts.
![excahnge admin center - creating a mobile device mailbox policy. ](images/setupdeviceaccto365-10.png)
4. To create a New Surface Hub mobile device mailbox policy, click the **+** button from the controls above the list of policies to add a new policy. For the name, provide a name that will help you distinguish this policy from other device accounts (for example, *SurfaceHubDeviceMobilePolicy*). Make sure the policy does not require a password for the devices assigned to, so make sure **Require a Password** remains unchecked, then click **Save**.
![image showing new mobile device policy](images/setupdeviceaccto365-11.png)
5. After you have created the new mobile device mailbox policy, go back to the **Exchange Admin Center** and you will see the new policy listed.
![image with new mobile device mailbox policy in exchange admin center. ](images/setupdeviceaccto365-12.png)
6. Now, to apply the ActiveSync policy without using PowerShell, you can do the following: In the EAC, click **Recipients** &gt; **Mailboxes** and then select a mailbox.
![image showing mailbox in exchange admin center. ](images/setupdeviceaccto365-13.png)
7. In the Details pane, scroll to **Phone and Voice Features** and click **View details** to display the **Mobile Device Details** screen.
![image showing mobile device details for the mailbox. ](images/setupdeviceaccto365-14.png)
8. The mobile device mailbox policy that’s currently assigned is displayed. To change the mobile device mailbox policy, click **Browse**.
![image with details for the mobile device policy. ](images/setupdeviceaccto365-15.png)
9. Choose the appropriate mobile device mailbox policy from the list, click **OK** and then click **Save**.
![image showing multiple mobile device mailbox policies. ](images/setupdeviceaccto365-16.png)
### <a href="" id="create-device-acct-o365-complete-acct"></a>Use PowerShell to complete device account creation
From here on, you'll need to finish the account creation process using PowerShell to set up some configuration.
In order to run cmdlets used by these PowerShell scripts, the following must be installed for the admin PowerShell console:
- [Microsoft Online Services Sign-In Assistant for IT Professionals BETA](http://go.microsoft.com/fwlink/?LinkId=718149)
- [Windows Azure Active Directory Module for Windows PowerShell](http://go.microsoft.com/fwlink/p/?linkid=236297)
- [Skype for Business Online, Windows PowerShell Module](http://www.microsoft.com/download/details.aspx?id=39366)
### Connecting to online services
1. Run Windows PowerShell as Administrator.
![image showing how to start windows powershell and run as administrator. ](images/setupdeviceaccto365-17.png)
2. Create a Credentials object, then create a new session that connects to Skype for Business Online, and provide the global tenant administrator account, then click **OK**.
![image for windows powershell credential request. ](images/setupdeviceaccto365-18.png)
3. To connect to Microsoft Online Services, run:
``` syntax
Connect-MsolService -Credential $Cred
```
![image showing powershell cmdlet.](images/setupdeviceaccto365-19.png)
4. Now to connect to Skype for Business Online Services, run:
``` syntax
$sfbsession = New-CsOnlineSession -Credential $cred
```
![image showing powershell cmdlet.](images/setupdeviceaccto365-20.png)
5. Finally, to connect to Exchange Online Services, run:
``` syntax
$exchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
"https://outlook.office365.com/powershell-liveid/" -Credential $cred -Authentication "Basic" –AllowRedirection
```
![image showing powershell cmdlet.](images/setupdeviceaccto365-21.png)
6. Now you have to import the Skype for Business Online Session and the Exchange Online session you have just created, which will import the Exchange and Skype Commands so you can use them locally.
``` syntax
Import-PSSession $exchangesession -AllowClobber -WarningAction SilentlyContinue
Import-PSSession $sfbsession -AllowClobber -WarningAction SilentlyContinue
```
Note that this could take a while to complete.
![image showing powershell cmdlet.](images/setupdeviceaccto365-22.png)
7. Once you’re connected to the online services you need to run a few more cmdlets to configure this account as a Surface Hub device account.
### <a href="" id="create-device-acct-o365-configure-exch-prop"></a>Use PowerShell to configure Exchange properties of the account
Now that you're connected to the online services, you can finish setting up the device account. You'll use the device account email address to:
- Change the mailbox type from regular to room.
- Set the password and enable the room mailbox account
- Change various Exchange properties
- Set the user account password to never expire.
1. You’ll need to enter the account’s mail address and create a variable with that value:
``` syntax
$mailbox = (Get-Mailbox <your device account’s alias>)
```
To store the value get it from the mailbox:
``` syntax
$strEmail = $mailbox.WindowsEmailAddress
```
Print the value:
``` syntax
$strEmail
```
You will see the correct email address.
![image showing powershell cmdlet.](images/setupdeviceaccto365-23.png)
2. You need to convert the account into to a room mailbox, so run:
![image showing powershell cmdlet.](images/setupdeviceaccto365-24.png)
``` syntax
Set-Mailbox $strEmail -Type Room
```
3. In order for the device account to be authenticated on a Surface Hub, you need to enable the room mailbox account and set a password, so the account can be used by the device to get meeting information using ActiveSync and log in to Skype for Business.
``` syntax
Set-Mailbox $strEmail -RoomMailboxPassword (ConvertTo-SecureString -String "<your password>" -AsPlainText -Force) -EnableRoomMailboxAccount $true
```
![image showing powershell cmdlet.](images/setupdeviceaccto365-25.png)
4. Various Exchange properties can be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
``` syntax
Set-CalendarProcessing -Identity $acctUpn -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
Set-CalendarProcessing -Identity $acctUpn -AddAdditionalResponse $true -AdditionalResponse "This is a <tla rid="surface_hub"/> room!"
```
![image showing powershell cmdlet.](images/setupdeviceaccto365-26.png)
5. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information.
``` syntax
Set-MsolUser -UserPrincipalName $strEmail -PasswordNeverExpires $True
```
### <a href="" id="create-device-acct-o365-skype-for-business"></a>Enable the account with Skype for Business
Enable the device account with Skype for Business.
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.
1. Start by creating a remote PowerShell session from a PC.
```PowerShell
Import-Module LyncOnlineConnector
$cssess=New-CsOnlineSession -Credential $cred
Import-PSSession $cssess -AllowClobber
```
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
```PowerShell
Enable-CsMeetingRoom -Identity $rm -RegistrarPool
"sippoolbl20a04.infra.lync.com" -SipAddressType EmailAddress
```
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:
```PowerShell
Get-CsOnlineUser -Identity ‘alice@contoso.microsoft.com’| fl *registrarpool*
```
## <a href="" id="create-device-acct-eac"></a>Create a device account using the Exchange Admin Center
You can use the Exchange Admin Center to create a device account:
1. [Create an account and mailbox with the Exchange Admin Center](#create-device-acct-exch-admin-ctr).
2. [Create a mobile device mailbox policy from the Exchange Admin Center](#create-device-acct-exch-mbx-policy).
3. [Use PowerShell to configure the account](#create-device-acct-exch-powershell-conf).
4. [Enable the account with Skype for Business](#create-device-acct-exch-skype-for-business).
### <a href="" id="create-device-acct-exch-admin-ctr"></a>Create an account and mailbox with the Exchange Admin Center
1. Sign in to your Exchange Admin Center using Exchange admin credentials.
2. Once you are at the Exchange Admin Center (EAC), navigate to **Recipients** in the left panel.
![image showing mailboxes in exchange admin center. ](images/setupdeviceacctexch-01.png)
3. On the controls above the list of mailboxess, choose **+** to create a new one, and provide a **Display name**, **Name**, and **User logon name**, and then click **Save**.
![image showing creating a new mailbox. ](images/setupdeviceacctexch-02.png)
### <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).
 
1. Go to the Exchange Admin Center.
![image showing exchange admin center. ](images/setupdeviceacctexch-03.png)
2. To create a mobile device mailbox policy, click **Mobile** from the left panel, then **Mobile device mailbox policies**. Surface Hubs require an account with a mobile device mailbox policy that does not require a password, so if you already have an existing policy that matches this requirement, you can apply that policy to the account. Otherwise use the following steps to create a new one to be used only for Surface Hub device accounts.
![image showing using exchange admin center to create a mobile device mailbox policy. ](images/setupdeviceacctexch-05.png)
3. To create a new mobile device account mailbox policy, click the **+** button from the controls above the list of policies to add a new policy. For the name provide a name that will help you distinguish this policy from other device accounts (for example, *SurfaceHubDeviceMobilePolicy*). The policy must not be password-protected, so make sure **Require a Password** remains unchecked, then click **Save**.
![image showing new mobile device mailbox policy. ](images/setupdeviceacctexch-06.png)
4. After you have created the new mobile device mailbox policy, go back to the Exchange Admin Center and you will see the new policy listed.
![image showing new mobile device mailbox policy in exchange admin center. ](images/setupdeviceacctexch-07.png)
5. To apply the ActiveSync policy without using PowerShell, you can do the following:
- In the EAC, click **Recipients** &gt; **Mailboxes** and select a mailbox.
![image showing exchange admin center. ](images/setupdeviceacctexch-08.png)
- In the **Details** pane, scroll to **Phone and Voice Features** and click **View details** to display the **Mobile Device Details** screen.
![image showing mailbox details. ](images/setupdeviceacctexch-09.png)
- The mobile device mailbox policy that’s currently assigned is displayed. To change the mobile device mailbox policy, click **Browse**.
![image showing the currently assigned mobile device mailbox policy. ](images/setupdeviceacctexch-10.png)
- Choose the appropriate mobile device mailbox policy from the list, click **OK** and then click **Save**.
![image showing list of mobile device mailbox policies. ](images/setupdeviceacctexch-11.png)
### <a href="" id="create-device-acct-exch-powershell-conf"></a>Use PowerShell to configure the account
Now that you're connected to the online services, you can finish setting up the device account. You'll use the device account email address to:
- Change the mailbox type from regular to room.
- Change various Exchange properties
- Set the user account password to never expire.
1. You’ll need to enter the account’s mail address and create a variable with that value:
``` syntax
$mailbox = (Get-Mailbox <your device account’s alias>)
```
To store the value got it from the mailbox:
``` syntax
$strEmail = $mailbox.WindowsEmailAddress
```
Print the value by running:
``` syntax
$strEmail
```
You will see the correct email address.
2. You need to convert the account into to a room mailbox, so run:
``` syntax
Set-Mailbox $strEmail -Type Room
```
3. In order for the device account to be authenticated on a Surface Hub, you need to enable the room mailbox account and set a password, so the account can be used by the device to get meeting information using ActiveSync and log in to Skype for Business.
``` syntax
Set-Mailbox $strEmail -RoomMailboxPassword (ConvertTo-SecureString -String "<your password>" -AsPlainText -Force) -EnableRoomMailboxAccount $true
```
4. Various Exchange properties can be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
``` syntax
Set-CalendarProcessing -Identity $acctUpn -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
Set-CalendarProcessing -Identity $acctUpn -AddAdditionalResponse $true -AdditionalResponse "This is a <tla rid="surface_hub"/> room!"
```
5. Now we have to set some properties in AD. To do that, you need the alias of the account (this is the part of the UPN that becomes before the “@”).
``` syntax
$strAlias = “<your device account’s alias>”
```
6. The user needs to be enabled in AD before it can authenticate with a Surface Hub. Run:
``` syntax
Set-ADUser $strAlias -Enabled $True
```
7. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information.
``` syntax
Set-ADUser $strAlias -PasswordNeverExpires $True
```
### <a href="" id="create-device-acct-exch-skype-for-business"></a>Enable the account with Skype for Business
Enable the device account with Skype for Business.
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.
1. Start by creating a remote PowerShell session from a PC.
```PowerShell
Import-Module LyncOnlineConnector
$cssess=New-CsOnlineSession -Credential $cred
Import-PSSession $cssess -AllowClobber
```
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
```PowerShell
Enable-CsMeetingRoom -Identity $rm -RegistrarPool
"sippoolbl20a04.infra.lync.com" -SipAddressType EmailAddress
```
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:
```PowerShell
Get-CsOnlineUser -Identity ‘alice@contoso.microsoft.com’| fl *registrarpool*
```

186
devices/surface-hub/create-and-test-a-device-account-surface-hub.md Normal file
View File

@ -0,0 +1,186 @@
---
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"]
author: TrudyHa
---
# Create and test a device account (Surface Hub)
This topic introduces how to create and test the device account that Microsoft Surface Hub uses to communicate with Microsoft Exchange and Skype.
A "device account" is an account that the Microsoft Surface Hub uses to:
- sync its meeting calendar,
- send mail,
- and enable Skype for Business compatibility.
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.
 
Every device account is unique to a single Surface Hub, and requires some setup:
- The device account must be configured correctly, as described in the folllowing sections.
- Your infrastructure must be configured to allow the Surface Hub to validate the device account, and to reach the appropriate Microsoft services.
You can think of a device account as the resource account that people recognize as a conference room’s or meeting space’s account. When you want to schedule a meeting using that conference room, you invite the account to that meeting. In order to use the Surface Hub most effectively, you do the same with the device account that's assigned to each one.
If you already have a resource mailbox account set up for the meeting space where you’re putting a Surface Hub, you can change that resource account into a device account. Once that’s done, all you need to do is add the device account to a Surface Hub. See step 2 of either [On-premises deployment](on-premises-deployment-surface-hub-device-accounts.md) or [Online deployment (Office 365)](online-deployment-surface-hub-device-accounts.md).
The following sections will describe how to create and test a device account before configuring your Surface Hub.
### Basic configuration
These properties represent the minimum configuration for a device account to work on a Surface Hub. Your device account may require further setup, which is covered in [Advanced configuration](#advanced-config).
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Property</th>
<th align="left">Purpose</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Exchange mailbox (Exchange 2010 or later, or Exchange Online)</p></td>
<td align="left"><p>Enabling the account with an Exchange mailbox gives the device account the capability to receive and send both mail and meeting requests, and to display a meetings calendar on the Surface Hub’s welcome screen. The Surface Hub mailbox must be a room mailbox.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Skype for Business-enabled (Lync/Skype for Business 2010 or later or Skype for Business Online)</p></td>
<td align="left"><p>Skype for Business must be enabled in order to use various conferencing features, like video calls, IM, and screen-sharing.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Password-enabled</p></td>
<td align="left"><p>The device account must be enabled with a password, or it cannot authenticate with either Exchange or Skype for Business.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Compatible EAS policies</p></td>
<td align="left"><p>The device account must use a compatible EAS policy in order for it to sync its mail and calendar. In order to implement this policy, the PasswordEnabled property must be set to False. If an incompatible EAS policy is used, the Surface Hub will not be able to use any services provided by Exchange and ActiveSync.</p></td>
</tr>
</tbody>
</table>
 
### <a href="" id="advanced-config"></a>Advanced configuration
While the properties for the basic configuration will allow the device account to be set up in a simple environment, it is possible your environment has other restrictions on directory accounts that must be met in order for the Surface Hub to successfully use the device account.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Property</th>
<th align="left">Purpose</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Certificate-based authentication</p></td>
<td align="left"><p>Certificates may be required for both ActiveSync and Skype for Business. To deploy certificates, you need to use provisioning packages or an MDM solution.</p>
<p>See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) for details.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Allowed device IDs (ActiveSync Device ID)</p></td>
<td align="left"><p>Your Exchange ActiveSync setup may require that an account must whitelist device IDs so that ActiveSync can retrieve the device account’s mail and calendar. You must ensure that the Surface Hub’s device ID is added to this whitelist. This can either be configured using PowerShell (by setting the <code>ActiveSyncAllowedDeviceIDs</code> property) or the Exchange administrative portal.</p>
<p>You can find out how to find and whitelist a device ID with PowerShell in [Allowing device IDs for ActiveSync](appendix-a-powershell-scripts-for-surface-hub.md#whitelisting-device-ids-cmdlet).</p></td>
</tr>
</tbody>
</table>
 
### How do I set up the account?
The best way to set up device accounts is to configure them using remote PowerShell. We provide several PowerShell scripts that will help create new device accounts, or validate existing resource accounts you have in order to help you turn them into compatible Surface Hub device accounts. These PowerShell scripts, and instructions for their use, are in [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md).
You can check online for updated versions at [Surface Hub device account scripts](http://aka.ms/surfacehubscripts).
### Device account configuration
Your infrastructure will likely fall into one of three configurations. Which configuration you have will affect how you prepare for device setup.
![](images/deploymentoptions-01.png)
- [Online deployment (Office 365)](online-deployment-surface-hub-device-accounts.md): Your organization’s environment is deployed entirely on Office 365.
- [On-premises deployment](on-premises-deployment-surface-hub-device-accounts.md): Your organization has servers that it controls, where Active Directory, Exchange, and Skype for Business (or Lync) are hosted.
- [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md): Your organization has a mix of services, with some hosted on-premises and some hosted online through Office 365.
If you prefer to use the Office 365 UI over PowerShell cmdlets, some steps can be performed manually. See [Creating a device account using Office 365](create-a-device-account-using-office-365.md).
### Device account resources
These sections describe resources used by the Surface Hub device account.
- [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md): The Exchange properties of the device account must be set to particular values for the Surface Hub to work properly.
- [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md): The Surface Hub uses ActiveSync to sync both mail and its meeting calendar.
- [Password management](password-management-for-surface-hub-device-accounts.md): Every device account requires a password to authenticate. This section describes your options for managing this password.
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Online deployment](online-deployment-surface-hub-device-accounts.md)</p></td>
<td align="left"><p>This topic has instructions for adding a device account for your Surface Hub when you have a pure, online deployment.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[On-premises deployment](on-premises-deployment-surface-hub-device-accounts.md)</p></td>
<td align="left"><p>This topic explains how you add a device account for your Surface Hub when you have a single-forest, on-premises deployment.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md)</p></td>
<td align="left"><p>A hybrid deployment requires special processing in order to set up a device account for your 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](#hybrid-exchange-on-prem), and [Exchange hosted online](#hybrid-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).)</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Create a device account using UI](create-a-device-account-using-office-365.md)</p></td>
<td align="left"><p>If you prefer to use a graphical user interface, you can create a device account for your Surface Hub with either the [Office 365 UI](#create-device-acct-o365) or the [Exchange Admin Center](#create-device-acct-eac).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md)</p></td>
<td align="left"><p>Some Exchange properties of the device account must be set to particular values to have the best meeting experience on Surface Hub. The following table lists various Exchange properties based on PowerShell cmdlet parameters, their purpose, and the values they should be set to.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md)</p></td>
<td align="left"><p>The 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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Password management](password-management-for-surface-hub-device-accounts.md)</p></td>
<td align="left"><p>Every Surface Hub device account requires a password to authenticate and enable features on the device.</p></td>
</tr>
</tbody>
</table>
 
 
 

44
devices/surface-hub/device-reset-suface-hub.md Normal file
View File

@ -0,0 +1,44 @@
---
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"]
author: TrudyHa
---
# Device reset (Surface Hub)
You may wish to reset your Microsoft Surface Hub.
Typical reasons for a reset include:
- The device isn’t running well after installing an update.
- You’re repurposing the device for a new meeting space and want to reconfigure it.
- You want to change how you locally manage the device.
Initiating a reset will return the device to the last cumulative Windows update, and remove all local user files and configuration, including:
- The device account
- MDM enrollment
- Domain join or Azure AD join information
- Local admins on the device
- Configurations from MDM or the Settings app.
After the reset, you'll be taken through the [first run program](first-run-program-surface-hub.md) again.
## Related topics
[Manage Microsoft Surface Hub](manage-surface-hub.md)
[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
 
 

96
devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md Normal file
View File

@ -0,0 +1,96 @@
---
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"]
author: TrudyHa
---
# Microsoft Exchange properties (Surface Hub)
Some Microsoft Exchange properties of the device account must be set to particular values to have the best meeting experience on Microsoft Surface Hub. The following table lists various Exchange properties based on PowerShell cmdlet parameters, their purpose, and the values they should be set to.
<table>
<colgroup>
<col width="25%" />
<col width="25%" />
<col width="25%" />
<col width="25%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Property</th>
<th align="left">Description</th>
<th align="left">Value</th>
<th align="left">Impact</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>AutomateProcessing</p></td>
<td align="left"><p>The AutomateProcessing parameter enables or disables calendar processing on the mailbox.</p></td>
<td align="left"><p>AutoAccept</p></td>
<td align="left"><p>The Surface Hub will be able to automatically accept or decline meeting requests based on its availability.</p></td>
</tr>
<tr class="even">
<td align="left"><p>AddOrganizerToSubject</p></td>
<td align="left"><p>The AddOrganizerToSubject parameter specifies whether the meeting organizer's name is used as the subject of the meeting request.</p></td>
<td align="left"><p>$False</p></td>
<td align="left"><p>The welcome screen will not show the meeting organizer twice (instead of showing it as both the organizer and in the meeting subject).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>AllowConflicts</p></td>
<td align="left"><p>The AllowConflicts parameter specifies whether to allow conflicting meeting requests.</p></td>
<td align="left"><p>$False</p></td>
<td align="left"><p>The Surface Hub will decline meeting requests that conflict with another meeting’s time.</p></td>
</tr>
<tr class="even">
<td align="left"><p>DeleteComments</p></td>
<td align="left"><p>The DeleteComments parameter specifies whether to remove or keep any text in the message body of incoming meeting requests.</p></td>
<td align="left"><p>$False</p></td>
<td align="left"><p>The message body of meetings can be retained and retrieved from a Surface Hub if you need it during a meeting.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>DeleteSubject</p></td>
<td align="left"><p>The DeleteSubject parameter specifies whether to remove or keep the subject of incoming meeting requests.</p></td>
<td align="left"><p>$False</p></td>
<td align="left"><p>Meeting request subjects can be shown on the Surface Hub.</p></td>
</tr>
<tr class="even">
<td align="left"><p>RemovePrivateProperty</p></td>
<td align="left"><p>The RemovePrivateProperty parameter specifies whether to clear the private flag for incoming meeting requests.</p></td>
<td align="left"><p>$False</p></td>
<td align="left"><p>Private meeting subjects will show as Private on the welcome screen.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>AddAdditionalResponse</p></td>
<td align="left"><p>The AddAdditionalResponse parameter specifies whether additional information will be sent from the resource mailbox when responding to meeting requests.</p></td>
<td align="left"><p>$True</p></td>
<td align="left"><p>When a response is sent to a meeting request, custom text will be provided in the response.</p></td>
</tr>
<tr class="even">
<td align="left"><p>AdditionalResponse</p></td>
<td align="left"><p>The AdditionalResponse parameter specifies the additional information to be included in responses to meeting requests.</p>
<div class="alert">
<strong>Note</strong>  This text will not be sent unless AddAdditionalResponse is set to $True.
</div>
<div>
 
</div></td>
<td align="left"><p>Your choice—the additional response can be used to inform people how to use a Surface Hub or point them towards resources.</p></td>
<td align="left"><p>Adding an additional response message can provide people an introduction to how they can use a Surface Hub in their meeting.</p></td>
</tr>
</tbody>
</table>
 
 
 

435
devices/surface-hub/first-run-program-surface-hub.md Normal file
View File

@ -0,0 +1,435 @@
---
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"]
author: TrudyHa
---
# First-run program (Surface Hub)
The term "first run" 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 "out-of-box experience" (OOBE). This section will walk you through the process.
By now, you should have gone through all of the previous steps:
- [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md)
- [Physically install your Surface Hub device](physically-install-your-surface-hub-device.md), and
- [Setup worksheet](setup-worksheet-surface-hub.md)
Assuming that's the case, first run should be both simple and quick.
The normal procedure goes through six steps:
1. [Hi there page](#first-page)
2. [Set up for you page](#set-up-for-you)
3. [Device account page](#device-account)
4. [Name this device page](#name-this-device)
5. [Set up admins for this device page](#setup-admins)
6. [Update the Surface Hub](#update-surface-hub)
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.
 
## <a href="" id="first-page"></a>Hi there page
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.
 
![icd options checklist](images/setuplocale.png)
### Details
If the default values shown are correct, then you can click **Next** to go on. Otherwise, you'll need to enter data in the appropriate boxes.
- **Country/region:** Select the country or region where the Surface Hub will be used.
- **App language:** Apps and features will display in this language and language format.
- **Keyboard layout:** Select the keyboard layout for the on-screen and physical keyboards that will be used with your device.
- **Time zone:** Select the time zone where the Surface Hub will be used.
### 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.
 
When the settings are accepted, the device will check for a wired network connection. If the connection is fine, it will display the [Set up for you page](#set-up-for-you). If there is a problem with the wired connection, the device will display the [Network setup page](#network-setup).
If no wired connection can be found, then the device will attempt to set up a wireless connection, and will display the [Network setup page](#network-setup).
## <a href="" id="network-setup"></a>Network setup page
If your device does not detect a wired connection that it can use to connect to a network or the Internet, you will see this page. Here you can either connect to a wireless network, or skip making the network connection.
![](images/setupnetworksetup-1.png)
### Details
This screen is shown only if the device fails to detect a wired network. If you see this screen, you have three choices:
- You can select one of the wireless networks shown. If the network is secured, you'll be taken to a login page. See [Wireless network setup](#wireless) for details.
- Click **Skip this step** to skip connecting to a network. 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 system updates and 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)).
 
- You can plug in a network cable while this screen is visible. The device will detect it, and will add **Next** to the screen. Click **Next** to continue with making the wired connection.
### What happens?
If the device has a wired connection when it starts, and can establish a network or Internet connection, then this page will not be displayed. If you want to connect the device to a wireless connection, make sure no Ethernet cable is plugged in at first run, which will bring you to this screen. No matter what you choose to set up now, you can [use Settings](wireless-network-management-for-surface-hub.md) to set up different connections later.
If you want to connect to a secured wireless network from this page, click on the network of your choice, and then provide the necessary information (password or account credentials) to connect. See [Wireless network setup](#wireless).
## <a href="" id="wireless"></a>Wireless network setup
This page will be shown when you've selected a secured wireless network.
![](images/setupnetworksetup-3.png)
### Details
- **User name:** Enter the user name for the selected wireless network.
- **Password:** This is the password for the network.
### What happens?
The device will attempt to connect to the specified network. If it's successful, you'll be taken to the [Set up for you page](#set-up-for-you).
## <a href="" id="proxy"></a>Network proxy setup
This page will be shown when the device detects a wired connection with limited connectivity. You have three options:
- You can select a wireless network to use instead of the limited wired connection.
- 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)).
 
- You can select **Enter proxy settings** which will allow you to specify how to use the network proxy. You'll be taken to the next screen.
![](images/setupnetworksetup-2.png)
This is the screen you'll see if you clicked **Enter proxy settings** on the previous screen.
![](images/setupnetworksetup-4.png)
### Details
In order to make a network connection, you'll need to fill in either a script name, or the proxy server and port info.
- **Proxy script:** Provide the address of a proxy script.
- **Proxy server and port:** You can provide the proxy server address and port.
### What happens?
When you click **Next**, the device will attempt to connect to the proxy server. If successful, you'll be taken to the [Set up for you page](#set-up-for-you).
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)).
 
## <a href="" id="set-up-for-you"></a>Set up for you page
This screen is purely informational, and shows which recommended settings have been enabled by default.
![](images/setupsetupforyou.png)
### Details
You should read this screen and note which services have been enabled by default. All of them can be changed using the Settings app if need be, but you should be careful about the effects of doing so. For example, Cortana depends on some of these settings, and may not work if you disable them. See [Intro to Surface Hub](intro-to-surface-hub.md) for details.
Once you're done reviewing the settings, click **Next** to go on.
### What happens?
The settings shown on the page have already been made, and can't be changed until after first run is completed.
## <a href="" id="device-account"></a>Device account page
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.
 
![icd options checklist](images/setupdeviceacct.png)
### Details
Use either a **user principal name (UPN)** or a **domain\\user name** as the account identifier in the first entry field.
- **User principal name:** This is the UPN of the device account for this Surface Hub. If you’re using Azure Active Directory (Azure AD) or a hybrid deployment, then you must enter the UPN of the device account.
- **Domain\\user name:** This is the identity of the device account for this Surface Hub, in domain\\user name format. If you’re using an Active Directory (AD) deployment, then you must enter the account in this format.
- **Password:** Enter the device account password.
Click **Skip setting up a device account** to skip setting up a device account. However, if you don't set up a device account, the device will not be fully integrated into your infrastructure. For example, people won't be able to:
- See a meeting calendar on the Welcome screen
- Start a meeting from the Welcome screen
- Start a meeting using Cortana
- Email whiteboards from OneNote
- Use Skype for Business for meetings.
If you skip setting it up now, you can add a device account later by using the Settings app.
If you click **Skip setting up a device account**, the device will display a dialog box showing what will happen if the device doesn't have a device account. If you choose **Yes, skip this**, you will be sent to the [Name this device page](#name-this-device).
![icd options checklist](images/setupskipdeviceacct.png)
### What happens?
The device will use the UPN or DOMAIN\\User name and password for the device account to do the following:
- Check if the account exists in Active Directory (AD) or Azure Active Directory (Azure AD):
- If a UPN was entered: the device will look for the account in Azure AD.
- If a DOMAIN\\User name was entered: the device will look for the account in AD.
- Look up the Microsoft Exchange server for the account’s mailbox.
- Look up the Session Initiation Protocol (SIP) address for the account.
- Pull the account’s display name and alias attributes.
## <a href="" id="exchange-server"></a>Exchange server page
This page will only be shown if there's a problem. Typically, it means that the device account that you provided was found in Active Directory (AD) or Azure Active Directory (Azure AD), but the Exchange server for the account was not discovered.
![icd options checklist](images/setupexchangeserver-01.png)
### Details
Enter the name of the Exchange server where the device account's mailbox is hosted.
Click **Skip setting up Exchange services** to skip this step. If you do, people will not be able to:
- See a meeting calendar on the welcome screen.
- Start a meeting from the welcome screen.
- Start a meeting using Cortana.
- Email whiteboards from OneNote.
See [Intro to Surface Hub](intro-to-surface-hub.md) for details on setup dependencies.
You can enable Exchange services for a device account later by using the Settings app.
If you click **Skip setting up Exchange services**, the device will display a dialog showing what will happen. If you choose **Yes, skip this**, then Exchange services will not be set up.
![icd options checklist](images/setupexchangeserver-02.png)
### What happens?
The Surface Hub will attempt to validate the device account on the Exchange server that you enter here. If the Exchange server can be reached and validates, then first run will proceed.
If you choose to skip setting up Exchange services, the Surface Hub will stop looking for the Exchange server, and no Exchange services (mail and calendar) will be enabled.
## <a href="" id="exchange-policies"></a>Exchange policies page
This page will be shown when:
- The device account is using an Exchange Active Sync (EAS) policy where the PasswordEnabled policy is set to 1.
- There’s no connection to Exchange.
- Exchange returns a status code indicating an error. (For example: The account has been provisioned to too many devices.)
- Exchange supported protocols are not supported by the Surface Hub.
- Exchange returns incorrect XML.
![icd options checklist](images/setupexchangepolicies.png)
### Details
This page is purely informational, so no input is required. However, you have two options for proceeding: either skipping ahead or retrying the validation that caused the error. Before deciding which option is best, please read the following **What happens?** section. You may be able to fix the problem elsewhere before you click on one of the options.
- **Click here to continue using unsupported policies**: click on this to continue first run. The Surface Hub will not be able to use Exchange services, or sync.
- **Retry**: check the policy on the Exchange server again.
### What happens?
The Surface Hub checks whether the device account’s EAS policy has the PasswordEnabled policy set to 0 (False). If this is not the case, mail and calendar can't be synced and the Surface Hub can't use any Exchange services. You can use your Exchange management tools from a PC to check that the device account has the PasswordEnabled policy set to 0. If that's not the case, you can reconfigure the account and click **Retry** here.
If the policy has already been configured properly, check that your device is properly connected to the network or Internet, and can reach your Exchange server, because this page will also be shown if the Surface Hub can't reach the Exchange server.
Another possible reason for not being able to reach Exchange is because of certificate-based authentication. You may wind up on this page because of certificate issues. Note that if the device displays error codes 0x80072F0D or 0X800C0019, then a certificate is required. Because provisioning is done on the first page of the first run process, you must disable Exchange services by clicking **Click here to continue using unsupported policies**, and then install the correct certificates through the Settings app.
If you choose to skip this check, the Surface Hub will stop looking for the Exchange server and validating EAS policies, and no Exchange services will be enabled. See [Intro to Surface Hub](intro-to-surface-hub.md) for details on setup dependencies.
## <a href="" id="name-this-device"></a>Name this device page
This page asks you to provide two names that will be used for identifying the Surface Hub.
![icd options checklist](images/setupnamedevice.png)
### Details
If the default values shown are correct, then you can click **Next** to go on. Otherwise, enter data in one or both of the text boxes.
- **Friendly name:** This is the name that people will see when they want to wirelessly connect to the Surface Hub.
- **Device name:** Can be set to any unique name as described on the screen.
As long as both names are within the length requirements and do not use restricted characters, clicking **Next** will take you to the next page, [Set up admins for this device](#setup-admins).
### What happens?
The Surface Hub requires two names for the device, which will default to:
- **Friendly name:** Defaults to the Display Name of the device account
- **Device name:** Defaults to the alias of the device account
While either of the names can be changed later, keep in mind that:
- The friendly name should be recognizable and different so that people can distinguish one Surface Hub from another when trying to wirelessly connect.
- If you decide to domain join the device, the device name must not be the same as any other device on the account’s Active Directory domain. The device can't join the domain if it is using the same name as another domain-joined device.
## <a href="" id="setup-admins"></a>Set up admins for this device page
On this page, you will choose from several options for how you want to set up admin accounts to locally manage your device.
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.
 
![icd options checklist](images/setupsetupadmins.png)
### Details
Choose one of the three available options:
- **Use Microsoft Azure Active Directory**
- **Use Active Directory Domain Services**
- **Use a local admin**
### What happens?
This is what happens when you choose an option.
- **Use Microsoft Azure Active Directory**
Clicking this option allows you to join the device to Azure AD. Once you click **Next**, the device will restart to apply some settings, and then you’ll be taken to the [Use Microsoft Azure Active Directory](#use-microsoft-azure) page and asked to enter credentials that can allow you to join Azure AD. After joining, admins from the joined organization will be able to use the Settings app. The specific people that will be allowed depends on your Azure AD subscription and how you’ve configured the settings for your Azure AD organization.
- **Use Active Directory Domain Services**
Click this option to join the device to AD. Once you click **Next**, you’ll be taken to the [Use Active Directory Domain Services](#use-active-directory) page and asked to enter credentials that allow you to join the specified domain. After joining, you can pick a security group from the joined domain, and people from that security group will be able to use the Settings app.
- **Use a local admin**
Choosing this option will allow you to create a single local admin. This admin won’t be backed by any directory service, so we recommend you only choose this case if the device does not have access to Azure AD or AD. Once you create an admin’s user name and password on the [Use a local admin](#use-a-local-admin) page, you will need to re-enter those same credentials whenever you open the Settings app.
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.
 
### <a href="" id="use-microsoft-azure"></a>Use Microsoft Azure Active Directory
If you've decided to join your Surface Hub to Azure Active Directory (Azure AD), you'll see this **What happens next** page. Read it and click **Next** to go to the **Let's get you signed in page**.
Joining Azure AD has two primary benefits:
1. Some employees from your organization will be able to access the device as admins, and will be able to start the Settings app and configure the device. People that have admin permissions will be defined in your Azure AD subscription.
2. If your Azure AD is connected to a mobile device management (MDM) solution, the device will enroll with that MDM solution so you can apply policies and configuration.
![](images/setupjoiningazuread-1.png)
### Details
The following input is required:
- **User's UPN:** The user principal name (UPN) of an account that can join Azure AD.
- **Password:** The password of the account you’re using to join Azure AD.
![](images/setupjoiningazuread-2.png)
If you get to this point and don't have valid credentials for an Azure AD account, the device will allow you to continue by creating a local admin account. Click **Set up Windows with a local account instead**.
![](images/setupjoiningazuread-3.png)
### What happens?
Once you enter valid Azure AD account credentials, the device will try to join the associated Azure AD organization. If this succeeds, then the device will provision employees in that organization to be local admins on the device. If your Azure AD tenant was configured for it, the device will also enroll into MDM.
### <a href="" id="use-active-directory"></a>Use Active Directory Domain Services
This page will ask for credentials to join a domain so that the Surface Hub can provision a security group as administrators of the device.
Once the device has been domain joined, you must specify a security group from the domain you joined. This security group will be provisioned as administrators on the Surface Hub, and anyone from the security group can enter their domain credentials to access Settings.
![icd options checklist](images/setupdomainjoin.png)
### Details
The following input is required:
- **Domain:** This is the fully qualified domain name (FQDN) of the domain that you want to join. A security group from this domain can be used to manage the device.
- **User name:** The user name of an account that has sufficient permission to join the specified domain.
- **Password:** The password for the account.
After the credentials are verified, you will be asked to type a security group name. This input is required.
![icd options checklist](images/setupsecuritygroup-1.png)
### What happens?
Using the provided domain, account credentials from the [Use Active Directory Domain Services page](#use-active-directory) and the device name from the [Name this device](#name-this-device) page, the Surface Hub will attempt to join the domain. If the join is successful, first run will continue, and will ask for a security group. If the join is not successful, first run will halt and ask you to change the information provided.
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.
 
### Use a local admin
If you decide not to use Azure Active Directory (Azure AD) or Active Directory (AD) to manage the Surface Hub, you'll need to create a local admin account.
![](images/setuplocaladmin.png)
### Details
The following input is required:
- **User name:** This is the user name of the local admin account that will be created for this Surface Hub.
- **Password:** This is the password of the device account.
- **Re-enter password:** Verifying the password as in the previous box.
### What happens?
This page will attempt to create a new admin account using the credentials that you enter here. If it's successful, then first run will end. If not, you'll be asked for different credentials.
## <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.
 
In order to get the latest features and fixes, you should update your Surface Hub as soon as you finish all of the preceding first-run steps.
1. Make sure the device has access to the Windows Update servers or to Windows Server Update Services (WSUS). To configure WSUS, see [Using WSUS](manage-windows-updates-for-surface-hub.md#using-wsus).
2. Open Settings, click **Update & security**, then **Windows Update**, and then click **Check for updates**.
3. If updates are available, they will be downloaded. Once downloading is complete, click the **Update now** button to install the updates.
4. Follow the onscreen prompts after the updates are installed. You may need to restart the device.
 
 

311
devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md Normal file
View File

@ -0,0 +1,311 @@
---
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"]
author: TrudyHa
---
# 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](#hybrid-exchange-on-prem), and [Exchange hosted online](#hybrid-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 ps1 (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 ps1 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.
1. For this procedure, you'll be using AD admin tools to add an email address for your on-prem domain account. This account will be synced to Office 365.
- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.<p>
![new object box for creating a new user in active directory](images/hybriddeployment-01a.png)
- 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.
![image showing password dialog box](images/hybriddeployment-02a.png)
- Click **Finish** to create the account.
![image with account name, logon name, and password options for new user](images/hybriddeployment-03a.png)
2. After you've created the account, run a directory synchronization. When it's complete, go to the users page in your Office 365 admin center and verify that the account created in the previous steps has merged to online.
3. Enable the remote mailbox.
Open your on-prem Exchange Management Shell with administrator permissions, and run this cmdlet.
```ps1
Enable-Mailbox &#39;HUB01@contoso.com&#39; -RemoteRoutingAddress &#39;HUB01@contoso.com&#39; -Room
```
5. Connect to Microsoft Exchange Online and set some properties for the account in Office 365.
Start a remote ps1 session on a PC and connect to Microsoft Exchange. Be sure you have the right permissions set to run the associated cmdlets.
The next steps will be run on your Office 365 tenant.
```ps1
Set-ExecutionPolicy Unrestricted
$org=&#39;contoso.com&#39;
$cred=Get-Credential $admin@$org
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri &#39;https://outlook.office365.com/ps1-liveid/&#39; -Credential $cred -Authentication Basic -AllowRedirection
Import-PSSession $sess
```
5. 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.
```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.
```ps1
Set-CASMailbox &#39;HUB01@contoso.com&#39; -ActiveSyncMailboxPolicy $easPolicy
```
6. Set Exchange properties.
Setting Exchange properties on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
```ps1
Set-CalendarProcessing -Identity &#39;HUB01@contoso.com&#39; -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
Set-CalendarProcessing -Identity &#39;HUB01@contoso.com&#39; -AddAdditionalResponse $true -AdditionalResponse &#39;This is a Surface Hub room!&#39;
```
7. Connect to Azure AD.
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
```ps1
Connect-MsolService -Credential $cred
```
8. Assign an Office 365 license.
The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
Next, you can use `Get-MsolAccountSku` to retrieve a list of available SKUs for your O365 tenant.
Once you list out the SKUs, you can add a license using the `Set-MsolUserLicense` cmdlet. In this case, `$strLicense` is the SKU code that you see (for example, *contoso:STANDARDPACK*).
```ps1
Set-MsolUser -UserPrincipalName &#39;HUB01@contoso.com&#39; -UsageLocation &#39;US&#39;
Get-MsolAccountSku
Set-MsolUserLicense -UserPrincipalName &#39;HUB01@contoso.com&#39; -AddLicenses $strLicense
```
9. Enable the device account with Skype for Business.
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.
- Start by creating a remote ps1 session from a PC.
```ps1
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:
```ps1
Enable-CsMeetingRoom -Identity $rm -RegistrarPool
&#39;sippoolbl20a04.infra.lync.com&#39; -SipAddressType EmailAddress
```
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*
```
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.
- Click on **Users and Groups** and then **Add users, reset passwords, and more**.
- Click the Surface Hub account, and then click the pen icon to edit the account information.
- Click **Licenses**.
- In **Assign licenses**, select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Surface Hub.
- 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.
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.
1. Create an email account in Office 365.
Start a remote ps1 session on a PC and connect to Exchange. Be sure you have the right permissions set to run the associated cmdlets.
```ps1
Set-ExecutionPolicy Unrestricted
$org=&#39;contoso.microsoft.com
$cred=Get-Credential $admin@$org
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/ps1-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
Import-PSSession $sess
```
2. Set up mailbox.
After establishing a session, you’ll either create a new mailbox and enable it as a RoomMailboxAccount, or change the settings for an existing room mailbox. This will allow the account to authenticate into the Surface Hub.
If you're changing an existing resource mailbox:
```ps1
Set-Mailbox -Identity &#39;HUB01&#39; -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
```
If you’re creating a new resource mailbox:
```ps1
New-Mailbox -MicrosoftOnlineServicesID &#39;HUB01@contoso.com&#39; -Alias HUB01 -Name "Hub-01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
```
3. Create Exchange ActiveSync 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.
```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. 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 &#39;HUB01@contoso.com&#39; -ActiveSyncMailboxPolicy $easPolicy
Set-Mailbox &#39;HUB01@contoso.com&#39; -Type Room
Set-Mailbox &#39;HUB01@contoso.com&#39; -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
```
4. Set Exchange properties.
Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
```ps1
Set-CalendarProcessing -Identity &#39;HUB01@contoso.com&#39; -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
Set-CalendarProcessing -Identity &#39;HUB01@contoso.com&#39; -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
```
5. Add email address for your on-prem domain account.
For this procedure, you'll be using AD admin tools to add an email address for your on-prem domain account.
- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.
![new object box for creating a new user in active directory](images/hybriddeployment-01a.png)
- 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.
![image showing password dialog box](images/hybriddeployment-02a.png)
- Click **Finish** to create the account.
![image with account name, logon name, and password options for new user](images/hybriddeployment-03a.png)
6. 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.
7. Connect to Azure AD.
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
```ps1
Connect-MsolService -Credential $cred
```
8. Assign an Office 365 license.
The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
Next, you can use `Get-MsolAccountSku` to retrieve a list of available SKUs for your O365 tenant.
Once you list out the SKUs, you can add a license using the `Set-MsolUserLicense` cmdlet. In this case, `$strLicense` is the SKU code that you see (for example, *contoso:STANDARDPACK*).
```ps1
Set-MsolUser -UserPrincipalName &#39;HUB01@contoso.com&#39; -UsageLocation &#39;US&#39;
Get-MsolAccountSku
Set-MsolUserLicense -UserPrincipalName &#39;HUB01@contoso.com&#39; -AddLicenses $strLicense
```
9. Enable the device account with Skype for Business.
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.
Start by creating a remote ps1 session from a PC.
```ps1
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:
```ps1
Enable-CsMeetingRoom -Identity $rm -RegistrarPool
&#39;sippoolbl20a04.infra.lync.com&#39; -SipAddressType EmailAddress
```
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*
```
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.
- Click on **Users and Groups** and then **Add users, reset passwords, and more**.
- Click the Surface Hub account, and then click the pen icon to edit the account information.
- Click **Licenses**.
- In **Assign licenses**, select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Surface Hub.
- 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.
For validation, you should be able to use any Skype for Business client (PC, Android, etc) to log in to this account.

BIN
devices/surface-hub/images/deploymentoptions-01.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 98 KiB

BIN
devices/surface-hub/images/hybriddeployment-01a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.0 KiB

BIN
devices/surface-hub/images/hybriddeployment-02a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 7.4 KiB

BIN
devices/surface-hub/images/hybriddeployment-03a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 7.6 KiB

BIN
devices/surface-hub/images/idcfeatureschecklist.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 102 KiB

BIN
devices/surface-hub/images/managesettingsmdm-enroll.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 63 KiB

BIN
devices/surface-hub/images/networkmgtwired-01.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 28 KiB

BIN
devices/surface-hub/images/networkmgtwired-02.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

BIN
devices/surface-hub/images/networkmgtwireless-01.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
devices/surface-hub/images/networkmgtwireless-02.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
devices/surface-hub/images/networkmgtwireless-03.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 19 KiB

BIN
devices/surface-hub/images/networkmgtwireless-04.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 19 KiB

BIN
devices/surface-hub/images/provisioningpackageoobe-01.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 132 KiB

BIN
devices/surface-hub/images/provisioningpackageoobe-02.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 169 KiB

BIN
devices/surface-hub/images/provisioningpackageoobe-03.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 182 KiB

BIN
devices/surface-hub/images/provisioningpackageoobe-04.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 123 KiB

BIN
devices/surface-hub/images/provisioningpackagesettings-01.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 10 KiB

BIN
devices/surface-hub/images/provisioningpackagesettings-02.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 9.7 KiB

BIN
devices/surface-hub/images/provisioningpackagesettings-03.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.1 KiB

BIN
devices/surface-hub/images/roomcontrolwiring.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.4 KiB

BIN
devices/surface-hub/images/setupdeviceacct.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 93 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-01.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 56 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-02.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 19 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-03.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 56 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-05.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 62 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-06.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 25 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-07.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 66 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-08.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 26 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-09.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 10 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-10.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 12 KiB

BIN
devices/surface-hub/images/setupdeviceacctexch-11.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-02.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 66 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-03.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 57 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-04.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 28 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-05.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-06.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 64 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-07.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 23 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-08.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 49 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-09.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 50 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-10.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 35 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-11.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 25 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-12.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-13.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 26 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-14.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 10 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-15.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 12 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-16.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 16 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-17.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 12 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-18.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 63 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-19.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 42 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-20.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 45 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-21.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 76 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-22.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 119 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-23.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 43 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-24.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 75 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-25.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 98 KiB

BIN
devices/surface-hub/images/setupdeviceaccto365-26.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 56 KiB

BIN
devices/surface-hub/images/setupdomainjoin.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 484 KiB

BIN
devices/surface-hub/images/setupexchangepolicies.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 294 KiB

BIN
devices/surface-hub/images/setupexchangeserver-01.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 279 KiB

BIN
devices/surface-hub/images/setupexchangeserver-02.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 167 KiB

BIN
devices/surface-hub/images/setupjoiningazuread-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 43 KiB

BIN
devices/surface-hub/images/setupjoiningazuread-2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 44 KiB

BIN
devices/surface-hub/images/setupjoiningazuread-3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 45 KiB

BIN
devices/surface-hub/images/setuplocaladmin.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 452 KiB

BIN
devices/surface-hub/images/setuplocale.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 401 KiB

BIN
devices/surface-hub/images/setupnamedevice.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 123 KiB

BIN
devices/surface-hub/images/setupnetworksetup-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 130 KiB

BIN
devices/surface-hub/images/setupnetworksetup-2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 137 KiB

BIN
devices/surface-hub/images/setupnetworksetup-3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 193 KiB

BIN
devices/surface-hub/images/setupnetworksetup-4.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 200 KiB

BIN
devices/surface-hub/images/setupsecuritygroup-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 457 KiB

BIN
devices/surface-hub/images/setupsetupadmins.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 237 KiB

BIN
devices/surface-hub/images/setupsetupforyou.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 220 KiB

BIN
devices/surface-hub/images/setupskipdeviceacct.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 110 KiB

BIN
devices/surface-hub/images/wicd-screen-apps-02a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 9.1 KiB

BIN
devices/surface-hub/images/wicd-screen-apps-03a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 62 KiB

BIN
devices/surface-hub/images/wicd-screen-apps-04a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 75 KiB

BIN
devices/surface-hub/images/wicd-screen-apps-06a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 76 KiB

BIN
devices/surface-hub/images/wicd-screen-apps-08a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.0 KiB

BIN
devices/surface-hub/images/wicd-screen-apps-10a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.6 KiB

BIN
devices/surface-hub/images/wicd-screen-apps-11a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 11 KiB

BIN
devices/surface-hub/images/wicd-screen-apps-12a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
devices/surface-hub/images/wicd-screen01a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
devices/surface-hub/images/wicd-screen02a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 9.3 KiB

BIN
devices/surface-hub/images/wicd-screen02b.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.0 KiB

BIN
devices/surface-hub/images/wicd-screen02c.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.7 KiB

BIN
devices/surface-hub/images/wicd-screen03a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 67 KiB

BIN
devices/surface-hub/images/wicd-screen04a.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 75 KiB

Some files were not shown because too many files have changed in this diff Show More