mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
Merge branch 'public' into repo_sync_working_branch
This commit is contained in:
Tina Burden
GitHub
@ -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.
|
||||
|
||||
|
||||
@ -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,11 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Use HoloLens offline
|
||||
|
||||
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 +33,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/* | | | |
|
||||
| | 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 | | | |
|
||||
| | 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 | | | |
|
||||
| | 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
|
||||
|
||||
|
||||
@ -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).
|
||||
|
||||
|
||||
@ -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