mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 11:23:45 +00:00
Merge branch 'master' into wdav-missed
This commit is contained in:
Denise Vangel-MSFT
@ -16,9 +16,11 @@
|
||||
## [Install localized version of HoloLens (1st gen)](hololens1-install-localized.md)
|
||||
## [Getting around HoloLens (1st gen)](hololens1-basic-usage.md)
|
||||
|
||||
# HoloLens in commercial environments
|
||||
## [Commercial feature overview](hololens-commercial-features.md)
|
||||
# Deploying HoloLens and Mixed Reality Apps in Commercial Environments
|
||||
## [Deployment planning](hololens-requirements.md)
|
||||
## [Commercial feature overview](hololens-commercial-features.md)
|
||||
## [Lincense Requriements](hololens-licenses-requirements.md)
|
||||
## [Commercial Infrastructure Guidance](hololens-commercial-infrastructure.md)
|
||||
## [Unlock Windows Holographic for Business features](hololens1-upgrade-enterprise.md)
|
||||
## [Configure HoloLens using a provisioning package](hololens-provisioning.md)
|
||||
## [Enroll HoloLens in MDM](hololens-enroll-mdm.md)
|
||||
|
||||
113
devices/hololens/hololens-commercial-infrastructure.md
Normal file
113
devices/hololens/hololens-commercial-infrastructure.md
Normal file
@ -0,0 +1,113 @@
|
||||
---
|
||||
title: Infrastructure Guidelines for HoloLens
|
||||
description:
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
author: pawinfie
|
||||
ms.author: pawinfie
|
||||
audience: ITPro
|
||||
ms.topic: article
|
||||
ms.localizationpriority: high
|
||||
ms.date: 1/23/2020
|
||||
ms.reviewer:
|
||||
manager: bradke
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Configure Your Network
|
||||
|
||||
This portion of the document will require the following people:
|
||||
1. Network Admin with permissions to make changes to the proxy/firewall
|
||||
2. Azure Active Directory Admin
|
||||
3. Mobile Device Manager Admin
|
||||
4. Teams admin for Remote Assist only
|
||||
|
||||
## Infrastructure Requirements
|
||||
|
||||
### HoloLens Specific Network Requirements
|
||||
Make sure that these ports and URLs are allowed on your network firewall. This will enable HoloLens to function properly. The latest list can be found [here](hololens-offline.md).
|
||||
|
||||
### Remote Assist Specific Network Requirements
|
||||
|
||||
1. The recommended bandwidth for optimal performance of Remote Assist is 1.5Mbps. Detailed network requirements and additional information can be found [here](https://docs.microsoft.com/MicrosoftTeams/prepare-network).
|
||||
**Please note, if you don’t network have network speeds of at least 1.5Mbps, Remote Assist will still work. However, quality may suffer.**
|
||||
1. Make sure that these ports and URLs are allowed on your network firewall. This will enable Microsoft Teams to function. The latest list can be found [here](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams).
|
||||
|
||||
### Guides Specific Network Requirements
|
||||
Guides only require network access to download and use the app.
|
||||
|
||||
## Azure Active Directory Guidance
|
||||
This step is only necessary if your company plans on managing the HoloLens and mixed reality apps.
|
||||
|
||||
### 1. Ensure that you have an Azure AD License.
|
||||
Please [HoloLens Licenses Requirements](hololens-licenses-requirements.md)for additional information.
|
||||
|
||||
### 2. Ensure that your company’s users are in Azure Active Directory (Azure AD).
|
||||
Instructions for adding users can be found [here](https://docs.microsoft.com/azure/active-directory/fundamentals/add-users-azure-active-directory).
|
||||
|
||||
### 3. We suggest that users who will be need similar licenses are added to a group.
|
||||
1. [Create a Group](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-groups-create-azure-portal)
|
||||
|
||||
2. [Add users to groups](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-groups-members-azure-portal)
|
||||
|
||||
### 4. Ensure that your company’s users (or group of users) are assigned the necessary licenses.
|
||||
Directions for assigning licenses can be found [here](https://docs.microsoft.com/azure/active-directory/fundamentals/license-users-groups).
|
||||
|
||||
### 5. **IMPORTANT:** Only do this step if users are expected to enroll their HoloLens/Mobile device onto the network.
|
||||
These steps ensure that your company’s users (or a group of users) can add devices.
|
||||
1. Option 1: Give all users permission to join devices to Azure AD.
|
||||
**Sign in to the Azure portal as an administrator** > **Azure Active Directory** > **Devices** > **Device Settings** >
|
||||
**Set Users may join devices to Azure AD to *All***
|
||||
|
||||
1. Option 2: Give selected users/groups permission to join devices to Azure AD
|
||||
**Sign in to the Azure portal as an administrator** > **Azure Active Directory** > **Devices** > **Device Settings** >
|
||||
**Set Users may join devices to Azure AD to *Selected***
|
||||
|
||||
|
||||
1. Option 3: You can block all users from joining their devices to the domain. This means that all devices will need to be manually enrolled by your IT department.
|
||||
|
||||
## Mobile Device Manager Admin Steps
|
||||
|
||||
### Scenario 1: Kiosk Mode
|
||||
As a note, auto-launching an app does not currently work for HoloLens.
|
||||
|
||||
How to Set Up Kiosk Mode Using Microsoft Intune.
|
||||
#### 1. Sync Microsoft Store to Intune ([Here](https://docs.microsoft.com/intune/apps/windows-store-for-business))
|
||||
|
||||
#### 2. Check your app settings
|
||||
|
||||
1. Log into your Microsoft Store Business account
|
||||
1. **Manage** > **Products and Services** > **Apps and Software** > **Select the app you want to sync** > **Private Store Availability** > **Select “Everyone” or “Specific Groups”**
|
||||
1. If you do not see your apps in **Intune** > **Client Apps** > **Apps** , you may have to [sync your apps](https://docs.microsoft.com/intune/apps/windows-store-for-business#synchronize-apps) again.
|
||||
|
||||
#### 3. Configuring Kiosk Mode using MDM
|
||||
|
||||
Information on configuring Kiosk Mode in Intune can be found [here](https://docs.microsoft.com/hololens/hololens-kiosk#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803)
|
||||
|
||||
>[!NOTE]
|
||||
>You can configure different users to have different Kiosk Mode experiences by using “Azure AD” as the “User logon type”. However, this option is only available in Multi-App kiosk mode. Multi-App kiosk mode will work with only one app as well as multiple apps.
|
||||
|
||||
|
||||
|
||||
If you are configuring Kiosk Mode on an MDM other than Intune, please check your MDM provider's documentation.
|
||||
|
||||
## Additional Intune Quick Links
|
||||
|
||||
1. [Create Profiles:](https://docs.microsoft.com/intune/configuration/device-profile-create) Profiles allow you to add and configure settings that will be pushed to the devices in your organization.
|
||||
|
||||
1. [CSPs (Configuration Service Providers)](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices) allows you to create and deploy management settings for the devices on your network. Some CSPs are supported by HoloLens devices. (See the list of CSPs for HoloLens [here](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices).
|
||||
|
||||
1. [Create Compliance Policy](https://docs.microsoft.com/intune/protect/create-compliance-policy)
|
||||
|
||||
1. Conditional Access allows/denies mobile devices and mobile applications from accessing company resources. Two documents you may find helpful are [Plan your CA Deployment](https://docs.microsoft.com/azure/active-directory/conditional-access/plan-conditional-access) and [Best Practices](https://docs.microsoft.com/azure/active-directory/conditional-access/best-practices).
|
||||
|
||||
## Certificates and Authentication
|
||||
### MDM Certificate Distribution
|
||||
If your company requires certificates, Intune supports PKCS, PFX, and SCEP. It is important to understand which certificate is right for your company. Please visit [here](https://docs.microsoft.com/intune/protect/certificates-configure) to determine which cert is best for you. If you plan to use certs for HoloLens Authentication, PFX or SCEP may be right for you.
|
||||
|
||||
Steps for SCEP can be found [here](https://docs.microsoft.com/intune/protect/certificates-profile-scep).
|
||||
|
||||
### Device Certificates
|
||||
Certificates can also be added to the HoloLens through package provisioning. Please see [HoloLens Provisioning](hololens-provisioning.md) for additional information.
|
||||
@ -20,7 +20,7 @@ In Windows 10, version 1803, you can configure your HoloLens devices to run as m
|
||||
|
||||
When HoloLens is configured as a multi-app kiosk, only the allowed apps are available to the user. The benefit of a multi-app kiosk, or fixed-purpose device, is to provide an easy-to-understand experience for individuals by putting in front of them only the things they need to use, and removing from their view the things they don’t need to access.
|
||||
|
||||
Single-app kiosk mode starts the specified app when the user signs in, and restricts the user's ability to launch new apps or change the running app. When single-app kiosk mode is enabled for HoloLens, the bloom gesture and Cortana are disabled, and placed apps aren't shown in the user's surroundings.
|
||||
Single-app kiosk mode starts the specified app when the user signs in, and restricts the user's ability to launch new apps or change the running app. When single-app kiosk mode is enabled for HoloLens, the [start gestures](https://docs.microsoft.com/hololens/hololens2-basic-usage#start-gesture) (including [Bloom](https://docs.microsoft.com/hololens/hololens1-basic-usage) on HoloLens (1st Gen)) and Cortana are disabled, and placed apps aren't shown in the user's surroundings.
|
||||
|
||||
The following table lists the device capabilities in the different kiosk modes.
|
||||
|
||||
|
||||
50
devices/hololens/hololens-licenses-requirements.md
Normal file
50
devices/hololens/hololens-licenses-requirements.md
Normal file
@ -0,0 +1,50 @@
|
||||
---
|
||||
title: Licenses for Mixed Reality Deployment
|
||||
description:
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
author: pawinfie
|
||||
ms.author: pawinfie
|
||||
audience: ITPro
|
||||
ms.topic: article
|
||||
ms.localizationpriority: high
|
||||
ms.date: 1/23/2020
|
||||
ms.reviewer:
|
||||
manager: bradke
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Licenses Required for Mixed Reality Deployment
|
||||
|
||||
If you plan on using a Mobile Device Management system (MDM) to manage your HoloLens, please review the MDM License Guidance section.
|
||||
|
||||
## Mobile Device Management (MDM) Licenses Guidance
|
||||
|
||||
If you plan on using an MDM other than Intune, an [Azure Active Directory Licenses](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) is required.
|
||||
|
||||
If you plan on using Intune as your MDM, you can acquire an [Enterprise Mobility + Security (EMS) suite (E3 or E5) licenses](https://www.microsoft.com/microsoft-365/enterprise-mobility-security/compare-plans-and-pricing). **Please note that Azure AD is included in both suites.**
|
||||
|
||||
## Identify the licenses needed for your scenario and products
|
||||
|
||||
### Remote Assist License Requirements
|
||||
Make sure you have the required licensing and device. Updated licensing and product requirements can be found [here](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/requirements).
|
||||
|
||||
1. [Remote Assist License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)
|
||||
1. [Teams Freemium/Teams](https://products.office.com/microsoft-teams/free)
|
||||
1. [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)
|
||||
|
||||
### Guides License Requirements
|
||||
Updated licensing and device requirements can be found [here](https://docs.microsoft.com/dynamics365/mixed-reality/guides/requirements).
|
||||
|
||||
1. [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)
|
||||
1. [Power BI](https://powerbi.microsoft.com/desktop/)
|
||||
1. [Guides](https://docs.microsoft.com/dynamics365/mixed-reality/guides/setup)
|
||||
|
||||
### Scenario 1: Kiosk Mode
|
||||
If you are not planning to use an MDM to manage your device and you are planning to use a local account or an MSA as the login identity, you will not need any additional licenses. Kiosk mode can be accomplished using a provisioning packages.
|
||||
|
||||
1. If you are **not** planning to use an MDM to manage your device and you are planning to use a local account or an MSA as the login identity, you will not need any additional licenses. Kiosk mode can be accomplished using a provisioning packages.
|
||||
1. If you are planning to use an MDM other than Intune, your MDM provider will have steps on configuring Kiosk mode.
|
||||
1. If you are planning to use **Intune** as your MDM, implementation directions can be found in [Configuring your Network for HoloLens]().
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Use HoloLens offline
|
||||
title: Manage connection endpoints for HoloLens
|
||||
description: To set up HoloLens, you'll need to connect to a Wi-Fi network
|
||||
keywords: hololens, offline, OOBE
|
||||
audience: ITPro
|
||||
@ -17,13 +17,13 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Use HoloLens offline
|
||||
# Manage connection endpoints for HoloLens
|
||||
|
||||
HoloLens support a limited set of offline experiences for connectivity conscious customers and for customers who have environmental limits on connectivity.
|
||||
Some HoloLens components, apps, and related services transfer data to Microsoft network endpoints. This article lists different endpoints and URLs that need to be whitelisted in your network configuratiion (e.g. proxy or firewall) for those components to be functional.
|
||||
|
||||
## Near-offline setup
|
||||
|
||||
HoloLens need a network connection to go through initial device set up. If your corporate network has network restrictions, the following URLs will need to be available:
|
||||
HoloLens supports a limited set of offline experiences for customers who have network environment restrictions. However, HoloLens needs network connection to go through initial device set up and the following URLs have to be enabled:
|
||||
|
||||
| Purpose | URL |
|
||||
|------|------|
|
||||
@ -35,9 +35,125 @@ HoloLens need a network connection to go through initial device set up. If your
|
||||
| MSA | https://login.live.com/ppsecure/inlineconnect.srf?id=80600 |
|
||||
| MSA Pin | https://account.live.com/msangc?fl=enroll |
|
||||
|
||||
Additional references:
|
||||
## Endpoint configuration
|
||||
|
||||
In addition to the list above, to take full advantage of HoloLens functionality, the following endpoints need to be enabled in your network configuration.
|
||||
|
||||
|
||||
| Purpose | URL |
|
||||
|------|------|
|
||||
| Azure | wd-prod-fe.cloudapp.azure.com | | |
|
||||
| | ris-prod-atm.trafficmanager.net | | | |
|
||||
| | validation-v2.sls.trafficmanager.net | | | |
|
||||
| Azure AD Multi-Factor Authentication | https://secure.aadcdn.microsoftonline-p.com | | | |
|
||||
| Intune and MDM Configurations | activation-v2.sls.microsoft.com/* | | | |
|
||||
| | cdn.onenote.net | | | |
|
||||
| | client.wns.windows.com | | | |
|
||||
| | crl.microsoft.com/pki/crl/* | | | |
|
||||
| | ctldl.windowsupdate.com | | | |
|
||||
| | *displaycatalog.mp.microsoft.com | | | |
|
||||
| | dm3p.wns.windows.com | | | |
|
||||
| | *microsoft.com/pkiops/* | | | |
|
||||
| | ocsp.digicert.com/* | | | |
|
||||
| | r.manage.microsoft.com | | | |
|
||||
| | tile-service.weather.microsoft.com | | | |
|
||||
| | settings-win.data.microsoft.com | | | |
|
||||
| Certificates | activation-v2.sls.microsoft.com/* | | | |
|
||||
| | crl.microsoft.com/pki/crl/* | | | |
|
||||
| | ocsp.digicert.com/* | | | |
|
||||
| | https://www.microsoft.com/pkiops/* | | | |
|
||||
| Cortana and Search | store-images.*microsoft.com | | | |
|
||||
| | www.bing.com/client | | | |
|
||||
| | www.bing.com | | | |
|
||||
| | www.bing.com/proactive | | | |
|
||||
| | www.bing.com/threshold/xls.aspx | | | |
|
||||
| | exo-ring.msedge.net | | | |
|
||||
| | fp.msedge.net | | | |
|
||||
| | fp-vp.azureedge.net | | | |
|
||||
| | odinvzc.azureedge.net | | | |
|
||||
| | spo-ring.msedge.net | | | |
|
||||
| Device Authentication | login.live.com* | | | |
|
||||
| Device metadata | dmd.metaservices.microsoft.com | | | |
|
||||
| Location | inference.location.live.net | | | |
|
||||
| | location-inference-westus.cloudapp.net | | | |
|
||||
| Diagnostic Data | v10.events.data.microsoft.com | | | |
|
||||
| | v10.vortex-win.data.microsoft.com/collect/v1 | | | |
|
||||
| | https://www.microsoft.com | | | |
|
||||
| | co4.telecommand.telemetry.microsoft.com | | | |
|
||||
| | cs11.wpc.v0cdn.net | | | |
|
||||
| | cs1137.wpc.gammacdn.net | | | |
|
||||
| | modern.watson.data.microsoft.com* | | | |
|
||||
| | watson.telemetry.microsoft.com | | | |
|
||||
| Licensing | licensing.mp.microsoft.com | | | |
|
||||
| Microsoft Account | login.msa.akadns6.net | | | |
|
||||
| | us.configsvc1.live.com.akadns.net | | | |
|
||||
| Microsoft Edge | iecvlist.microsoft.com | | | |
|
||||
| Microsoft forward link redirection service (FWLink) | go.microsoft.com | | | |
|
||||
| Microsoft Store | *.wns.windows.com | | | |
|
||||
| | storecatalogrevocation.storequality.microsoft.com | | | |
|
||||
| | img-prod-cms-rt-microsoft-com* | | | |
|
||||
| | store-images.microsoft.com | | | |
|
||||
| | .md.mp.microsoft.com | | |
|
||||
| | *displaycatalog.mp.microsoft.com | | | |
|
||||
| | pti.store.microsoft.com | | | |
|
||||
| | storeedgefd.dsx.mp.microsoft.com | | | |
|
||||
| | markets.books.microsoft.com | | | |
|
||||
| | share.microsoft.com | | | |
|
||||
| Network Connection Status Indicator (NCSI) | www.msftconnecttest.com* | | | |
|
||||
| Office | *.c-msedge.net | | | |
|
||||
| | *.e-msedge.net | | | |
|
||||
| | *.s-msedge.net | | | |
|
||||
| | nexusrules.officeapps.live.com | | | |
|
||||
| | ocos-office365-s2s.msedge.net | | | |
|
||||
| | officeclient.microsoft.com | | | |
|
||||
| | outlook.office365.com | | | |
|
||||
| | client-office365-tas.msedge.net | | | |
|
||||
| | https://www.office.com | | | |
|
||||
| | onecollector.cloudapp.aria | | | |
|
||||
| | v10.events.data.microsoft.com/onecollector/1.0/ | | | |
|
||||
| | self.events.data.microsoft.com | | | |
|
||||
| | to-do.microsoft.com | | | |
|
||||
| OneDrive | g.live.com/1rewlive5skydrive/* | | | |
|
||||
| | msagfx.live.com | | | |
|
||||
| | oneclient.sfx.ms | | | |
|
||||
| Photos App | evoke-windowsservices-tas.msedge.net | | | |
|
||||
| Settings | cy2.settings.data.microsoft.com.akadns.net | | | |
|
||||
| | settings.data.microsoft.com | | | |
|
||||
| | settings-win.data.microsoft.com | | | |
|
||||
| Windows Defender | wdcp.microsoft.com | | | |
|
||||
| | definitionupdates.microsoft.com | | | |
|
||||
| | go.microsoft.com | | | |
|
||||
| | *smartscreen.microsoft.com | | | |
|
||||
| | smartscreen-sn3p.smartscreen.microsoft.com | | | |
|
||||
| | unitedstates.smartscreen-prod.microsoft.com | | | |
|
||||
| Windows Spotlight | *.search.msn.com | | | |
|
||||
| | arc.msn.com | | | |
|
||||
| | g.msn.com* | | | |
|
||||
| | query.prod.cms.rt.microsoft.com | | | |
|
||||
| | ris.api.iris.microsoft.com | | | |
|
||||
| Windows Update | *.prod.do.dsp.mp.microsoft.com | | | |
|
||||
| | cs9.wac.phicdn.net | | | |
|
||||
| | emdl.ws.microsoft.com | | | |
|
||||
| | *.dl.delivery.mp.microsoft.com | | | |
|
||||
| | *.windowsupdate.com | | | |
|
||||
| | *.delivery.mp.microsoft.com | | | |
|
||||
| | *.update.microsoft.com | | | |
|
||||
|
||||
|
||||
|
||||
## References
|
||||
|
||||
> [!NOTE]
|
||||
> If you are deploying D365 Remote Assist, you will have to enable the endpoints on this [list](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams)
|
||||
- [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization)
|
||||
- [Manage connection endpoints for Windows 10 Enterprise, version 1903](https://docs.microsoft.com/windows/privacy/manage-windows-1903-endpoints)
|
||||
- [Manage connections from Windows 10 operating system components to Microsoft services](https://docs.microsoft.com/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services)
|
||||
- [Manage connections from Windows 10 operating system components to Microsoft services using Microsoft Intune MDM Server](https://docs.microsoft.com/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-mdm)
|
||||
- [Intune network configuration requirements and bandwidth](https://docs.microsoft.com/intune/fundamentals/network-bandwidth-use#network-communication-requirements)
|
||||
- [Network endpoints for Microsoft Intune](https://docs.microsoft.com/intune/fundamentals/intune-endpoints)
|
||||
- [Office 365 URLs and IP address ranges](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges)
|
||||
- [Prerequisites for Azure AD Connect](https://docs.microsoft.com/azure/active-directory/hybrid/how-to-connect-install-prerequisites)
|
||||
|
||||
- [Technical reference for AAD related IP ranges and URLs](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges)
|
||||
|
||||
## HoloLens limitations
|
||||
|
||||
|
||||
BIN
devices/hololens/images/aad-kioskmode.PNG
Normal file
BIN
devices/hololens/images/aad-kioskmode.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
BIN
devices/hololens/images/azure-ad-image.PNG
Normal file
BIN
devices/hololens/images/azure-ad-image.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
@ -93,7 +93,7 @@ Internet Connectivity |Device does have Internet connectivity |Device does not h
|
||||
HTTP Version |1.1 |1.0 |If HTTP 1.0 found, it will cause issue with WU and Store |
|
||||
Direct Internet Connectivity |Device has a Proxy configured Device has no Proxy configured |N/A |Informational. Is your device behind a proxy? |
|
||||
Proxy Address | | |If configured, returns proxy address. |
|
||||
Proxy Authentication |Proxy does not require Authentication |Proxy requires Proxy Auth |Result may be a false positive if a user already has an open session in Edge and has authenticated thru the proxy. |[Configuring a proxy for your Surface Hub](https://blogs.technet.microsoft.com/y0av/2017/12/03/7/)
|
||||
Proxy Authentication |Proxy does not require Authentication |Proxy requires Proxy Auth |Result may be a false positive if a user already has an open session in Edge and has authenticated through the proxy. |[Configuring a proxy for your Surface Hub](https://blogs.technet.microsoft.com/y0av/2017/12/03/7/)
|
||||
Proxy Auth Types | | |If proxy authentication is used, return the Authentication methods advertised by the proxy. |
|
||||
|
||||
#### Environment
|
||||
|
||||
@ -29,10 +29,8 @@ Although the deployment and management of Surface devices is fundamentally the s
|
||||
|
||||
## Updating Surface device drivers and firmware
|
||||
|
||||
|
||||
For devices that recieve updates through Windows Update, drivers for Surface components (and even firmware updates) are applied automatically as part of the Windows Update process. For devices with managed updates, such as those updated through Windows Server Update Services (WSUS) or Configuration Manager, see [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-driver-and-firmware-updates/).
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> Surface device drivers and firmware are signed with SHA-256, which is not natively supported by Windows Server 2008 R2. A workaround is available for Configuration Manager environments running on Windows Server 2008 R2. For more information, see [Can't import drivers into Microsoft Endpoint Configuration Manager (KB3025419)](https://support.microsoft.com/kb/3025419).
|
||||
|
||||
|
||||
@ -50,6 +50,54 @@ To add the keyboard drivers to the selection profile, follow these steps:
|
||||
4. Right-click the **WindowsPEX64** folder and select **Import Drivers**.
|
||||
5. Follow the instructions in the Import Driver Wizard to import the driver folders into the WindowsPEX64 folder.
|
||||
|
||||
> [!NOTE]
|
||||
> Check the downloaded MSI package to determine the format and directory structure. The directory structure will start with either SurfacePlatformInstaller (older MSI files) or SurfaceUpdate (Newer MSI files) depending on when the MSI was released.
|
||||
|
||||
To support Surface Laptop (1st Gen), import the following folders:
|
||||
|
||||
- SurfacePlatformInstaller\Drivers\System\GPIO
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceHidMiniDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\PreciseTouch
|
||||
|
||||
Or for newer MSI files beginning with "SurfaceUpdate", use:
|
||||
|
||||
- SurfaceUpdate\SerialIOGPIO
|
||||
- SurfaceUpdate\SurfaceHidMiniDriver
|
||||
- SurfaceUpdate\SurfaceSerialHubDriver
|
||||
- SurfaceUpdate\Itouch
|
||||
|
||||
To support Surface Laptop 2, import the following folders:
|
||||
|
||||
- SurfacePlatformInstaller\Drivers\System\GPIO
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceHIDMiniDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
|
||||
- SurfacePlatformInstaller\Drivers\System\I2C
|
||||
- SurfacePlatformInstaller\Drivers\System\SPI
|
||||
- SurfacePlatformInstaller\Drivers\System\UART
|
||||
- SurfacePlatformInstaller\Drivers\System\PreciseTouch
|
||||
|
||||
Or for newer MSI files beginning with "SurfaceUpdate", use:
|
||||
|
||||
- SurfaceUpdate\SerialIOGPIO
|
||||
- SurfaceUpdate\IclSerialIOI2C
|
||||
- SurfaceUpdate\IclSerialIOSPI
|
||||
- SurfaceUpdate\IclSerialIOUART
|
||||
- SurfaceUpdate\SurfaceHidMini
|
||||
- SurfaceUpdate\SurfaceSerialHub
|
||||
- SurfaceUpdate\Itouch
|
||||
|
||||
|
||||
To support Surface Laptop 3 with Intel Processor, import the following folders:
|
||||
|
||||
- SurfaceUpdate\IclSerialIOGPIO
|
||||
- SurfaceUpdate\IclSerialIOI2C
|
||||
- SurfaceUpdate\IclSerialIOSPI
|
||||
- SurfaceUpdate\IclSerialIOUART
|
||||
- SurfaceUpdate\SurfaceHidMini
|
||||
- SurfaceUpdate\SurfaceSerialHub
|
||||
- SurfaceUpdate\SurfaceHotPlug
|
||||
- SurfaceUpdate\Itouch
|
||||
> [!NOTE]
|
||||
> Check the downloaded MSI package to determine the format and directory structure. The directory structure will start with either SurfacePlatformInstaller (older MSI files) or SurfaceUpdate (Newer MSI files) depending on when the MSI was released.
|
||||
|
||||
@ -119,7 +167,8 @@ To add the keyboard drivers to the selection profile, follow these steps:
|
||||
|
||||
9. Verify that you have configured the remaining Surface Laptop drivers by using either a selection profile or a **DriverGroup001** variable.
|
||||
- For Surface Laptop (1st Gen), the model is **Surface Laptop**. The remaining Surface Laptop drivers should reside in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop folder as shown in the figure that follows this list.
|
||||
- For Surface Laptop 2, the model is **Surface Laptop 2**. The remaining Surface Laptop drivers should reside in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop 2 folder.
|
||||
- For Surface Laptop 2, the model is **Surface Laptop 2**. The remaining Surface Laptop drivers should reside in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop 2 folder.
|
||||
- For Surface Laptop 3 with Intel processor, the model is Surface Laptop 3. The remaining Surface Laptop drivers are located in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop 3 folder.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -33,9 +33,6 @@ The primary concern when selecting an Ethernet adapter is how that adapter will
|
||||
|
||||
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://www.microsoft.com/surface/accessories/surface-dock) use a chipset that is compatible with the Surface firmware.
|
||||
|
||||
> [!NOTE]
|
||||
> PXE boot is not supported on Surface Pro X. For more information, refer to [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md)
|
||||
|
||||
The following Ethernet devices are supported for network boot with Surface devices:
|
||||
|
||||
- Surface USB-C to Ethernet and USB 3.0 Adapter
|
||||
|
||||
Reference in New Issue
Block a user