The Administrator can open a DosBox, using the command Set, and see all the Environment Variables that do exist.
Those Environment Variables can be used while defining Applications for the Users.
The Benefit of this can be that a Backup/Restore of AADS Application Control Settings is more usable. When restoring an AADS Backup to a different Server, to a new Server, with a different Windows version, by using Environment Variables the defined Applications in Application Control are usable and OK on this other Server.
AADS Maintenance Control now has a new button that opens the Control Panel, containing direct links to "everything" that can be set on Windows.
Note: this "everything" view of the Control Panel is available on Windows Vista and higher. It is unfortunately not available on Windows XP and Server 2003.
Many small performance improvements are applied due to smarter coding.
AADS has its own userinit program because of security and AADS Application Control. Unfortunately some viruses, trojan horses or other malicious software do "abuse" the userinit.exe setting,
and because of that, some anti-virus software are strict and rigid when it comes to userinit.exe setting
AADS has now more built-in functions to handle situations where some anti-virus software does disable our userinit program.
However, if anti-virus software really, really, really does not want AADS to utilize userinit-settings, then it still might happen that the AADServer becomes unusable because the anti-virus software removes the AADS userinit module and reverts Windows back to single user, single logon.
Our main License Term, and business, is
The implication of this, is that when the server changes, the installed AADS license becomes invalid. Changes in the server can happen more easily when Virtualization is being used.
When this situation does happen, a specific popup message is shown:
When this message is shown, re-install AADS. AADS Setup will bound the AADS License to the new server.
When re-installing AADS fails because of "Administrative Reasons ":
a License Reset is required.
Occasionally it might be required that a so called FQDN (Fully Qualified Domain Name) is entered as a name for the AADServer when it sends the Notifications:
Wether or not a FQDN is required, is not an AADS-issue. It depends on the mailserver. In the example above, the mailserver is "mail.bigcompany.com". The Administrator of this mailserver will tell you if a FQDN for this AADServer is required, and what the FQDN should be.
The built-in WWW-server did not always show the html-error pages. This is now fixed.
AADS Application Control gives the user a limited desktop and menu: only the Applications the user needs.
Now it is possible to place this Limited Menu in each of the 4 corners of the screen:
The Limited Menu is placed "Top Right" on the desktop of the user:
It is possible to show the AADS Limited Menu in either 1 or 2 columns. Example 2 columns:
The AADS Limited Menu is shown "Bottom Left" with "2" columns. The result is as follows:
Configuring the AADS Limited Menu for 1 column:
The result is as follows:
The Performance settings of AADS Client for Windows, OSX and Linux are updated.
A new settings is the ability to enable "Font Smoothing":
Implemented a fix / improvement in AADS Client for Linux / OSX. This was needed in case rdesktop 1.8.x is being used.
Upgrade SSL modules to OpenSSL 1.0.2g.
Note: the AADS client on Linux and OSX uses the OpenSSL libraries as included in Linux and OSX.
© 2012-2022 AADS WorldWide. Terminal Server | Application Server | Remote Desktop solutions | Firewall