We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
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.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. 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. And always feel free to hit us up on Twitter @MxdRealityDev.
Why can't I deploy my solution to one of the two HoloLens headsets I have through Wi-Fi?
I'm a university intern, and have two HoloLens headsets within a company that I should not explain what we are.. On an unsecured Wi-Fi network, one of them can have the apps be deployed by Remote Machine on that network or by Device mode through Visual Studio 2017. The other one, though, can only have a solution be deployed to it by Device mode.
I don't understand why I can only deploy my compiled solution to one of them rather than the both of them. On the Wi-Fi Properties group in the Advanced Settings pane, both of them say the Wi-Fi type is 802.11ac.
Are there any files or settings on the Windows Device Portal that would restrict one HoloLens from downloading a solution I'm trying to deploy? This is something me and my partners have been trying to figure out for the past three months.
Our first impression is that our Wi-Fi network may be too slow, but if that's the case, then it would not be possible to deploy the solution to one of them. It doesn't make sense with the evidence we have. Another impression is that there's something wrong with the Wi-Fi dongle that's in the troubled HoloLens, but if that's the case, it would not be connected to the network at all. And now, my impression is that there's something in the connection settings that's restricting it from loading the app being deployed through Wi-Fi.
I don't know if resetting the HoloLens to factory settings is going to solve the problem.