mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
fixing merge conflicts
This commit is contained in:
Trudy Hakala
1
devices/hololens/TOC.md
Normal file
1
devices/hololens/TOC.md
Normal file
@ -0,0 +1 @@
|
||||
# [Placeholder](index.md)
|
||||
37
devices/hololens/docfx.json
Normal file
37
devices/hololens/docfx.json
Normal file
@ -0,0 +1,37 @@
|
||||
{
|
||||
"build": {
|
||||
"content": [
|
||||
{
|
||||
"files": [
|
||||
"**/*.md"
|
||||
],
|
||||
"exclude": [
|
||||
"**/obj/**",
|
||||
"devices/hololens/**",
|
||||
"**/includes/**"
|
||||
]
|
||||
}
|
||||
],
|
||||
"resource": [
|
||||
{
|
||||
"files": [
|
||||
"**/*.png",
|
||||
"**/*.jpg"
|
||||
],
|
||||
"exclude": [
|
||||
"**/obj/**",
|
||||
"devices/hololens/**",
|
||||
"**/includes/**"
|
||||
]
|
||||
}
|
||||
],
|
||||
"overwrite": [],
|
||||
"externalReference": [],
|
||||
"globalMetadata": {},
|
||||
"fileMetadata": {},
|
||||
"template": [
|
||||
null
|
||||
],
|
||||
"dest": "devices/hololens"
|
||||
}
|
||||
}
|
||||
3
devices/hololens/index.md
Normal file
3
devices/hololens/index.md
Normal file
@ -0,0 +1,3 @@
|
||||
---
|
||||
redirect_url: https://developer.microsoft.com/windows/holographic/commercial_features
|
||||
---
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surfacehub
|
||||
ms.sitesec: library
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Accessibility (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Admin group management (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Appendix: PowerShell (Surface Hub)
|
||||
@ -34,7 +35,7 @@ You can check online for updated versions at [Surface Hub device account scripts
|
||||
What do the scripts do?
|
||||
|
||||
- Create device accounts for setups using pure single-forest on-premises (Microsoft Exchange and Skype 2013 and later only) or online (Microsoft Office 365), that are configured correctly for your Surface Hub.
|
||||
- Validate existing device accounts for any setup (on-premises, online, or hybrid using Exchange or Lync 2010 or later) to make sure they're compatible with Surface Hub.
|
||||
- Validate existing device accounts for any setup (on-premises or online) to make sure they're compatible with Surface Hub.
|
||||
- Provide a base template for anyone wanting to create their own device account creation or validation scripts.
|
||||
|
||||
What do you need in order to run the scripts?
|
||||
@ -611,7 +612,7 @@ catch
|
||||
{
|
||||
PrintError "Some dependencies are missing"
|
||||
PrintError "Please install the Windows PowerShell Module for Lync Online. For more information go to http://www.microsoft.com/download/details.aspx?id=39366"
|
||||
PrintError "Please install the Azure Active Directory module for PowerShell from http://go.microsoft.com/fwlink/p/?linkid=236297"
|
||||
PrintError "Please install the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
|
||||
CleanupAndFail
|
||||
}
|
||||
|
||||
@ -1118,7 +1119,7 @@ if ($fHasOnline)
|
||||
}
|
||||
catch
|
||||
{
|
||||
CleanupAndFail "To verify accounts in online tenants you need the Azure Active Directory module for PowerShell from http://go.microsoft.com/fwlink/p/?linkid=236297"
|
||||
CleanupAndFail "To verify accounts in online tenants you need the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
|
||||
}
|
||||
}
|
||||
|
||||
@ -1517,7 +1518,7 @@ if ($online)
|
||||
{
|
||||
PrintError "Some dependencies are missing"
|
||||
PrintError "Please install the Windows PowerShell Module for Lync Online. For more information go to http://www.microsoft.com/download/details.aspx?id=39366"
|
||||
PrintError "Please install the Azure Active Directory module for PowerShell from http://go.microsoft.com/fwlink/p/?linkid=236297"
|
||||
PrintError "Please install the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
|
||||
CleanupAndFail
|
||||
}
|
||||
}
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Applying ActiveSync policies to device accounts (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Change the Microsoft Surface Hub device account
|
||||
|
||||
@ -7,6 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Connect other devices and display with Surface Hub
|
||||
@ -224,7 +225,7 @@ In replacement PC mode, the embedded computer of the Surface Hub is turned off a
|
||||
|
||||
### Software requirements
|
||||
|
||||
You can run Surface Hub in replacement PC mode with 64-bit versions of Windows 10 Home, Windows 10 Pro and Windows 10 Enterprise. You can download the [Surface Hub Replacement PC driver package](https://www.microsoft.com/en-us/download/details.aspx?id=52210) from the Microsoft download center. We recommend that you install these drivers on any computer you plan to use as a replacement PC.
|
||||
You can run Surface Hub in replacement PC mode with 64-bit versions of Windows 10 Home, Windows 10 Pro and Windows 10 Enterprise. You can download the [Surface Hub Replacement PC driver package](https://www.microsoft.com/download/details.aspx?id=52210) from the Microsoft download center. We recommend that you install these drivers on any computer you plan to use as a replacement PC.
|
||||
|
||||
### Hardware requirements
|
||||
|
||||
@ -389,7 +390,7 @@ Replacement PC ports on 84" Surface Hub.
|
||||
|
||||
**To use replacement PC mode**
|
||||
|
||||
1. Download and install the [Surface Hub Replacement PC driver package](https://www.microsoft.com/en-us/download/details.aspx?id=52210) on the replacement PC.
|
||||
1. Download and install the [Surface Hub Replacement PC driver package](https://www.microsoft.com/download/details.aspx?id=52210) on the replacement PC.
|
||||
|
||||
**Note** We recommend that you set sleep or hibernation on the replacement PC so the Surface Hub will turn off the display when it isn't being used.
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Create a device account using UI (Surface Hub)
|
||||
@ -26,7 +27,7 @@ If you prefer to use a graphical user interface, you can create a device account
|
||||
|
||||
### <a href="" id="create-device-acct-o365-admin-ctr"></a>Create the account in the Office 365 Admin Center
|
||||
|
||||
1. Sign in to Office 365 by visiting http://portal.office.com/admin/
|
||||
1. Sign in to Office 365 by visiting http://portal.office.com
|
||||
2. Provide the admin credentials for your Office 365 tenant. This will take you to your Office 365 Admin Center.
|
||||
|
||||
|
||||
@ -53,7 +54,7 @@ If you prefer to use a graphical user interface, you can create a device account
|
||||
|
||||
|
||||
|
||||
From the list, uncheck **Skype for Business Online (plan 2)** (this license may vary depending on your organization), and click **SAVE**.
|
||||
From the list, select **Skype for Business Online (Plan 2)**, and then click **SAVE**. The license may vary depending on your organization (for example, you might have Plan 2, or Plan 3).
|
||||
|
||||
### <a href="" id="create-device-acct-o365-mbx-policy"></a>Create a mobile device mailbox (ActiveSync) policy from the Exchange Admin Center
|
||||
|
||||
@ -99,8 +100,8 @@ From here on, you'll need to finish the account creation process using PowerShel
|
||||
|
||||
In order to run cmdlets used by these PowerShell scripts, the following must be installed for the admin PowerShell console:
|
||||
|
||||
- [Microsoft Online Services Sign-In Assistant for IT Professionals BETA](http://go.microsoft.com/fwlink/?LinkId=718149)
|
||||
- [Windows Azure Active Directory Module for Windows PowerShell](http://go.microsoft.com/fwlink/p/?linkid=236297)
|
||||
- [Microsoft Online Services Sign-In Assistant for IT Professionals BETA](https://go.microsoft.com/fwlink/?LinkId=718149)
|
||||
- [Windows Azure Active Directory Module for Windows PowerShell](https://go.microsoft.com/fwlink/p/?linkid=236297)
|
||||
- [Skype for Business Online, Windows PowerShell Module](http://www.microsoft.com/download/details.aspx?id=39366)
|
||||
|
||||
### Connecting to online services
|
||||
@ -132,8 +133,7 @@ In order to run cmdlets used by these PowerShell scripts, the following must be
|
||||
5. Finally, to connect to Exchange Online Services, run:
|
||||
|
||||
``` syntax
|
||||
$exchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
|
||||
"https://outlook.office365.com/powershell-liveid/" -Credential $cred -Authentication "Basic" –AllowRedirection
|
||||
$exchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri"https://outlook.office365.com/powershell-liveid/" -Credential $cred -Authentication "Basic" –AllowRedirection
|
||||
```
|
||||
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Create and test a device account (Surface Hub)
|
||||
@ -55,11 +56,11 @@ These properties represent the minimum configuration for a device account to wor
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Exchange mailbox (Exchange 2010 or later, or Exchange Online)</p></td>
|
||||
<td align="left"><p>Exchange mailbox (Exchange 2013 or later, or Exchange Online)</p></td>
|
||||
<td align="left"><p>Enabling the account with an Exchange mailbox gives the device account the capability to receive and send both mail and meeting requests, and to display a meetings calendar on the Surface Hub’s welcome screen. The Surface Hub mailbox must be a room mailbox.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Skype for Business-enabled (Lync/Skype for Business 2010 or later or Skype for Business Online)</p></td>
|
||||
<td align="left"><p>Skype for Business-enabled (Lync/Skype for Business 2013 or later or Skype for Business Online)</p></td>
|
||||
<td align="left"><p>Skype for Business must be enabled in order to use various conferencing features, like video calls, IM, and screen-sharing.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -116,8 +117,6 @@ You can check online for updated versions at [Surface Hub device account scripts
|
||||
|
||||
Your infrastructure will likely fall into one of three configurations. Which configuration you have will affect how you prepare for device setup.
|
||||
|
||||
|
||||
|
||||
- [Online deployment (Office 365)](online-deployment-surface-hub-device-accounts.md): Your organization’s environment is deployed entirely on Office 365.
|
||||
- [On-premises deployment](on-premises-deployment-surface-hub-device-accounts.md): Your organization has servers that it controls, where Active Directory, Exchange, and Skype for Business (or Lync) are hosted.
|
||||
- [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md): Your organization has a mix of services, with some hosted on-premises and some hosted online through Office 365.
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Device reset (Surface Hub)
|
||||
description: You may wish to reset your Microsoft Surface Hub.
|
||||
ms.assetid: 44E82EEE-1905-464B-A758-C2A1463909FF
|
||||
redirect_url: https://technet.microsoft.com/en-us/itpro/surface-hub/device-reset-surface-hub
|
||||
redirect_url: https://technet.microsoft.com/itpro/surface-hub/device-reset-surface-hub
|
||||
keywords: reset Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -11,36 +11,6 @@ ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
# Device reset (Surface Hub)
|
||||
|
||||
|
||||
You may wish to reset your Microsoft Surface Hub.
|
||||
|
||||
Typical reasons for a reset include:
|
||||
|
||||
- The device isn’t running well after installing an update.
|
||||
- You’re repurposing the device for a new meeting space and want to reconfigure it.
|
||||
- You want to change how you locally manage the device.
|
||||
|
||||
Initiating a reset will return the device to the last cumulative Windows update, and remove all local user files and configuration, including:
|
||||
|
||||
- The device account
|
||||
- MDM enrollment
|
||||
- Domain join or Azure AD join information
|
||||
- Local admins on the device
|
||||
- Configurations from MDM or the Settings app
|
||||
|
||||
**Important Note**</br>
|
||||
Performing a device reset may take up to 6 hours. Do not interrupt the reset process. Interrupting the process will render the device inoperable, requiring warranty service to return to normal functionality.
|
||||
|
||||
After the reset, you'll be taken through the [first run program](first-run-program-surface-hub.md) again.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Manage Microsoft Surface Hub](manage-surface-hub.md)
|
||||
|
||||
[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Device reset (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Microsoft Exchange properties (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# First-run program (Surface Hub)
|
||||
@ -153,7 +154,7 @@ This screen is purely informational, and shows which recommended settings have b
|
||||
|
||||
### Details
|
||||
|
||||
You should read this screen and note which services have been enabled by default. All of them can be changed using the Settings app if need be, but you should be careful about the effects of doing so. For example, Cortana depends on some of these settings, and may not work if you disable them. See [Intro to Surface Hub](intro-to-surface-hub.md) for details.
|
||||
You should read this screen and note which services have been enabled by default. All of them can be changed using the Settings app if need be, but you should be careful about the effects of doing so. See [Intro to Surface Hub](intro-to-surface-hub.md) for details.
|
||||
|
||||
Once you're done reviewing the settings, click **Next** to go on.
|
||||
|
||||
@ -184,9 +185,8 @@ Click **Skip setting up a device account** to skip setting up a device account.
|
||||
|
||||
- See a meeting calendar on the Welcome screen
|
||||
- Start a meeting from the Welcome screen
|
||||
- Start a meeting using Cortana
|
||||
- Email whiteboards from OneNote
|
||||
- Use Skype for Business for meetings.
|
||||
- Use Skype for Business for meetings
|
||||
|
||||
If you skip setting it up now, you can add a device account later by using the Settings app.
|
||||
|
||||
@ -221,7 +221,6 @@ Click **Skip setting up Exchange services** to skip this step. If you do, people
|
||||
|
||||
- See a meeting calendar on the welcome screen.
|
||||
- Start a meeting from the welcome screen.
|
||||
- Start a meeting using Cortana.
|
||||
- Email whiteboards from OneNote.
|
||||
|
||||
See [Intro to Surface Hub](intro-to-surface-hub.md) for details on setup dependencies.
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Hybrid deployment (Surface Hub)
|
||||
@ -40,7 +41,7 @@ Use this procedure if you use Exchange on-prem.
|
||||
Open your on-prem Exchange Management Shell with administrator permissions, and run this cmdlet.
|
||||
|
||||
```ps1
|
||||
Enable-Mailbox 'HUB01@contoso.com' -RemoteRoutingAddress 'HUB01@contoso.com' -Room
|
||||
Enable-RemoteMailbox 'HUB01@contoso.com' -RemoteRoutingAddress 'HUB01@contoso.com' -Room
|
||||
```
|
||||
|
||||
4. Connect to Microsoft Exchange Online and set some properties for the account in Office 365.
|
||||
|
||||
@ -7,6 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# End a Surface Hub meeting with I'm Done
|
||||
@ -61,7 +62,6 @@ User interface (UI) settings are returned to their default values when **I'm Don
|
||||
- Reset Quick Actions to default state
|
||||
- Clear Toast notifications
|
||||
- Reset volume levels
|
||||
- Reset Cortana relaunch count
|
||||
- Reset sidebar width
|
||||
- Reset tablet mode layout
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 28 KiB |
@ -7,6 +7,7 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Microsoft Surface Hub
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, store
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Install apps on your Microsoft Surface Hub
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Intro to Microsoft Surface Hub
|
||||
@ -33,7 +34,7 @@ The capabilities of your Surface Hub will depend on what other Microsoft product
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>One-touch meeting join, meetings calendar, and email (for example, sending whiteboards)</p></td>
|
||||
<td align="left"><p>Device account with Microsoft Exchange 2010 or later, or Exchange Online and a network connection to where the account is hosted.</p></td>
|
||||
<td align="left"><p>Device account with Microsoft Exchange 2013 or later, or Exchange Online and a network connection to where the account is hosted.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Meetings using Skype for Business</p></td>
|
||||
@ -43,10 +44,6 @@ The capabilities of your Surface Hub will depend on what other Microsoft product
|
||||
<td align="left"><p>Web browsing through Microsoft Edge</p></td>
|
||||
<td align="left"><p>Internet connectivity.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Cortana meeting room assistant (voice commands, search)</p></td>
|
||||
<td align="left"><p>Internet connectivity needed to process questions and do searches.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Remote and multi-device management</p></td>
|
||||
<td align="left"><p>Supported mobile device management (MDM) solutions (Microsoft Intune, System Center 2012 R2 Configuration Manager, or supported third-party solution).</p></td>
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Manage settings with a local admin account (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, mobility
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Manage settings with an MDM provider (Surface Hub)
|
||||
@ -34,7 +35,7 @@ Alternatively, the device can be enrolled like any other Windows device by going
|
||||
|
||||
### Manage a device through MDM
|
||||
|
||||
The following table lists the device settings that can be managed remotely using MDM, including the OMA URI paths that 3rd party MDM providers need to create policies. Intune and SCCM have special templates to help create policies to manage these settings.
|
||||
The following table lists the device settings that can be managed remotely using MDM, including the OMA URI paths that 3rd party MDM providers need to create policies. Intune and System Center Configuration Manager have special templates to help create policies to manage these settings.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Manage Microsoft Surface Hub
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Windows updates (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Monitor your Microsoft Surface Hub
|
||||
@ -15,18 +16,18 @@ author: TrudyHa
|
||||
|
||||
Monitoring for Microsoft Surface Hub devices is enabled through Microsoft Operations Management Suite (OMS).
|
||||
|
||||
The [Operations Management Suite (OMS)](http://go.microsoft.com/fwlink/?LinkId=718138) is Microsoft's IT management solution that helps you manage and protect your entire IT infrastructure, including your Surface Hubs. You can use OMS to help you track the health of your Surface Hubs as well as understand how they are being used. Log files are read on the devices and sent to the OMS service. Issues like servers being offline, the calendar not syncing, or the device account being unable to log into Skype are shown in OMS in the Surface Hub dashboard. By using the data in the dashboard, you can identify devices that are not running, or that are having other problems, and potentially apply fixes for the detected issues.
|
||||
The [Operations Management Suite (OMS)](https://go.microsoft.com/fwlink/?LinkId=718138) is Microsoft's IT management solution that helps you manage and protect your entire IT infrastructure, including your Surface Hubs. You can use OMS to help you track the health of your Surface Hubs as well as understand how they are being used. Log files are read on the devices and sent to the OMS service. Issues like servers being offline, the calendar not syncing, or the device account being unable to log into Skype are shown in OMS in the Surface Hub dashboard. By using the data in the dashboard, you can identify devices that are not running, or that are having other problems, and potentially apply fixes for the detected issues.
|
||||
|
||||
### OMS requirements
|
||||
|
||||
In order to manage your Surface Hubs from the Microsoft Operations Management Suite (OMS), you'll need the following:
|
||||
|
||||
- A valid [subscription to OMS](http://www.microsoft.com/server-cloud/operations-management-suite/overview.aspx).
|
||||
- [Subscription level](http://go.microsoft.com/fwlink/?LinkId=718139) in line with the number of devices. OMS pricing varies depending on how many devices are enrolled, and how much data it processes. You'll want to take this into consideration when planning your Surface Hub rollout.
|
||||
- [Subscription level](https://go.microsoft.com/fwlink/?LinkId=718139) in line with the number of devices. OMS pricing varies depending on how many devices are enrolled, and how much data it processes. You'll want to take this into consideration when planning your Surface Hub rollout.
|
||||
|
||||
Next, you will either add an OMS subscription to your existing Microsoft Azure subscription or create a new workspace directly through the OMS portal. Detailed instructions for setting up the account can be found at: [Onboard in minutes](http://go.microsoft.com/fwlink/?LinkId=718141). Once the OMS subscription is set up, there are two ways to enroll your Surface Hub devices:
|
||||
Next, you will either add an OMS subscription to your existing Microsoft Azure subscription or create a new workspace directly through the OMS portal. Detailed instructions for setting up the account can be found at: [Onboard in minutes](https://go.microsoft.com/fwlink/?LinkId=718141). Once the OMS subscription is set up, there are two ways to enroll your Surface Hub devices:
|
||||
|
||||
1. Automatically through [InTune](http://go.microsoft.com/fwlink/?LinkId=718150), or
|
||||
1. Automatically through [InTune](https://go.microsoft.com/fwlink/?LinkId=718150), or
|
||||
2. Manually through Settings.
|
||||
|
||||
### Setting up monitoring
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# On-premises deployment (Surface Hub)
|
||||
@ -15,7 +16,7 @@ author: TrudyHa
|
||||
|
||||
This topic explains how you add a device account for your Microsoft Surface Hub when you have a single-forest, on-premises deployment.
|
||||
|
||||
If you have a single-forest on-premises deployment with Microsoft Exchange 2013 or later and Skype for Business 2013 or later, then you can [use the provided PowerShell scripts](appendix-a-powershell-scripts-for-surface-hub.md#create-on-premise-ps-scripts) to create device accounts. If you’re using a multi-forest deployment, or are using Exchange 2010 or Lync 2010, you can use equivalent cmdlets that will produce the same results. Those cmdlets are described in this section.
|
||||
If you have a single-forest on-premises deployment with Microsoft Exchange 2013 or later and Skype for Business 2013 or later, then you can [use the provided PowerShell scripts](appendix-a-powershell-scripts-for-surface-hub.md#create-on-premise-ps-scripts) to create device accounts. If you’re using a multi-forest deployment, you can use equivalent cmdlets that will produce the same results. Those cmdlets are described in this section.
|
||||
|
||||
1. Start a remote PowerShell session from a PC and connect to Exchange.
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Online deployment with Office 365 (Surface Hub)
|
||||
@ -15,7 +16,7 @@ author: TrudyHa
|
||||
|
||||
This topic has instructions for adding a device account for your Microsoft Surface Hub when you have a pure, online deployment.
|
||||
|
||||
If you have a pure, online (O365) deployment, then you can [use the provided PowerShell scripts](appendix-a-powershell-scripts-for-surface-hub.md#create-os356-ps-scripts) to create device accounts. If you’re using Microsoft Exchange 2010 or Lync 2010, you can use equivalent cmdlets that will produce the same results. Those cmdlets are described in this section.
|
||||
If you have a pure, online (O365) deployment, then you can [use the provided PowerShell scripts](appendix-a-powershell-scripts-for-surface-hub.md#create-os356-ps-scripts) to create device accounts.
|
||||
|
||||
1. Start a remote PowerShell session on a PC and connect to Exchange.
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Password management (Surface Hub)
|
||||
|
||||
@ -8,17 +8,18 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, readiness
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Physically install Microsoft Surface Hub
|
||||
|
||||
|
||||
The Microsoft Surface Hub Readiness Guide will help make sure that your site is ready for the installation. You can download the Guide from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkId=718144). It includes planning information for both the 55" and 84" devices, as well as info on moving the Surface Hub from receiving to the installation location, mounting options, and a list of what's in the box.
|
||||
The Microsoft Surface Hub Readiness Guide will help make sure that your site is ready for the installation. You can download the Guide from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=718144). It includes planning information for both the 55" and 84" devices, as well as info on moving the Surface Hub from receiving to the installation location, mounting options, and a list of what's in the box.
|
||||
|
||||
You may also want to check out the Unpacking Guide. It will show you how to unpack the devices efficiently and safely. There are two guides, one for the 55" and one for the 84". A printed version of the Unpacking Guide is attached to the outside front of each unit's shipping crate.
|
||||
|
||||
- Download the 55" Unpacking Guide from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkId=718145).
|
||||
- Download the 84" version from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkId=718146).
|
||||
- Download the 55" Unpacking Guide from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=718145).
|
||||
- Download the 84" version from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=718146).
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: plan
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Prepare your environment for Microsoft Surface Hub
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Create provisioning packages (Surface Hub)
|
||||
@ -36,7 +37,6 @@ To create and apply a provisioning package to a Surface Hub, you'll need the fol
|
||||
|
||||
You'll create the provisioning package on a PC runing 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:
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, security
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Save your BitLocker key (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Set up Microsoft Surface Hub
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Setup worksheet (Surface Hub)
|
||||
@ -29,12 +30,12 @@ You should fill out one list for each Surface Hub you need to configure, althoug
|
||||
<p>Proxy information</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>If your network uses a proxy to for network and/or Internet access, you must provide a script or server/port information.</p>
|
||||
<p>If your network uses a proxy for network and/or Internet access, you must provide a script or server/port information.</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>http://contoso/proxy.pa (proxy script)
|
||||
OR
|
||||
10.10.10.100, port 8080 (server, port)
|
||||
<p>Proxy script: http://contoso/proxy.pa </br>
|
||||
- OR - </br>
|
||||
Server and port info: 10.10.10.100, port 80
|
||||
</p>
|
||||
</td>
|
||||
<td>
|
||||
@ -63,7 +64,9 @@ OR
|
||||
<p>This is the User Principal Name (UPN) or the domain\username, and the password of the device account. Mail, calendar, and Skype for Business depend on a compatible device account.</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>ConfRoom15@contoso.com, #Passw0rd1 (for UPN) OR CONTOSO\ConfRoom15, #Passw0rd1 (for Domain\username)</p>
|
||||
<p> UPN: ConfRoom15@contoso.com, #Passw0rd1 </br>
|
||||
- OR - <br>
|
||||
Domain and username: CONTOSO\ConfRoom15, #Passw0rd1</p>
|
||||
</td>
|
||||
<td>
|
||||
<p></p>
|
||||
@ -95,7 +98,7 @@ Mail, calendar, and Skype for Business depend on a compatible device account.
|
||||
For Skype for Business to work, the device account must have a valid SIP address. The device will try to find this automatically.</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>sip:ConfRoom15@contoso.com</p>
|
||||
<p>sip: ConfRoom15@contoso.com</p>
|
||||
</td>
|
||||
<td>
|
||||
<p></p>
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Microsoft Surface Hub administrator's guide
|
||||
@ -38,7 +39,7 @@ Before you power on Microsoft Surface Hub for the first time, make sure you've [
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md)</p></td>
|
||||
<td align="left"><p>The Surface Hub Readiness Guide will help make sure that your site is ready for the installation. You can download the Guide from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkId=718144). It includes planning information for both the 55" and 84" devices, as well as info on moving the Surface Hub from receiving to the installation location, mounting options, and a list of what's in the box.</p></td>
|
||||
<td align="left"><p>The Surface Hub Readiness Guide will help make sure that your site is ready for the installation. You can download the Guide from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=718144). It includes planning information for both the 55" and 84" devices, as well as info on moving the Surface Hub from receiving to the installation location, mounting options, and a list of what's in the box.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)</p></td>
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: support
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Troubleshoot Microsoft Surface Hub
|
||||
|
||||
@ -4,6 +4,7 @@ description: Troubleshoot common problems, including setup issues, Exchange Acti
|
||||
ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
|
||||
keywords: ["Troubleshoot common problems", "setup issues", "Exchange ActiveSync errors"]
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# When to use a fully qualified domain name with Surface Hub
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Using a room control system (Surface Hub)
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub, networking
|
||||
author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Wireless network management (Surface Hub)
|
||||
|
||||
@ -12,6 +12,7 @@
|
||||
## [Surface Data Eraser](microsoft-surface-data-eraser.md)
|
||||
## [Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md)
|
||||
### [Step by step: Surface Deployment Accelerator](step-by-step-surface-deployment-accelerator.md)
|
||||
### [Using the Surface Deployment Accelerator deployment share](using-the-sda-deployment-share.md)
|
||||
## [Surface Diagnostic Toolkit](surface-diagnostic-toolkit.md)
|
||||
## [Surface Dock Updater](surface-dock-updater.md)
|
||||
## [Surface Enterprise Management Mode](surface-enterprise-management-mode.md)
|
||||
|
||||
@ -3,6 +3,7 @@ title: Advanced UEFI security features for Surface Pro 3 (Surface)
|
||||
description: This article describes how to install and configure the v3.11.760.0 UEFI update to enable additional security options for Surface Pro 3 devices.
|
||||
ms.assetid: 90F790C0-E5FC-4482-AD71-60589E3C9C93
|
||||
keywords: security, features, configure, hardware, device, custom, script, update
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
@ -20,9 +21,9 @@ To address more granular control over the security of Surface devices, the v3.11
|
||||
## Manually install the UEFI update
|
||||
|
||||
|
||||
Before you can configure the advanced security features of your Surface device, you must first install the v3.11.760.0 UEFI update. This update is installed automatically if you receive your updates from Windows Update. For more information about how to configure Windows to update automatically by using Windows Update, see [How to configure and use Automatic Updates in Windows]( http://go.microsoft.com/fwlink/p/?LinkID=618030).
|
||||
Before you can configure the advanced security features of your Surface device, you must first install the v3.11.760.0 UEFI update. This update is installed automatically if you receive your updates from Windows Update. For more information about how to configure Windows to update automatically by using Windows Update, see [How to configure and use Automatic Updates in Windows]( https://go.microsoft.com/fwlink/p/?LinkID=618030).
|
||||
|
||||
To update the UEFI on Surface Pro 3, you can download and install the Surface UEFI updates as part of the Surface Pro 3 Firmware and Driver Pack. These firmware and driver packs are available from the [Surface Pro 3 page](https://www.microsoft.com/en-us/download/details.aspx?id=38826) on the Microsoft Download Center. You can find out more about the firmware and driver packs at [Download the latest firmware and drivers for Surface devices](https://technet.microsoft.com/en-us/itpro/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices). The firmware and driver packs are available as both self-contained Windows Installer (.msi) and archive (.zip) formats. You can find out more about these two formats and how you can use them to update your drivers at [Manage Surface driver and firmware updates](https://technet.microsoft.com/en-us/itpro/surface/manage-surface-pro-3-firmware-updates).
|
||||
To update the UEFI on Surface Pro 3, you can download and install the Surface UEFI updates as part of the Surface Pro 3 Firmware and Driver Pack. These firmware and driver packs are available from the [Surface Pro 3 page](https://www.microsoft.com/download/details.aspx?id=38826) on the Microsoft Download Center. You can find out more about the firmware and driver packs at [Download the latest firmware and drivers for Surface devices](https://technet.microsoft.com/itpro/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices). The firmware and driver packs are available as both self-contained Windows Installer (.msi) and archive (.zip) formats. You can find out more about these two formats and how you can use them to update your drivers at [Manage Surface driver and firmware updates](https://technet.microsoft.com/itpro/surface/manage-surface-pro-3-firmware-updates).
|
||||
|
||||
## Manually configure additional security settings
|
||||
|
||||
@ -48,13 +49,13 @@ After the v3.11.760.0 UEFI update is installed on a Surface device, an additiona
|
||||
## Automate additional security settings
|
||||
|
||||
|
||||
As an IT professional with administrative privileges, you can automate the configuration of UEFI settings by leveraging [Surface Pro 3 Firmware Tools (476 KB)](http://go.microsoft.com/fwlink/p/?LinkID=618038) available from the Microsoft Download Center. These tools install a .NET assembly that can be called from any custom application or script.
|
||||
As an IT professional with administrative privileges, you can automate the configuration of UEFI settings by leveraging [Surface Pro 3 Firmware Tools (476 KB)](https://go.microsoft.com/fwlink/p/?LinkID=618038) available from the Microsoft Download Center. These tools install a .NET assembly that can be called from any custom application or script.
|
||||
|
||||
**Prerequisites**
|
||||
|
||||
- The sample scripts below leverage the previously mentioned extension and therefore assume that the tool has been installed on the device being managed.
|
||||
- The scripts must be run with administrative privilege.
|
||||
- The Windows PowerShell command [**Set-ExecutionPolicy Unrestricted**](http://go.microsoft.com/fwlink/p/?LinkID=618039) must be called prior to running sample scripts if they are not digitally signed.
|
||||
- The Windows PowerShell command [**Set-ExecutionPolicy Unrestricted**](https://go.microsoft.com/fwlink/p/?LinkID=618039) must be called prior to running sample scripts if they are not digitally signed.
|
||||
|
||||
**Sample scripts**
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: Customize the OOBE for Surface deployments (Surface)
|
||||
description: This article will walk you through the process of customizing the Surface out-of-box experience for end users in your organization.
|
||||
ms.assetid: F6910315-9FA9-4297-8FA8-2C284A4B1D87
|
||||
keywords: deploy, customize, automate, network, Pen, pair, boot
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
@ -21,12 +22,12 @@ It is common practice in a Windows deployment to customize the user experience f
|
||||
|
||||
In some scenarios, you may want to provide complete automation to ensure that at the end of a deployment, computers are ready for use without any interaction from the user. In other scenarios, you may want to leave key elements of the experience for users to perform necessary actions or select between important choices. For administrators deploying to Surface devices, each of these scenarios presents a unique challenge to overcome.
|
||||
|
||||
This article provides a summary of the scenarios where a deployment might require additional steps. It also provides the required information to ensure that the desired experience is achieved on any newly deployed Surface device. This article is intended for administrators who are familiar with the deployment process, as well as concepts such as answer files and [reference images](http://go.microsoft.com/fwlink/p/?LinkID=618042).
|
||||
This article provides a summary of the scenarios where a deployment might require additional steps. It also provides the required information to ensure that the desired experience is achieved on any newly deployed Surface device. This article is intended for administrators who are familiar with the deployment process, as well as concepts such as answer files and [reference images](https://go.microsoft.com/fwlink/p/?LinkID=618042).
|
||||
|
||||
>**Note:** Although the OOBE phase of setup is still run during a deployment with an automated deployment solution such as the [Microsoft Deployment Toolkit (MDT)](http://go.microsoft.com/fwlink/p/?LinkId=618117) or System Center Configuration Manager Operating System Deployment (OSD), it is automated by the settings supplied in the Deployment Wizard and task sequence. For more information see:<br/>
|
||||
- [Deploy Windows 10 with the Microsoft Deployment Toolkit](http://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit)
|
||||
>**Note:** Although the OOBE phase of setup is still run during a deployment with an automated deployment solution such as the [Microsoft Deployment Toolkit (MDT)](https://go.microsoft.com/fwlink/p/?LinkId=618117) or System Center Configuration Manager Operating System Deployment (OSD), it is automated by the settings supplied in the Deployment Wizard and task sequence. For more information see:<br/>
|
||||
- [Deploy Windows 10 with the Microsoft Deployment Toolkit](http://technet.microsoft.com/itpro/windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit)
|
||||
<br/>
|
||||
- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](http://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-windows-10-with-system-center-2012-r2-configuration-manager)
|
||||
- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](http://technet.microsoft.com/itpro/windows/deploy/deploy-windows-10-with-system-center-2012-r2-configuration-manager)
|
||||
|
||||
|
||||
|
||||
@ -35,7 +36,7 @@ This article provides a summary of the scenarios where a deployment might requir
|
||||
|
||||
When a wireless network adapter is present during OOBE, the **Join a wireless network** page is displayed, which prompts a user to connect to a wireless network. This page is not automatically hidden by deployment technologies, including MDT 2013, and therefore will be displayed even when a deployment is configured for complete automation.
|
||||
|
||||
To ensure that an automated deployment is not stopped by this page, the page must be hidden by configuring an additional setting in the answer file, **HideWirelessSetupInOOBE**. You can find additional information about the **HideWirelessSetupInOOBE** setting in [Unattended Windows Setup Reference](http://go.microsoft.com/fwlink/p/?LinkID=618044).
|
||||
To ensure that an automated deployment is not stopped by this page, the page must be hidden by configuring an additional setting in the answer file, **HideWirelessSetupInOOBE**. You can find additional information about the **HideWirelessSetupInOOBE** setting in [Unattended Windows Setup Reference](https://go.microsoft.com/fwlink/p/?LinkID=618044).
|
||||
|
||||
## Scenario 2: Surface Pen pairing in OOBE
|
||||
|
||||
@ -53,7 +54,7 @@ To provide the factory Surface Pen pairing experience in OOBE, you must copy fou
|
||||
|
||||
|
||||
|
||||
The step-by-step process for adding these required files to an image is described in [Deploying Surface Pro 3 Pen and OneNote Tips](http://go.microsoft.com/fwlink/p/?LinkID=618045). This blog post also includes tips to ensure that the necessary updates for the Surface Pen Quick Note-Taking Experience are installed, which allows users to send notes to OneNote with a single click.
|
||||
The step-by-step process for adding these required files to an image is described in [Deploying Surface Pro 3 Pen and OneNote Tips](https://go.microsoft.com/fwlink/p/?LinkID=618045). This blog post also includes tips to ensure that the necessary updates for the Surface Pen Quick Note-Taking Experience are installed, which allows users to send notes to OneNote with a single click.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: Download the latest firmware and drivers for Surface devices (Surface)
|
||||
description: This article provides a list of the available downloads for Surface devices and links to download the drivers and firmware for your device.
|
||||
ms.assetid: 7662BF68-8BF7-43F7-81F5-3580A770294A
|
||||
keywords: update Surface, newest, latest, download, firmware, driver, tablet, hardware, device
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
@ -32,14 +33,14 @@ Installation files for administrative tools, drivers for accessories, and update
|
||||
|
||||
Recent additions to the downloads for Surface devices provide you with options to install Windows 10 on your Surface devices and update LTE devices with the latest Windows 10 drivers and firmware.
|
||||
|
||||
>**Note:** A battery charge of 40% or greater is required before you install firmware to a Surface device. See [Microsoft Support article KB2909710](http://go.microsoft.com/fwlink/p/?LinkId=618106) for more information.
|
||||
>**Note:** A battery charge of 40% or greater is required before you install firmware to a Surface device. See [Microsoft Support article KB2909710](https://go.microsoft.com/fwlink/p/?LinkId=618106) for more information.
|
||||
|
||||
|
||||
|
||||
## Surface Book
|
||||
|
||||
|
||||
Download the following updates [for Surface Book from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=691691).
|
||||
Download the following updates [for Surface Book from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=691691).
|
||||
|
||||
- SurfaceBook\_Win10\_xxxxxx.msi – Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
@ -48,7 +49,7 @@ Download the following updates [for Surface Book from the Microsoft Download Cen
|
||||
## Surface Pro 4
|
||||
|
||||
|
||||
Download the following updates for [Surface Pro 4 from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=691692).
|
||||
Download the following updates for [Surface Pro 4 from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=691692).
|
||||
|
||||
- SurfacePro4\_Win10\_xxxxxx.msi – Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
@ -57,7 +58,7 @@ Download the following updates for [Surface Pro 4 from the Microsoft Download Ce
|
||||
## <a href="" id="surface-pro-3-"></a>Surface Pro 3
|
||||
|
||||
|
||||
Download the following updates [for Surface Pro 3 from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=690288).
|
||||
Download the following updates [for Surface Pro 3 from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=690288).
|
||||
|
||||
- SurfacePro3\_Win10\_xxxxxx.msi – Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
@ -84,7 +85,7 @@ Download the following updates [for Surface Pro 3 from the Microsoft Download Ce
|
||||
## Surface 3
|
||||
|
||||
|
||||
Download the following updates [for Surface 3 from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=690289).
|
||||
Download the following updates [for Surface 3 from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=690289).
|
||||
|
||||
- Surface3\_Win10\_xxxxxx.zip – Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
@ -101,7 +102,7 @@ Download the following updates [for Surface 3 from the Microsoft Download Center
|
||||
## Surface 3 LTE
|
||||
|
||||
|
||||
Download the following updates [for AT&T 4G LTE versions of Surface 3 from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=690290).
|
||||
Download the following updates [for AT&T 4G LTE versions of Surface 3 from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=690290).
|
||||
|
||||
- Surface3\_US1\_Win10\_xxxxxx.msi – Surface 3 LTE AT&T - Cumulative firmware and driver update for locked carrier dependent AT&T devices in the US, running Windows 10
|
||||
|
||||
@ -117,7 +118,7 @@ Download the following updates [for AT&T 4G LTE versions of Surface 3 from the M
|
||||
|
||||
- Wintab-xxxxx-64-bit.zip – Tablet driver update for all supported x64-based versions of Windows 8.1
|
||||
|
||||
Download the following updates [for non-AT&T 4G LTE versions of Surface 3 from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=690291).
|
||||
Download the following updates [for non-AT&T 4G LTE versions of Surface 3 from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=690291).
|
||||
|
||||
- Surface3\_NAG\_Win10\_xxxxxx.msi – Surface 3 LTE North America - Cumulative firmware and driver update for unlocked carrier independent devices in the US, running Windows 10
|
||||
|
||||
@ -133,7 +134,7 @@ Download the following updates [for non-AT&T 4G LTE versions of Surface 3 from t
|
||||
|
||||
- Wintab-xxxxx-64-bit.zip – Tablet driver update for all supported x64-based versions of Windows 8.1
|
||||
|
||||
Download the following updates [for 4G LTE Surface 3 versions for regions outside North America from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=690292).
|
||||
Download the following updates [for 4G LTE Surface 3 versions for regions outside North America from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=690292).
|
||||
|
||||
- Surface3\_ROW\_Win10\_xxxxxx.msi – Surface 3 LTE rest of the world cumulative - Cumulative firmware and driver update for carrier independent devices outside of the US, as well as for Japan, running Windows 10
|
||||
|
||||
@ -152,7 +153,7 @@ Download the following updates [for 4G LTE Surface 3 versions for regions outsid
|
||||
## Surface Pro 2
|
||||
|
||||
|
||||
Download the following updates [for Surface Pro 2 from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=690293).
|
||||
Download the following updates [for Surface Pro 2 from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=690293).
|
||||
|
||||
- SurfacePro2\_Win10\_xxxxxx.zip – Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
@ -167,7 +168,7 @@ Download the following updates [for Surface Pro 2 from the Microsoft Download Ce
|
||||
## Surface Pro
|
||||
|
||||
|
||||
Download the following updates [for Surface Pro from the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=690294).
|
||||
Download the following updates [for Surface Pro from the Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=690294).
|
||||
|
||||
- SurfacePro\_Win10\_xxxxxx.zip – Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
@ -184,7 +185,7 @@ Download the following updates [for Surface Pro from the Microsoft Download Cent
|
||||
|
||||
There are no downloadable firmware or driver updates available for Surface RT. Updates can only be applied using Windows Update.
|
||||
|
||||
If you have additional questions on the driver pack and updates, please contact [Microsoft Surface support for business](http://go.microsoft.com/fwlink/p/?LinkId=618107).
|
||||
If you have additional questions on the driver pack and updates, please contact [Microsoft Surface support for business](https://go.microsoft.com/fwlink/p/?LinkId=618107).
|
||||
|
||||
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices (Surface)
|
||||
description: Find out how to enable support for PEAP, EAP-FAST, or Cisco LEAP protocols on your Surface device.
|
||||
ms.assetid: A281EFA3-1552-467D-8A21-EB151E58856D
|
||||
keywords: network, wireless, device, deploy, authentication, protocol
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
@ -15,14 +16,14 @@ author: miladCA
|
||||
|
||||
Find out how to enable support for PEAP, EAP-FAST, or Cisco LEAP protocols on your Surface device.
|
||||
|
||||
If you use PEAP, EAP-FAST, or Cisco LEAP in your enterprise network, you probably already know that these three wireless authentication protocols are not supported by Surface devices out of the box. Some users may discover this when they attempt to connect to your wireless network; others may discover it when they are unable to gain access to resources inside the network, like file shares and internal sites. For more information, see [Extensible Authentication Protocol](http://go.microsoft.com/fwlink/p/?LinkId=716899).
|
||||
If you use PEAP, EAP-FAST, or Cisco LEAP in your enterprise network, you probably already know that these three wireless authentication protocols are not supported by Surface devices out of the box. Some users may discover this when they attempt to connect to your wireless network; others may discover it when they are unable to gain access to resources inside the network, like file shares and internal sites. For more information, see [Extensible Authentication Protocol](https://go.microsoft.com/fwlink/p/?LinkId=716899).
|
||||
|
||||
You can add support for each protocol by executing a small MSI package from a USB stick or from a file share. For organizations that want to enable EAP support on their Surface devices, the MSI package format supports deployment with many management and deployment tools, like the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager.
|
||||
|
||||
## <a href="" id="download-peap--eap-fast--or-cisco-leap-installation-files--"></a>Download PEAP, EAP-FAST, or Cisco LEAP installation files
|
||||
|
||||
|
||||
You can download the MSI installation files for PEAP, EAP-FAST, or Cisco LEAP in a single zip archive file from the Microsoft Download Center. To download this file, go to the [Surface Tools for IT](http://go.microsoft.com/fwlink/p/?LinkId=618121) page on the Microsoft Download Center, click **Download**, and then select the **Cisco EAP-Supplicant Installer.zip** file.
|
||||
You can download the MSI installation files for PEAP, EAP-FAST, or Cisco LEAP in a single zip archive file from the Microsoft Download Center. To download this file, go to the [Surface Tools for IT](https://go.microsoft.com/fwlink/p/?LinkId=618121) page on the Microsoft Download Center, click **Download**, and then select the **Cisco EAP-Supplicant Installer.zip** file.
|
||||
|
||||
## Deploy PEAP, EAP-FAST, or Cisco LEAP with MDT
|
||||
|
||||
@ -78,7 +79,7 @@ To specify the protocol(s) explicitly, follow these steps:
|
||||
|
||||
For organizations that manage Surface devices with Configuration Manager, it is even easier to deploy PEAP, EAP-FAST, or Cisco LEAP support to Surface devices. Simply import each MSI file as an application from the Software Library and configure a deployment to your Surface device collection.
|
||||
|
||||
For more information on how to deploy applications with Configuration Manager see [How to Create Applications in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=761079) and [How to Deploy Applications in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=761080).
|
||||
For more information on how to deploy applications with Configuration Manager see [How to Create Applications in Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=761079) and [How to Deploy Applications in Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=761080).
|
||||
|
||||
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: Ethernet adapters and Surface deployment (Surface)
|
||||
description: This article provides guidance and answers to help you perform a network deployment to Surface devices.
|
||||
ms.assetid: 5273C59E-6039-4E50-96B3-426BB38A64C0
|
||||
keywords: ethernet, deploy, removable, network, connectivity, boot, firmware, device, adapter, PXE boot, USB
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
@ -24,7 +25,7 @@ Before you can address the concerns of how you will boot to your deployment envi
|
||||
|
||||
The primary concern when selecting an Ethernet adapter is how that adapter will boot your Surface device from the network. If you are pre-staging clients with Windows Deployment Services (WDS) or if you are using System Center Configuration Manager, you may also want to consider whether the removable Ethernet adapters will be dedicated to a specific Surface device or shared among multiple devices. See the [Manage MAC addresses with removable Ethernet adapters](#manage-mac-addresses) section of this article for more information on potential conflicts with shared adapters.
|
||||
|
||||
Booting from the network (PXE boot) is only supported when you use an Ethernet adapter or docking station from Microsoft. To boot from the network, the chipset in the Ethernet adapter or dock must be detected and configured as a boot device in the firmware of the Surface device. Microsoft Ethernet adapters, such as the Surface Ethernet Adapter and the [Surface Dock](http://go.microsoft.com/fwlink/p/?LinkId=722364) use a chipset that is compatible with the Surface firmware.
|
||||
Booting from the network (PXE boot) is only supported when you use an Ethernet adapter or docking station from Microsoft. To boot from the network, the chipset in the Ethernet adapter or dock must be detected and configured as a boot device in the firmware of the Surface device. Microsoft Ethernet adapters, such as the Surface Ethernet Adapter and the [Surface Dock](https://go.microsoft.com/fwlink/p/?LinkId=722364) use a chipset that is compatible with the Surface firmware.
|
||||
|
||||
The following Ethernet devices are supported for network boot with Surface devices:
|
||||
|
||||
@ -57,8 +58,7 @@ To boot a Surface device from an alternative boot device, follow these steps:
|
||||
>**Note:** In addition to an Ethernet adapter, a keyboard must also be connected to the Surface device to enter the preinstallation environment and navigate the deployment wizard.
|
||||
|
||||
|
||||
|
||||
To support booting from the network in a Windows Preinstallation Environment (WinPE), such as is used in the Microsoft Deployment Toolkit and Configuration Manager, you must add drivers for the Ethernet adapter to WinPE. You can download the drivers for Surface Ethernet adapters from the Microsoft Download Center page for your specific device. For a list of the available downloads for Surface devices, see [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md).
|
||||
For Windows 10, version 1511 and later – including the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10, version 1511 – the drivers for Microsoft Surface Ethernet Adapters are present by default. If you are using a deployment solution that uses Windows Preinstallation Environment (WinPE), like the Microsoft Deployment Toolkit, and booting from the network with PXE, ensure that your deployment solution is using the latest version of the Windows ADK.
|
||||
|
||||
## <a href="" id="manage-mac-addresses"></a>Manage MAC addresses with removable Ethernet adapters
|
||||
|
||||
@ -67,7 +67,7 @@ Another consideration for administrators performing Windows deployment over the
|
||||
|
||||
The simplest solution to avoid MAC address conflicts is to provide a dedicated removable Ethernet adapter for each Surface device. This can make sense in many scenarios where the Ethernet adapter or the additional functionality of the docking station will be used regularly. However, not all scenarios call for the additional connectivity of a docking station or support for wired networks.
|
||||
|
||||
Another potential solution to avoid conflict when adapters are shared is to use the [Microsoft Deployment Toolkit (MDT)](http://go.microsoft.com/fwlink/p/?LinkId=618117) to perform deployment to Surface devices. MDT does not use the MAC address to identify individual computers and thus is not subject to this limitation. However, MDT does use Windows Deployment Services to provide PXE boot functionality, and is subject to the limitations regarding pre-staged clients which is covered later in this section.
|
||||
Another potential solution to avoid conflict when adapters are shared is to use the [Microsoft Deployment Toolkit (MDT)](https://go.microsoft.com/fwlink/p/?LinkId=618117) to perform deployment to Surface devices. MDT does not use the MAC address to identify individual computers and thus is not subject to this limitation. However, MDT does use Windows Deployment Services to provide PXE boot functionality, and is subject to the limitations regarding pre-staged clients which is covered later in this section.
|
||||
|
||||
When you use a shared adapter for deployment, the solution for affected deployment technologies is to use another means to identify unique systems. For Configuration Manager and WDS, both of which can be affected by this issue, the solution is to use the System Universal Unique Identifier (System UUID) that is embedded in the computer firmware by the computer manufacturer. For Surface devices, you can see this entry in the computer firmware under **Device Information**.
|
||||
|
||||
@ -78,9 +78,9 @@ To access the firmware of a Surface device, follow these steps:
|
||||
3. Press and release the **Power** button.
|
||||
4. After the device begins to boot, release the **Volume Up** button.
|
||||
|
||||
When deploying with WDS, the MAC address is only used to identify a computer when the deployment server is configured to respond only to known, pre-staged clients. When pre-staging a client, an administrator creates a computer account in Active Directory and defines that computer by the MAC address or the System UUID. To avoid the identity conflicts caused by shared Ethernet adapters, you should use [System UUID to define pre-staged clients](http://go.microsoft.com/fwlink/p/?LinkId=618118). Alternatively, you can configure WDS to respond to unknown clients that do not require definition by either MAC address or System UUID by selecting the **Respond to all client computers (known and unknown)** option on the [**PXE Response** tab](http://go.microsoft.com/fwlink/p/?LinkId=618119) in **Windows Deployment Server Properties**.
|
||||
When deploying with WDS, the MAC address is only used to identify a computer when the deployment server is configured to respond only to known, pre-staged clients. When pre-staging a client, an administrator creates a computer account in Active Directory and defines that computer by the MAC address or the System UUID. To avoid the identity conflicts caused by shared Ethernet adapters, you should use [System UUID to define pre-staged clients](https://go.microsoft.com/fwlink/p/?LinkId=618118). Alternatively, you can configure WDS to respond to unknown clients that do not require definition by either MAC address or System UUID by selecting the **Respond to all client computers (known and unknown)** option on the [**PXE Response** tab](https://go.microsoft.com/fwlink/p/?LinkId=618119) in **Windows Deployment Server Properties**.
|
||||
|
||||
The potential for conflicts with shared Ethernet adapters is much higher with Configuration Manager. Where WDS only uses MAC addresses to define individual systems when configured to do so, Configuration Manager uses the MAC address to define individual systems whenever performing a deployment to new or unknown computers. This can result in improperly configured devices or even the inability to deploy more than one system with a shared Ethernet adapter. There are several potential solutions for this situation that are described in detail in the [How to Use The Same External Ethernet Adapter For Multiple SCCM OSD](http://go.microsoft.com/fwlink/p/?LinkId=618120) blog post on the Ask Premier Field Engineering (PFE) Platforms TechNet blog.
|
||||
The potential for conflicts with shared Ethernet adapters is much higher with Configuration Manager. Where WDS only uses MAC addresses to define individual systems when configured to do so, Configuration Manager uses the MAC address to define individual systems whenever performing a deployment to new or unknown computers. This can result in improperly configured devices or even the inability to deploy more than one system with a shared Ethernet adapter. There are several potential solutions for this situation that are described in detail in the [How to Use The Same External Ethernet Adapter For Multiple SCCM OSD](https://go.microsoft.com/fwlink/p/?LinkId=618120) blog post on the Ask Premier Field Engineering (PFE) Platforms TechNet blog.
|
||||
|
||||
|
||||
|
||||
|
||||
BIN
devices/surface/images/using-sda-driverfiles-fig1.png
Normal file
BIN
devices/surface/images/using-sda-driverfiles-fig1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
BIN
devices/surface/images/using-sda-installcommand-fig2.png
Normal file
BIN
devices/surface/images/using-sda-installcommand-fig2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
BIN
devices/surface/images/using-sda-newinstall-fig3.png
Normal file
BIN
devices/surface/images/using-sda-newinstall-fig3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 59 KiB |
@ -2,6 +2,7 @@
|
||||
title: Manage Surface Dock firmware updates (Surface)
|
||||
description: Read about the different methods you can use to manage the process of Surface Dock firmware updates.
|
||||
ms.assetid: 86DFC0C0-C842-4CD1-A2D7-4425471FFE3F
|
||||
localizationpriority: high
|
||||
keywords: firmware, update, install, drivers
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -15,13 +16,13 @@ author: jobotto
|
||||
|
||||
Read about the different methods you can use to manage the process of Surface Dock firmware updates.
|
||||
|
||||
The Surface Dock provides external connectivity to Surface devices through a single cable connection that includes Power, Ethernet, Audio, USB 3.0, and DisplayPort. The numerous connections provided by the Surface Dock are enabled by a smart chipset within the Surface Dock device. Like a Surface device’s chipset, the chipset that is built into the Surface Dock is controlled by firmware. For more information about the Surface Dock, see the [Surface Dock demonstration](https://technet.microsoft.com/en-us/mt697552) video.
|
||||
The Surface Dock provides external connectivity to Surface devices through a single cable connection that includes Power, Ethernet, Audio, USB 3.0, and DisplayPort. The numerous connections provided by the Surface Dock are enabled by a smart chipset within the Surface Dock device. Like a Surface device’s chipset, the chipset that is built into the Surface Dock is controlled by firmware. For more information about the Surface Dock, see the [Surface Dock demonstration](https://technet.microsoft.com/mt697552) video.
|
||||
|
||||
Like the firmware for Surface devices, firmware for Surface Dock is also contained within a downloaded driver that is visible in Device Manager. This driver stages the firmware update files on the Surface device. When a Surface Dock is connected and the driver is loaded, the newer version of the firmware staged by the driver is detected and firmware files are copied to the Surface Dock. The Surface Dock then begins a two-phase process to apply the firmware internally. Each phase requires the Surface Dock to be disconnected from the Surface device before the firmware is applied. The driver copies the firmware into the dock, but only applies it when the user disconnects the Surface device from the Surface Dock. This ensures that there are no disruptions because the firmware is only applied when the user leaves their desk with the device.
|
||||
|
||||
>**Note:** You can learn more about the firmware update process for Surface devices and how firmware is updated through driver installation at the following links:<br/>
|
||||
- [How to manage and update Surface drivers and firmware](https://technet.microsoft.com/en-us/mt697551) from Microsoft Mechanics
|
||||
- [Windows Update Makes Surface Better](http://go.microsoft.com/fwlink/p/?LinkId=785354) on the Microsoft Devices Blog
|
||||
- [How to manage and update Surface drivers and firmware](https://technet.microsoft.com/mt697551) from Microsoft Mechanics
|
||||
- [Windows Update Makes Surface Better](https://go.microsoft.com/fwlink/p/?LinkId=785354) on the Microsoft Devices Blog
|
||||
|
||||
|
||||
|
||||
@ -78,7 +79,7 @@ Windows Update is the method that most users will use. The drivers for the Surfa
|
||||
|
||||
This method is used mostly in environments where Surface device drivers and firmware are managed separately from Windows Update. See [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md) for more information about the different methods to manage Surface device driver and firmware updates. Updating the Surface Dock firmware through this method involves downloading and deploying an MSI package to the Surface device that contains the updated Surface Dock drivers and firmware. This is the same method recommended for updating all other Surface drivers and firmware. The two-phase firmware update process occurs in the background each time the Surface Dock is disconnected, just like it does with the Windows Update method.
|
||||
|
||||
For more information about how to deploy MSI packages see [Create and deploy an application with System Center Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=785355).
|
||||
For more information about how to deploy MSI packages see [Create and deploy an application with System Center Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=785355).
|
||||
|
||||
>**Note:** When drivers are installed through Windows Update or the MSI package, registry keys are added that indicate the version of firmware installed on the Surface Dock and contained within the Surface Dock driver. These registry keys can be found in:<br/><br/>
|
||||
**HLKM\\Software\\Microsoft\\Windows NT\\CurrentVersion\\WUDF\\Services\\SurfaceDockFwUpdate\\Parameters**
|
||||
@ -102,7 +103,7 @@ Firmware status is displayed for both the main chipset (displayed as **Component
|
||||
|
||||
The manual method using the Microsoft Surface Dock Updater tool to update the Surface Dock is used mostly in environments where IT prepares Surface Docks prior to delivery to the end user, or for troubleshooting of a Surface Dock. Microsoft Surface Dock Updater is a tool that you can run from any Surface device that is compatible with the Surface Dock, and will walk you through the process of performing the Surface Dock firmware update in the least possible amount of time. You can also use this tool to verify the firmware status of a connected Surface Dock.
|
||||
|
||||
For more information about how to use the Microsoft Surface Dock Updater tool, please see [Microsoft Surface Dock Updater](surface-dock-updater.md). You can download the Microsoft Surface Dock Updater tool from the [Surface Tools for IT page](http://go.microsoft.com/fwlink/p/?LinkId=618121) on the Microsoft Download Center.
|
||||
For more information about how to use the Microsoft Surface Dock Updater tool, please see [Microsoft Surface Dock Updater](surface-dock-updater.md). You can download the Microsoft Surface Dock Updater tool from the [Surface Tools for IT page](https://go.microsoft.com/fwlink/p/?LinkId=618121) on the Microsoft Download Center.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: Manage Surface driver and firmware updates (Surface)
|
||||
description: This article describes the available options to manage firmware and driver updates for Surface devices.
|
||||
ms.assetid: CD1219BA-8EDE-4BC8-BEEF-99B50C211D73
|
||||
keywords: Surface, Surface Pro 3, firmware, update, device, manage, deploy, driver, USB
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
@ -30,26 +31,26 @@ The simplest solution to ensure that firmware on Surface devices in your organiz
|
||||
|
||||
Although this solution ensures that firmware will be updated as new releases are made available to Windows Update, it does present potential drawbacks. Each Surface device that receives Windows Updates directly will separately download each update rather than accessing a central location, which increases demand on Internet connectivity and bandwidth. Updates are also provided automatically to devices, without being subjected to testing or review by administrators.
|
||||
|
||||
For details about Group Policy for client configuration of WSUS or Windows Update, see [Step 5: Configure Group Policy Settings for Automatic Updates](http://go.microsoft.com/fwlink/p/?LinkId=618172).
|
||||
For details about Group Policy for client configuration of WSUS or Windows Update, see [Step 5: Configure Group Policy Settings for Automatic Updates](https://go.microsoft.com/fwlink/p/?LinkId=618172).
|
||||
|
||||
**Windows Installer Package**
|
||||
|
||||
The firmware and driver downloads for Surface devices now include Windows Installer files for firmware and driver updates. These Windows Installer packages can be deployed with utilities that support application deployment, including the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager. This solution allows for centralized deployment and for administrators to test and review firmware updates before they are deployed. For more information about the Windows Installer package delivery method for firmware and driver updates, including details on what drivers are updated by the package and why certain drivers and firmware are not updated by the Windows Installer package, see the [Surface Pro 3 MSI Now Available](http://go.microsoft.com/fwlink/p/?LinkId=618173) blog post.
|
||||
The firmware and driver downloads for Surface devices now include Windows Installer files for firmware and driver updates. These Windows Installer packages can be deployed with utilities that support application deployment, including the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager. This solution allows for centralized deployment and for administrators to test and review firmware updates before they are deployed. For more information about the Windows Installer package delivery method for firmware and driver updates, including details on what drivers are updated by the package and why certain drivers and firmware are not updated by the Windows Installer package, see the [Surface Pro 3 MSI Now Available](https://go.microsoft.com/fwlink/p/?LinkId=618173) blog post.
|
||||
|
||||
For instructions on how to deploy with System Center Configuration Manager, refer to [How to Deploy Applications in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=618175). For deployment of applications with MDT, see [Step 4: Add an application in the Deploy a Windows 8.1 Image Using MDT 2013](http://go.microsoft.com/fwlink/p/?LinkId=618176). Note that you can deploy applications separately from an operating system deployment through MDT by using a Post OS Installation task sequence.
|
||||
For instructions on how to deploy with System Center Configuration Manager, refer to [How to Deploy Applications in Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=618175). For deployment of applications with MDT, see [Step 4: Add an application in the Deploy a Windows 8.1 Image Using MDT 2013](https://go.microsoft.com/fwlink/p/?LinkId=618176). Note that you can deploy applications separately from an operating system deployment through MDT by using a Post OS Installation task sequence.
|
||||
|
||||
**Provisioning packages**
|
||||
|
||||
New in Windows 10, provisioning packages (PPKG files) provide a simple method to apply a configuration to a destination device. You can find out more about provisioning packages, including instructions for how to create your own, in [Provisioning packages](http://go.microsoft.com/fwlink/p/?LinkId=761075). For easy application of a complete set of drivers and firmware to devices running Windows 10, a provisioning package is supplied for Surface Pro 3 devices. This file contains all of the instructions and required assets to update a Surface Pro 3 device with Windows 10 to the latest drivers and firmware.
|
||||
New in Windows 10, provisioning packages (PPKG files) provide a simple method to apply a configuration to a destination device. You can find out more about provisioning packages, including instructions for how to create your own, in [Provisioning packages](https://go.microsoft.com/fwlink/p/?LinkId=761075). For easy application of a complete set of drivers and firmware to devices running Windows 10, a provisioning package is supplied for Surface Pro 3 devices. This file contains all of the instructions and required assets to update a Surface Pro 3 device with Windows 10 to the latest drivers and firmware.
|
||||
|
||||
**Windows PowerShell**
|
||||
|
||||
Another method you can use to update the firmware when Windows Updates are managed in the organization is to install the firmware from the firmware and driver pack by using PowerShell. This method allows for a similar deployment experience to the Windows Installer package and can similarly be deployed as a package by using System Center Configuration Manager. You can find the PowerShell script and details on how to perform the firmware deployment in the [Deploying Drivers and Firmware to Surface Pro](http://go.microsoft.com/fwlink/p/?LinkId=618177) blog post.
|
||||
Another method you can use to update the firmware when Windows Updates are managed in the organization is to install the firmware from the firmware and driver pack by using PowerShell. This method allows for a similar deployment experience to the Windows Installer package and can similarly be deployed as a package by using System Center Configuration Manager. You can find the PowerShell script and details on how to perform the firmware deployment in the [Deploying Drivers and Firmware to Surface Pro](https://go.microsoft.com/fwlink/p/?LinkId=618177) blog post.
|
||||
|
||||
## Operating system deployment considerations
|
||||
|
||||
|
||||
The deployment of firmware updates during an operating system deployment is a straightforward process. The firmware and driver pack can be imported into either System Center Configuration Manager or MDT, and are used to deploy a fully updated environment, complete with firmware, to a target Surface device. For a complete step-by-step guide for deployment to Surface Pro 3 using either Configuration Manager or MDT, download the [Deployment and Administration Guide for Surface Pro 3](http://go.microsoft.com/fwlink/p/?LinkId=618178) from the Microsoft Download Center.
|
||||
The deployment of firmware updates during an operating system deployment is a straightforward process. The firmware and driver pack can be imported into either System Center Configuration Manager or MDT, and are used to deploy a fully updated environment, complete with firmware, to a target Surface device. For a complete step-by-step guide for deployment to Surface Pro 3 using either Configuration Manager or MDT, download the [Deployment and Administration Guide for Surface Pro 3](https://go.microsoft.com/fwlink/p/?LinkId=618178) from the Microsoft Download Center.
|
||||
|
||||
The individual driver files are also made available in the Microsoft Download Center if you are using deployment tools. The driver files are available in the ZIP archive file in the list of available downloads for your device.
|
||||
|
||||
@ -59,7 +60,7 @@ A best practice for deployment with any solution that uses the Windows Preinstal
|
||||
|
||||
**Update Surface Pro 3 firmware offline through USB**
|
||||
|
||||
In some early versions of Surface Pro 3 firmware, PXE boot performance can be quite slow. This has been resolved with updated firmware, but for organizations where firmware will be updated through operating system deployment, this issue is encountered before the updates can be deployed to the device. In this scenario, you can deploy updated firmware through a USB drive to ensure that when the operating system deployment is initiated, the network boot is quick, and deployment can complete in a timely fashion. To create a USB drive to update Surface Pro 3 firmware, see [How to Update the Surface Pro 3 Firmware Offline using a USB Drive](http://go.microsoft.com/fwlink/p/?LinkId=618189) on the Ask Premier Field Engineering (PFE) Platforms TechNet Blog.
|
||||
In some early versions of Surface Pro 3 firmware, PXE boot performance can be quite slow. This has been resolved with updated firmware, but for organizations where firmware will be updated through operating system deployment, this issue is encountered before the updates can be deployed to the device. In this scenario, you can deploy updated firmware through a USB drive to ensure that when the operating system deployment is initiated, the network boot is quick, and deployment can complete in a timely fashion. To create a USB drive to update Surface Pro 3 firmware, see [How to Update the Surface Pro 3 Firmware Offline using a USB Drive](https://go.microsoft.com/fwlink/p/?LinkId=618189) on the Ask Premier Field Engineering (PFE) Platforms TechNet Blog.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Manage Surface UEFI settings (Surface)
|
||||
description: Use Surface UEFI settings to enable or disable devices or components, configure security settings, and adjust Surface device boot settings.
|
||||
keywords: firmware, security, features, configure, hardware
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
@ -25,7 +26,7 @@ On the **PC information** page, detailed information about your Surface device i
|
||||
- **UUID** – This Universally Unique Identification number is specific to your device and is used to identify the device during deployment or management.
|
||||
|
||||
- **Serial Number** – This number is used to identify this specific Surface device for asset tagging and support scenarios.
|
||||
- **Asset Tag** – The asset tag is assigned to the Surface device with the [Asset Tag Tool](https://www.microsoft.com/en-us/download/details.aspx?id=44076).
|
||||
- **Asset Tag** – The asset tag is assigned to the Surface device with the [Asset Tag Tool](https://www.microsoft.com/download/details.aspx?id=44076).
|
||||
|
||||
You will also find detailed information about the firmware of your Surface device. Surface devices have several internal components that each run different versions of firmware. The firmware version of each of the following devices is displayed on the **PC information** page (as shown in Figure 1):
|
||||
|
||||
@ -43,7 +44,7 @@ You will also find detailed information about the firmware of your Surface devic
|
||||
|
||||
*Figure 1. System information and firmware version information*
|
||||
|
||||
You can find up-to-date information about the latest firmware version for your Surface device in the [Surface Update History](https://www.microsoft.com/surface/en-us/support/install-update-activate/surface-update-history) for your device.
|
||||
You can find up-to-date information about the latest firmware version for your Surface device in the [Surface Update History](https://www.microsoft.com/surface/support/install-update-activate/surface-update-history) for your device.
|
||||
|
||||
##Security
|
||||
|
||||
@ -69,7 +70,7 @@ On the **Security** page you can also change the configuration of Secure Boot on
|
||||
|
||||
*Figure 3. Configure Secure Boot*
|
||||
|
||||
You can also enable or disable the Trusted Platform Module (TPM) device on the **Security** page, as shown in Figure 4. The TPM is used to authenticate encryption for your device’s data with BitLocker. Read more about [BitLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/bitlocker-overview) in the TechNet Library.
|
||||
You can also enable or disable the Trusted Platform Module (TPM) device on the **Security** page, as shown in Figure 4. The TPM is used to authenticate encryption for your device’s data with BitLocker. Read more about [BitLocker](https://technet.microsoft.com/itpro/windows/keep-secure/bitlocker-overview) in the TechNet Library.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Microsoft Surface Data Eraser (Surface)
|
||||
description: Find out how the Microsoft Surface Data Eraser tool can help you securely wipe data from your Surface devices.
|
||||
ms.assetid: 8DD3F9FE-5458-4467-BE26-E9200341CF10
|
||||
localizationpriority: high
|
||||
keywords: tool, USB, data, erase
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -15,7 +16,7 @@ author: miladCA
|
||||
|
||||
Find out how the Microsoft Surface Data Eraser tool can help you securely wipe data from your Surface devices.
|
||||
|
||||
[Microsoft Surface Data Eraser](http://go.microsoft.com/fwlink/p/?LinkId=691148) is a tool that boots from a USB stick and allows you to perform a secure wipe of all data from a compatible Surface device. A Microsoft Surface Data Eraser USB stick requires only the ability to boot from USB. The USB tool is easy to create by using the provided wizard, the Microsoft Surface Data Eraser Wrapper, and is easy to use with a simple graphic interface, no command line needed. To learn more about the data wiping capabilities and practices Microsoft uses during the service process for Surface, see [Protecting your data if you send your Surface in for service](http://go.microsoft.com/fwlink/p/?LinkId=691222).
|
||||
[Microsoft Surface Data Eraser](https://go.microsoft.com/fwlink/p/?LinkId=691148) is a tool that boots from a USB stick and allows you to perform a secure wipe of all data from a compatible Surface device. A Microsoft Surface Data Eraser USB stick requires only the ability to boot from USB. The USB tool is easy to create by using the provided wizard, the Microsoft Surface Data Eraser Wrapper, and is easy to use with a simple graphic interface, no command line needed. To learn more about the data wiping capabilities and practices Microsoft uses during the service process for Surface, see [Protecting your data if you send your Surface in for service](https://go.microsoft.com/fwlink/p/?LinkId=691222).
|
||||
|
||||
Compatible Surface devices include:
|
||||
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Microsoft Surface Deployment Accelerator (Surface)
|
||||
description: Microsoft Surface Deployment Accelerator provides a quick and simple deployment mechanism for organizations to reimage Surface devices.
|
||||
ms.assetid: E7991E90-4AAE-44B6-8822-58BFDE3EADE4
|
||||
localizationpriority: high
|
||||
keywords: deploy, install, tool
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -19,13 +20,13 @@ SDA includes a wizard that automates the creation and configuration of a Microso
|
||||
|
||||
SDA is built on the powerful suite of deployment tools available from Microsoft including the Windows Assessment and Deployment Kit (ADK), the Microsoft Deployment Toolkit (MDT), and Windows Deployment Services (WDS). The resulting deployment share encompasses the recommended best practices for managing drivers during deployment and automating image creation and can serve as a starting point upon which you build your own customized deployment solution.
|
||||
|
||||
You can find more information about how to deploy to Surface devices, including step-by-step walkthroughs of customized deployment solution implementation, on the Deploy page of the [Surface TechCenter](http://go.microsoft.com/fwlink/p/?LinkId=691693).
|
||||
You can find more information about how to deploy to Surface devices, including step-by-step walkthroughs of customized deployment solution implementation, on the Deploy page of the [Surface TechCenter](https://go.microsoft.com/fwlink/p/?LinkId=691693).
|
||||
|
||||
**Download Microsoft Surface Deployment Accelerator**
|
||||
|
||||
You can download the installation files for SDA from the Microsoft Download Center. To download the installation files:
|
||||
|
||||
1. Go to the [Surface Tools for IT](http://go.microsoft.com/fwlink/p/?LinkId=618121) page on the Microsoft Download Center.
|
||||
1. Go to the [Surface Tools for IT](https://go.microsoft.com/fwlink/p/?LinkId=618121) page on the Microsoft Download Center.
|
||||
|
||||
2. Click the **Download** button, select the **Surface\_Deployment\_Accelerator\_xxxx.msi** file, and then click **Next**.
|
||||
|
||||
@ -59,7 +60,7 @@ As you progress through the SDA wizard, you will be asked some basic questions a
|
||||
|
||||
When the SDA completes, you can use the deployment share to deploy over the network immediately. Simply boot your Surface device from the network using a Surface Ethernet Adapter and select the Surface deployment share you created with the SDA wizard. Select the **1- Deploy Microsoft Surface** task sequence and the wizard will walk you through an automated deployment of Windows to your Surface device.
|
||||
|
||||
You can modify the task sequence in the MDT Deployment Workbench to [include your own apps](http://go.microsoft.com/fwlink/p/?linkid=691700), or to [pause the automated installation routine](http://go.microsoft.com/fwlink/p/?linkid=691701). While the installation is paused, you can make changes to customize your reference image. After the image is captured, you can configure a deployment task sequence and distribute this custom configuration by using the same network boot capabilities as before.
|
||||
You can modify the task sequence in the MDT Deployment Workbench to [include your own apps](https://go.microsoft.com/fwlink/p/?linkid=691700), or to [pause the automated installation routine](https://go.microsoft.com/fwlink/p/?linkid=691701). While the installation is paused, you can make changes to customize your reference image. After the image is captured, you can configure a deployment task sequence and distribute this custom configuration by using the same network boot capabilities as before.
|
||||
|
||||
>**Note:** With SDA v1.9.0258, Surface Pro 3, Surface Pro 4, and Surface Book are supported for Windows 10 deployment, and Surface Pro 3 is supported for Windows 8.1 deployment.
|
||||
|
||||
@ -82,7 +83,7 @@ You can find a full list of available driver downloads at [Download the latest f
|
||||
|
||||
## Changes and updates
|
||||
|
||||
SDA is periodically updated by Microsoft. For instructions on how these features are used, see [Step-by-Step: Microsoft Surface Deployment Accelerator](https://technet.microsoft.com/en-us/itpro/surface/step-by-step-surface-deployment-accelerator).
|
||||
SDA is periodically updated by Microsoft. For instructions on how these features are used, see [Step-by-Step: Microsoft Surface Deployment Accelerator](https://technet.microsoft.com/itpro/surface/step-by-step-surface-deployment-accelerator).
|
||||
|
||||
>**Note:** To install a newer version of SDA on a server with a previous version of SDA installed, you only need to run the installation file for the new version of SDA. The installer will handle the upgrade process automatically. If you used SDA to create a deployment share prior to the upgrade and want to use new features of the new version of SDA, you will need to create a new deployment share. SDA does not support upgrades of an existing deployment share.
|
||||
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Step by step Surface Deployment Accelerator (Surface)
|
||||
description: This article shows you how to install Microsoft Surface Deployment Accelerator (SDA), configure a deployment share for the deployment of Windows to Surface devices, and perform a deployment to Surface devices.
|
||||
ms.assetid: A944FB9C-4D81-4868-AFF6-B9D1F5CF1032
|
||||
localizationpriority: high
|
||||
keywords: deploy, configure
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -20,7 +21,7 @@ This article shows you how to install Microsoft Surface Deployment Accelerator (
|
||||
|
||||
For information about prerequisites and instructions for how to download and install SDA, see [Microsoft Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md).
|
||||
|
||||
1. Download SDA, which is included in [Surface Tools for IT](http://go.microsoft.com/fwlink/p/?LinkId=618121) on the Microsoft Download Center.
|
||||
1. Download SDA, which is included in [Surface Tools for IT](https://go.microsoft.com/fwlink/p/?LinkId=618121) on the Microsoft Download Center.
|
||||
|
||||
2. Run the SDA installation file, named **Surface\_Deployment\_Accelerator\_*xxxx*.msi**, where *xxxx* is the current version number.
|
||||
|
||||
@ -76,7 +77,7 @@ The following steps show you how to create a deployment share for Windows 10 th
|
||||
|
||||
- **Windows 10 Deployment Services**
|
||||
|
||||
- Select the **Import boot media into the local Windows Deployment Service** check box if you would like to boot your Surface devices from the network to perform the Windows deployment. Windows Deployment Services must be installed and configured to respond to PXE boot requests. See [Windows Deployment Services Getting Started Guide for Windows Server 2012](http://go.microsoft.com/fwlink/p/?LinkId=761072) for more information about how to configure Windows Deployment Services for PXE boot.
|
||||
- Select the **Import boot media into the local Windows Deployment Service** check box if you would like to boot your Surface devices from the network to perform the Windows deployment. Windows Deployment Services must be installed and configured to respond to PXE boot requests. See [Windows Deployment Services Getting Started Guide for Windows Server 2012](https://go.microsoft.com/fwlink/p/?LinkId=761072) for more information about how to configure Windows Deployment Services for PXE boot.
|
||||
|
||||
- **Windows 10 Source Files**
|
||||
|
||||
@ -146,7 +147,7 @@ You can use USB media to perform an SDA deployment if your Surface device is una
|
||||
|
||||
|
||||
|
||||
Before you can create bootable media files within the MDT Deployment Workbench or copy those files to a USB drive, you must first configure that USB drive to be bootable. Using [DiskPart](http://go.microsoft.com/fwlink/p/?LinkId=761073), create a partition, format the partition as FAT32, and set the partition to be active. To run DiskPart, open an administrative PowerShell or Command Prompt window, and then run the following sequence of commands, as shown in Figure 7:
|
||||
Before you can create bootable media files within the MDT Deployment Workbench or copy those files to a USB drive, you must first configure that USB drive to be bootable. Using [DiskPart](https://go.microsoft.com/fwlink/p/?LinkId=761073), create a partition, format the partition as FAT32, and set the partition to be active. To run DiskPart, open an administrative PowerShell or Command Prompt window, and then run the following sequence of commands, as shown in Figure 7:
|
||||
|
||||
1. **diskpart** – Opens DiskPart to manage disks and partitions.
|
||||
|
||||
@ -299,7 +300,7 @@ The **2 – Create Windows Reference Image** task sequence is used to perform a
|
||||
|
||||
Like the **1 – Deploy Microsoft Surface** task sequence, the **2 – Create Windows Reference Image** task sequence performs a deployment of the unaltered Windows image directly from the installation media. Creation of a reference image should always be performed on a virtual machine. Using a virtual machine as your reference system helps to ensure that the resulting image is compatible with different hardware configurations.
|
||||
|
||||
>**Note:** Using a virtual machine when you create a reference image for Windows deployment is a recommended practice for performing Windows deployments with Microsoft deployment tools including the Microsoft Deployment Toolkit and System Center Configuration Manager. These Microsoft deployment technologies use the hardware agnostic images produced from a virtual machine and a collection of managed drivers to deploy to different configurations of hardware. For more information, see [Deploy a Windows 10 image using MDT 2013 Update 2](http://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt).
|
||||
>**Note:** Using a virtual machine when you create a reference image for Windows deployment is a recommended practice for performing Windows deployments with Microsoft deployment tools including the Microsoft Deployment Toolkit and System Center Configuration Manager. These Microsoft deployment technologies use the hardware agnostic images produced from a virtual machine and a collection of managed drivers to deploy to different configurations of hardware. For more information, see [Deploy a Windows 10 image using MDT 2013 Update 2](http://technet.microsoft.com/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt).
|
||||
|
||||
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: Microsoft Surface Diagnostic Toolkit (Surface)
|
||||
description: Find out how you can use the Microsoft Surface Diagnostic Toolkit to test the hardware of your Surface device.
|
||||
ms.assetid: FC4C3E76-3613-4A84-A384-85FE8809BEF1
|
||||
keywords: hardware, device, tool, test, component
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
@ -15,7 +16,7 @@ author: miladCA
|
||||
|
||||
Find out how you can use the Microsoft Surface Diagnostic Toolkit to test the hardware of your Surface device.
|
||||
|
||||
The [Microsoft Surface Diagnostic Toolkit](http://go.microsoft.com/fwlink/p/?LinkId=618121) is a small, portable diagnostic tool that runs through a suite of tests to diagnose the hardware of Surface devices. The Microsoft Surface Diagnostic Toolkit executable file is less than 3 MB, which allows it to be distributed through email. It does not require installation, so it can be run directly from a USB stick or over the network. The Microsoft Surface Diagnostic Toolkit walks you through several tests of individual components including the touchscreen, cameras, and sensors.
|
||||
The [Microsoft Surface Diagnostic Toolkit](https://go.microsoft.com/fwlink/p/?LinkId=618121) is a small, portable diagnostic tool that runs through a suite of tests to diagnose the hardware of Surface devices. The Microsoft Surface Diagnostic Toolkit executable file is less than 3 MB, which allows it to be distributed through email. It does not require installation, so it can be run directly from a USB stick or over the network. The Microsoft Surface Diagnostic Toolkit walks you through several tests of individual components including the touchscreen, cameras, and sensors.
|
||||
|
||||
>**Note:** A Surface device must boot into Windows to run the Microsoft Surface Diagnostic Toolkit. The Microsoft Surface Diagnostic Toolkit will run only on the following Surface devices:
|
||||
|
||||
@ -122,7 +123,7 @@ This test checks for any outstanding Windows updates and will prompt you to inst
|
||||
|
||||
#### Device information
|
||||
|
||||
This test reads the Device ID and serial number in addition to basic system information such as device model, operating system version, processor, memory, and storage. The Device ID is recorded in the name of the log file and can be used to identify a log file for a specific device. Several system log files are also collected, including update and rollback logs, and output from several Windows built-in tools, such as [DirectX Diagnostics](http://go.microsoft.com/fwlink/p/?LinkId=746476) and [System Information](http://go.microsoft.com/fwlink/p/?LinkId=746477), power configuration, disk health, and event logs. See the following list for a full set of collected log files:
|
||||
This test reads the Device ID and serial number in addition to basic system information such as device model, operating system version, processor, memory, and storage. The Device ID is recorded in the name of the log file and can be used to identify a log file for a specific device. Several system log files are also collected, including update and rollback logs, and output from several Windows built-in tools, such as [DirectX Diagnostics](https://go.microsoft.com/fwlink/p/?LinkId=746476) and [System Information](https://go.microsoft.com/fwlink/p/?LinkId=746477), power configuration, disk health, and event logs. See the following list for a full set of collected log files:
|
||||
|
||||
- Output of **Get-WindowsUpdateLog** if the operating system is Windows 10
|
||||
|
||||
@ -338,7 +339,7 @@ The device orientation sensor determines what the angle of the Surface device is
|
||||
This test cycles the screen through brightness levels from 0 percent to 100 percent, and then a message is displayed to confirm if the brightness level changed accordingly. You are then prompted to test for brightness reaction. To test the reaction of brightness when running on battery, disconnect the power adapter. The screen should automatically dim when power is disconnected.
|
||||
|
||||
#### Surface Dock test
|
||||
The Microsoft Surface Diagnostic Toolkit uses this test only if a Surface Dock is connected to the device. If a Surface Dock is detected, this test verifies that the Surface Dock driver firmware is updated. For more detailed analysis of Surface Dock firmware status and how to manually initiate the firmware update process, see the [Microsoft Surface Dock Updater](https://technet.microsoft.com/en-us/itpro/surface/surface-dock-updater) article.
|
||||
The Microsoft Surface Diagnostic Toolkit uses this test only if a Surface Dock is connected to the device. If a Surface Dock is detected, this test verifies that the Surface Dock driver firmware is updated. For more detailed analysis of Surface Dock firmware status and how to manually initiate the firmware update process, see the [Microsoft Surface Dock Updater](https://technet.microsoft.com/itpro/surface/surface-dock-updater) article.
|
||||
|
||||
|
||||
#### System assessment
|
||||
@ -349,11 +350,11 @@ The Windows System Assessment Tool (WinSAT) runs a series of benchmarks against
|
||||
|
||||
#### Performance Monitor test
|
||||
|
||||
Performance and diagnostic trace logs are recorded from Performance Monitor for 30 seconds and collected in the .zip file output of the Microsoft Surface Diagnostic Toolkit by this test. You can analyze these trace logs with the [Windows Performance Analyzer](http://go.microsoft.com/fwlink/p/?LinkId=746486) to identify causes of application crashes, performance issues, or other undesirable behavior in Windows.
|
||||
Performance and diagnostic trace logs are recorded from Performance Monitor for 30 seconds and collected in the .zip file output of the Microsoft Surface Diagnostic Toolkit by this test. You can analyze these trace logs with the [Windows Performance Analyzer](https://go.microsoft.com/fwlink/p/?LinkId=746486) to identify causes of application crashes, performance issues, or other undesirable behavior in Windows.
|
||||
|
||||
#### Crash dump collection
|
||||
|
||||
If your Surface device has encountered an error that caused the device to fail or produce a blue screen error, this stage of the Microsoft Surface Diagnostic Toolkit records the information from the automatically recorded crash dump files in the diagnostic log. You can use these crash dump files to identify a faulty driver, hardware component, or application through analysis. Use the [Windows Debugging Tool](http://go.microsoft.com/fwlink/p/?LinkId=746488) to analyze these files. If you are not familiar with the analysis of crash dump files, you can describe your issue and post a link to your crash dump files (uploaded to OneDrive or another file sharing service) in the [Windows TechNet Forums](http://go.microsoft.com/fwlink/p/?LinkId=746489).
|
||||
If your Surface device has encountered an error that caused the device to fail or produce a blue screen error, this stage of the Microsoft Surface Diagnostic Toolkit records the information from the automatically recorded crash dump files in the diagnostic log. You can use these crash dump files to identify a faulty driver, hardware component, or application through analysis. Use the [Windows Debugging Tool](https://go.microsoft.com/fwlink/p/?LinkId=746488) to analyze these files. If you are not familiar with the analysis of crash dump files, you can describe your issue and post a link to your crash dump files (uploaded to OneDrive or another file sharing service) in the [Windows TechNet Forums](https://go.microsoft.com/fwlink/p/?LinkId=746489).
|
||||
|
||||
#### Connected standby text
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: Microsoft Surface Dock Updater (Surface)
|
||||
description: This article provides a detailed walkthrough of Microsoft Surface Dock Updater.
|
||||
ms.assetid: 1FEFF277-F7D1-4CB4-8898-FDFE8CBE1D5C
|
||||
keywords: install, update, firmware
|
||||
localizationpriority: high
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
@ -15,7 +16,7 @@ author: jobotto
|
||||
|
||||
This article provides a detailed walkthrough of Microsoft Surface Dock Updater.
|
||||
|
||||
The [Microsoft Surface Dock Updater](http://go.microsoft.com/fwlink/p/?LinkId=618121) tool allows you to check the firmware status of a Surface Dock and to manually update the firmware of Surface Dock devices. It is most often used to update Surface Docks prior to deployment of those Surface Docks to end users or as a troubleshooting tool. Microsoft Surface Dock Updater walks you through the process of updating the firmware on one or more Surface Docks, including the required connect and disconnect steps to perform the complete firmware installation.
|
||||
The [Microsoft Surface Dock Updater](https://go.microsoft.com/fwlink/p/?LinkId=618121) tool allows you to check the firmware status of a Surface Dock and to manually update the firmware of Surface Dock devices. It is most often used to update Surface Docks prior to deployment of those Surface Docks to end users or as a troubleshooting tool. Microsoft Surface Dock Updater walks you through the process of updating the firmware on one or more Surface Docks, including the required connect and disconnect steps to perform the complete firmware installation.
|
||||
|
||||
When you run the Microsoft Surface Dock Updater installer you will be prompted to accept an End User License Agreement (EULA).
|
||||
|
||||
@ -24,7 +25,7 @@ When you run the Microsoft Surface Dock Updater installer you will be prompted t
|
||||
## Update a Surface Dock with Microsoft Surface Dock Updater
|
||||
|
||||
|
||||
After you install the [Microsoft Surface Dock Updater](http://go.microsoft.com/fwlink/p/?LinkId=618121) tool, you can find Microsoft Surface Dock Updater under **All Apps** in your Start menu. Click **Microsoft Surface Dock Updater** to start the application.
|
||||
After you install the [Microsoft Surface Dock Updater](https://go.microsoft.com/fwlink/p/?LinkId=618121) tool, you can find Microsoft Surface Dock Updater under **All Apps** in your Start menu. Click **Microsoft Surface Dock Updater** to start the application.
|
||||
|
||||
To update a Surface Dock with Microsoft Surface Dock Updater, follow these steps:
|
||||
|
||||
|
||||
163
devices/surface/using-the-sda-deployment-share.md
Normal file
163
devices/surface/using-the-sda-deployment-share.md
Normal file
@ -0,0 +1,163 @@
|
||||
---
|
||||
title: Using the Microsoft Surface Deployment Accelerator deployment share (Surface)
|
||||
description: Explore the scenarios where you can use SDA to meet the deployment needs of your organization including Proof of Concept, pilot deployment, as well as import additional drivers and applications.
|
||||
keywords: deploy, install, automate, deployment solution
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: Scottmca
|
||||
---
|
||||
|
||||
# Using the Microsoft Surface Deployment Accelerator deployment share
|
||||
|
||||
With Microsoft Surface Deployment Accelerator (SDA), you can quickly and easily set up a deployment solution that is ready to deploy Windows to Surface devices. The prepared environment is built on powerful deployment technologies available from Microsoft, such as the [Microsoft Deployment Toolkit (MDT)](https://technet.microsoft.com/en-us/windows/dn475741), and is capable of immediately performing a deployment after configuration. See [Step-by-Step: Surface Deployment Accelerator](https://technet.microsoft.com/en-us/itpro/surface/step-by-step-surface-deployment-accelerator) for a comprehensive walkthrough of using the SDA wizard to set up a deployment share and perform a deployment.
|
||||
|
||||
For more information about SDA and information on how to download SDA, see [Microsoft Surface Deployment Accelerator (SDA)](https://technet.microsoft.com/en-us/itpro/surface/microsoft-surface-deployment-accelerator).
|
||||
|
||||
Using SDA provides these primary benefits:
|
||||
|
||||
* With SDA, you can create a ready-to-deploy environment that can deploy to target devices as fast as your download speeds allow. The wizard experience enables you to check a few boxes and then the automated process builds your deployment environment for you.
|
||||
|
||||
* With SDA, you prepare a deployment environment built on the industry leading deployment solution of MDT. With MDT you can scale from a relatively basic deployment of a few Surface devices to a solution capable of deploying to thousands of devices including all of the different makes and models in your organization and all of the applications required by each device and user.
|
||||
|
||||
This article explores four scenarios where you can use SDA to meet the needs of your organization. See [Deploy Windows 10](https://technet.microsoft.com/en-us/itpro/windows/deploy/index) to explore the capabilities of MDT and the Windows deployment technologies available from Microsoft in greater detail.
|
||||
|
||||
## Perform a Proof of Concept deployment
|
||||
|
||||
One of the primary scenarios for use of SDA is as a Proof of Concept. A *Proof of Concept* (PoC) enables you to test or evaluate the capabilities of a solution or technology. A PoC is often used to illustrate the benefits of the solution or technology to decision makers. For example, if you want to recommend Surface devices as a replacement of older point of sale (POS) systems, you could perform a PoC to demonstrate how Surface devices provide superior computing power, flexibility, and connectivity when compared to alternate options.
|
||||
|
||||
Using SDA to prepare a PoC of Surface devices enables you to very quickly prepare a demonstration of Surface device or devices, which gives you more time for customization or preparation. The flexibility of SDA even lets you import resources, like applications and drivers, from existing MDT deployment infrastructure. See the [Work with existing deployment shares](#work-with-existing-deployment-shares) section later in this article for more information.
|
||||
|
||||
SDA is also an excellent PoC of the capabilities of MDT. SDA demonstrates just how quickly an MDT deployment environment can be prepared and made ready for deployment to devices. It also shows just how flexible and customizable the MDT solution can be, with support for Windows 10 and Windows 8.1, for Windows Store and desktop applications, and several models of Surface devices.
|
||||
|
||||
Some recommendations for a successful PoC with SDA are:
|
||||
|
||||
* Keep your SDA deployment environment separate from your production network. This ensures optimal performance and reduces potential for conflicts during your PoC deployment.
|
||||
|
||||
* Use a fresh and updated instance of Windows Server to house your SDA deployment share to maintain the simplicity and performance of the demonstration environment.
|
||||
|
||||
* Test the deployment process before you demonstrate your PoC. This reduces the potential for unexpected situations and keeps the demonstration focused on the deployment process and Surface devices.
|
||||
|
||||
* Use offline files with SDA to further reduce installation times.
|
||||
|
||||
* For help with your PoC, contact [Surface Support](https://www.microsoft.com/surface/en-us/support/contact-us-business).
|
||||
|
||||
## Perform a pilot deployment
|
||||
|
||||
A pilot deployment differs from a PoC. Where a PoC is usually a closed demonstration that is performed prior to the deployment process in order to get approval for the use of certain technologies or solutions, a *pilot deployment* is performed during the deployment process as a limited scope deployment for testing and validation. The focus of a pilot deployment can be as narrow as only a handful of devices, or wide enough to include a significant portion of your organization.
|
||||
|
||||
>[!NOTE]
|
||||
>A pilot deployment should not replace the testing process that should be performed regularly in the lab as the deployment environment is built and developed. A deployment solution should be tested in virtual and physical environments as new applications and drivers are added and when task sequences are modified and before a pilot deployment is performed.
|
||||
|
||||
For example, you are tasked with deploying Surface devices to mobile workers and you want to test the organization’s MDT deployment process by providing a small number of devices to executives. You can use SDA to create an isolated Surface deployment environment and then copy the task sequence, applications, and drivers needed from the production deployment share. This not only enables you to quickly create a Surface deployment, but it also minimizes the risk to the production deployment process used for other types of devices.
|
||||
|
||||
For small organizations, the pilot deployment environment of SDA may suffice as a complete deployment solution. Even if you do not have an existing deployment environment, you can import drivers and applications (covered later in this article) to provide a complete deployment solution based on MDT. Even without previous knowledge of MDT or Windows deployment, you can follow the [Step-by-Step: Surface Deployment Accelerator](https://technet.microsoft.com/en-us/itpro/surface/step-by-step-surface-deployment-accelerator) article to get started with a deployment to Surface devices.
|
||||
|
||||
## Import additional drivers
|
||||
|
||||
The SDA deployment share includes all of the drivers needed for Surface devices. This includes the drivers for the components inside the Surface device, such as the wireless network adapter and the main chipset, as well as drivers for Surface accessories, such as the Surface Dock or Surface USB Ethernet adapters. The SDA deployment share does not, however, include drivers for third-party devices or peripherals.
|
||||
|
||||
For example, you may intend to use your Surface device with a thermal printer, credit card reader, and barcode scanner as a POS terminal. In this scenario, the thermal printer, credit card reader, and barcode scanner will very likely require installation of drivers to operate properly. You could potentially download and install these drivers from Windows Update when each peripheral is connected, or you could install the driver package from the manufacturer manually on each Surface device, but the ideal solution is to have these drivers already present in Windows so that when the peripheral is connected, it will just work.
|
||||
|
||||
Because SDA is built on MDT, adding the drivers to the SDA deployment share is easy and simple.
|
||||
|
||||
>[!NOTE]
|
||||
>The drivers must be in the Setup Information File (.inf) format. If the drivers for your device come as an executable file (.exe), they may need to be extracted or installed to procure the .inf file. Some device drivers come packaged with applications, for example an all-in-one printer bundled with scan software. These applications will need to be installed separately from the drivers.
|
||||
|
||||
To import drivers for a peripheral device:
|
||||
|
||||
1. Download the drivers for your device from the manufacturer web site.
|
||||
|
||||
2. Open the MDT Deployment Workbench.
|
||||
|
||||
3. Expand the **Deployment Shares** node and expand the SDA deployment share.
|
||||
|
||||
4. Expand the **Out-of-Box Drivers** folder.
|
||||
|
||||
5. Select the folder of the Surface model for which you would like to include this driver.
|
||||
|
||||
6. Click **Import Drivers** to start the Import Drivers Wizard, as shown in Figure 1.
|
||||
|
||||
|
||||
|
||||
*Figure 1. Provide the location of your driver files*
|
||||
|
||||
7. The Import Drivers Wizard presents a series of steps:
|
||||
|
||||
- **Specify Directory** – Click **Browse** and navigate to the folder where you stored the drivers in Step 1.
|
||||
- **Summary** – Review the specified configuration on this page before you click **Next** to begin the import process.
|
||||
- **Progress** – While the drivers are imported, a progress bar is displayed on this page.
|
||||
- **Confirmation** – When the import process completes, the success of the process is displayed on this page. Click **Finish** to complete the Import Drivers Wizard.
|
||||
|
||||
8. Repeat Steps 5-7 for each Surface model on which you would like to include this driver.
|
||||
|
||||
9. Close the Deployment Workbench.
|
||||
|
||||
After the drivers are imported for the Surface model, the deployment task sequence will automatically select the drivers during the deployment process and include them in the Windows environment. When you connect your device, such as the barcode scanner in the example, Windows should automatically detect the device and you should be able to use it immediately.
|
||||
|
||||
>[!NOTE]
|
||||
>You can even import drivers for other computer makes and models to support other devices. See **Step 5: Prepare the drivers repository** in [Deploy a Windows 10 image using MDT 2013 Update 2](https://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt) for more information about how to import drivers for other makes and models.
|
||||
|
||||
## Import additional applications
|
||||
|
||||
As with drivers, the SDA deployment share can be pre-configured with apps like the Surface App and Microsoft Office 365. You can also add applications to the SDA deployment share and configure them to be installed on your Surface devices during deployment of Windows. In the ideal scenario, your Surface devices deployed with the SDA deployment share will include all of the applications needed to be ready for your end users.
|
||||
|
||||
In the previous example for including drivers for a POS system, you would also need to include POS software for processing transactions and recording the input from the barcode scanner and credit card reader. To import an application and prepare it for installation on your Surface devices during Windows deployment:
|
||||
|
||||
1. Download the application installation files or locate the installation media for your application.
|
||||
|
||||
2. Determine the command line instruction for silent installation, usually provided by the developer of the application. For Windows Installer files (.msi), see [Standard Installer Command-Line Options](https://msdn.microsoft.com/library/windows/desktop/aa372024) in the Windows Dev Center.
|
||||
|
||||
3. Open the MDT Deployment Workbench.
|
||||
|
||||
4. Expand the **Deployment Shares** node and expand the SDA deployment share.
|
||||
|
||||
5. Expand the **Applications** folder.
|
||||
|
||||
6. Click **New Application** to start the New Application Wizard, as shown in Figure 2.
|
||||
|
||||
|
||||
|
||||
*Figure 2: Provide the command to install your application*
|
||||
|
||||
7. Follow the steps of the New Application Wizard:
|
||||
|
||||
- **Application Type** – Click **Application with Source Files**, and then click **Next**.
|
||||
- **Details** – Enter a name for the application in the **Application Name** field. Enter publisher, version, and language information in the **Publisher**, **Version**, and **Language** fields if desired. Click **Next**.
|
||||
- **Source** – Click **Browse** to navigate to and select the folder with the application installation files procured in Step 1, and then click **Next**.
|
||||
- **Destination** – Enter a name for the folder where the application files will be stored in the **Specify the Name of the Directory that Should Be Created** field or click **Next** to accept the default name.
|
||||
- **Command Details** – Enter the silent command-line instruction, for example `setup.msi /quiet /norestart`
|
||||
- **Summary** – Review the specified configuration on this page before you click **Next** to begin the import process.
|
||||
- **Progress** – While the installation files are imported, a progress bar is displayed on this page.
|
||||
- **Confirmation** – When the import process completes, the success of the process is displayed on this page. Click **Finish** to complete the New Application Wizard.
|
||||
|
||||
8. Click the **Task Sequences** folder, right-click **1 - Deploy Microsoft Surface**, and then click **Properties**.
|
||||
|
||||
9. Click the **Task Sequence** tab to view the steps that are included in the new task sequence.
|
||||
|
||||
10. Select the **Windows Update (Pre-Application Installation)** step, and then click **Add**.
|
||||
|
||||
11. Hover the mouse over **General** under the **Add** menu, and then click **Install Application**. This will add a new step after the selected step for the installation of a specific application as shown in Figure 3.
|
||||
|
||||
|
||||
|
||||
*Figure 3. A new Install Application step for Sample POS App*
|
||||
|
||||
12. On the **Properties** tab of the new **Install Application** step, enter **Install - Sample POS App** in the **Name** field, where *Sample POS App* is the name of your app.
|
||||
|
||||
13. Click **Install a Single Application**, and then click **Browse** to view available applications that have been imported into the deployment share.
|
||||
|
||||
14. Select your app from the list of applications, and then click **OK**.
|
||||
|
||||
15. Click **OK** to close the task sequence properties.
|
||||
|
||||
16. Close the Deployment Workbench.
|
||||
|
||||
## Work with existing deployment shares
|
||||
|
||||
One of the many benefits of an MDT deployment share is the simplicity of how deployment resources are stored. The MDT deployment share is, at its core, just a standard network file share. All deployment resources, such as Windows images, application installation files, and drivers, are stored in a share that can be browsed with File Explorer, copied and pasted, and moved just like any other file share, provided that you have the necessary permissions. This makes working with deployment resources extremely easy. MDT even allows you to make it easier by allowing you to open multiple deployment shares from the Deployment Workbench and to transfer or copy resources between them.
|
||||
|
||||
This ability gives SDA some extra capabilities when used in an environment with an existing MDT infrastructure. For example, if you install SDA on an isolated server to prepare a PoC and then log on to your production MDT deployment share from the Deployment Workbench on your SDA server, you can copy applications, drivers, task sequences, and other components into the SDA deployment share that is prepared with Surface apps and drivers. With this process, in a very short amount time, you can have a deployment environment ready to deploy your organization’s precise requirements to Surface devices.
|
||||
|
||||
You can also use this capability in reverse. For example, you can copy the Surface drivers, deployment task sequences, and apps directly into a lab or testing environment following a successful PoC. Using these resources, you can immediately begin to integrate Surface deployment into your existing deployment infrastructure.
|
||||
Reference in New Issue
Block a user