Hey,
I constantly have to remind staff to logout of SIMS when I run updates. Is there a way to log all staff out at once?
Thanks for your help!
Printable View
Hey,
I constantly have to remind staff to logout of SIMS when I run updates. Is there a way to log all staff out at once?
Thanks for your help!
If you:
Click on Start > Computer > Manage > Shared Folders > Sessions
End All The Sessions In There
*Server 2003
Not Sure where they have moved it to in 2008.
James.
Sometimes ending the sessions doesn't work & they reconnect. I always reboot the SIMS server :)
I always put the Server into Single User Mode before running a SIMS Upgrade!
From SupportNet see:- KB88695 - How to force Users out of Sims.net
Thanks for all your suggestions, it would be useful if Capita released an upgrade that included a 'force logout' option though!
At one point im sure they did but no longer, probably something to do with data integrity. I use the single user mode too.
To be fair i do all my patches/upgrades outside of working hours now.
This is from supportnet - KB88695 - It stops poeple connecting to the sims server... except the server itself :D (I have the sims client installed on the server to test with)
How to force Users out of Sims.net KB88695
THIS SOLUTION CANNOT BE USED FOR HOSTED SQL INSTANCES
The following workaround will terminate any current connections to the SIMS SQL Instance, and if users are actually using SIMS .net, this will force them out.
Any unsaved changes will be lost.
Please set the Surface Area Configuration of the SIMS SQL Server to Local Connections Only.
This means that only applications that use the SIMS SQL instance on the Server, itself, will be able to connect.
This will stop the user refresh from logging into the database when trying to upgrade, and allow SOLUS, DBupgrade, and DBAttach to complete successfully.
To re-configure this, please do the following:
Click Start
All Programs
Microsoft SQL Server 2005
Configuration Tools
SQL Server Surface Area Configuration
Click Surface Area Configuration for Services and Connections
From the instance list, please click Remote Connections under the Database Engine for the correct instance (ie SIMS2005)
Click Local Connections Only (The 1st radio button)
Click Apply
Click OK to the message
Click the Service
Click Stop, Click Start
This will stop the Users from connecting to the Server outside of the actual box
Run the specified application as required
When complete, please do the following
Click Start
All Programs
Microsoft SQL Server 2005
Configuration Tools
SQL Server Surface Area Configuration
Click Surface Area Configuration for Services and Connections
From the instance list, please click Remote Connections under the Database Engine for the correct instance
Click Local and remote connections
Click Using both TCP/IP and named pipes
Click Apply
Click OK to the message
Click the Service
Click Stop, Click Start
Now I wonder where I saw that KB before ....................... :D
lol!! :D
I dont know what your on about... its all from my expert knowledge of SIMS... Hoooooooonest :p
Look at one of my previous posts above! ;)
DOH!! :D
*makes note to read whole thread*
I just copied it from our internal faq page as its one I dont want to have to dig around for :D
Hey.......
I've done that many a time! Usually on SupportNet tho' - not 'ere! :D
With so many people going in and editing data, writing reports, using finance (!) i'm hesitant unless it's a last resort.
Personally, i go to this section and remove permissions to the shared drive. Assuming all your users redirect their connect.ini to the shared drive, by removing permissions new people will not be able to log on. This doesn't remove existing users, but, is a nice way to stop people inadvertently logging in.
Solus has an info page that tells you who is left logged into the database though i've never trusted the list, i also have a script that i got from a different thread in this forum that shows logged in users. I use this info to contact the relevant people and make sure they are out. Once out, they can't go back in without access to the shared drive.
After this, i would use the single user mode option. It's a pain, but usually, there are only 4/5 culprits. I publicise a time slightly earlier than i want to start, i remove permissions, email staff, then start, it's usually clear.
These sorts of problems can only get worse, as the usage of SIMS grows and you have remote users logging in, including parents via SLG or other applications . . .
Doing upgrades at the weekend is bad enough without having to consider remote users in different timezones. ARGH! :eek::eek: