Two members discussed the driving use cases for choosing ControlUp Edge DX, including Corp laptop having VPN connectivity issues, seeing network latency/connectivity/ISP, and providing admin-level support to users’ machines even when not connected to a VPN. Edge DX is designed for FatClients, providing detailed information without needing to be connected to VMs. RemoteDX can also be installed but is solely for showing information while connected to Win365, XenDesktop or Horizon.
Read the entire ‘Driving Use Cases for Choosing Edge DX’ thread below:
General question for the community, what were the driving use cases that made you choose Edge DX?
Corp laptop having vpn connectivity issues and not having any issues when plugged in to the corp LAN. With Edge DX we could see 70% wifi signal and high LAN and WAN latency on the users home network.
@member that is a great use case.
Of course it’s still my problem since the user pays for the top tier ISP.
Thanks for the question Rodger and reply Brian.
Currently evaluating EdgeDX. Looking for direct comparison between FatClient vs, Win365, vs. XenDesktop on prem.
Still not sure, if it is a valid use case to install the agent as well on a remote desktop. Would really like to see the difference between FatClient and ThinClient connected to remote Windows.@member Sorry for the late reply. Edge DX is designed for the FatClient, the actual endpoint, your laptop, desktop, thinClient. This will give you detailed information about those machines that you use to connect into your Win365, Horizon or XenDesktop VMs. And to be clear, with Edge DX you DO NOT have to be connected to VMs. It is 100% standalone. RemoteDX also can go on those FatClients but it is used ONLY to show information while connected to Win365 or XenDesktop or Horizon.
I wanted something that would allow us to provide admin-level support to users’ machines even if not connected to the corp VPN. Our previous solution needed the VPN to be up to work.
I also wanted something that could do alerting and reporting on those machines, similar to what we have for servers, but that was tailored to endpoints that can legitimately be offline (people turn their laptops off!).
The session history is nice, as is seeing network latency/connectivity/ISP.
Continue reading and comment on the thread ‘Driving Use Cases for Choosing ControlUp Edge DX’. Not a member? Join Here!
Categories: All Archives, ControlUp Edge DX, ControlUp Scripts & Triggers