+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 16
MIS Systems Thread, Kicking People Out Of SIMS? in Technical; Morning Guys, What's the best way for kicking people out of SIMS and making sure no one is conected to ...
  1. #1
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    610
    Thank Post
    102
    Thanked 42 Times in 40 Posts
    Rep Power
    19

    Kicking People Out Of SIMS?

    Morning Guys,

    What's the best way for kicking people out of SIMS and making sure no one is conected to the database when it comes to running patches and upgrades?

  2. #2

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,374
    Thank Post
    906
    Thanked 1,811 Times in 1,559 Posts
    Blog Entries
    12
    Rep Power
    468
    Not done it in ages. I used to rename the connect.ini. Then stop SQL wait a while then start it again. rename connect.ini back to they can use SIMS again.
    Last edited by FN-GM; 17th May 2013 at 01:08 PM.

  3. #3

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    7,231
    Thank Post
    1,446
    Thanked 1,859 Times in 1,252 Posts
    Blog Entries
    22
    Rep Power
    559
    I stop TCP/IP and named pipes connections to the db and restart sql, do the upgrade, then re-enable.

  4. #4

    Join Date
    Oct 2007
    Location
    Northamptonshire
    Posts
    315
    Thank Post
    22
    Thanked 83 Times in 70 Posts
    Rep Power
    45
    You can also run the sp_who2 command in SQL Management Studio to see who is still connected.

  5. #5
    Ghostgame's Avatar
    Join Date
    Jun 2012
    Location
    Ipswich
    Posts
    297
    Thank Post
    36
    Thanked 68 Times in 40 Posts
    Rep Power
    34
    2 ways which I have come across is:

    -stop the SQL service and only start it up when you want to apply the patch/upgrade/etc.

    -disconnect the network cable to the server so no-one on the network can get on it (might not be a good idea if your internet connection goes through it first)

  6. #6

    broc's Avatar
    Join Date
    Jan 2006
    Location
    England
    Posts
    2,046
    Thank Post
    104
    Thanked 401 Times in 265 Posts
    Rep Power
    151
    I have been known to reboot the SIMS Server VM......

  7. #7
    mcrompton01's Avatar
    Join Date
    May 2006
    Location
    Burntwood
    Posts
    44
    Thank Post
    1
    Thanked 10 Times in 7 Posts
    Rep Power
    19
    We give people 48hrs notice of downtime/patches being applied (if possible) and tell them to out of sims. If the the patch has to be applied during the day we:

    1. Check SQL Management Studio to find who is logged in
    2. Rename the connect.ini to prevent new connections
    3. At the given update time we run shutdown -i and add all the computers listed above (step one) and shut them down
    4. Wait for all connections in SQL Management studio to disappear
    5. Start the upgrade

    I've even shutdown down senior leaders computers before as they know the time, they have had plenty of warning. Works well here and you'd be surprised to hear not people leave themselves logged in to sims on patch or update day.

  8. 2 Thanks to mcrompton01:

    Jamman960 (17th May 2013), vikpaw (18th May 2013)

  9. #8
    skunk's Avatar
    Join Date
    Mar 2006
    Location
    North West
    Posts
    311
    Thank Post
    88
    Thanked 40 Times in 33 Posts
    Rep Power
    30
    Give a time they have to out by and then kill the pulsar.exe process on all machines on the network at that time. Can be done via pskill or we use Impero.

  10. #9

    Join Date
    Jan 2007
    Posts
    101
    Thank Post
    0
    Thanked 35 Times in 24 Posts
    Rep Power
    22
    Easiest is to stop TCP/IP and(/or) named pipes connections to SIMS and restart SQL service.
    This will still allow you to test upgrades and patches in SIMS on the server before releasing back to users.

    If any users have full connect.in's locally rather than redirects then renaminng connect.ini on the server will not prevent their access.

  11. Thanks to Greg from:

    vikpaw (18th May 2013)

  12. #10
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 493 Times in 376 Posts
    Rep Power
    0
    I can't remember who created this SQL script, but I'm sure I got it off another Edugeeker from a similar thread. We use this in management studio and it works a treat to see exactly who's in SIMS:

    Code:
    declare @mySIMSdb as nvarchar(100)
     
    set @mySIMSdb = 'sims'
    
    
    
    -- drop table #sp_who2
    
    create table #sp_who2 
    (
    spid int,
    status varchar(100),
    loginname varchar(2000),
    hostname varchar(2000),
    blkby varchar(100),
    dbname varchar(200),
    cmd varchar(max),
    cputime int,
    diskio int,
    lastbatch varchar(100),
    pgmname varchar(500),
    parentspid int,
    request_id int
    )
    
    insert into #sp_who2
    EXEC sp_who2
    
    select loginname, hostname, dbname  from #sp_who2
    where dbname = @mySIMSdb
    
    
    drop table #sp_who2
    If your using SOLUS2 to run the upgrade, script it (or run it via a command line) and use the /FORCEUPGRADE /SAUSER=sa /SAPASSWORD=password switches. This will disconnect any usert and apply the upgrade, handy for those few users who always leave SIMS .net running overnight! SOLUS3 should kick users out too by default.
    Last edited by Rawns; 17th May 2013 at 02:09 PM.

  13. #11

    Join Date
    Jan 2008
    Location
    South West
    Posts
    1,842
    Thank Post
    219
    Thanked 271 Times in 219 Posts
    Rep Power
    70
    meh- I just run solus and see if it works. if it does then no one can use the database

  14. #12

    Join Date
    Jan 2013
    Location
    Switzerland
    Posts
    170
    Thank Post
    13
    Thanked 24 Times in 23 Posts
    Rep Power
    8
    I used AB tutor to connect to all workstations, and then send them all a polite message, before remotely terminating the application after 20 seconds.

  15. #13

    jinnantonnixx's Avatar
    Join Date
    Mar 2011
    Location
    In the Calamatorium.
    Posts
    2,086
    Thank Post
    123
    Thanked 534 Times in 357 Posts
    Blog Entries
    2
    Rep Power
    336
    @Rawns, that was a first attempt.
    A better script to see who's using the system is this:

    Code:
    use master;
    
    select 	upper (sysprocesses.loginame) [SIMS User],
    	sysprocesses.hostname [Machine],
    	sysprocesses.dbid,
    --	sysdatabases.dbid,
    	sysdatabases.name [Database]	
    from sysprocesses
    
    join sysdatabases on sysprocesses.dbid = sysdatabases.dbid
    
    where sysdatabases.name like 'sims%'     --change this to your database name
    
    order by sysdatabases.name  -- works for multihosting systems
    Note that the connections are transient, so they come and go as and when needed by the client application. This means that you can't rely on it to use see who's got SIMS running on their desktop; it only shows if they're doing something with SIMS at the time you run the script.

    But it's better than nothing.


    It would be easy for SIMS to put a flag into the database to indicate when a user is logged on.
    Last edited by jinnantonnixx; 17th May 2013 at 03:29 PM.

  16. Thanks to jinnantonnixx from:

    Rawns (17th May 2013)

  17. #14
    Steven_Cleaver's Avatar
    Join Date
    Jul 2008
    Location
    Birmingham
    Posts
    479
    Thank Post
    183
    Thanked 86 Times in 70 Posts
    Rep Power
    52
    Abtutor here as well, Email staff day before then if they haven't closed SIM's close SIM's on their machines and leave message on their screens but usually do it end of day.

  18. #15

    synaesthesia's Avatar
    Join Date
    Jan 2009
    Location
    Northamptonshire
    Posts
    6,515
    Thank Post
    627
    Thanked 1,173 Times in 900 Posts
    Blog Entries
    15
    Rep Power
    524
    There's some half-assed solutions there!

    1. Email all staff. Whinge that they never do what they're told and they're the reason for it not working.
    2. Unplug server from network. Upgrade. (fit to an isolated vlan/different switch if you want to do it remotely or if you cba to download the updates beforehand)
    3. Consume tea.
    4. Plug server back in and head to the pub for a pint.



SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 20
    Last Post: 20th March 2013, 03:42 PM
  2. Replies: 1
    Last Post: 10th February 2013, 08:37 AM
  3. [SIMS] Error 9 : Subscript out of range - SIMS .net reporting
    By Lizziepuff in forum MIS Systems
    Replies: 5
    Last Post: 28th May 2012, 02:20 PM
  4. Replies: 22
    Last Post: 1st March 2010, 01:53 PM
  5. safe way to kick people out of sims.net?
    By The_Traveller in forum Windows
    Replies: 18
    Last Post: 17th July 2008, 10:11 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •