ARD for me is based on a LAN, but can be used over WAN via VPN, but the latency makes ARD a less ideal tool. There are other cross platform tools that can do what ARD does which to me add value when managing a mixed environment
Remote Desktop Services provides access to work environments from any device. This allows us to ensure business continuity in case of disaster. It provides admins more control over access and security. Remote Desktop Services simplifies software updates and compliance management by reducing the need to act on end users devices.
Relative ease of setup: in comparison to some of the other solutions on the market (Citrix, etc.), Remote Desktop Services is rather easy to set up and get configured in your environment.
Feature set: Microsoft offers a good deal of the same features many competitors offer in the same space including a mobile app and the ability to have a "native" app feel for a remote application.
Inexpensive Licensing: in comparison to other solutions on the market Remote Desktop Services is inexpensive.
Move LOB applications closer to their server counterparts: this goes for all remote solutions, but if you have a line of business application that makes a great deal of calls across the network to your data center, your remote office users will likely benefit from the performance and stability side by moving those client side applications into the data center.
It is a fairly unique tool in the level of integration it has with Apple Desktop products. It definitely needs some engineering attention, and it should be expanded to the iOS arena. It is not perfect, but it is very useful and fills an otherwise fairly empty niche in the support toolkit realm. The built-in screen sharing app in macOS handles the direct screen control or viewing function fairly well, but it does not have all of the other mass control features that Apple Remote Desktop supplies.
Once it is set up, it is quite straightforward to use. However, currently, it requires both a script to run to set up permissions and controls, AND a command from the MDM to authorize it to be active. The MDM management command is manual. This is not conducive to an automated workflow, and sometimes gets forgotten. Then, the endpoint is not contactable until someone realizes that the MDM command was not sent or was not successful.
Once set up it works well and is extremely easy for users. Getting it right can be difficult, it is easy to setup insecurely. Maintenance can be difficult with only a single broker and with manual switchover required for redundant gateways. Troubleshooting access issues can also be difficult
As with any Microsoft Server product, support for Remote Desktop Services requires a paid support package. These are license-based and very costly, on top of the already costly product licensing. Microsoft's licensing is complicated to begin with, so setting up licensing alone essentially requires a licensing expert's counsel. There is community documentation and support available on Microsoft websites, as well as community websites.
I would feel much more comfortable having one of these alternative solutions as our Remote Desktop management tools. Each has their drawbacks and expenses associated with them, but we simply have too large of a deployment to not be considering alternatives. If it is the only solution you can afford, it is OK to start here. I could see where this would have a return on investment, but it is really only suitable for a very small and localized scale. If employees are at all mobile, the duct taping of products necessary (VPN, distribution points, script repositories) would be very cumbersome.
We used RDS on-site primarily because of how easy it is for users to transition from their own desktop to a remote desktop. However, from off-site, there are VPN and other security considerations to take into account, and the process gets a little more complex. In this situation, especially if you're trying to support a user who is outside the local network, it can be easier to use something like Chrome Remote Desktop or TeamViewer. However, the Windows functionality of RDS is totally unmatched.
Apple Remote Desktop has a positive return on investment because for the expense to the school, the value it brings to teachers is important. The return on improved student performance is very difficult to measure financially, but there is a definite return.
The overall objective of education is to increase student learning, ARD does that phenomenally. Parents see the tool used and are impressed at what the capabilities of the tool can do and how it impacts how active their students are as well as how well they can learn.
One negative impact is that teachers rely too much on this tool rather than on actually teaching sometimes.
Remote Desktop Services has had a major positive ROI impact at our firm. There were a number of times when our staff was traveling abroad to business meetings with a laptop that had missing presentations. But once they had internet access, a Remote Desktop Services connection is established, and presentation data can now be shown directly from their laptops as if theyr'e sitting in our office.
Remote Desktop Services has made it possible for Mac staff users to use their computing devices to access our network system to run Windows applications and access all our network data.
Remote Desktop Services has made it possible for our staff to successfully work remotely from outside the office. There were many occasions when emergencies came up which prevented staff from coming into the office to work. But as long as they have a computer with an internet connection, they used Remote Desktop Services to connect to our terminal server and successfully ran the programs to modify data files on the network without losing a beat.
