(Updated 23 Apr 2020)
Initially AADS Client shows the Authorization details in a "read only" modus, such to avoid that accidentally the Authorization details are changed.
When clicking on the small "edit button", next to "Username", it becomes possible for the user to enter and change the Authorization details:
Note: when AADS Client is started, and initially there is no "Username" or "Host", for example because it is the very first time AADS Client is started, then AADS Client does not start in "read only" mode; AADS Client immediately allows for the user to enter the Authorization details:
In this case the user needs to be able to enter the Authorization details.
Windows 10 / Server 2016 / 2019 is still ambiguous when it comes to settings. Most settings are done by "Settings" with the UWP user interface. However, often it will be required or desirable to do settings using the "classic" Control Panel user interface.
About the "classic" Control Panel user interface:
Whenever technically possible, AADServer offers an Application for Control Panel settings when using Windows 10 / Server 2016 / 2019:
The Group Policy "Do Not delete temp folders upon exit" was never applied. This is fixed.
More Firewall rules and/or filters. For example:
We are considering to deliver our own, simple "Explorer" as a replacement for the Windows Explorer. It will offer the user a desktop experience similar to what is known since Windows XP. The Administrator has the ability to limit the functionality as available to the user. It will not contain an AppStore. It can be used for running the usual Desktop Applications.
Some kind of alternative to Search for files and folders. Since Windows 10, Search does (too...) often not work anymore, because Search is now done with Cortana, and integrated / connected somehow to Bing. Our alternative will be less complicated: search for files, folders, maybe within the Start Menu. A search local on the local server. No integration with Cortana, Bing or the internet in general.
Some kind of "smart resume" options, in case of a re-connected RDP sessions, between the same Client and Server.
A separate project within AADS WorldWide has been started to translate the product to (many) more languages.
We are considering to deliver a Chat functionality that runs on our RDP+ protocol. The Chat function we have in mind, runs by the AADServer, and by doing so, whatever is being chatted by the employees, stays within the your own company, your own AADServer. Nothing is shared with WeChat, WhatsApp, Telegram, Google, Facebook, Microsoft, AADS WorldWide LTD, etc, etc.
Copyright 2012-2020 AADS WorldWide LTD. AADS Terminal Server | Application Server | Remote Desktop solutions | Firewall