deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 20:03:40 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

new build 4/20/16

Browse Source
This commit is contained in:
Brian Lich
2016-04-20 11:35:24 -07:00
parent 984c4d3651
commit b96c0a192b
5 changed files with 490 additions and 255 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -288,19 +288,19 @@ You can use the Exchange Admin Center to create a device account:
5. To apply the ActiveSync policy without using PowerShell, you can do the following:
1. In the EAC, click **Recipients** > **Mailboxes** and select a mailbox.
- In the EAC, click **Recipients** > **Mailboxes** and select a mailbox.
![image showing exchange admin center. ](images/setupdeviceacctexch-08.png)
2. In the **Details** pane, scroll to **Phone and Voice Features** and click **View details** to display the **Mobile Device Details** screen.
- 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)
3. The mobile device mailbox policy that’s currently assigned is displayed. To change the mobile device mailbox policy, click **Browse**.
- 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)
4. Choose the appropriate mobile device mailbox policy from the list, click **OK** and then click **Save**.
- 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)

52
devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md
View File

@ -18,18 +18,18 @@ 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.
1. 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**.
2. Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.
- 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)
3. 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.
- 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**  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)
4. Click **Finish** to create the account.
- Click **Finish** to create the account.
![image with account name, logon name, and password options for new user. ](images/hybriddeployment-03a.png)
@ -112,7 +112,9 @@ Use this procedure if you use Exchange on-prem.
- 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.
<!-- -->
- Start by creating a remote PowerShell session from a PC.
```PowerShell
Import-Module LyncOnlineConnector
@ -120,7 +122,7 @@ Use this procedure if you use Exchange on-prem.
Import-PSSession $cssess -AllowClobber
```
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
- To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
```PowerShell
Enable-CsMeetingRoom -Identity $rm -RegistrarPool
@ -137,12 +139,12 @@ Use this procedure if you use Exchange on-prem.
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.
1. Login as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
2. Click on **Users and Groups** and then **Add users, reset passwords, and more**.
3. Click the Surface Hub account, and then click the pen icon to edit the account information.
4. Click **Licenses**.
5. 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.
6. Click **Save**.
- 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**  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.
@ -217,18 +219,18 @@ Use this procedure if you use Exchange online.
For this procedure, you'll be using AD admin tools to add an email address for your on-prem domain account.
1. 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**.
2. Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.
- 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)
3. 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.
- 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**  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)
4. Click **Finish** to create the account.
- Click **Finish** to create the account.
![image with account name, logon name, and password options for new user. ](images/hybriddeployment-03a.png)
@ -267,7 +269,9 @@ Use this procedure if you use Exchange online.
- 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.
<!-- -->
- Start by creating a remote PowerShell session from a PC.
```PowerShell
Import-Module LyncOnlineConnector
@ -275,7 +279,7 @@ Use this procedure if you use Exchange online.
Import-PSSession $cssess -AllowClobber
```
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
- To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
```PowerShell
Enable-CsMeetingRoom -Identity $rm -RegistrarPool
@ -292,12 +296,12 @@ Use this procedure if you use Exchange online.
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.
1. Login as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
2. Click on **Users and Groups** and then **Add users, reset passwords, and more**.
3. Click the Surface Hub account, and then click the pen icon to edit the account information.
4. Click **Licenses**.
5. 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.
6. Click **Save**.
- 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**  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.

18
devices/surface-hub/online-deployment-surface-hub-device-accounts.md
View File

@ -100,7 +100,9 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
- 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.
<!-- -->
- Start by creating a remote PowerShell session from a PC.
```PowerShell
Import-Module LyncOnlineConnector
@ -108,7 +110,7 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
Import-PSSession $cssess -AllowClobber
```
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
- To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
```PowerShell
Enable-CsMeetingRoom -Identity $rm -RegistrarPool
@ -125,12 +127,12 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
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.
1. Login as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
2. Click on **Users and Groups** and then **Add users, reset passwords, and more**.
3. Select the Surface Hub account, and then click or tap the pen icon, which means edit.
4. Click on the **Licenses** option.
5. In the **Assign licenses** section, you need to select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and what you've decided in terms of needing Enterprise Voice. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Surface Hub.
6. Click **Save** and you're done.
- 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**.
- Select the Surface Hub account, and then click or tap the pen icon, which means edit.
- Click on the **Licenses** option.
- In the **Assign licenses** section, you need to select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and what you've decided in terms of needing Enterprise Voice. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Surface Hub.
- Click **Save** and you're done.
**Note**  It's also possible to use the Windows Azure Active Directory Module for Windows PowerShell to run the cmdlets needed to assign one of these licenses, but that's not covered here.

315
devices/surface-hub/setup-worksheet-surface-hub.md
View File

@ -13,99 +13,228 @@ When you've finished pre-setup and are ready to start first-time setup for your
You should fill out one list for each Surface Hub you need to configure, although some information can be used on all Surface Hubs, like the proxy information or domain credentials. Some of this information may not be needed, depending on how you've decided to configure your device, or depending on how the environment is configured for your organization's infrastructure.
Property
What this is used for
Example
Actual value
Proxy information
If your network uses a proxy to for network and/or Internet access, you must provide a script or server/port information.
http://contoso/proxy.pa (proxy script) OR 10.10.10.100, port 8080 (server, port)
Wireless network credentials (username and password)
If you decide to connect your device to Wi-Fi, and your wireless network requires user credentials.
admin1@contoso.com, \#MyPassw0rd
Device account UPN or Domain\\username and device account password
This is the User Principal Name (UPN) or the domain\\username, and the password of the device account. Mail, calendar, and Skype for Business depend on a compatible device account.
ConfRoom15@contoso.com, \#Passw0rd1 (for UPN) OR CONTOSO\\ConfRoom15, \#Passw0rd1 (for Domain\\username)
Device account Microsoft Exchange server
This is the device account's Exchange server. Mail, calendar, and Skype for Business depend on a compatible device account. For mail and calendar to work, the device account must have a valid Exchange server. The device will try to find this automatically.
outlook.office365.com
Device account Session Initiation Protocol (SIP) address
This is the device account's Skype for Business SIP address. Mail, calendar, and Skype for Business depend on a compatible device account. For Skype for Business to work, the device account must have a valid SIP address. The device will try to find this automatically.
sip:ConfRoom15@contoso.com
Friendly name
The friendly name of the device is the broadcast name that people will see when they try to wirelessly connect to the Surface Hub. This name will be displayed prominently on the Surface Hub's screen. We suggest that the friendly name you choose is recognizable and unique so that people can distinguish one Surface Hub from another when trying to connect.
Conference Room 15
Device name
The device name is the name that will be used for domain join, and is the identity you will see in your MDM provider if the device is enrolled into MDM. The device name you choose must not be the same name as any other device on the user’s Active Directory domain (if you decide to domain join the device). The device cannot join the domain if its name is not unique.
confroom15
**IF YOU'RE JOINING AZURE AD**
Azure AD tenant user credentials (username and password)
If you decide to have people in your Azure Active Directory (Azure AD) organization become admins on the device, then you'll need to join Azure AD. To join Azure AD, you will need valid user credentials.
admin1@contoso.com, \#MyPassw0rd
**IF YOU'RE JOINING A DOMAIN**
Domain to join
This is the domain you will need to join so that a security group of your choice can be admins for the device. You may need the fully qualified domain name (FQDN).
contoso (short name) OR contoso.corp.com (FQDN)
Domain account credentials (username and password)
A domain can't be joined unless you provide sufficient account credentials to join the domain. Once you provide a domain to join and credentials to join the domain, then a security group of your choice can change settings on the device.
admin1, \#MyPassw0rd
Admin security group alias
This is a security group in your Active Directory (AD); any members of this security group can change settings on the device.
SurfaceHubAdmins
**IF YOU'RE USING A LOCAL ADMIN**
Local admin account credentials (username and password)
If you decide not to join an AD domain or Azure AD, you can create a local admin account on the device.
admin1, \#MyPassw0rd
**IF YOU NEED TO INSTALL CERTIFICATES OR APPS**
USB drive
If you know before first run that you want to install certificates or universal apps, follow the steps in [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md). Your provisioning packages will be created on a USB drive.
 
 
 
<table>
<tr>
<th>Property</th>
<th>What this is used for</th>
<th>Example</th>
<th>Actual value</th>
</tr>
<tr>
<td>
<p>Proxy information</p>
</td>
<td>
<p>If your network uses a proxy to for network and/or Internet access, you must provide a script or server/port information.</p>
</td>
<td>
<p>http://contoso/proxy.pa (proxy script)
OR
10.10.10.100, port 8080 (server, port)
</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>Wireless network credentials (username and password)</p>
</td>
<td>
<p>If you decide to connect your device to Wi-Fi, and your wireless network requires user credentials.</p>
</td>
<td>
<p>admin1@contoso.com, #MyPassw0rd</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>Device account UPN or Domain\username and device account password</p>
</td>
<td>
<p>This is the User Principal Name (UPN) or the domain\username, and the password of the device account. Mail, calendar, and Skype for Business depend on a compatible device account.</p>
</td>
<td>
<p>ConfRoom15@contoso.com, #Passw0rd1 (for UPN) OR CONTOSO\ConfRoom15, #Passw0rd1 (for Domain\username)</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>Device account Microsoft Exchange server</p>
</td>
<td>
<p>This is the device account's Exchange server.
Mail, calendar, and Skype for Business depend on a compatible device account.
For mail and calendar to work, the device account must have a valid Exchange server. The device will try to find this automatically.</p>
</td>
<td>
<p>outlook.office365.com</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>Device account Session Initiation Protocol (SIP) address</p>
</td>
<td>
<p>This is the device account's Skype for Business SIP address.
Mail, calendar, and Skype for Business depend on a compatible device account.
For Skype for Business to work, the device account must have a valid SIP address. The device will try to find this automatically.</p>
</td>
<td>
<p>sip:ConfRoom15@contoso.com</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>Friendly name</p>
</td>
<td>
<p>The friendly name of the device is the broadcast name that people will see when they try to wirelessly connect to the Surface Hub. This name will be displayed prominently on the Surface Hub's screen.
We suggest that the friendly name you choose is recognizable and unique so that people can distinguish one Surface Hub from another when trying to connect.</p>
</td>
<td>
<p>Conference Room 15</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>Device name</p>
</td>
<td>
<p>The device name is the name that will be used for domain join, and is the identity you will see in your MDM provider if the device is enrolled into MDM.
The device name you choose must not be the same name as any other device on the user’s Active Directory domain (if you decide to domain join the device). The device cannot join the domain if its name is not unique.
</p>
</td>
<td>
<p>confroom15</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td colspan="4">
<p><b>IF YOU'RE JOINING AZURE AD</b></p>
</td>
</tr>
<tr>
<td>
<p>Azure AD tenant user credentials (username and password)</p>
</td>
<td>
<p>If you decide to have people in your Azure Active Directory (Azure AD) organization become admins on the device, then you'll need to join Azure AD.
To join Azure AD, you will need valid user credentials.</p>
</td>
<td>
<p>admin1@contoso.com, #MyPassw0rd</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td colspan="4">
<p><b>IF YOU'RE JOINING A DOMAIN</b></p>
</td>
</tr>
<tr>
<td>
<p>Domain to join</p>
</td>
<td>
<p>This is the domain you will need to join so that a security group of your choice can be admins for the device.
You may need the fully qualified domain name (FQDN).</p>
</td>
<td>
<p>contoso (short name) OR contoso.corp.com (FQDN)</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>Domain account credentials (username and password)</p>
</td>
<td>
<p>A domain can't be joined unless you provide sufficient account credentials to join the domain. Once you provide a domain to join and credentials to join the domain, then a security group of your choice can change settings on the device.</p>
</td>
<td>
<p>admin1, #MyPassw0rd</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>Admin security group alias</p>
</td>
<td>
<p>This is a security group in your Active Directory (AD); any members of this security group can change settings on the device.</p>
</td>
<td>
<p>SurfaceHubAdmins</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td colspan="4">
<p><b>IF YOU'RE USING A LOCAL ADMIN</b></p>
</td>
</tr>
<tr>
<td>
<p>Local admin account credentials (username and password)</p>
</td>
<td>
<p>If you decide not to join an AD domain or Azure AD, you can create a local admin account on the device.</p>
</td>
<td>
<p>admin1, #MyPassw0rd</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td colspan="4">
<p><b>IF YOU NEED TO INSTALL CERTIFICATES OR APPS</b></p>
</td>
</tr>
<tr>
<td>
<p>USB drive</p>
</td>
<td>
<p>If you know before first run that you want to install certificates or universal apps, follow the steps in <a href="prepare_your_environment_for_surface_hub_create_provisioning_packages_for_certificates.htm">Create provisioning packages</a>. Your provisioning packages will be created on a USB drive.</p>
</td>
<td>
<p></p>
</td>
<td>
<p></p>
</td>
</tr>
</table> 

352
devices/surface-hub/troubleshoot-surface-hub.md
View File

@ -25,60 +25,107 @@ This section lists causes, and possible fixes to help troubleshoot issues you mi
Possible fixes for issues on the Surface Hub after you've completed the first-run program.
Issue
Causes
Possible fixes
Not receiving automatic accept/decline messages.
The device account isn't configured to automatically accept/decline messages.
Use PowerShell`cmdlet Set-CalendarProcessing $upn -AutomateProcessing AutoAccept`.
The device account isn't configured to process external meeting requests.
Use PowerShell cmdlet `Set-CalendarProcessing $upn -ProcessExternalMeetingMessages $true`.
Calendar is not showing on the Welcome screen, or message "Appointments of date (no account provisioned)" is being displayed.
No device account is set up on this Surface Hub.
Provision a device account through Settings.
Calendar is not showing on the Welcome screen or message "Appointments of date (overprovisioned)" is being displayed.
The device account is provisioned on too many devices.
Remove the device account from other devices that it's provisioned to. This can be done using the Exchange admin portal.
Calendar is not showing on the Welcome screen or message "Appointments of date (invalid credentials)" is being displayed.
The device account's password has expired and is no longer valid.
Update the account's password in Settings. Also see [Password management](password-management-for-surface-hub-device-accounts.md).
Calendar is not showing on the Welcome screen or message "Appointments of date (account policy)" is being displayed.
The device account is using an invalid ActiveSync policy.
Make sure the device account has an ActiveSync policy where `PasswordEnabled == False`.
Calendar is not showing on the Welcome screen or message "Appointments may be out of date" is being displayed.
Exchange is not enabled.
Enable the device account for Exchange services through Settings. You need to make sure you have the right set of ActiveSync policies and have also installed any necessary certificates for Exchange services to work.
Can't log in to Skype for Business.
The device account does not have a Session Initiation Protocol (SIP) address property.
The account does not have a SIP address property and its User Principal Name (UPN) does not match the actual SIP address. The account must have its SIP address set, or the SIP address should be added using the Settings app.
Can't log in to Skype for Business.
The device account requires a certificate to authenticate into Skype for Business.
Install the appropriate certificate using provisioning packages.
<table>
<tr>
<th>Issue</th>
<th>Causes</th>
<th>Possible fixes</th>
</tr>
<tr>
<td rowspan="2">
<p>Not receiving automatic accept/decline messages.</p>
</td>
<td>
<p>The device account isn't configured to automatically accept/decline messages.</p>
</td>
<td>
<p>Use PowerShell<code>cmdlet Set-CalendarProcessing $upn -AutomateProcessing AutoAccept</code>.</p>
</td>
</tr>
<tr>
<td>
<p>The device account isn't configured to process external meeting requests.</p>
</td>
<td>
<p>Use PowerShell cmdlet <code>Set-CalendarProcessing $upn -ProcessExternalMeetingMessages $true</code>.</p>
</td>
</tr>
<tr>
<td>
<p>Calendar is not showing on the Welcome screen, or message "Appointments of date (no account provisioned)" is being displayed.</p>
</td>
<td>
<p>No device account is set up on this Surface Hub.</p>
</td>
<td>
<p>Provision a device account through Settings.</p>
</td>
</tr>
<tr>
<td>
<p>Calendar is not showing on the Welcome screen or message "Appointments of date (overprovisioned)" is being displayed.</p>
</td>
<td>
<p>The device account is provisioned on too many devices.</p>
</td>
<td>
<p>Remove the device account from other devices that it's provisioned to. This can be done using the Exchange admin portal.</p>
</td>
</tr>
<tr>
<td>
<p>Calendar is not showing on the Welcome screen or message "Appointments of date (invalid credentials)" is being displayed.</p>
</td>
<td>
<p>The device account's password has expired and is no longer valid.</p>
</td>
<td>
<p>Update the account's password in Settings. Also see <a href="prepare_your_environment_for_surface_hub_how_do_i_password_management.htm">Password management</a>.</p>
</td>
</tr>
<tr>
<td>
<p>Calendar is not showing on the Welcome screen or message "Appointments of date (account policy)" is being displayed.</p>
</td>
<td>
<p>The device account is using an invalid ActiveSync policy.</p>
</td>
<td>
<p>Make sure the device account has an ActiveSync policy where <code>PasswordEnabled == False</code>.</p>
</td>
</tr>
<tr>
<td>
<p>Calendar is not showing on the Welcome screen or message "Appointments may be out of date" is being displayed.</p>
</td>
<td>
<p>Exchange is not enabled.</p>
</td>
<td>Enable the device account for Exchange services through Settings. You need to make sure you have the right set of ActiveSync policies and have also installed any necessary certificates for Exchange services to work.</td>
</tr>
<tr>
<td>
<p>Can't log in to Skype for Business.</p>
</td>
<td>
<p>The device account does not have a Session Initiation Protocol (SIP) address property.</p>
</td>
<td>
<p>The account does not have a SIP address property and its User Principal Name (UPN) does not match the actual SIP address. The account must have its SIP address set, or the SIP address should be added using the Settings app.</p>
</td>
</tr>
<tr>
<td>
<p>Can't log in to Skype for Business.</p>
</td>
<td>
<p>The device account requires a certificate to authenticate into Skype for Business.</p>
</td>
<td>
<p>Install the appropriate certificate using provisioning packages.</p>
</td>
</tr>
</table>
 
### First run
@ -152,78 +199,131 @@ Possible fixes for issues with Surface Hub first-run program.
### Device account page, issues for existing account settings
Issue
Causes
Error codes
Possible fixes
Account could not authenticate with the specified credentials.
The account is not enabled as a user in Active Directory (AD), needs a password to authenticate, or the password is incorrect.
None
Make sure the credentials are entered correctly. Enable the account as a user in AD and add a password, or set the RoomMailboxPassword
.
Error 0x800C0019 is displayed when providing an Exchange server.
The device account requires a certificate to authenticate.
0x800C0019
Install the appropriate certificate using provisioning packages.
Device account credentials are not valid for the provided Exchange server.
The provided Exchange server is not where the device account's mailbox is hosted.
None
Make sure you are providing the correct Exchange mail server for the device account.
HTTP timeout while trying to reach Exchange server.
0x80072EE2
Couldn't find the provided Exchange server.
The Exchange server provided could not be found.
None
Ensure that you have a working network or Internet connection, and that the Exchange server you provided is correct.
http not supported.
An Exchange server with *http://* instead of *https://* was provided.
None
Use an Exchange server that uses https.
**Note**  
People land on the page titled "There's a problem with this account" regarding ActiveSync.
 
The ActiveSync policy PasswordEnabled is set to True (or 1).
None
Create a new ActiveSync policy where PasswordEnabled is set to False (or 0), and then apply that policy to the account.
The Surface Hub doesn't have a connection to Exchange.
None
Make sure that you have a working network or Internet connection.
Exchange returns a status code indicating an error.
None
Make sure that you have a working network or Internet connection.
<table>
<tr>
<th>Issue</th>
<th>Causes</th>
<th>Error codes</th>
<th>Possible fixes</th>
</tr>
<tr>
<td>
<p>Account could not authenticate with the specified credentials.</p>
</td>
<td>
<p>The account is not enabled as a user in Active Directory (AD), needs a password to authenticate, or the password is incorrect.</p>
</td>
<td>
<p>None</p>
</td>
<td>
<p>Make sure the credentials are entered correctly. Enable the account as a user in AD and add a password, or set the RoomMailboxPassword</p>. </td>
</tr>
<tr>
<td>
<p>Error 0x800C0019 is displayed when providing an Exchange server.</p>
</td>
<td>
<p>The device account requires a certificate to authenticate.</p>
</td>
<td>
<p>0x800C0019</p>
</td>
<td>
<p>Install the appropriate certificate using provisioning packages.</p>
</td>
</tr>
<tr>
<td>
<p>Device account credentials are not valid for the provided Exchange server.</p>
</td>
<td>
<p>The provided Exchange server is not where the device account's mailbox is hosted.</p>
</td>
<td>
<p>None</p>
</td>
<td>
<p>Make sure you are providing the correct Exchange mail server for the device account.</p>
</td>
</tr>
<tr>
<td>
<p>HTTP timeout while trying to reach Exchange server.</p>
</td>
<td></td>
<td>
<p>0x80072EE2</p>
</td>
<td></td>
</tr>
<tr>
<td>
<p>Couldn't find the provided Exchange server.</p>
</td>
<td>
<p>The Exchange server provided could not be found.</p>
</td>
<td>
<p>None</p>
</td>
<td>
<p>Ensure that you have a working network or Internet connection, and that the Exchange server you provided is correct.</p>
</td>
</tr>
<tr>
<td>
<p>http not supported.</p>
</td>
<td>
<p>An Exchange server with <i>http://</i> instead of <i>https://</i> was provided.</p>
</td>
<td>
<p>None</p>
</td>
<td>
<p>Use an Exchange server that uses https.</p>
</td>
</tr>
<tr>
<td rowspan="3">
<div class="alert"><b>Note</b>  <p class="note">People land on the page titled "There's a problem with this account" regarding ActiveSync.</p>
</div>
<div> </div>
</td>
<td>
<p>The ActiveSync policy PasswordEnabled is set to True (or 1).</p>
</td>
<td>
<p>None</p>
</td>
<td>
<p>Create a new ActiveSync policy where PasswordEnabled is set to False (or 0), and then apply that policy to the account.</p>
</td>
</tr>
<tr>
<td>
<p>The Surface Hub doesn't have a connection to Exchange.</p>
</td>
<td>
<p>None</p>
</td>
<td>
<p>Make sure that you have a working network or Internet connection.</p>
</td>
</tr>
<tr>
<td>
<p>Exchange returns a status code indicating an error.</p>
</td>
<td>
<p>None</p>
</td>
<td>
<p>Make sure that you have a working network or Internet connection.</p>
</td>
</tr>
</table>
 
### <a href="" id="first-run-domain-join-page"></a>First run, Domain join page issues