ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Suggestions for Updates >> Lock Out Button for Updates/ETC.
http://www.istechforum.com/YaBB.pl?num=1135180059

Message started by Lenette on 12/21/05 at 07:47:39

Title: Lock Out Button for Updates/ETC.
Post by Lenette on 12/21/05 at 07:47:39

It would be nice if you had a feature that would prevent people from loggin into DBA while running updates, utilities, etc. After all you have pop ups that say you can't do stuff because people are logged in... what about YOU CAN LOGIN NOW...

Title: Re: Lock Out Button for Updates/ETC.
Post by JNAPIER on 12/21/05 at 08:37:22

Most definitly.......................... I wonder if it will be easier now with InstallShield being used?

John

Title: Re: Lock Out Button for Updates/ETC.
Post by Vman on 12/21/05 at 08:37:30

And/or maybe methods in place that if you start a routine that everyone but you has to be logged out (and are at the start), that they can't log in until the routine ends. (Not sure if this is implemented some places now). Maybe way to query how many users are logged in from within DBA/EVO.
Or maybe an administrator-type setting where individual users can be temorarily locked out when you are updating, with a message at the start up telling the user that.

(Shouldn't have had that second cup of tea with all that sugar.)

Title: Re: Lock Out Button for Updates/ETC.
Post by Cic on 03/11/06 at 06:08:47

This would definitely be a nice feature. By the time we go around to get everyone out, someone comes in and goes on and we have to get them out.

Title: Re: Lock Out Button for Updates/ETC.
Post by wildco on 03/13/06 at 12:44:47

I agree, this would be a nice feature.

Title: Re: Lock Out Button for Updates/ETC.
Post by tcook on 03/16/06 at 08:02:50

That would be extremely helpful for us as well.

Title: Re: Lock Out Button for Updates/ETC.
Post by awaretec on 03/21/06 at 12:21:13

How about this:

The sys admin sends a notification to users with DBA open stating, "System will be going down for maintenance in x minutes." After the allotted time, everyone is forced out and not able to get back in until sys admin enables client logins.

On a related note, notify/force idle users off after x minutes would be very helpful to those of us with limited seats. Additionally, this would help to ensure everyone is out after hours so we can get complete backups.

Title: Re: Lock Out Button for Updates/ETC.
Post by timgolds on 03/22/06 at 11:05:32

awaretec,

The logout on idle or at a specific time is a good idea but flawed.

1. server logout does not close the pipe to pervasive on the server. you will have to wait for it to time out.

2. when the forced logout is issued, dba and EVO go balistic because it can't file the btrive engine. the user gets to hit the OK button about 20 times on errors before they can exit. and DBA will require a workstation reboot.

3. if your time server freaks out, users can be logged outin the middle of the day and lose work. (Had this happen with NIST was hit with a virus and their NTP servers had to do a date roll through.

Just some points. Hope it helps,

Tim

Title: Re: Lock Out Button for Updates/ETC.
Post by Vman on 03/30/06 at 13:13:26

Also,

If a user is running a long process and gets forced out midstream, a bunch of data can get corrupted. I agree that some sort of message capability at login notifying users of scheduled maintenance would be nice. Once everyone is logged out, then you can lock the system down until the updates/maintenance is done.

Title: Re: Lock Out Button for Updates/ETC.
Post by timgolds on 03/31/06 at 08:53:02

I guess you could remove your pervasive licenses so only one exists, logon and do the update then replace the licenses.

That would only allow one user to use the system for updates.

Not that I would suggest this idea but it might spark something in someone else!

Personally, I do all updates after hours. Before I update, I disable VPN cababilites so no one gets on remotely.

I also have a stand alone server for testing installation and functionality before I install into production.

Hope it helps,

Tim