Suspending server and no time near from recovery

We need a resolution on what user can understand and what user can do in regard to this case when server is suspended because of no-soon-to-recover issues. Because many desktops will still be using it.

  1. Now as far as I can see, there seems to be issue here. When ca3 suspended, it is pointing to ca1. This ended up 401 Unauthorized response from TPAPI. Need a understanding about what happened? And I think it should respond 503. Service not available

  2. Suspending is not always “not accessible” or “not recoverable”. But when it is, what shall we do with the existing desktops and what do we say to the user?

@bszlachta @xiongpeng @Julian_Robbins @mhussain