I saw this issue in 4.05 MAS 200 when trying to run the both TS and Application server on the same box. The final solution was have the Terminal Server (RDS now) as a separate box and left the Application Server to itself. If someone locked up their TS session, it didn't cause the entire installation to halt since they weren't running directly on the server. Granted that was over a decade ago, but I think Sage recommends both to be separate machines anyway. Hope that helps!

I saw this issue in 4.05 MAS 200 when trying to run the both TS and Application server on the same box. The final solution was have the Terminal Server (RDS now) as a separate box and left the Application Server to itself. If someone locked up their TS session, it didn't cause the entire installation to halt since they weren't running directly on the server. Granted that was over a decade ago, but I think Sage recommends both to be separate machines anyway. Hope that helps!

SOP when deploying TS.