The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Hololens in Enterprise Network
We will deploy a Hololens experience in an enterprise setting. The device will be connected to a WPA2-Enterprise Network (Username & Password) and will be behind a restrictive Firewall and UDP Traffic is mostly blocked. We can connect to the network without a problem (on the Hololens) and internet access over 80/443 seems to work fine.
In the Hololens documentation it states that it needs internet access for positioning of holograms but I could not find any information regarding what kind of ports and protocols are involved and are needed for the Hololens to work correctly. What requirements are there? Do we need anything special on the Network side to make sure it all works as it should?
We seem to have an issue where the Hololens can't determine in which space it currently is. We never had this issue before on other networks but are not entirely sure if it is related to the network. It will show an error to select the space on the start menu and also ask to select one. If the network configuration is the cause of this it would be great to find out what the issue is.