Next build AADS Terminal Server

(Updated 7 Mar 2021)

Improvement

• When joining an AADServer to a Windows Domain, the Domain Group "Domain Users" is added to the Local Group "Remote Desktop Users". This used to be done everytime AADS was installed or upgraded. Now it is done only once.
• When un-installing AADS, the Domain Group "Domain Users" is removed from the Local Group "Remote Desktop Users".

Bug fix

The "label" of the 2 menu-items is "swapped":

• The "white" button is for "Copy to Allow List". The "white" button incorrectly shows the label "Copy to Deny List".
• The "black" button is for "Copy to Deny List". The "black" button incorrectly shows the label "Copy to Allow List".

(not done yet...)

More Application Control

A new and different approach on Application Control is considered.

RDP Firewall

More Firewall rules and/or filters. For example:

• Filter on valid Client Names.
• Filter on allowed Client Names.

Own Explorer

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.

Improvement File transfer

Some kind of "smart resume" options, in case of a re-connected RDP sessions, between the same Client and Server.

More languages / translations

A separate project within AADS WorldWide has been started to translate the product to (many) more languages.

Chat functionality

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.