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

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.

That would be extremely helpful for us as well.

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

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