Forum Discussion
PaulKlerkx
Jun 03, 2021Iron Contributor
Desktop Analytics - Internet Access Requirements
Hi, we have configured Desktop Analytics and connection health has the majority of devices as properly enrolled, however we have around 130 with a configuration alert of "Can't connect to the Con...
Nathan Blasac
Jun 18, 2021Iron Contributor
Sounds good Paul cheers.
PaulKlerkx
Jul 21, 2021Iron Contributor
We have the firewall rules in now and it made no difference to the devices with the message. "Can't connect to the Connected User Experience and Telemetry endpoint (Vortex). Check your network/proxy settings"
After inputting the firewall rules however, around 20 devices that were in a state of "Awaiting enrolment" for the past couple of months suddenly were configured correctly so it "may" have helped there.
We tested the alternate theory of assigning an E3 license to one of the devices temporarily and this resolved the issue overnight.
Findings
"Can't connect to the Connected User Experience and Telemetry endpoint (Vortex). Check your network/proxy settings" in our case had nothing to do with network or proxy config, for us it meant the user of the device hasn't been issued an E3/E5 license. (as per licensing costs on this page - https://docs.microsoft.com/en-us/mem/configmgr/desktop-analytics/overview ) opportunity for MS to improve DA there, a message indicating the lack of an appropriate license might be better than the current message.
Rather than spending an extra $15k per year on licensing these consoles to get them registered in DA (about 8% of our fleet), I'll just export them to a collection and do a report of software to analyse manually. As they are only consoles, I doubt they'll have much past our base soe anyway.
thanks for your input.