Training
Learning path
Configure networking on Windows clients - Training
MD-100 Configure networking on Windows clients
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
To do most things on your HoloLens, you have to be connected to a network. HoloLens contains a 802.11ac-capable, 2x2 Wi-Fi radio and connecting it to a network is similar to connecting a Windows 10 Desktop or Mobile device to a Wi-Fi network. This guide helps you to:
Read more about using HoloLens offline.
The first time you use your HoloLens, you'll be guided through connecting to a Wi-Fi network. If you have trouble connecting to Wi-Fi during setup, make sure that your network is either an open, password-protected network or a captive portal network. Also, confirm that the network doesn't require you to use a certificate to connect. After setup, you can connect to other types of Wi-Fi networks.
On HoloLens 2 devices, users may also use a USB-C to Ethernet adapter to connect directly to Wi-Fi to help setting up the device. Once the device is set up, users may continue to use the adapter, or they may disconnect the device from the adapter and connect to wi-fi after setup.
To confirm you're connected to a Wi-Fi network, check the Wi-Fi status in the Start menu:
Tip
If Wi-Fi is not available, you can also connect to Cellular and 5G networks.
Important
By design, users cannot fine-tune the Wi-Fi roaming behavior of the HoloLens 2. The only way to refresh the Wi-Fi list is to toggle the Wi-Fi Off and On. This prevents many issues, like where a device can remain "stuck" to an AP once it is out of range.
When connecting HoloLens 2 devices to a Wi-Fi network, use the following technical specifications to ensure good roaming between Wi-Fi terminals.
The Wi-Fi signal level directly affects roaming because throughput requirements vary by use case. Consider the following specifications when setting up Wi-Fi terminals.
Enterprise Wi-Fi profiles use Extensible Authentication Protocol (EAP) to authenticate Wi-Fi connections. The HoloLens Enterprise Wi-Fi profile can be configured through MDM or a provisioning package created by Windows Configuration Designer.
For a Microsoft Intune managed device, refer to Intune for configuration instructions.
To create a Wi-Fi provisioning package in WCD, a preconfigured Wi-Fi profile .xml file is required. Here's a sample Wi-Fi profile for WPA2-Enterprise with EAP-TLS authentication:
<?xml version="1.0"?>
<WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1">
<name>SampleEapTlsProfile</name>
<SSIDConfig>
<SSID>
<hex>53616d706c65</hex>
<name>Sample</name>
</SSID>
<nonBroadcast>true</nonBroadcast>
</SSIDConfig>
<connectionType>ESS</connectionType>
<connectionMode>auto</connectionMode>
<autoSwitch>false</autoSwitch>
<MSM>
<security>
<authEncryption>
<authentication>WPA2</authentication>
<encryption>AES</encryption>
<useOneX>true</useOneX>
<FIPSMode xmlns="http://www.microsoft.com/networking/WLAN/profile/v2">false</FIPSMode>
</authEncryption>
<PMKCacheMode>disabled</PMKCacheMode>
<OneX xmlns="http://www.microsoft.com/networking/OneX/v1">
<authMode>machine</authMode>
<EAPConfig>
<EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig">
<EapMethod>
<Type xmlns="http://www.microsoft.com/provisioning/EapCommon">13</Type>
<VendorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorId>
<VendorType xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorType>
<AuthorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</AuthorId>
</EapMethod>
<Config xmlns="http://www.microsoft.com/provisioning/EapHostConfig">
<Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1">
<Type>13</Type>
<EapType xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV1">
<CredentialsSource><CertificateStore><SimpleCertSelection>true</SimpleCertSelection>
</CertificateStore>
</CredentialsSource>
<ServerValidation>
<DisableUserPromptForServerValidation>false</DisableUserPromptForServerValidation>
<ServerNames></ServerNames>
<TrustedRootCA>00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13</TrustedRootCA>
</ServerValidation>
<DifferentUsername>false</DifferentUsername>
<PerformServerValidation xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2">true</PerformServerValidation>
<AcceptServerName xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2">false</AcceptServerName>
</EapType>
</Eap>
</Config>
</EapHostConfig>
</EAPConfig>
</OneX>
</security>
</MSM>
</WLANProfile>
Depending on the EAP type, a server root CA certificate and client certificate may have to be provisioned on the device.
Other resources:
Check our Troubleshooting page if you're having trouble connecting to your Wi-Fi.
This table lists IP protocols and TCP/UDP ports used by HoloLens 2 system services.
Port | Protocol | Application protocol | System service name |
---|---|---|---|
N/A | ICMP | ICMP (IP protocol 1) | TCP/IP |
N/A | IGMP | IGMP (IP protocol 2) | TCP/IP |
N/A | IPv6 | IPv6 Encapsulation | TCP/IP |
N/A | ESP | IPsec ESP (IP protocol 50) | Routing and Remote Access |
N/A | AH | IPsec AH (IP protocol 51) | Routing and Remote Access |
N/A | IPv6-ICMP | ICMP for IPv6 (IP protocol 58) | TCP/IP |
53 | UDP | DNS | DNS Client |
67 | UDP | DHCP | TCP/IP |
80 | TCP | HTTP | Apps & Services |
123 | UDP | SNTP | Windows Time |
443 | TCP | HTTPS | Apps & Services |
500 | UDP | IPSec IKE | Routing and Remote Access |
546 | UDP | DHCPv6 | TCP/IP |
1701 | UDP | L2TP | Routing and Remote Access |
1900 | UDP | SSDP | SSDP Discovery Service |
2869 | TCP | SSDP event notification | SSDP Discovery Service |
4500 | UDP | NAT-T | Routing and Remote Access |
5353 | UDP | mDNS | DNS Client |
5355 | UDP | LLMNR | DNS Client |
7236 | TCP | Mixed Reality Capture | MRC Service |
7236 | UDP | Mixed Reality Capture | MRC Service |
This section covers network proxy for HoloLens OS and Universal Windows Platform (UWP) Apps using Windows HTTP stack. Applications using non-Windows HTTP stack may have their own proxy configuration and handling.
There are three ways to provision proxies:
Settings UI:
MDM
PPKG
CSPs are behind many of the management tasks and policies for Windows 10, both in Microsoft Intune and in non-Microsoft MDM service providers. You can also use Windows Configuration Designer to create a provisioning package and apply it to the HoloLens 2. The most likely CSPs that will be applied to your HoloLens 2 are:
Other CSPs supported in HoloLens devices
A VPN connection can help provide a more secure connection and access to your company's network and the Internet. HoloLens 2 supports built-in VPN client and Universal Windows Platform (UWP) VPN plug-in.
Supported Built-in VPN protocols:
If certificate is used for authentication for built-in VPN client, the required client certificate needs to be added to user certificate store. To find if a 3rd party VPN plug-in supports HoloLens 2, go to Store to locate VPN app and check if HoloLens is listed as a supported device and in the System Requirement page the app supports ARM or ARM64 architecture. HoloLens only supports Universal Windows Platform applications for 3rd party VPN.
VPN can be managed by MDM via Settings/AllowVPN, and set via Vpnv2-csp policy.
Learn more about how to configure VPN with these guides.
VPN isn't enabled by default but can be enabled manually by opening Settings app and navigating to Network & Internet -> VPN.
Tip
In our Windows Holographic, version 20H2 we fixed a proxy configuration issue for VPN connection. Please consider upgrading devices to this build if you intend to use this flow.
Just follow the Intune documents to get started. When following these steps, keep in mind the built-in VPN protocols that HoloLens devices support.
Create VPN profiles to connect to VPN servers in Intune.
Windows 10 and Windows Holographic device settings to add VPN connections using Intune.
When done, remember to assign the profile.
3rd party VPN connection example:
<!-- Configure VPN Server Name or Address (PhoneNumber=) [Comma Separated]-->
<Add>
<CmdID>10001</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/PluginProfile/ServerUrlList</LocURI>
</Target>
<Data>selfhost.corp.contoso.com</Data>
</Item>
</Add>
<!-- Configure VPN Plugin AppX Package ID (ThirdPartyProfileInfo=) -->
<Add>
<CmdID>10002</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/PluginProfile/PluginPackageFamilyName</LocURI>
</Target>
<Data>TestVpnPluginApp-SL_8wekyb3d8bbwe</Data>
</Item>
</Add>
<!-- Configure Microsoft's Custom XML (ThirdPartyProfileInfo=) -->
<Add>
<CmdID>10003</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/PluginProfile/CustomConfiguration</LocURI>
</Target> <Data><pluginschema><ipAddress>auto</ipAddress><port>443</port><networksettings><routes><includev4><route><address>172.10.10.0</address><prefix>24</prefix></route></includev4></routes><namespaces><namespace><space>.vpnbackend.com</space><dnsservers><server>172.10.10.11</server></dnsservers></namespace></namespaces></networksettings></pluginschema></Data>
</Item>
</Add>
Native IKEv2 VPN example:
<Add>
<CmdID>10001</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/NativeProfile/Servers</LocURI>
</Target>
<Data>Selfhost.corp.contoso.com</Data>
</Item>
</Add>
<Add>
<CmdID>10002</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/NativeProfile/RoutingPolicyType</LocURI>
</Target>
<Data>ForceTunnel</Data>
</Item>
</Add>
<!-- Configure VPN Protocol Type (L2tp, Pptp, Ikev2) -->
<Add>
<CmdID>10003</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/NativeProfile/NativeProtocolType</LocURI>
</Target>
<Data>Ikev2</Data>
</Item>
</Add>
<!-- Configure VPN User Method (Mschapv2, Eap) -->
<Add>
<CmdID>10004</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/NativeProfile/Authentication/UserMethod</LocURI>
</Target>
<Data>Eap</Data>
</Item>
</Add>
<Add>
<CmdID>10004</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/NativeProfile/Authentication/Eap/Configuration</LocURI>
</Target>
<Data>EAP_configuration_xml_content</Data>
</Item>
</Add>
Open the Start menu.
Select the Settings app from Start or from the All Apps list on the right of the Start menu. The Settings app will be auto-placed in front of you.
Select Network & Internet.
Select the Wi-Fi slider switch to move it to the Off position. This will turn off the RF components of the Wi-Fi radio and disable all Wi-Fi functionality on HoloLens.
Warning
When the Wi-Fi radio is disabled, HoloLens will not be able to automatically load your spaces.
Move the slider switch to the On position to turn on the Wi-Fi radio and restore Wi-Fi functionality on Microsoft HoloLens. The selected Wi-Fi radio state (On or Off) will persist across reboots.
Open the Start menu.
Select the Settings app from Start or from the All Apps list on the right of the Start menu. The Settings app will be auto-placed in front of you.
Select Network & Internet.
Scroll down to beneath the list of available Wi-Fi networks and select Hardware properties.
The IP address appears next to IPv4 address.
Depending on your devices build you can either use built in voice commands or Cortana to display your IP address. On builds after 19041.1103 speak "What's my IP address?" and it will be displayed. For earlier builds or HoloLens (1st gen) say "Hey Cortana, What's my IP address?" and Cortana will display and read out your IP address.
Training
Learning path
Configure networking on Windows clients - Training
MD-100 Configure networking on Windows clients
Documentation
Connect to Bluetooth and USB-C devices
Get started connecting to Bluetooth and USB-C devices and accessories from your HoloLens mixed reality devices.
Find and save files on HoloLens
Learn how to use File Explorer on HoloLens to open, view, and manage files on your mixed reality device.
Capture, record, and share mixed reality photos and videos
Learn how to capture, record, and view, and mixed reality photos and videos using HoloLens mixed reality devices. Learn how to share via Miracast or gathered files.