This is not really a AADS Terminal Server issue. It is a generic Microsoft Domain related issue, and needs to be fixed at the domain controller.
Cause of this issue can be that the "specifications" of the AADS Terminal Server are different then before. For example:
then the domain server does notice a "different" PC then before and therefore does not accept or does not "trust" the PC anymore.
After the Reboot:
On the Domain Controller this AADServer was "deleted". Now it will be "added" again in the Domain, "fresh en new" as if it has never been seen before on the Domain.
Copyright 2012-2017 AADS WorldWide LTD. AADS Terminal Server | Application Server | Remote Desktop solutions | Firewall