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

This commit is contained in:
LizRoss
2017-01-03 13:32:20 -08:00
3 changed files with 17 additions and 6 deletions

View File

@ -14,6 +14,12 @@ localizationpriority: medium
This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md). This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md).
## January 2017
| New or changed topic | Description |
| --- | --- |
| [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md) | Added graphics cards verified to work with 84" Surface Hubs and added information about the lengths of cables. |
## December 2016 ## December 2016
| New or changed topic | Description| | New or changed topic | Description|

View File

@ -251,7 +251,7 @@ In Replacement PC Mode, Surface Hub supports any graphics adapter that can produ
**55" Surface Hubs** - For best experience, use a graphics card capable of 1080p resolution at 120Hz. **55" Surface Hubs** - For best experience, use a graphics card capable of 1080p resolution at 120Hz.
**84" Surface Hubs** - For best experience, use a graphics card capable of outputting four DisplayPort 1.2 streams to produce 2160p at 120Hz (3840 x 2160 at 120Hz vertical refresh). We've verified that this works with the NVIDIA Quadro K2200, NVIDIA Quadro K4200, and NVIDIA Quadro M6000. These are not the only graphics cards - others are available from other vendors. **84" Surface Hubs** - For best experience, use a graphics card capable of outputting four DisplayPort 1.2 streams to produce 2160p at 120Hz (3840 x 2160 at 120Hz vertical refresh). We've verified that this works with the NVIDIA Quadro K2200, NVIDIA Quadro K4200, NVIDIA Quadro M6000, AMD FirePro W5100, AMD FirePro W7100, and AMD FirePro W9100. These are not the only graphics cards - others are available from other vendors.
Check directly with graphics card vendors for the latest drivers. Check directly with graphics card vendors for the latest drivers.
@ -273,7 +273,7 @@ Check directly with graphics card vendors for the latest drivers.
</tr> </tr>
<tr class="even"> <tr class="even">
<td><p>AMD</p></td> <td><p>AMD</p></td>
<td><p>[http://support.amd.com/download](http://support.amd.com/download)</p></td> <td><p>[http://support.amd.com/en-us/download](http://support.amd.com/en-us/download)</p></td>
</tr> </tr>
<tr class="odd"> <tr class="odd">
<td><p>Intel</p></td> <td><p>Intel</p></td>
@ -470,6 +470,11 @@ Video Out port on the 84" Surface Hub
</tbody> </tbody>
</table> </table>
## Cables
Both the 55” and 84” Surface Hub devices have been tested to work with Certified DisplayPort and HDMI cables. While vendors do sell longer cables that may work with the Surface Hub, only those cables that have been certified by testing labs are certain to work with the Hub. For example, DisplayPort cables are certified only up to 3 meters, however many vendors sell cables that are 3 times that length. If a long cable is necessary, we strongly suggest using HDMI. HDMI has many cost-effective solutions for long-haul cables, including the use of repeaters. Nearly every DisplayPort source will automatically switch to HDMI signaling if a HDMI sink is detected.
## Bluetooth accessories ## Bluetooth accessories
You can connect the following accessories to Surface Hub using Bluetooth: You can connect the following accessories to Surface Hub using Bluetooth:

View File

@ -107,10 +107,10 @@ When you run Windows ICD, you have several options for creating your package.
> [!WARNING] > [!WARNING]
> If you don't create a local administrator account and the device fails to enroll in Active Directory for any reason, you will have to reimage the device and start over. As a best practice, we recommend: > If you don't create a local administrator account and the device fails to enroll in Active Directory for any reason, you will have to reimage the device and start over. As a best practice, we recommend:
>
- Use a least-privileged domain account to join the device to the domain. >- Use a least-privileged domain account to join the device to the domain.
- Create a temporary administrator account to use for debugging or reprovisioning if the device fails to enroll successfully. >- Create a temporary administrator account to use for debugging or reprovisioning if the device fails to enroll successfully.
- [Use Group Policy to delete the temporary administrator account](https://blogs.technet.microsoft.com/canitpro/2014/12/10/group-policy-creating-a-standard-local-admin-account/) after the device is enrolled in Active Directory. >- [Use Group Policy to delete the temporary administrator account](https://blogs.technet.microsoft.com/canitpro/2014/12/10/group-policy-creating-a-standard-local-admin-account/) after the device is enrolled in Active Directory.
9. Click **Finish**. 9. Click **Finish**.
10. Review your settings in the summary. You can return to previous pages to change your selections. Then, under **Protect your package**, toggle **Yes** or **No** to encrypt the provisioning package. If you select **Yes**, enter a password. This password must be entered to apply the encrypted provisioning package. 10. Review your settings in the summary. You can return to previous pages to change your selections. Then, under **Protect your package**, toggle **Yes** or **No** to encrypt the provisioning package. If you select **Yes**, enter a password. This password must be entered to apply the encrypted provisioning package.