10 Mar 2017: Changelog AADS Terminal Server for Windows 10 (Build 135.10)
|
|
|
|
|
Windows 10 is for the most of it "the same" as it predecessors, except for the StartMenu and this new type of UWP-App (Universal Windows Platform). Due to this, the StartMenu of Windows 10 is a bit slow, and we intend to improve and change this, such that Windows 10 becomes better suitable for its AADS functions: a Terminal Server for Windows.
A simple Wizard will be available for a default configuration of Windows that does offer better performance for a Terminal Server:
There is some (or a lot of...) trouble related Windows 10, updates, reboots, and the impact on other software like AADS. Due to the updates and (unexpected) reboots, it does happen that AADS settings are removed and AADS needs to be re-installed.
We have done a lot of testing and a lot of extra logic is now implemented in AADS, such that it will survive Windows Updates and reboots. Please note: Microsoft does not document the details of Windows Update. There is no proper "pre-information" about the next Windows Update and the impact it will have. If Microsoft comes with a fresh, new, never-done-before way of updating Windows, it might again happen that there is some impact on third party software like AADS. However, if Microsoft keeps on doing updates and reboots in Window 10 as they have done in the past year, we do expect that AADS will survive the updates and reboots, and continue to work OK.
It will be possible to define Application-Sets and assign 1 or more Sets to users and groups:
Updates and changes in the RDP Firewall were not correctly send across the Farm. This is fixed.
|
© 2012-2024 AADS WorldWide. Terminal Server | Application Server | Remote Desktop solutions | Firewall |
|
|
|