Our school is using Novell and the (disobedient) teachers won't log off when they leave their machines. Is there a way to work a "LogOff after 5 min of inactivity" policy into Novell?
We are using (NovelWare Admin ver 5.1.9f) and client 4.x.
Thanks
Printable View
Our school is using Novell and the (disobedient) teachers won't log off when they leave their machines. Is there a way to work a "LogOff after 5 min of inactivity" policy into Novell?
We are using (NovelWare Admin ver 5.1.9f) and client 4.x.
Thanks
up...there must be something I can use (either Novell or Third Party Software).
Suggestions please....
Thanks
in my opinion novell sux,
but
maybe you can connect via socks that will disconnect after a time by default ?
There is a bumpup button that you can use to revive threads. What about enabling screen saver lockout after a period of inactivity? What OS are the teachers' on? If it's Windows 2K/XP isn't this a feature built-in to the Security Policies that you could enable?
Within Novell itself, there is no setting or policy to activate a logout/timeout. If you are using ZEN there may be a policy within it to perform this task but I haven't looked. If I get some time I will check it out, as well as third party products, and let you know what I find (this may take some time, pretty busy right now).
When was the last time you saw a published exploit for Novell? :pQuote:
in my opinion novell sux
Cheers:
Maybe that's why it sucks? :DQuote:
When was the last time you saw a published exploit for Novell?
oh... and DjM is probably right: Zenworks would be the best option. Found this Tidbit
exploit? uh?
may be 2002?
however i saw a unknown machine in the net at work last month,
(claiming to be something administrative)
glad not to be admin there.
all problems in their net are caused by novell.
but some older applications were programmed specially to use it.
Me?? Do a shot?? :DQuote:
MsM, is that a shot?
At who?? I personally like Novell. I've never had net problems with it even when using it with their BorderManager product (which I was quite good at bringing down when I was annoyed by the top admin -- thankfully he has a good sense of humour).
Any NOS can be problematic if the installation, configuration and administration are not done properly. For unonthedl's situation I would suggest the screensaver lockout option for now. IIRC, (memory is the 2nd thing to go) it should cause the CTL+ALT+DEL screen to appear in WinNT/2K/XP. If it's 95/98 however...
Good suggestion MsM, and fairly easy to implement too.Quote:
Originally posted here by MsMittens
For unonthedl's situation I would suggest the screensaver lockout option for now. IIRC, (memory is the 2nd thing to go) it should cause the CTL+ALT+DEL screen to appear in WinNT/2K/XP. If it's 95/98 however...
Cheers:
Thank you for all of your replies. They have been very helpful. The screensaver route seems the way to go. I was looking at our Teacher policy in netware admin, and I created a new policy to run when the screen saver is activated. What do I tell it to run? what exe will cause a hard shutdown or restart?
Checkout PsShutdown from sysinternals, that should do the trick for you.
Cheers:
I found the solution:
Quote:
Winexit.scr: Windows Exit Screen Saver
--------------------------------------------------------------------------------
WinExit is a screen saver that logs the current user off after the specified time has elapsed. In other respects it is similar to other screen savers and can be configured and tested on the Screen Saver tab of the Display Properties dialog box in Control Panel.
WinExit displays a dialog box containing the countdown timer and a user-defined message. When the countdown timer reaches zero, the logoff process is initiated