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!
|
|
Knock Network Users Off?
Posted: 10 Apr 07 4:55 PM
|
Hello again 
I already ran this by SLX and they said that the issue was being addressed by Hellen Waite and I should go to her for resolution. 
How can I disconnect network users from SLX to preform DB maintenance such as Integrity Checker? As an example, @ 6 PM I still have 45 (of 545) users connected. Even if I dropped the SLX server (gotta admit: that would kick them off) there is no way to prevent them from climbing back on.
No: I can't "unplug" SLX from the network and work locally 
Michael |
|
|
|
Re: Knock Network Users Off?
Posted: 11 Apr 07 6:25 AM
|
I developed a tool to prevent clients from logging in by hooking into ApplicationLogon Complete. It's not that difficult.
However, IF you have users that leave their pc's logged in and go home you have only one choice: Force them out.. and then put a network wide Windows idle time logout policy in place to prevent this kind of thing.
--
rjl
|
|
|
|
Re: Knock Network Users Off?
Posted: 11 Apr 07 8:17 AM
|
You could de-activate all the users. This won't kick them off but it will prevent them from logging back in. To do this you will run the following query in admin>>>tools>>>execute sql:
Update usersecurity
set enabled = 'F' where type = 'N'
this will make all network users in active. when you finish run this next query:
Update usersecurity
set enable = 'T' where type= 'N'
the users are all active again. Like I said this won't kick them out but will prevent them from logging back in once you do kick them out. Hope that helps ML |
|
|
|
Re: Knock Network Users Off?
Posted: 12 Apr 07 11:37 AM
|
fiogf49gjkf0d If you do this via excute SQL you will synch it out.. I suggest if you not use the provider go "direct".
--
rjl |
|
|
|
Re: Knock Network Users Off?
Posted: 13 Apr 07 9:11 AM
|
fiogf49gjkf0d Just brainstorming here... Could a global script be created to fire an event in the client on a regular basis, then check the db for the presence of a "terminate" flag = true in a table. The developer would then set the flag to true when he/she wanted everyone off, and the next time the event fired, the script would terminate the application (in a friendly manner, of course)? |
|
|
|
Re: Knock Network Users Off?
Posted: 14 Apr 07 9:10 AM
|
Global scripts are "Event Handlers".. they don't fire events..
AFAIK there's NO event that fires off ion any kind of deterministic pattern.. except for DB Close "fires" every time there is a Ctrl-F5..
It's 100% possible to prevent a SalesLogix login.. but except for brute force termination.. you cannot deterministically log someone out. You are fighting the "thinker-doer" model.. and when one is in "think" mode.. nothing is happening in the SalesLogix client - total idle.. no events happening.
--
rjl |
|
|
|
Re: Knock Network Users Off?
Posted: 15 Apr 07 6:42 AM
|
Ahhh... but what about Contact Processes?
If "Scan for Processes" is turned on, it will periodically check to see if anything needs to be run. I once used them to have the activities refresh on a remote machine when a new activitiy was assigned to that user.
You would need to make sure that there is a contact that the user has access to.
Launch a process against that contact, assigned to the offending user that has a single step. (You can do that via script)
The step would be a vbscript that forces a logout -- this may be the show stopper though.... how do you log out via code?
Sendkeys?
BTW... I think this is getting really twisted, but hey... that's never stopped any of us before 
ws |
|
|
|
Re: Knock Network Users Off?
Posted: 15 Apr 07 2:12 PM
|
fiogf49gjkf0d What about this approach:
- Take the SLX Server offline (this disconects all current users).
- Change the Port to something other than 1706
- Have a separate aliase configured with your alternate Port
- Start the SLX Server
Once you are done with your maintenance, shut down your SLX Server, restore it to the default Port and Start the service to make it available to all users.
Enjoy. |
|
|
|
Re: Knock Network Users Off?
Posted: 16 Apr 07 6:09 AM
|
fiogf49gjkf0d GOOD POINT!
Scan (contact) process is really a great way to knock people off...
You could setup a contact process where the first function was a vbscript that checks for a flag in one of the "user" fields userprofile. It could be hooked up to a hidden contact record (a contact record that has no address record(s) 
Walter.. this is the best idea I've seen so far!
--
rjl |
|
|
|
Re: Knock Network Users Off?
Posted: 16 Apr 07 3:53 PM
|
Application.Quit logs out, well more specifically closes the application.
I'm not entirely sure how it behaves when say a Data Form is opened that hasn't been saved. Does modality kick in and prevent it from quitting? You'd hope not in this case but causing data issues is not entirely sound either.
Hypothetically you could code around this using Application.State. Make sure you're in the asReady state then loop through Application.Forms checking if Form.Modified = true. If it is, use Form.Post to save the form. The only issue I see with that is if a form doesn't validate then it won't post. Ideally it'd also be nice to persist the data path so that when the client opened again it could go right to Account "X" record "Y" but that's probably too much overhead. You would have to persist the path every time a new record is opened and this doesn't even take Managed Forms into account. Personally I'd stop at posting valid forms because you'll always have those users that "keep everything open expecting it all to be as they left it". |
|
|
|
Re: Knock Network Users Off?
Posted: 17 Apr 07 6:12 AM
|
If you want to avoid problems using this approach... I recommend that you create a table called "Shutdown_Request".
Create a window of time - i.e. a start date/time & an end date/time
launch the process for each user.
when the process runs
- if it is inside the window, then shut down
- if the window has expired, then exit the process
Then... the next time you run the shutdown process, you can also do your garbage collection (cleaning out the old instances of the process, etc)
The thing I am not sure about is what will happen if they are in a modal window when this thing fires off.... just like Jeremy pointed out.
ws |
|
|
|