@skunk - it is a cushy little number though isn't it? .
With regards the solution, i'm sure it's widely known, but since the thread has been awakened:
I'm pretty sure that unless you kill the clients, rebooting the server wont break the connection. The client will just stall, and keep trying to connect, once SIMS is open, the homepages keep trying to make a link to the server, and sims doesn't even need the connect.ini any more, that's just first time use. So when the server is live again, they will connect and maintain a connection.
I once tried a reboot and went into single user mode, but the first client that connects, takes over the connection. It was a pain to even go back out of single user mode! Stipulating only local logons is the better way to do it.
I use an SQL script, and there are many around, which will show you who is logged in and where. My users are aware that they cannot access SIMS after midnight on any night and forewarned of update times when i'm actually going to do an upgrade. After that, i can run the script and just remote reboot the workstation to kill the connection. There are a number of similar scripts around, and also somewhere, someone shared an app, that you can program to kill certain processes after an idle time. Can't think what it was called, looked quite good.
Just need to replace the DB names on penultimate line to match user systems.
select distinct sysprocesses.loginame,
/* sysprocesses.spid, */
/* sysprocesses.nt_username, */
/* sysprocesses.login_time, */
join sysdatabases on sysprocesses.dbid = sysdatabases.dbid
where sysdatabases.name = 'sims' OR sysdatabases.name = 'fms'
order by sysdatabases.name, sysprocesses.loginame