I can't think of a way to do exactly what you are asking.  But as a best practice, we generally suggest that a) you schedule the upgrade/maintenance work for off hours (assuming people don't use the app 24/7), and b) that you have a backup image of the machine so that you can quickly restore back to previous state if any issues with the upgrade/maintenance work.

Hi Andrew;

   Unfortunately, not at this time.

   I know what you are talking about though .. normally, App servers have something like a "Quiesce" command that tells the server to stop new sessions but allow existing ones to complete. We saw this feature in Sybase's EAServer product.

  Please submit a Support Ticket for this as a PowerServer enhancement request. In the mean-time, I would suggest using a "scheduled" outage approach for now and then just vary the URL offline in IIS.

Regards ... Chris

I think this is for you as the application developer to setup and handle and has nothing to do with powerserver.

You built a logon screen, as part of that process you should have whether or not the user is allowed to log in.  This is fairly simple regardless of the log in screen.  Whether you have that part of it setup as a non PS website, or as part of your PS app, simply have it check as to whether a user is allowed to login.

during our logon process, we have two validations in addition to the standard un/pwd: 1 whether any user is allowed to logon and 2 if we have a message that will display.  When we have a situation when we want to disallow new logons, we enter a message to display (application unavailable due to scheduled work) and then end the application. 

Hi Andrew,

some databases have logon triggers so a config table in database may have a row like:

• Key = MyApp.LogonAction
• UserGroup = ALL
• Value = DENY

I have worked in such environment at several different companies.

HTH /Michael