Edge DX and geolocation issues were discussed; Windows Location Services is used and if not enabled the ISP is looked up, followed by a default centre in Wichita. An article was suggested for further info – https://support.controlup.com/docs/device-geolocation.
Read the entire ‘Understanding Edge DX Geolocation’ thread below:
What’s the deal with Edge DX and geolocation? I have two devices in the same building in Connecticut with the same External IP. One shows location as New Hampshire and one is in Central Pennsylvania.
Make sure location services is enabled on both.
It uses Windows Location Services first. If its not enabled it uses the ISP, if it can’t detect the ISP you wind up in Whichita.
Is that a setting on the device or in Solve\Edge DX console?
thx. I’ll give that a try
still showing central PA. I’ll look more in to this tomorrow. We are an ISP to 100+ clients and we have 20 in Edge DX and they are all over the place:
I take that back, Not all of these use us as an ISP.
Well its supposed to use location services, ISP lookup of the public IP, then center of the US (whichita).
I changed ISPs and my location for 1/2 my machines (linux boxes mostly) moved about 20 miles apart from one city I don’t live in to another I don’t live in. The Windows boxes with location services are pretty much spot on.
When I moved last year it took quite some time for Windows to catch up. Not sure how reliable their update mechanism is. But we just show what the OS tells us and if it doesn’t we fall back to IP based (ISP) geo location as Landon mentioned
Hey @member take a look at this article for more info about Edge location data – https://support.controlup.com/docs/device-geolocation
Continue reading and comment on the thread ‘Understanding ControlUp Edge DX Geolocation’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops, ControlUp for VDI