Squashed commit of the following:

commit d6a8bce79e491a8a245a37a9e20e6a6bec4d325b
Merge: 0ab4e4e1 a7c70ad4
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 23 10:35:16 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 0ab4e4e119590e0e8cef691eee2b87180b07c5b3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 23 10:29:48 2017 -0700

    Jordan feedback

commit 4454eeadbebb5fccdbfb3b1d07e87d708fefbe87
Merge: 03444e15 ef670cb5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 23 09:26:54 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 03444e15f5b51bd1bdf1e76745f62cbbed3b529d
Merge: 603408f3 660a6984
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 22 11:00:46 2017 -0700

    Merge branch 'rs2' into jdrs2sh

commit 603408f38ecd99e6f7fce1f61a4f199918fd67c4
Merge: 6821f22f b96e1555
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:54:33 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 6821f22f07f1864bb0a5c8eda33f7daf4f9531bc
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:41:44 2017 -0700

    change ICD references

commit 5804bc18db376fba16e8c863f5af8ffdd965359a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:39:55 2017 -0700

    rename file

commit 9268142c9b881b0e0ad4fc2a0d4dcfddc180a1b3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:32:31 2017 -0700

    update what's new

commit 503be68ec3a731434ca789df2da1f1c4783fdca7
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:30:48 2017 -0700

    art

commit 93914a2cf2aef9622b172c8ea97a3c1d72544c6a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:30:43 2017 -0700

    Jordan updates

commit 27b1445ba4149fa78b7ec628870b19933307ba38
Merge: 9578dffe 6f0a1f7f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 08:19:27 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 9578dffee198b0be16992368f571eed81f261818
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 20 09:09:56 2017 -0700

    new oobe image

commit 616c10e4e404574ecce7726fc76d7582c56b318e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 20 08:23:53 2017 -0700

    get bulk token warning

commit 5600a6c7b320c4968686c07df90c62d8110764c9
Merge: cf29bb53 4b34636b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 20 08:22:02 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit cf29bb53ec1c6e45e068219a796b2a5b04347b15
Merge: 695ec39f a5ec4c4d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Mar 17 09:42:51 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 695ec39f81b6da46b442ce8e52c9d9b28d65434a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 16 12:25:06 2017 -0700

    delete

    # Conflicts:
    #	devices/surface-hub/TOC.md
    #	devices/surface-hub/intro-to-surface-hub.md
    #	devices/surface-hub/surface-hub-administrators-guide.md

commit cc123f7aa0718efaa7cd355df4e3693afb073b9c
Merge: 6b7ddf3e 3c12e864
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 16 12:23:40 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 6b7ddf3e498d541c2dbb531dd132e7ec0f45eb9d
Merge: 278d14c4 032c25d4
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 16 11:34:53 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 278d14c462fa386e8979c4e998c464f2cdbf6a6c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 15 10:26:22 2017 -0700

    get bulk token

commit 005f12e3939f8134143314e95e6bc9f76db8c3de
Merge: 410e7508 1bff6ddd
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 15 10:25:19 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 410e750850a5037d843fe9d9c64a477d252ff10e
Merge: d2f94c8f 8eed0956
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 13:51:32 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit d2f94c8f9d73868dec86e472fe5ace87b7370ac3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 13:27:23 2017 -0700

    tweak

commit f629b4f1fd27fad24c258a7de903e6c18e85ec8c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 12:44:21 2017 -0700

    fix mdm enrollment

commit 1dd74f9e7e353ba9ce5e71c8797cfa8cd02342a7
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 12:33:24 2017 -0700

    add proxy

commit c71e5af71bc866f1a5fe9abefb82b5124fb957fd
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 12:03:09 2017 -0700

    add install link

commit 0344deee4c68ae3c81529dc9cb602eec2af0b5c3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:57:43 2017 -0700

    stick

commit be7ed51e1fb7b1a578c8e843b56e701bcf90be9d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:56:52 2017 -0700

    resize art

commit 857be3cdfca07da3c5dfb470b3a3a3aee290a07c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:55:09 2017 -0700

    moved note to correct cell

commit a91ca3943b8c0454549a1c0c5455b919ed46de8c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:52:21 2017 -0700

    sync

commit 5bcf3c1db3c97d87ca60bfd4d688b908d4d9e518
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:43:25 2017 -0700

    fix link

commit de7d60524a2e1ba0d5e1bc1074da9bf887fa6457
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:42:46 2017 -0700

    add apps to provisioning

commit 67e14be35b30f4bfa45fb79815c25ef2317a171c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:37:27 2017 -0700

    sync to switch branches

commit c6b9d8dae5d29f441ea262323baaad5e41b2bc9f
Merge: 3260248b 4b13310a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 08:35:04 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 3260248b8a0511c081a5547419109f9380ea9b26
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 13 08:56:25 2017 -0700

    fix table for non-IE browsers

    # Conflicts:
    #	windows/whats-new/images/wcd-options.png

commit a3ece5c8d4a6c37645f4aa5b39b582be855b98b9
Merge: 4ed80574 759b4a41
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 13 08:53:34 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 4ed80574020c1291ba4e853553330a7b84f21657
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 12:00:27 2017 -0800

    fix typo

commit 7541a4507508822dcd51da773536b89a5a49f305
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:53:38 2017 -0800

    fix table

commit 37254f098396342dd23115ea10885f121f5b9371
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:51:48 2017 -0800

    resize art

commit a936a6c4768729fec66775528a31c64132fa4f8e
Merge: a217a9ae 9786c53a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:50:43 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit a217a9ae8e48af3b533eb421a716b5a580daecba
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:45:55 2017 -0800

    sync

commit f09e8ae9e87db16b7ee6982864a1c4c2fc8ebcdc
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:39:34 2017 -0800

    add image to index

commit 80a133370000b2b7ff8c9e1383aca7eb1769258a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:30:34 2017 -0800

    fix link

commit d8aa55211a62fecf56e6404146917b8e84b3c296
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:25:33 2017 -0800

    tweak TOC, get rid of intro

commit 6415e3739e13f47f2d3a6355066015d0bcd4cc7a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:16:33 2017 -0800

    remove admin guide level from toc

commit 0d016720488e8aa1e3e0621b50596a66db8d232f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 07:53:03 2017 -0800

    release in change history

commit 67a8f585dd788db1a18247827b1f9d22378d5b9f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 07:50:20 2017 -0800

    add what's new

commit be5e195fc41d9ce94cd1b6189f0da25e9e50b9f2
Merge: e3e75663 8e80f0e1
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 07:40:34 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit e3e756632b462d8a110b0538782bc22487e96d4b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 28 13:46:55 2017 -0800

    end session

    # Conflicts:
    #	windows/configure/windows-10-start-layout-options-and-policies.md

commit 0a9b86a2f6b69e5883fcdab48bb22f19cf1e6c32
Merge: 13e94977 4530d39f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 28 13:42:38 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 13e9497711b34daab936735edcfa87f13c89d006
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 11:29:01 2017 -0800

    resize art

commit 17d830dfde1174c95cb2bde7018fa1c85b8dcacc
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 10:59:56 2017 -0800

    delete file from images

commit 395946c6c9b54516461e79a232525e965632686d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 10:50:39 2017 -0800

    fix link

commit c328942818f6e4b5d2bd2062724a90687b85926e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 10:40:29 2017 -0800

    set up wizard table

commit 942af3c56e6e6f7736e1ea03d6801633237a9311
Merge: 6ce5c31d 819ba842
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 10:03:16 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 6ce5c31d127662010841791aa6498cd1606ed31e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 09:55:32 2017 -0800

    change branches

commit a3c28ae9e83bde3c97dd2d9232ad430e08ae972b
Merge: b794a681 0a914cf9
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 08:31:41 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/jdrs2icd' into jdrs2sh

commit b794a6819b1a3ad9deb834986a184f6b488497fa
Merge: af38dabf 2d1267b5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 07:37:48 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit af38dabf79f6b51971fbf3891d72be73f0f9035a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Feb 24 11:25:09 2017 -0800

    changed all to End Session

    # Conflicts:
    #	devices/surface-hub/index.md

commit 4e124566f0a01017232d6c2c6be95db15abf5db3
Merge: d07431ae 4b1663d8
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Feb 24 11:18:06 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit d07431ae706af0af4c6c44909c4e08b16b904ccc
Merge: 237cb29c 8bfa038e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 14 13:48:31 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 237cb29ce337e73ab6d707c1c06eaa89f5b49f3b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 15:06:27 2017 -0800

    undo all

commit 5461ccb226a5ee079f07c59d719c52f3fefe2343
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:53:02 2017 -0800

    sync

commit 1e56393ac1a33ff3d1b5eb2183e1ece4e776a9a6
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:41:45 2017 -0800

    sync

commit 25ad8424a8f0dff551367cebedad18563e9d1081
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:32:18 2017 -0800

    iframe

commit 114cccfb75b3f27f46b67b5577d05a5de55662c1
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:22:49 2017 -0800

    try span

commit 03c4b1bb5aad5871b6808c2b7c48e0e71b6c10c7
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:10:29 2017 -0800

    remove test

commit 8a55ced11b6e8d4117d940ec73e2b045a0d7cf24
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 06:59:19 2017 -0800

    test compass video

commit f4ae742993fa9892f4d7c411fa87683697849cf7
Merge: dd9a3df0 94b855cd
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 06:55:10 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

.openpublishing.redirection.json

@@ -6,6 +6,21 @@
 "redirect_document_id": true
 },
 {
+"source_path": "devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md",
+"redirect_url": "/itpro/surface-hub/finishing-your-surface-hub-meeting",
+"redirect_document_id": true
+},
+{
+"source_path": "devices/surface-hub/provisioning-packages-for-certificates-surface-hub.md",
+"redirect_url": "/itpro/surface-hub/provisioning-packages-for-surface-hub",
+"redirect_document_id": true
+},
+{
+"source_path": "devices/surface-hub/manage-settings-with-local-admin-account-surface-hub.md",
+"redirect_url": "/itpro/surface-hub/admin-group-management-for-surface-hub",
+"redirect_document_id": true
+},
+{
 "source_path": "devices/surface-hub/surface-hub-administrators-guide.md",
 "redirect_url": "/itpro/surface-hub/index",
 "redirect_document_id": true

devices/surface-hub/TOC.md

@@ -1,4 +1,6 @@
 # [Microsoft Surface Hub](index.md)
+## [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md)
+## [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md)
 ## [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
 ### [Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md)
 ### [Create and test a device account](create-and-test-a-device-account-surface-hub.md)
@@ -10,7 +12,7 @@
 #### [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)
+### [Create provisioning packages](provisioning-packages-for-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)
@@ -28,13 +30,12 @@
 #### [Use fully qualified domain name with Surface Hub](use-fully-qualified-domain-name-surface-hub.md)
 #### [Wireless network management](wireless-network-management-for-surface-hub.md)
 ### [Install apps on your Surface Hub](install-apps-on-surface-hub.md)
-### [End a Surface Hub meeting with I'm Done](i-am-done-finishing-your-surface-hub-meeting.md)
+### [End a Surface Hub meeting with End session](i-am-done-finishing-your-surface-hub-meeting.md)
 ### [Save your BitLocker key](save-bitlocker-key-surface-hub.md)
 ### [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md)
 ### [Using a room control system](use-room-control-system-with-surface-hub.md)
-## [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
+## [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md)
-## [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)
-## [Useful downloads for Surface Hub administrators](surface-hub-downloads.md)
-## [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md)
 ## [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md)
+## [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
+## [Useful downloads for Surface Hub administrators](surface-hub-downloads.md)
 ## [Change history for Surface Hub](change-history-surface-hub.md)

devices/surface-hub/accessibility-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.pagetype: surfacehub
 ms.sitesec: library
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -30,7 +30,7 @@ The full list of accessibility settings are available to IT admins in the **Sett
 | Mouse                 | Defaults selected for **Pointer size**, **Pointer color** and **Mouse keys**. |
 | Other options         | Defaults selected for **Visual options** and **Touch feedback**. |
 
-Additionally, these accessibility features and apps are returned to default settings when users press [I'm Done](i-am-done-finishing-your-surface-hub-meeting.md):
+Additionally, these accessibility features and apps are returned to default settings when users press [End session](finishing-your-surface-hub-meeting.md):
 - Narrator
 - Magnifier
 - High contrast

devices/surface-hub/admin-group-management-for-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub, security
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md

@@ -1,5 +1,5 @@
 ---
-title: Appendix PowerShell (Surface Hub)
+title: PowerShell for Surface Hub (Surface Hub)
 description: PowerShell scripts to help set up and manage your Microsoft Surface Hub .
 ms.assetid: 3EF48F63-8E4C-4D74-ACD5-461F1C653784
 keywords: PowerShell, set up Surface Hub, manage Surface Hub
@@ -7,14 +7,14 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
-# Appendix: PowerShell (Surface Hub)
+# PowerShell for Surface Hub
 
 
-PowerShell scripts to help set up and manage your Microsoft Surface Hub .
+PowerShell scripts to help set up and manage your Microsoft Surface Hub.
 
 -   [PowerShell scripts for Surface Hub admins](#scripts-for-admins)
     -   [Create an on-premise account](#create-on-premise-ps-scripts)
@@ -43,7 +43,8 @@ What do you need in order to run the scripts?
 -   Remote PowerShell access to your organization's domain or tenant, Exchange servers, and Skype for Business servers.
 -   Admin credentials for your organization's domain or tenant, Exchange servers, and Skype for Business servers.
 
->**Note**  Whether you’re creating a new account or modifying an already-existing account, the validation script will verify that your device account is configured correctly. You should always run the validation script before adding a device account to Surface Hub.
+>[!NOTE]
+>Whether you’re creating a new account or modifying an already-existing account, the validation script will verify that your device account is configured correctly. You should always run the validation script before adding a device account to Surface Hub.
 
  
 

devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/change-history-surface-hub.md

@@ -6,7 +6,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -14,6 +14,10 @@ localizationpriority: medium
 
 This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md).
 
+## RELEASE: Windows 10, version 1703
+
+The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update).
+
 ## February 2017
 
 | New or changed topic | Description |

devices/surface-hub/change-surface-hub-device-account.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

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

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/create-and-test-a-device-account-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/device-reset-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -49,21 +49,49 @@ If you see a blank screen for long periods of time during the **Reset device** p
 
     ![Image showing Update & Security group in Settings app for Surface Hub.](images/sh-settings-update-security.png)
  
-3.	Click **Recovery**, and then click **Get started**.
+3.	Click **Recovery**, and then, under **Reset device**, click **Get started**.
 
     ![Image showing Reset device option in Settings app for Surface Hub.](images/sh-settings-reset-device.png) 
 
-## Reset a Surface Hub from Windows Recovery Environment
+<span id="cloud-recovery" />
+## Recover a Surface Hub from the cloud
  
-On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device will automatically reboot and try again. But if this operation fails repeatedly, the device will be automatically locked to protect user data. To unlock it, you must reset the device from [Windows Recovery Environment](https://technet.microsoft.com/library/cc765966.aspx) (Windows RE). 
+In the Windows Recovery Environment (Windows RE), you can recover your device by downloading a factory build from the cloud and installing it on the Surface Hub. This allows devices in an unusable state to recover without requiring assistance from Microsoft Support.
 
-**To reset a Surface Hub from Windows Recovery Environment**
+### Recover a Surface Hub in a bad state
+
+If the device account gets into an unstable state or the Admin account is running into issues, you can use cloud recovery in **Settings**. You should only use cloud recovery when [reset](#reset-a-surface-hub-from-settings) doesn't fix the problem.  
+
+1. On your Surface Hub, go to **Settings** &gt; **Update & security** &gt; **Recovery**.
+
+2. Under **Recover from the cloud**, click **Restart now**.
+
+    ![recover from the cloud](images/recover-from-the-cloud.png)
+
+### Recover a locked Surface Hub
+
+On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device will automatically reboot and try again. But if this operation fails repeatedly, the device will be automatically locked to protect user data. To unlock it, you must reset or recover the device from [Windows RE](https://technet.microsoft.com/library/cc765966.aspx). 
 
 1.  From the welcome screen, toggle the Surface Hub's power switch 3 times. Wait a few seconds between each toggle. See the [Surface Hub Site Readiness Guide](https://www.microsoft.com/surface/support/surface-hub/surface-hub-site-readiness-guide) for help with locating the power switch. 
-2. The device should automatically boot into Windows RE. Select **Advanced Repair**.
+2. The device should automatically boot into Windows RE. 
-3. Select **Reset**.
+3. After the Surface Hub enters Windows RE, select **Recover from the cloud**. (Optionally, you can choose **Reset**, however **Recover from the cloud** is the recommended approach.)
-4. If prompted, enter your device's BitLocker key. 
+    >[!NOTE]
+    >When using **Recover from the cloud**, an ethernet connection is recommended.
+    
+    ![Recover from the cloud](images/recover-from-cloud.png)
+    
+4. Enter the Bitlocker key (if prompted).
+5. When prompted, select **Reinstall**.
 
+    ![Reinstall](images/reinstall.png)
+
+6. Select **Yes** to repartition the disk.
+ 
+    ![Repartition](images/repartition.png)
+    
+Reset will begin after the image is downloaded from the cloud. You will see progress indicators.
+
+![downloading 97&](images/recover-progress.png)
 
 ## Related topics
 

devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md

@@ -33,7 +33,7 @@ Surface Hub doesn't have a lock screen or a screen saver, but it has a similar f
 Surface Hub is designed to be used in communal spaces, such as meeting rooms. Unlike Windows PCs, anyone can walk up and use a Surface Hub without logging on. The system always runs as a local, auto logged-in, low-privilege user. It doesn't support logging in any additional users - including admin users.
 
 > [!NOTE]
-> Surface Hub supports signing in to Microsoft Edge and other apps. However, these credentials are deleted when users press **I'm done**. 
+> Surface Hub supports signing in to Microsoft Edge and other apps. However, these credentials are deleted when users press **End session**. 
 
 *Organization policies that this may affect:* <br> Generally, Surface Hub uses lockdown features rather than user access control to enforce security. Policies related to password requirements, interactive logon, user accounts, and access control don't apply for Surface Hub.
 
@@ -46,7 +46,7 @@ Users have access to a limited set of directories on the Surface Hub:
 - Pictures
 - Downloads
 
-Files saved locally in these directories are deleted when users press **I'm done**. To save content created during a meeting, users should save files to a USB drive or to OneDrive.
+Files saved locally in these directories are deleted when users press **End session**. To save content created during a meeting, users should save files to a USB drive or to OneDrive.
 
 *Organization policies that this may affect:* <br> Policies related to access permissions and ownership of files and folders don't apply for Surface Hub. Users can't browse and save files to system directories and network folders.
 

devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/finishing-your-surface-hub-meeting.md

@@ -0,0 +1,92 @@
+---
+title: End session - ending a Surface Hub meeting
+description: To end a Surface Hub meeting, tap End session. Surface Hub cleans up the application state, operating system state, and the user interface so that Surface Hub is ready for the next meeting.
+keywords: I am Done, end Surface Hub meeting, finish Surface Hub meeting, clean up Surface Hub meeting
+ms.prod: w10
+ms.mktglfcycl: manage
+ms.sitesec: library
+ms.pagetype: surfacehub
+author: jdeckerMS
+localizationpriority: medium
+---
+
+# End a Surface Hub meeting with End session
+Surface Hub is a collaboration device designed to be used in meeting spaces by different groups of people. At the end of a meeting, users can tap **End session** to clean up any sensitive data and prepare the device for the next meeting. Surface Hub will clean up, or reset, the following states:
+- Applications
+- Operating system
+- User interface
+
+This topic explains what **End session** resets for each of these states.
+
+## Applications
+When you start apps on Surface Hub, they are stored in memory and data is stored at the application level. Data is available to all users during that session (or meeting) until date is removed or overwritten. When **End session** is selected, Surface Hub application state is cleared out by closing applications, deleting browser history, resetting applications, and removing Skype logs.
+
+### Close applications
+Surface Hub closes all visible windows, including Win32 and Universal Windows Platform (UWP) applications. The application close stage uses the multitasking view to query the visible windows. Win32 windows that do not close within a certain timeframe are closed using **TerminateProcess**. 
+   
+### Delete browser history
+Surface Hub uses Delete Browser History (DBH) in Edge to clear Edge history and cached data. This is similar to how a user can clear out their browser history manually, but **End session** also ensures that application states are cleared and data is removed before the next session, or meeting, starts. 
+ 
+### Reset applications
+**End session** resets the state of each application that is installed on the Surface Hub. Resetting an application clears all background tasks, application data, notifications, and user consent dialogs. Applications are returned to their first-run state for the next people that use Surface Hub.  
+ 
+### Remove Skype logs
+Skype does not store personally-identifiable information on Surface Hub. Information is stored in the Skype service to meet existing Skype for Business guidance. Local Skype logging information is the only data removed when **End session** is selected. This includes Unified Communications Client Platform (UCCP) logs and media logs.   
+
+## Operating System
+The operating system hosts a variety of information about the state of the sessions that needs to be cleared after each Surface Hub meeting. 
+
+### File System
+Meeting attendees have access to a limited set of directories on the Surface Hub. When **End session** is selected, Surface Hub clears these directories:<br>
+- Music
+- Videos
+- Documents
+- Pictures
+- Downloads
+
+Surface Hub also clears these directories, since many applications often write to them:
+- Desktop
+- Favorites
+- Recent
+- Public Documents
+- Public Music
+- Public Videos
+- Public Downloads
+
+### Credentials
+User credentials that are stored in **TokenBroker**, **PasswordVault**, or **Credential Manager** are cleared when you tap **End session**.
+
+## User interface
+User interface (UI) settings are returned to their default values when **End session** is selected. 
+
+### UI items
+- Reset Quick Actions to default state
+- Clear Toast notifications
+- Reset volume levels
+- Reset sidebar width
+- Reset tablet mode layout
+- Sign user out of Office 365 meetings and files
+
+### Accessibility
+Accessibility features and apps are returned to default settings when **End session** is selected.
+- Filter keys
+- High contrast
+- Sticky keys
+- Toggle keys
+- Mouse keys
+- Magnifier
+- Narrator
+
+### Clipboard
+The clipboard is cleared to remove data that was copied to the clipboard during the session. 
+
+## Frequently asked questions
+**What happens if I forget to tap End session at the end of a meeting, and someone else uses the Surface Hub later?**<br>
+Surface Hub only cleans up meeting content when users tap **End session**. If you leave the meeting without tapping **End session**, the device will return to the welcome screen after some time. From the welcome screen, users have the option to resume the previous session or start a new one. You can also disable the ability to resume a session if **End session** is not pressed.
+
+**Are documents recoverable?**<br> 
+Removing files from the hard drive when **End session** is selected is just like any other file deletion from a hard disk drive. Third-party software might be able to recover data from the hard disk drive, but file recovery is not a supported feature on Surface Hub. To prevent data loss, always save the data you need before leaving a meeting.
+
+**Do the clean-up actions from End session comply with the US Department of Defense clearing and sanitizing standard: DoD 5220.22-M?**<br>
+No. Currently, the clean-up actions from **End session** do not comply with this standard.  
+  

devices/surface-hub/first-run-program-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -43,9 +43,10 @@ Each of these sections also contains information about paths you might take when
 
 This is the first screen you'll see when you power up the Surface Hub for the first time. It's where you input localization information for your device.
 
->**Note**  This is also where you begin the optional process of deploying a provisioning package. See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) if that's what you're doing.
+>[!NOTE]
+>This is also where you begin the optional process of deploying a provisioning package. See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) if that's what you're doing.
 
- 
+ Select a language and the initial setup options are displayed.
 
 ![Image showing ICD options checklist.](images/setuplocale.png)
 
@@ -326,6 +327,9 @@ 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.
+    
+    >[!IMPORTANT]
+    >If you join Surface Hub to Azure AD during first-run setup, single sign-on (SSO) for Office apps will not work properly. Users will have to sign in to each Office app individually.
 
 -   **Use Active Directory Domain Services**
 
@@ -382,7 +386,7 @@ Once the device has been domain joined, you must specify a security group from t
 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.
+-   **User name:** The user name of an account that has sufficient permission to join the specified domain. This account must be a computer object.
 -   **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.

devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md

@@ -1,91 +0,0 @@
----
-title: I am done - ending a Surface Hub meeting
-description: To end a Surface Hub meeting, tap I am Done. Surface Hub cleans up the application state, operating system state, and the user interface so that Surface Hub is ready for the next meeting.
-keywords: I am Done, end Surface Hub meeting, finish Surface Hub meeting, clean up Surface Hub meeting
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.pagetype: surfacehub
-author: TrudyHa
-localizationpriority: medium
----
-
-# End a Surface Hub meeting with I'm Done
-Surface Hub is a collaboration device designed to be used in meeting spaces by different groups of people. At the end of a meeting, users can tap **I'm Done** to clean up any sensitive data and prepare the device for the next meeting. Surface Hub will clean up, or reset, the following states:
-- Applications
-- Operating system
-- User interface
-
-This topic explains what **I'm Done** resets for each of these states.
-
-## Applications
-When you start apps on Surface Hub, they are stored in memory and data is stored at the application level. Data is available to all users during that session (or meeting) until date is removed or overwritten. When **I'm done** is selected, Surface Hub application state is cleared out by closing applications, deleting browser history, resetting applications, and removing Skype logs.
-
-### Close applications
-Surface Hub closes all visible windows, including Win32 and Universal Windows Platform (UWP) applications. The application close stage uses the multitasking view to query the visible windows. Win32 windows that do not close within a certain timeframe are closed using **TerminateProcess**. 
-   
-### Delete browser history
-Surface Hub uses Delete Browser History (DBH) in Edge to clear Edge history and cached data. This is similar to how a user can clear out their browser history manually, but **I'm Done** also ensures that application states are cleared and data is removed before the next session, or meeting, starts. 
- 
-### Reset applications
-**I'm Done** resets the state of each application that is installed on the Surface Hub. Resetting an application clears all background tasks, application data, notifications, and user consent dialogs. Applications are returned to their first-run state for the next people that use Surface Hub.  
- 
-### Remove Skype logs
-Skype does not store personally-identifiable information on Surface Hub. Information is stored in the Skype service to meet existing Skype for Business guidance. Local Skype logging information is the only data removed when **I'm Done** is selected. This includes Unified Communications Client Platform (UCCP) logs and media logs.   
-
-## Operating System
-The operating system hosts a variety of information about the state of the sessions that needs to be cleared after each Surface Hub meeting. 
-
-### File System
-Meeting attendees have access to a limited set of directories on the Surface Hub. When **I'm Done** is selected, Surface Hub clears these directories:<br>
-- Music
-- Videos
-- Documents
-- Pictures
-- Downloads
-
-Surface Hub also clears these directories, since many applications often write to them:
-- Desktop
-- Favorites
-- Recent
-- Public Documents
-- Public Music
-- Public Videos
-- Public Downloads
-
-### Credentials
-User credentials that are stored in **TokenBroker**, **PasswordVault**, or **Credential Manager** are cleared when you tap **I’m done**.
-
-## User interface
-User interface (UI) settings are returned to their default values when **I'm Done** is selected. 
-
-### UI items
-- Reset Quick Actions to default state
-- Clear Toast notifications
-- Reset volume levels
-- Reset sidebar width
-- Reset tablet mode layout
-
-### Accessibility
-Accessibility features and apps are returned to default settings when **I'm Done** is selected.
-- Filter keys
-- High contrast
-- Sticky keys
-- Toggle keys
-- Mouse keys
-- Magnifier
-- Narrator
-
-### Clipboard
-The clipboard is cleared to remove data that was copied to the clipboard during the session. 
-
-## Frequently asked questions
-**What happens if I forget to tap I'm Done at the end of a meeting, and someone else uses the Surface Hub later?**<br>
-Surface Hub only cleans up meeting content when users tap **I'm Done**. If you leave the meeting without tapping **I'm Done**, the device will return to the welcome screen after some time. From the welcome screen, users have the option to resume the previous session or start a new one.
-
-**Are documents recoverable?**<br> 
-Removing files from the hard drive when **I'm Done** is selected is just like any other file deletion from a hard disk drive. Third-party software might be able to recover data from the hard disk drive, but file recovery is not a supported feature on Surface Hub. To prevent data loss, always save the data you need before leaving a meeting.
-
-**Do the clean-up actions from I'm Done comply with the US Department of Defense clearing and sanitizing standard: DoD 5220.22-M?**<br>
-No. Currently, the clean-up actions from **I'm Done** do not comply with this standard.  
-  

devices/surface-hub/index.md

@@ -12,19 +12,36 @@ localizationpriority: medium
 
 # Microsoft Surface Hub
 
-
-Documents related to deploying and managing the Microsoft Surface Hub in your organization.
-
 >[Looking for the user's guide for Surface Hub?](https://www.microsoft.com/surface/support/surface-hub)
 
+<table><tr><td style="border: 0px;width: 75%;valign= top">Microsoft Surface Hub is an all-in-one productivity device that is intended for brainstorming, collaboration, and presentations. In order to get the maximum benefit from Surface Hub, your organization’s infrastructure and the Surface Hub itself must be properly set up and integrated. The documentation in this library describes what needs to be done both before and during setup in order to help you optimize your use of the device.</td><td align="left" style="border: 0px">![image of a Surface Hub](images/surfacehub.png) </td></tr></table>
+ 
+
+## Surface Hub setup process
+
+In some ways, adding your new Surface Hub is just like adding any other Microsoft Windows-based device to your network. However, in order to get your Surface Hub up and running at its full capacity, there are some very specific requirements. Here are the next topics you'll need:
+
+1. [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md)
+2. [Gather the information listed in the Setup worksheet](setup-worksheet-surface-hub.md)
+2. [Physically install your Surface Hub device](physically-install-your-surface-hub-device.md)
+3. [Run the Surface Hub first-run setup program (OOBE)](first-run-program-surface-hub.md)
+
+
+
 ## In this section
 
 | Topic | Description |
 | --- | --- |
-| [Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md) | This guide covers the installation and administration of devices running Surface Hub, and is intended for use by anyone responsible for these tasks, including IT administrators and developers.|
+| [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md) | Discover the changes and improvements for Microsoft Surface Hub in the Windows 10, version 1703 release (also known as Creators Update). |
 | [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) | This topic explains the differences between the operating system on Surface Hub and Windows 10 Enterprise. |
-| [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) | This topic provides guidance on Wi-Fi Direct security risks, how the Surface Hub has addressed those risks, and how Surface Hub administrators can configure the device for the highest level of security.  |
+| [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md) | This section contains an overview of the steps required to prepare your environment so that you can use all of the features of Surface Hub. See [Intro to Surface Hub](intro-to-surface-hub.md) for a description of how the device and its features interact with your IT environment. |
+| [Set up Microsoft Surface Hub](set-up-your-surface-hub.md) | Set up instructions for Surface Hub include a setup worksheet, and a walkthrough of the first-run program. |
+| [Manage Microsoft Surface Hub](manage-surface-hub.md) | How to manage your Surface Hub after finishing the first-run program. |
+| [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) | 
+| [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) | This topic provides guidance on Wi-Fi Direct security risks, how the Surface Hub has addressed those risks, and how Surface Hub administrators can configure the device for the highest level of security.  | PowerShell scripts to help set up and manage your Surface Hub. |
+| [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md) | Troubleshoot common problems, including setup issues, Exchange ActiveSync errors. |
 | [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) | This topic provides links to useful Surface Hub documents, such as product datasheets, the site readiness guide, and user's guide. |
-| [Change history for Surface Hub](change-history-surface-hub.md) | This topic lists new and updated topics in the Surface Hub documentation. |
+| [Change history for Surface Hub](change-history-surface-hub.md) | This topic lists new and updated topics in the Surface Hub documentation library. |
+
 
 

devices/surface-hub/install-apps-on-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: surfacehub, store
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/local-management-surface-hub-settings.md

@@ -6,7 +6,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -16,29 +16,38 @@ After initial setup of Microsoft Surface Hub, the device’s settings can be loc
 
 ## Surface Hub settings
 
-Surface Hubs have many settings that are common to other Windows devices, but also have settings which are only configurable on Surface Hubs. This table lists settings only cofigurable on Surface Hubs. 
+Surface Hubs have many settings that are common to other Windows devices, but also have settings which are only configurable on Surface Hubs. This table lists settings only configurable on Surface Hubs. 
 
 | Setting | Location | Description |
 | ------- | -------- | ----------- |
-| Device account | This device > Accounts | Set or change the Surface Hub's device account. |
+| Device account | Surface Hub > Accounts | Set or change the Surface Hub's device account. |
-| Device account sync status | This device > Accounts | Check the sync status of the device account’s mail and calendar on the Surface Hub. |
+| Device account sync status | Surface Hub > Accounts | Check the sync status of the device account’s mail and calendar on the Surface Hub. |
-| Password rotation | This device > Accounts | Choose whether to let the Surface Hub automatically rotate the device account's password. |
+| Password rotation | Surface Hub > Accounts | Choose whether to let the Surface Hub automatically rotate the device account's password. |
-| Change admin account password  | This device > Accounts | Change the password for the local admin account. This is only available if you configured the device to use a local admin during first run. |
+| Change admin account password  | Surface Hub > Accounts | Change the password for the local admin account. This is only available if you configured the device to use a local admin during first run. |
-| Configure Operations Management Suite (OMS) | This device > Device management | Set up monitoring for your Surface Hub using OMS. |
+| Device Management | Surface Hub > Device management | Manage policies and business applications using mobile device management (MDM). |
-| Open the Windows Store app | This device > Apps & features | The Windows Store app is only available to admins through the Settings app. |
+| Provisioning packages | Surface Hub > Device management | Set or change provisioning packages installed on the Surface Hub. |
-| Skype for Business domain name | This device > Calling | Configure a domain name for your Skype for Business server. |
+| Configure Operations Management Suite (OMS) | Surface Hub > Device management | Set up monitoring for your Surface Hub using OMS. |
-| Default microphone and speaker settings | This device > Calling | Configure a default microphone and speaker for calls, and a default speaker for media playback. |
+| Open the Windows Store app | Surface Hub > Apps & features | The Windows Store app is only available to admins through the Settings app. |
-| Turn off wireless projection using Miracast | This device > Wireless projection | Choose whether presenters can wirelessly project to the Surface Hub using Miracast. |
+| Skype for Business domain name | Surface Hub > Calling & Audio | Configure a domain name for your Skype for Business server. |
-| Require a PIN for wireless projection | This device > Wireless projection | Choose whether people are required to enter a PIN before they use wireless projection. |
+| Default Speaker volume | Surface Hub > Calling & Audio | Configure the default speaker volume for the Surface Hub when it starts a session. |
-| Wireless projection (Miracast) channel | This device > Wireless projection | Set the channel for Miracast projection. |
+| Default microphone and speaker settings | Surface Hub > Calling & Audio | Configure a default microphone and speaker for calls, and a default speaker for media playback. |
-| Meeting info shown on the welcome screen | This device > Welcome screen | Choose whether meeting organizer, time, and subject show up on the welcome screen. |
+| Enable Dolby Audio X2 | Surface Hub > Calling & Audio | Configure the Dolby Audio X2 speaker enhancements. |
-| Welcome screen background |  This device > Welcome screen | Choose a background image for the welcome screen. |
+| Open Connect App automatically | Surface Hub > Projection | Choose whether projection will automatically open the Connect app or wait for user input before opening. |
-| Turn on screen with motion sensors | This device > Session & clean up | Choose whether the screen turns on when motion is detected. |
+| Turn off wireless projection using Miracast | Surface Hub > Projection | Choose whether presenters can wirelessly project to the Surface Hub using Miracast. |
-| Session time out | This device > Session & clean up | Choose how long the device needs to be inactive before returning to the welcome screen. |
+| Require a PIN for wireless projection | Surface Hub > Projection | Choose whether people are required to enter a PIN before they use wireless projection. |
-| Sleep time out | This device > Session & clean up | Choose how long the device needs to be inactive before going to sleep mode. |
+| Wireless projection (Miracast) channel | Surface Hub > Projection | Set the channel for Miracast projection. |
-| Friendly name | This device > About | Set the Surface Hub name that people will see when connecting wirelessly. |
+| Meeting info shown on the welcome screen | Surface Hub > Welcome screen | Choose whether meeting organizer, time, and subject show up on the welcome screen. |
+| Welcome screen background |  Surface Hub > Welcome screen | Choose a background image for the welcome screen. |
+| Idle timeout to Welcome screen | Surface Hub > Session & Power | Choose how long until the Surface Hub returns to the welcome screen after no motion is detected. |
+| Resume session | Surface Hub > Session & Power | Choose to allow users to resume a session after no motion is detected or to automatically clean up a session. |
+| Access to Office 365 meetings and files | Surface Hub > Session & Power | Choose whether a user can sign in to Office 365 to get access to their meetings and files. |
+| Turn on screen with motion sensors | Surface Hub > Session & clean up | Choose whether the screen turns on when motion is detected. |
+| Session time out | Surface Hub > Session & clean up | Choose how long the device needs to be inactive before returning to the welcome screen. |
+| Sleep time out | Surface Hub > Session & clean up | Choose how long the device needs to be inactive before going to sleep mode. |
+| Friendly name | Surface Hub > About | Set the Surface Hub name that people will see when connecting wirelessly. |
 | Maintenance hours | Update & security > Windows Update > Advanced options | Configure when updates can be installed. |
 | Configure Windows Server Update Services (WSUS) server | Update & security > Windows Update > Advanced options | Change whether Surface Hub receives updates from a WSUS server instead of Windows Update. |
+| Recover from the cloud | Update & security > Recovery | Reinstall the operating system on Surface Hub to a manufacturer build from the cloud. |
 | Save BitLocker key | Update & security > Recovery | Backup your Surface Hub's BitLocker key to a USB drive. |
 | Collect logs | Update & security > Recovery | Save logs to a USB drive to send to Microsoft later. | 
 

devices/surface-hub/manage-settings-with-local-admin-account-surface-hub.md

@@ -1,13 +0,0 @@
----
-title: Manage settings with a local admin account (Surface Hub)
-description: A local admin account will be set up on every Microsoft Surface Hub as part of the first run program. The only way to change the local admin options that you chose at that time is to reset the device.
-ms.assetid: B4B3668B-985D-427E-8495-E30ABEECA679
-redirect_url: https://technet.microsoft.com/itpro/surface-hub/admin-group-management-for-surface-hub
-keywords: local admin account, Surface Hub, change local admin options
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.pagetype: surfacehub
-author: TrudyHa
-localizationpriority: medium
----

devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md

@@ -69,9 +69,19 @@ For more information, see [SurfaceHub configuration service provider](https://ms
 | Connect to your Operations Management Suite workspace | MOMAgent/WorkspaceID <br> MOMAgent/WorkspaceKey | Yes | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
 | Welcome screen background image | InBoxApps/Welcome/CurrentBackgroundPath | Yes | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
 | Meeting information displayed on the welcome screen | InBoxApps/Welcome/MeetingInfoOption | Yes | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
-| Friendly name for wireless projection | Properties/FriendlyName | Yes. <br> [Use a custom policy.](#example-intune)) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
+| Friendly name for wireless projection | Properties/FriendlyName | Yes <br> [Use a custom policy.](#example-intune)) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
 | Device account, including password rotation | DeviceAccount/*`<name_of_policy>`* <br> See [SurfaceHub CSP](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx). | No | No | Yes |
-\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
+| Specify Skype domain | InBoxApps/SkypeForBusiness/DomainName | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Auto launch Connect App when projection is initiated | InBoxApps/Connect/AutoLaunch | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Set default volume | Properties/DefaultVolume | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Set screen timeout | Properties/ScreenTimeout | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Set session timeout | Properties/SessionTimeout | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Set sleep timeout | Properties/SleepTimeout | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Allow session to resume after screen is idle | Properties/AllowSessionResume | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Allow device account to be used for proxy authentication | Properties/AllowAutoProxyAuth | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Disable auto-populating the sign-in dialog with invitees from scheduled meetings | Properties/DisableSignInSuggestions | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+| Disable "My meetings and files" feature in Start menu | Properties/DoNotShowMyMeetingsAndFiles | Yes </br> [Use a custom policy.](#example-intune)) | Yes<br> [Use a custom setting.] Yes |
+\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. 
 
 ### Supported Windows 10 settings
 
@@ -87,7 +97,7 @@ The following tables include info on Windows 10 settings that have been validate
 | Allow camera | Keep this enabled for Skype for Business. | [Camera/AllowCamera](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Camera_AllowCamera) | Yes. <br> Use a custom policy. | Yes.<br> Use a custom setting. | Yes |
 | Allow location | Keep this enabled to support apps such as Maps. | [System/AllowLocation](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowLocation) | Yes. <br> Use a custom policy. | Yes.<br> Use a custom setting. | Yes |
 | Allow telemetry | Keep this enabled to help Microsoft improve Surface Hub. | [System/AllowTelemetry](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowTelemetry) | Yes. <br> Use a custom policy. | Yes.<br> Use a custom setting. | Yes |
-\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
+\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
 
 #### Browser settings
 
@@ -102,7 +112,7 @@ The following tables include info on Windows 10 settings that have been validate
 | Allow SmartScreen | Keep this enabled to turn on SmartScreen. | [Browser/AllowSmartScreen](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSmartScreen) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
 | Prevent ignoring SmartScreen Filter warnings for websites | For extra security, use to stop users from ignoring SmartScreen Filter warnings and block them from accessing potentially malicious websites. | [Browser/PreventSmartScreenPromptOverride](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverride) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
 | Prevent ignoring SmartScreen Filter warnings for files | For extra security, use to stop users from ignoring SmartScreen Filter warnings and block them from downloading unverified files from Microsoft Edge. | [Browser/PreventSmartScreenPromptOverrideForFiles](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverrideForFiles) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
-\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
+\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
 
 #### Windows Update settings
 
@@ -115,7 +125,7 @@ The following tables include info on Windows 10 settings that have been validate
 | Pause quality updates | See above. | [Update/PauseQualityUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseQualityUpdates) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes|
 | Configure device to use WSUS| Use to connect your Surface Hub to WSUS instead of Windows Update – see [Windows updates](manage-windows-updates-for-surface-hub.md). | [Update/UpdateServiceUrl](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_UpdateServiceUrl) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
 | Delivery optimization | Use peer-to-peer content sharing to reduce bandwidth issues during updates. See [Configure Delivery Optimization for Windows 10](https://technet.microsoft.com/itpro/windows/manage/waas-delivery-optimization) for details. | DeliveryOptimization/*`<name of policy>`* <br> See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
-\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
+\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
 
 #### Windows Defender settings
 
@@ -123,7 +133,7 @@ The following tables include info on Windows 10 settings that have been validate
 | ----------- | ---------------- | ------------- |-------------------------- | ---------------------------------------- | ------------------------- |
 | Defender policies | Use to configure various Defender settings, including a scheduled scan time. | Defender/*`<name of policy>`* <br> See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes. <br>  Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
 | Defender status | Use to initiate a Defender scan, force a signature update, query any threats detected. | [Defender CSP](https://msdn.microsoft.com/library/windows/hardware/mt187856.aspx) | No. | No. | Yes |
-\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
+\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
 
 #### Remote reboot
 
@@ -132,7 +142,7 @@ The following tables include info on Windows 10 settings that have been validate
 | Reboot the device immediately | Use in conjunction with OMS to minimize support costs – see [Monitor your Microsoft Surface Hub](monitor-surface-hub.md). | ./Vendor/MSFT/Reboot/RebootNow <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | No | No | Yes |
 | Reboot the device at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/Single <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
 | Reboot the device daily at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/DailyRecurrent <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes. <br> Use a custom policy. | Yes. <br> Use a custom setting. | Yes |
-\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
+\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
 
 #### Install certificates
 
@@ -142,7 +152,7 @@ The following tables include info on Windows 10 settings that have been validate
 <!--
 | Install client certificates  | Use to deploy Personal Information Exchange (.pfx, .p12) certificates. | [ClientCertificateInstall CSP](https://msdn.microsoft.com/library/windows/hardware/dn920023.aspx) | Yes. <br> See [How to Create and Deploy PFX Certificate Profiles in Intune Standalone](https://blogs.technet.microsoft.com/karanrustagi/2016/03/16/want-to-push-a-certificate-to-device-but-cant-use-ndes-continue-reading/). | Yes. <br> See [How to create PFX certificate profiles in System Center Configuration Manager](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/create-pfx-certificate-profiles). | Yes |
 -->
-\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
+\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
 
 #### Collect logs
 
@@ -151,7 +161,7 @@ The following tables include info on Windows 10 settings that have been validate
 | Collect ETW logs | Use to remotely collect ETW logs from Surface Hub. | [DiagnosticLog CSP](https://msdn.microsoft.com/library/windows/hardware/mt219118.aspx) | No | No | Yes |
 <!--
 | Collect security auditing logs | Use to remotely collect security auditing logs from Surface Hub. | SecurityAuditing node in [Reporting CSP](https://msdn.microsoft.com/en-us/library/windows/hardware/mt608321.aspx) | No | No | Yes |-->
-\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package.
+\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
 
 ### Generate OMA URIs for settings 
 You need to use a setting’s OMA URI to create a custom policy in Intune, or a custom setting in System Center Configuration Manager.
@@ -252,7 +262,7 @@ For more information, see [Create configuration items for Windows 8.1 and Window
 
 [Manage Microsoft Surface Hub](manage-surface-hub.md)
 
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
+
 
  
 

devices/surface-hub/manage-surface-hub-settings.md

@@ -6,7 +6,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/manage-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -30,7 +30,7 @@ Learn about managing and updating Surface Hub.
 | [Remote Surface Hub management](remote-surface-hub-management.md) |Topics related to managing your Surface Hub remotely. Include install apps, managing settings with MDM and monitoring with Operations Management Suite. |
 | [Manage Surface Hub settings](manage-surface-hub-settings.md) |Topics related to managing Surface Hub settings: accessibility, device account, device reset, fully qualified domain name, Windows Update settings, and wireless network |
 | [Install apps on your Surface Hub]( https://technet.microsoft.com/itpro/surface-hub/install-apps-on-surface-hub) | Admins can install apps can from either the Windows Store or the Windows Store for Business.|
-| [End a meeting with I’m done](https://technet.microsoft.com/itpro/surface-hub/i-am-done-finishing-your-surface-hub-meeting) | At the end of a meeting, users can tap I'm Done to clean up any sensitive data and prepare the device for the next meeting.|
+| [End a meeting with End session](https://technet.microsoft.com/itpro/surface-hub/i-am-done-finishing-your-surface-hub-meeting) | At the end of a meeting, users can tap **End session** to clean up any sensitive data and prepare the device for the next meeting.|
 | [Save your BitLocker key](https://technet.microsoft.com/itpro/surface-hub/save-bitlocker-key-surface-hub) | Every Surface Hub is automatically set up with BitLocker drive encryption software. Microsoft strongly recommends that you make sure you back up your BitLocker recovery keys.|
 | [Connect other devices and display with Surface Hub](https://technet.microsoft.com/itpro/surface-hub/connect-and-display-with-surface-hub) | You can connect other device to your Surface Hub to display content.|
 | [Using a room control system]( https://technet.microsoft.com/itpro/surface-hub/use-room-control-system-with-surface-hub) | Room control systems can be used with your Microsoft Surface Hub.|

devices/surface-hub/manage-windows-updates-for-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/monitor-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/online-deployment-surface-hub-device-accounts.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/password-management-for-surface-hub-device-accounts.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub, security
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/physically-install-your-surface-hub-device.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub, readiness
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/prepare-your-environment-for-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: plan
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -27,11 +27,12 @@ Review these dependencies to make sure Surface Hub features will work in your IT
 | Skype for Business (Lync Server 2013 or later, or Skype for Business Online)  | Skype for Business is used for various conferencing features, like video calls, instant messaging, and screen sharing.</br></br>If screen sharing on a Surface Hub fails and the error message **An error occurred during the screen presentation** is displayed, see [Video Based Screen Sharing not working on Surface Hub](https://support.microsoft.com/help/3179272/video-based-screen-sharing-not-working-on-surface-hub) for help. |
 | Mobile device management (MDM) solution (Microsoft Intune, System Center Configuration Manager, or supported third-party MDM provider) | If you want to apply settings and install apps remotely, and to multiple devices at a time, you must set up a MDM solution and enroll the device to that solution. See [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) for details. |
 | Microsoft Operations Managmement Suite (OMS)   | OMS is used to monitor the health of Surface Hub devices. See [Monitor your Surface Hub](monitor-surface-hub.md) for details. |
-| Network and Internet access   | <p>In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred.</p><p>**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.</p>**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. |
+| Network and Internet access   | <p>In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred. 802.1x Authentication is supported for both wired and wireless connections.</p><p>**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.</p>**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. Proxy credentials are stored across Surface Hub sessions and only need to be set once. |
 
 Additionally, note that Surface Hub requires the following open ports:
 - HTTPS: 443
 - HTTP: 80
+- NTP: 123
 
 Depending on your environment, access to additional ports may be needed:
 - For online environments, see [Office 365 IP URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US).
@@ -49,7 +50,7 @@ Surface Hub interacts with a few different products and services. Depending on t
 
 ## Create and verify device account
 
-A device account is an Exchange resource account that Surface Hub uses to display its meeting calendar, join Skype for Business calls, and send email. See [Create and test a device account](create-and-test-a-device-account-surface-hub.md) for details.
+A device account is an Exchange resource account that Surface Hub uses to display its meeting calendar, join Skype for Business calls, send email, and (optionally) to authenticate to Exchange. See [Create and test a device account](create-and-test-a-device-account-surface-hub.md) for details.
 
 After you've created your device account, there are a couple of ways to verify that it's setup correctly.
 - Run Surface Hub device account validation PowerShell scripts. For more information, see [Surface Hub device account scripts](https://gallery.technet.microsoft.com/scriptcenter/Surface-Hub-device-account-6db77696) in Script Center, or [PowerShell scripts for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) later in this guide. 

devices/surface-hub/provisioning-packages-for-certificates-surface-hub.md

@@ -1,221 +0,0 @@
----
-title: Create provisioning packages (Surface Hub)
-description: For Windows 10, settings that use the registry or a content services platform (CSP) can be configured using provisioning packages. You can also add certificates during first run using provisioning.
-ms.assetid: 8AA25BD4-8A8F-4B95-9268-504A49BA5345
-keywords: add certificate, provisioning package
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype: surfacehub
-author: TrudyHa
-localizationpriority: medium
----
-
-# Create provisioning packages (Surface Hub)
-
-This topic explains how to create a provisioning package using the Windows Imaging and Configuration Designer (ICD), and apply it to Surface Hub devices. For Surface Hub, you can use provisioning packages to add certificates, install Universal Windows Platform (UWP) apps, and customize policies and settings.
-
-You can apply a provisioning package using a USB during first run, or through the **Settings** app. 
-
-
-## Advantages
--   Quickly configure devices without using a MDM provider.
-
--   No network connectivity required.
-
--   Simple to apply.
-
-[Learn more about the benefits and uses of provisioning packages.](https://technet.microsoft.com/itpro/windows/whats-new/new-provisioning-packages)
-
-
-## Requirements 
-
-To create and apply a provisioning package to a Surface Hub, you'll need the following:
-
--   Windows Imaging and Configuration Designer (ICD), which is installed as a part of the [Windows 10 Assessment and Deployment Kit (ADK)](http://go.microsoft.com/fwlink/p/?LinkId=526740).
--   A PC running Windows 10.
--   A USB flash drive.
--   If you apply the package using the **Settings** app, you'll need device admin credentials.
-
-You'll create the provisioning package on a PC running Windows 10, save the package to a USB drive, and then deploy it to your Surface Hub.
-
-
-## Supported items for Surface Hub provisioning packages
-
-Currently, you can add these items to provisioning packages for Surface Hub:
-- **Certificates** - You can add certificates, if needed, to authenticate to Microsoft Exchange.
-- **Universal Windows Platform (UWP) apps** - You can install UWP apps. This can be an offline-licensed app from the Windows Store for Business, or an app created by an in-house dev.
-- **Policies** - Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD.
-- **Settings** - You can configure any setting in the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx).
-
-
-## Create the provisioning package
-
-Use the Windows Imaging and Configuration Designer (ICD) tool included in the Windows Assessment and Deployment Kit (ADK) for Windows 10 to create a provisioning package. When you install the ADK, you can choose to install only the Imaging and Configuration Designer (ICD).  [Install the ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740)
-
-1. Open Windows ICD (by default, `%windir%\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe`).
-
-2. Click **Advanced provisioning**.
-
-    ![ICD start options](images/ICDstart-option.PNG)  
-  
-3. Name your project and click **Next**.
-
-4. Select **Common to Windows 10 Team edition**, click **Next**, and then click **Finish**.
-
-    ![ICD new project](images/icd-new-project.png)
-
-5. In the project, under **Available customizations**, select **Common Team edition settings**.
-
-    ![ICD common settings](images/icd-common-settings.png)
-
-
-### Add a certificate to your package
-You can use provisioning packages to install certificates that will allow the device to authenticate to Microsoft Exchange.
-
-> [!NOTE]
-> Provisioning packages can only install certificates to the device (local machine) store, and not to the user store. If your organization requires that certificates must be installed to the user store, use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details.
-
-1. In the **Available customizations** pane, go to **Runtime settings** > **Certificates** > **ClientCertificates**. 
-
-2. Enter a **CertificateName** and then click **Add**. 
-
-2. Enter the **CertificatePassword**. 
-
-3. For **CertificatePath**, browse and select the certificate. 
-
-4. Set **ExportCertificate** to **False**.
-
-5. For **KeyLocation**, select **Software only**.
-
-
-### Add a Universal Windows Platform (UWP) app to your package
-Before adding a UWP app to a provisioning package, you need the app package (either an .appx, or .appxbundle) and any dependency files. If you acquired the app from the Windows Store for Business, you will also need the *unencoded* app license. See [Distribute offline apps](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app) to learn how to download these items from the Windows Store for Business.
-
-1. In the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextApp**.
-
-2. Enter a **PackageFamilyName** for the app and then click **Add**. For consistency, use the app's package family name. If you acquired the app from the Windows Store for Business, you can find the package family name in the app license. Open the license file using a text editor, and use the value between the \<PFM\>...\</PFM\> tags.
-
-3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle).
-
-4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. For Surface Hub, you will only need the x64 versions of these dependencies.
-
-If you acquired the app from the Windows Store for Business, you will also need to add the app license to your provisioning package.
-
-1. Make a copy of the app license, and rename it to use a **.ms-windows-store-license** extension. For example, "example.xml" becomes "example.ms-windows-store-license".
-
-2. In ICD, in the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextAppLicense**.
-
-3. Enter a **LicenseProductId** and then click **Add**. For consistency, use the app's license ID from the app license. Open the license file using a text editor. Then, in the \<License\> tag, use the value in the **LicenseID** attribute.
-
-4. Select the new **LicenseProductId** node. For **LicenseInstall**, click **Browse** to find and select the license file that you renamed in Step 1.
-
-
-### Add a policy to your package
-Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD.
-
-1. In the **Available customizations** pane, go to **Runtime settings** > **Policies**.
-
-2. Select one of the available policy areas.
-
-3. Select and set the policy you want to add to your provisioning package.
-
-
-### Add Surface Hub settings to your package 
-
-You can add settings from the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx) to your provisioning package. 
-
-1. In the **Available customizations** pane, go to **Runtime settings** > **WindowsTeamSettings**.
-
-2. Select one of the available setting areas.
-
-3. Select and set the setting you want to add to your provisioning package. 
-
-
-## Build your package
-
-1. When you are done configuring the provisioning package, on the **File** menu, click **Save**.
-
-2. Read the warning that project files may contain sensitive information, and click **OK**.
-
-    > [!IMPORTANT]
-    > When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
-
-3. On the **Export** menu, click **Provisioning package**.
-
-4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources.
-
-5. Set a value for **Package Version**, and then select **Next.**
-
-    > [!TIP]
-    > You can make changes to existing packages and change the version number to update previously applied packages.
-
-6. Optional: You can choose to encrypt the package and enable package signing.
-
-    -   **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
-
-    -   **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse...** and choosing the certificate you want to use to sign the package.
-
-        > [!IMPORTANT]
-        > We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently. 
-
-7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.<p>
-Optionally, you can click **Browse** to change the default output location.
-
-8. Click **Next**.
-
-9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.<p>
-If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
-
-10. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.<p>
-If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
-
-    -   If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build.
-    
-    -   If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
-
-11. Select the **output location** link to go to the location of the package. Copy the .ppkg to an empty USB flash drive.
-
-
-## Apply a provisioning package to Surface Hub
-
-There are two options for deploying provisioning packages to a Surface Hub. You can apply a provisioning packing [during the first run wizard](#apply-a-provisioning-package-during-first-run), or using [Settings](#apply-a-package-using-settings). 
-
-
-### Apply a provisioning package during first run
-
-> [!IMPORTANT]
-> Only use provisioning packages to install certificates during first run. Use the **Settings** app to install apps and apply other settings.
-
-1. When you turn on the Surface Hub for the first time, the first-run program will display the [**Hi there page**](first-run-program-surface-hub.md#first-page). Make sure that the settings are properly configured before proceeding.
-
-2. Insert the USB flash drive containing the .ppkg file into the Surface Hub. If the package is in the root directory of the drive, the first-run program will recognize it and ask if you want to set up the device. Select **Set up**.
-
-    ![Set up device?](images/provisioningpackageoobe-01.png)
-
-3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
-
-    ![Provision this device](images/provisioningpackageoobe-02.png)
-    
-4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**. Note that you can only install one package during first run.
-
-    ![Choose a package](images/provisioningpackageoobe-03.png)
-
-5. The first-run program will show you a summary of the changes that the provisioning package will apply. Select **Yes, add it**. The package will be applied, and you'll be taken to the next page in the first-run program.
-
-    ![Do you trust this package?](images/provisioningpackageoobe-04.png)
-
-
-### Apply a package using Settings
-
-1. Insert the USB flash drive containing the .ppkg file into the Surface Hub.
-
-2. From the Surface Hub, start **Settings** and enter the admin credentials when prompted.
-
-3. Navigate to **This device** > **Device management**. Under **Provisioning packages**, select **Add or remove a provisioning package**.
-
-4. Select **Add a package**.
-
-5. Choose your provisioning package and select **Add**. You may have to re-enter the admin credentials if prompted.
-
-6. You'll see a summary of the changes that the provisioning package will apply. Select **Yes, add it**.

devices/surface-hub/provisioning-packages-for-surface-hub.md

@@ -0,0 +1,319 @@
+---
+title: Create provisioning packages (Surface Hub)
+description: For Windows 10, settings that use the registry or a configuration service provider (CSP) can be configured using provisioning packages. 
+ms.assetid: 8AA25BD4-8A8F-4B95-9268-504A49BA5345
+keywords: add certificate, provisioning package
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: surfacehub
+author: jdeckerMS
+localizationpriority: medium
+---
+
+# Create provisioning packages (Surface Hub)
+
+This topic explains how to create a provisioning package using the Windows Configuration Designer, and apply it to Surface Hub devices. For Surface Hub, you can use provisioning packages to add certificates, install Universal Windows Platform (UWP) apps, and customize policies and settings.
+
+You can apply a provisioning package using a USB stick during first-run setup, or through the **Settings** app. 
+
+
+## Advantages
+-   Quickly configure devices without using a mobile device management (MDM) provider.
+
+-   No network connectivity required.
+
+-   Simple to apply.
+
+[Learn more about the benefits and uses of provisioning packages.](https://technet.microsoft.com/itpro/windows/configure/provisioning-packages)
+
+
+## Requirements 
+
+To create and apply a provisioning package to a Surface Hub, you'll need the following:
+
+-   Windows Configuration Designer, which can be installed from Windows Store or from the Windows 10 Assessment and Deployment Kit (ADK). [Learn how to install Windows Configuration Designer.](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd)
+-   A USB stick.
+-   If you apply the package using the **Settings** app, you'll need device admin credentials.
+
+You create the provisioning package on a PC running Windows 10, save the package to a USB drive, and then deploy it to your Surface Hub.
+
+
+## Supported items for Surface Hub provisioning packages
+
+Using the **Provision Surface Hub devices** wizard, you can:
+
+- Enroll in Active Directory, Azure Active Directory, or MDM 
+- Create an device administrator account 
+- Add applications and certificates
+- Configure proxy settings
+- Add a Surface Hub configuration file
+
+>[!WARNING]
+>You must run Windows Configuration Designer on Windows 10 to configure Azure Active Directory enrollment using the wizard.
+
+Using the advanced provisioning editor, you can add these items to provisioning packages for Surface Hub:
+
+- **Policies** - Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#surfacehubpolicies). 
+- **Settings** - You can configure any setting in the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx).
+
+>[!TIP]
+> Use the wizard to create a package with the common settings, then switch to the advanced editor to add other settings.
+>
+>![open advanced editor](images/icd-simple-edit.png)
+
+## Use the Surface Hub provisioning wizard
+
+After you [install Windows Configuration Designer](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd), you can create a provisioning package.
+
+### Create the provisioning package 
+
+1. Open Windows Configuration Designer:
+    - From either the Start screen or Start menu search, type 'Windows Configuration Designer' and click on the Windows Configuration Designer shortcut, 
+    
+    or
+    
+    - If you installed Windows Configuration Designer from the ADK, navigate to `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86` (on an x64 computer) or `C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe` (on an x86 computer), and then double-click **ICD.exe**.
+
+2. Click **Provision Surface Hub devices**.
+
+3. Name your project and click **Next**.
+
+### Configure settings
+
+<table>
+<tr><td style="width:45%" valign="top">![step one](images/one.png) ![add certificates](images/add-certificates.png)</br></br>To provision the device with a certificate, click **Add a certificate**. Enter a name for the certificate, and then browse to and select the certificate to be used.</td><td>![add a certificate](images/add-certificates-details.png)</td></tr> 
+<tr><td style="width:45%" valign="top">![step two](images/two.png)  ![configure proxy settings](images/proxy.png)</br></br>Toggle **Yes** or **No** for proxy settings. The default configuration for Surface Hub is to automatically detect proxy settings, so you can select **No** if that is the setting that you want. However, if your infrastructure previously required using a proxy server and has changed to not require a proxy server, you can use a provisioning package to revert your Surface Hub devices to the default settings by selecting **Yes** and **Automatically detect settings**. </br></br>If you toggle **Yes**, you can select to automatically detect proxy settings, or you can manually configure the settings by entering a URL to a setup script, or a static proxy server address. You can also identify whether to use the proxy server for local addresses, and enter exceptions (addresses that Surface Hub should connect to directly without using the proxy server).  </td><td>![configure proxy settings](images/proxy-details.png)</td></tr>
+<tr><td style="width:45%" valign="top">![step three](images/three.png)  ![device admins](images/set-up-device-admins.png)</br></br>You can enroll the device in Active Directory and specify a security group to use the Settings app, enroll in Azure Active Directory to allow global admins to use the Settings app, or create a local administrator account on the device.</br></br>To enroll the device in Active Directory, enter the credentials for a least-privileged user account to join the device to the domain, and specify the security group to have admin credentials on Surface Hub. If a provisioning package that enrolls a device in Active Directory is going to be applied to a Surface Hub that was reset, the same domain account can only be used if the account listed is a domain administrator or is the same account that set up the Surface Hub initially. Otherwise, a different domain account must be used in the provisioning package.</br></br>Before you use a Windows Configuration Designer wizard to configure bulk Azure AD enrollment, [set up Azure AD join in your organization](https://docs.microsoft.com/azure/active-directory/active-directory-azureadjoin-setup). The **maximum number of devices per user** setting in your Azure AD tenant determines how many times the bulk token that you get in the wizard can be used. To enroll the device in Azure AD, select that option and enter a friendly name for the bulk token you will get using the wizard. Set an expiration date for the token (maximum is 30 days from the date you get the token). Click **Get bulk token**. In the **Let's get you signed in** window, enter an account that has permissions to join a device to Azure AD, and then the password. Click **Accept** to give Windows Configuration Designer the necessary permissions.</br></br>To create a local administrator account, select that option and enter a user name and password. </br></br>**Important:** If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in.  </td><td>![join Active Directory, Azure AD, or create a local admin account](images/set-up-device-admins-details.png)</td></tr>
+<tr><td style="width:45%" valign="top">![step four](images/four.png) ![enroll in device management](images/enroll-mdm.png)</br></br>Toggle **Yes** or **No** for enrollment in MDM. </br></br>If you toggle **Yes**, you must provide a service account and password or certificate thumbprint that is authorized to enroll the device, and also specify the authentication type. If required by your MDM provider, also enter the URLs for the discovery service, enrollment service, and policy service. [Learn more about managing Surface Hub with MDM.](manage-settings-with-mdm-for-surface-hub.md)</td><td>![enroll in mobile device management](images/enroll-mdm-details.png)</td></tr>
+<tr><td style="width:45%" valign="top">![step five](images/five.png) ![add applications](images/add-applications.png)</br></br>You can install multiple Universal Windows Platform (UWP) apps in a provisioning package. For help with the settings, see [Provision PCs with apps](https://technet.microsoft.com/itpro/windows/configure/provision-pcs-with-apps). </br></br>**Important:** Although the wizard interface allows you to select a Classic Win32 app, only include UWP apps in a provisioning package that will be applied to Surface Hub. If you include a Classic Win32 app, provisioning will fail. </td><td>![add an application](images/add-applications-details.png)</td></tr>
+<tr><td style="width:45%" valign="top">![step six](images/six.png)  ![Add configuration file](images/add-config-file.png)</br></br>You don't configure any settings in this step. It provides instructions for including a configuration file that contains a list of device accounts. The configuration file must not contain column headers. When you apply the provisioning package to Surface Hub, if a Surface Hub configuration file is included on the USB drive, you can select the account and friendly name for the device from the file. See [Sample configuration file](#sample-configuration-file) for an example.</br></br>**Important:** The configuration file can only be applied during the out-of-box setup experience (OOBE) and can only be used with provisioning packages created using the Windows Configuration Designer released with Windows 10, version 1703.  </td><td>![Add a Surface Hub configuration file](images/add-config-file-details.png)</td></tr>
+<tr><td style="width:45%" valign="top">  ![finish](images/finish.png)</br></br>You can set a password to protect your provisioning package. You must enter this password when you apply the provisioning package to a device.</td><td>![Protect your package](images/finish-details.png)</td></tr>
+</table>
+
+After you're done, click **Create**. It only takes a few seconds. When the package is built, the location where the package is stored is displayed as a hyperlink at the bottom of the page.
+
+## Sample configuration file
+
+A Surface Hub configuration file contains a list of device accounts that your device can use to connect to Exchange and Skype for Business. When you apply a provisioning package to Surface Hub, you can include a configuration file in the root directory of the USB flash drive, and then select the desired account to apply to that device. The configuration file can only be applied during the out-of-box setup experience (OOBE) and can only be used with provisioning packages created using the Windows Configuration Designer released with Windows 10, version 1703.
+
+Use Microsoft Excel or other CSV editor to create a CSV file named `SurfaceHubConfiguration.csv`. In the file, enter a list of device accounts and friendly names in this format:
+
+```
+<DeviceAccountName>,<DeviceAccountPassword>,<FriendlyName>
+```
+>[!IMPORTANT]
+>Because the configuration file stores the device account passwords in plaintext, we recommend that you update the passwords after you've applied the provisioning package to your devices. You can use the [DeviceAccount node](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp#deviceaccount) in the [Surface Hub configuration service provider (CSP)](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp) to update the passwords via MDM.
+
+
+The following is an example of `SurfaceHubConfiguration.csv`. 
+
+```
+Rainier@contoso.com,password,Rainier Surface Hub
+Adams@contoso.com,password,Adams Surface Hub
+Baker@contoso.com,password,Baker Surface Hub
+Glacier@constoso.com,password,Glacier Surface Hub
+Stuart@contoso.com,password,Stuart Surface Hub
+Fernow@contoso.com,password,Fernow Surface Hub
+Goode@contoso.com,password,Goode Surface Hub
+Shuksan@contoso.com,password,Shuksan Surface Hub
+Buckner@contoso.com,password,Buckner Surface Hub
+Logan@contoso.com,password,Logan Surface Hub
+Maude@consoto.com,password,Maude Surface hub
+Spickard@contoso.com,password,Spickard Surface Hub
+Redoubt@contoso.com,password,Redoubt Surface Hub
+Dome@contoso.com,password,Dome Surface Hub
+Eldorado@contoso.com,password,Eldorado Surface Hub
+Dragontail@contoso.com,password,Dragontail Surface Hub
+Forbidden@contoso.com,password,Forbidden Surface Hub
+Oval@contoso.com,password,Oval Surface Hub
+StHelens@contoso.com,password,St Helens Surface Hub
+Rushmore@contoso.com,password,Rushmore Surface Hub
+```
+
+## Use advanced provisioning
+
+After you [install Windows Configuration Designer](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd), you can create a provisioning package.
+
+### Create the provisioning package (advanced)
+
+1. Open Windows Configuration Designer:
+    - From either the Start screen or Start menu search, type 'Windows Configuration Designer' and click on the Windows Configuration Designer shortcut, 
+    
+    or
+    
+    - If you installed Windows Configuration Designer from the ADK, navigate to `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86` (on an x64 computer) or `C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe` (on an x86 computer), and then double-click **ICD.exe**.
+
+2. Click **Advanced provisioning**.
+   
+3. Name your project and click **Next**.
+
+4. Select **Common to Windows 10 Team edition**, click **Next**, and then click **Finish**.
+
+    ![ICD new project](images/icd-new-project.png)
+
+5. In the project, under **Available customizations**, select **Common Team edition settings**.
+
+    ![ICD common settings](images/icd-common-settings.png)
+
+
+### Add a certificate to your package
+You can use provisioning packages to install certificates that will allow the device to authenticate to Microsoft Exchange.
+
+> [!NOTE]
+> Provisioning packages can only install certificates to the device (local machine) store, and not to the user store. If your organization requires that certificates must be installed to the user store, use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details.
+
+1. In the **Available customizations** pane, go to **Runtime settings** > **Certificates** > **ClientCertificates**. 
+
+2. Enter a **CertificateName** and then click **Add**. 
+
+2. Enter the **CertificatePassword**. 
+
+3. For **CertificatePath**, browse and select the certificate. 
+
+4. Set **ExportCertificate** to **False**.
+
+5. For **KeyLocation**, select **Software only**.
+
+
+### Add a Universal Windows Platform (UWP) app to your package
+Before adding a UWP app to a provisioning package, you need the app package (either an .appx, or .appxbundle) and any dependency files. If you acquired the app from the Windows Store for Business, you will also need the *unencoded* app license. See [Distribute offline apps](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app) to learn how to download these items from the Windows Store for Business.
+
+1. In the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextApp**.
+
+2. Enter a **PackageFamilyName** for the app and then click **Add**. For consistency, use the app's package family name. If you acquired the app from the Windows Store for Business, you can find the package family name in the app license. Open the license file using a text editor, and use the value between the \<PFM\>...\</PFM\> tags.
+
+3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle).
+
+4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. For Surface Hub, you will only need the x64 versions of these dependencies.
+
+If you acquired the app from the Windows Store for Business, you will also need to add the app license to your provisioning package.
+
+1. Make a copy of the app license, and rename it to use a **.ms-windows-store-license** extension. For example, "example.xml" becomes "example.ms-windows-store-license".
+
+2. In ICD, in the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextAppLicense**.
+
+3. Enter a **LicenseProductId** and then click **Add**. For consistency, use the app's license ID from the app license. Open the license file using a text editor. Then, in the \<License\> tag, use the value in the **LicenseID** attribute.
+
+4. Select the new **LicenseProductId** node. For **LicenseInstall**, click **Browse** to find and select the license file that you renamed in Step 1.
+
+
+### Add a policy to your package
+Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD.
+
+1. In the **Available customizations** pane, go to **Runtime settings** > **Policies**.
+
+2. Select one of the available policy areas.
+
+3. Select and set the policy you want to add to your provisioning package.
+
+
+### Add Surface Hub settings to your package 
+
+You can add settings from the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx) to your provisioning package. 
+
+1. In the **Available customizations** pane, go to **Runtime settings** > **WindowsTeamSettings**.
+
+2. Select one of the available setting areas.
+
+3. Select and set the setting you want to add to your provisioning package. 
+
+
+## Build your package
+
+1. When you are done configuring the provisioning package, on the **File** menu, click **Save**.
+
+2. Read the warning that project files may contain sensitive information, and click **OK**.
+
+    > [!IMPORTANT]
+    > When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
+
+3. On the **Export** menu, click **Provisioning package**.
+
+4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources.
+
+5. Set a value for **Package Version**, and then select **Next.**
+
+    > [!TIP]
+    > You can make changes to existing packages and change the version number to update previously applied packages.
+
+6. Optional: You can choose to encrypt the package and enable package signing.
+
+    -   **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
+
+    -   **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse...** and choosing the certificate you want to use to sign the package.
+
+        > [!IMPORTANT]
+        > We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently. 
+
+7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.<p>
+Optionally, you can click **Browse** to change the default output location.
+
+8. Click **Next**.
+
+9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.<p>
+If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
+
+10. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.<p>
+If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
+
+    -   If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build.
+    
+    -   If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
+
+11. Select the **output location** link to go to the location of the package. Copy the .ppkg to an empty USB flash drive.
+
+
+## Apply a provisioning package to Surface Hub
+
+There are two options for deploying provisioning packages to a Surface Hub. You can apply a provisioning packing [during the first run wizard](#apply-a-provisioning-package-during-first-run), or using [Settings](#apply-a-package-using-settings). 
+
+
+### Apply a provisioning package during first run
+
+> [!IMPORTANT]
+> Only use provisioning packages to install certificates during first run. Use the **Settings** app to install apps and apply other settings.
+
+1. When you turn on the Surface Hub for the first time, the first-run program will display the [**Hi there page**](first-run-program-surface-hub.md#first-page). Make sure that the settings are properly configured before proceeding.
+
+2. Insert the USB flash drive containing the .ppkg file into the Surface Hub. If the package is in the root directory of the drive, the first-run program will recognize it and ask if you want to set up the device. Select **Set up**.
+
+    ![Set up device?](images/provisioningpackageoobe-01.png)
+
+3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
+
+    ![Provision this device](images/provisioningpackageoobe-02.png)
+    
+4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**. Note that you can only install one package during first run.
+
+    ![Choose a package](images/provisioningpackageoobe-03.png)
+
+5. The first-run program will show you a summary of the changes that the provisioning package will apply. Select **Yes, add it**.  
+
+    ![Do you trust this package?](images/provisioningpackageoobe-04.png)
+    
+6. If a configuration file is included in the root directory of the USB flash drive, you will see **Select a configuration**. The first device account in the configuration file will be shown with a summary of the account information that will be applied to the Surface Hub.
+
+    ![select a configuration](images/ppkg-config.png)    
+
+7. In **Select a configuration**, select the device name to apply, and then click **Next**.
+
+    ![select a friendly device name](images/ppkg-csv.png)
+    
+The settings from the provisioning package will be applied to the device and OOBE will be complete. After the device restarts, you can remove the USB flash drive.
+
+### Apply a package using Settings
+
+1. Insert the USB flash drive containing the .ppkg file into the Surface Hub.
+
+2. From the Surface Hub, start **Settings** and enter the admin credentials when prompted.
+
+3. Navigate to **Surface Hub** > **Device management**. Under **Provisioning packages**, select **Add or remove a provisioning package**.
+
+4. Select **Add a package**.
+
+5. Choose your provisioning package and select **Add**. You may have to re-enter the admin credentials if prompted.
+
+6. You'll see a summary of the changes that the provisioning package will apply. Select **Yes, add it**.
+
+

devices/surface-hub/remote-surface-hub-management.md

@@ -6,7 +6,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/save-bitlocker-key-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub, security
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/set-up-your-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/setup-worksheet-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/surfacehub-whats-new-1703.md

@@ -0,0 +1,31 @@
+---
+title: What's new in Windows 10, version 1703 for Surface Hub 
+description: Windows 10, version 1703 (Creators Update) brings new features to Microsoft Surface Hub.
+ms.prod: w10
+ms.mktglfcycl: manage
+ms.pagetype: devices
+ms.sitesec: library
+author: jdeckerMS
+localizationpriority: medium
+---
+
+# What's new in Windows 10, version 1703 for Microsoft Surface Hub?
+
+Windows 10, version 1703 (also called the Creators Update), introduces the following changes for Microsoft Surface Hub:
+
+
+- Settings have been added to mobile device management (MDM) and configuration service providers (CSPs) to expand the Surface Hub management capabilities. [Learn more about the new settings.](manage-settings-with-mdm-for-surface-hub.md)
+
+- An easy-to-use wizard helps you quickly create provisioning packages that you can apply to multiple Surface Hub devices. [Learn how to create a provisioning package for Surface Hub.](provisioning-packages-for-certificates-surface-hub.md)
+
+- When you reset a Surface Hub device, you now have the ability to download and install a factory build of the operating system from the cloud. [Learn more about cloud recovery.](device-reset-surface-hub.md#cloud-recovery)
+    >[!NOTE]
+    >Cloud recovery doesn't work if you use proxy servers.
+    
+- **I'm done** is now **End session**. [Learn how to use End session.](i-am-done-finishing-your-surface-hub-meeting.md) 
+
+
+
+ 
+
+ 

devices/surface-hub/troubleshoot-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: support
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md

@@ -3,7 +3,7 @@ title: Use fully qualified doman name with Surface Hub
 description: Troubleshoot common problems, including setup issues, Exchange ActiveSync errors.
 ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
 keywords: ["Troubleshoot common problems", "setup issues", "Exchange ActiveSync errors"]
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -16,7 +16,7 @@ There are a few scenarios where you need to specify the domain name of your Skyp
 
 **To configure the domain name for your Skype for Business server**</br>
 1. On Surface Hub, open **Settings**.
-2. Click **This device**, and then click **Calling**. 
+2. Click **Surface Hub**, and then click **Calling & Audio**. 
 3. Under **Skype for Business configuration**, click **Configure domain name**. 
 4. Type the domain name for your Skype for Business server, and then click **Ok**. 
 > [!TIP]

devices/surface-hub/use-room-control-system-with-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 

devices/surface-hub/wireless-network-management-for-surface-hub.md

@@ -7,7 +7,7 @@ ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
 ms.pagetype: surfacehub, networking
-author: TrudyHa
+author: jdeckerMS
 localizationpriority: medium
 ---
 
@@ -24,7 +24,7 @@ If a wired network connection is not available, the Surface Hub can use a wirele
 ### Choose a wireless access point
 
 1.  On the Surface Hub, open **Settings** and enter your admin credentials.
-2.  Click **System**, and then click **Network & Internet**. Under **Wi-Fi**, choose an access point. If you want Surface Hub to automatically connect to this access point, click **Connect automatically**. Click **Connect**.
+2.  Click **Network & Internet**. Under **Wi-Fi**, choose an access point. If you want Surface Hub to automatically connect to this access point, click **Connect automatically**. Click **Connect**.
 
     ![Image showing Wi-Fi settings, Network & Internet page.](images/networkmgtwireless-01.png)
 
@@ -35,7 +35,7 @@ If a wired network connection is not available, the Surface Hub can use a wirele
 ### Review wireless settings
 
 1.  On the Surface Hub, open **Settings** and enter your admin credentials.
-2.  Click **System**, click **Network & Internet**, then **Wi-Fi**, and then click **Advanced options**.
+2.  Click **Network & Internet**, then **Wi-Fi**, and then click **Advanced options**.
 3.  Surface Hub shows you the properties for the wireless network connection.
 
     ![Image showing properties for connected Wi-Fi.](images/networkmgtwireless-04.png)

windows/configure/windows-10-start-layout-options-and-policies.md

@@ -29,6 +29,7 @@ Organizations might want to deploy a customized Start and taskbar configuration
 >Using the layout modification XML to configure Start is not supported with roaming user profiles. For more information, see [Deploy Roaming User Profiles](https://technet.microsoft.com/library/jj649079.aspx).
 
 
+
 ## Start options
 
 ![start layout sections](images/startannotated.png)

windows/whats-new/whats-new-windows-10-version-1703.md

@@ -29,12 +29,14 @@ Windows Configuration Designer in Windows 10, version 1703, includes several new
 
 [Learn more about Windows Configuration Designer.](../configure/provisioning-packages.md)
 
+
 ### Bulk enrollment in Azure Active Directory
 
 Using the new wizards in Windows Configuration Designer, you can [create provisioning packages to enroll devices in Azure Active Directory](../configure/provisioning-packages.md#configuration-designer-wizards). Bulk enrollment in Azure AD is available in the desktop, mobile, kiosk, and Surface Hub wizards.
 
 ![get bulk token action in wizard](images/bulk-token.png) 
 
+
 ### Windows Spotlight
 
 The following new Group Policy and mobile device management (MDM) settings are added to help you configure Windows Spotlight user experiences: