7/10/2025 12:38:12 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss general administration topics for SalesLogix (including LAN & remote topics). View the code of conduct for posting guidelines.
|
|
|
|
Polite way to log off/ Lock out users?
Posted: 14 Dec 07 11:13 AM
|
I am trying to find a window to run Integrity Checker when none of my 700 world-wide users are on to no avail. Anyone else come up with a polite way to force the users off (not killing the server service), and keeping them out (without changing the DNS entry  )
Little app in a big pond  |
|
|
|
Re: Polite way to log off/ Lock out users?
Posted: 16 Dec 07 10:28 PM
|
Well, here's a way, but it might be somewhat more of a pain. I just don't think there's an easier way...
First send an email to all 700 users that lets them know that the SalesLogix will be down for maintenance at a certain time for however long you specify. This is where you get to decide how polite you'll be  Something like, "SalesLogix will be down for maintenace between 1 am and 1:30 am for maintenance. If you don't like it, tough." 
Next, find a text field in the table "UserSecurity" that you don't use (would be ClientLogPTR for me), and run this SQL statement: "UPDATE UserSecurity SET ClientLogPTR = Enabled"
Those first two tasks can be done earlier in the day. The next tasks are all done when you need to perform the maintenance:
1) Run this statement: "UPDATE UserSecurity SET Enabled = 'F' WHERE UserID <> 'ADMIN '"
2) Shutdown the SalesLogix server service for a minute, then start it back up.
3) Run the Integrity Checker and do whatever maintenance you need to do that requires everyone to be logged off.
4) Run this statement: "UPDATE UserSecurity SET Enabled = ClientLogPTR, ClientLogPTR = NULL WHERE UserID <> 'ADMIN '"
And that should be it. Please be aware, though, that I haven't used these SQL statements myself, so test - and use at your own risk. Yes, you would have to temporarily kill the server service, but it makes sense in this usage.
Good luck. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|