limit login

[whatwherewhen]

well we have it all set up on the server but it is not logging and log on information, script is set to run, client is on the workstation, ??

[whatwherewhen]

well, limit logon just doesnt work!! we are now trying userlock, we now have this working, has anyone used this or can warn me of any problems.

[DMcCoy]

Have you put any limits on the users? Limit login working perfectly here.

[SpuffMonkey]

Works fine for us too...

[Norphy]

well, limit logon just doesnt work!! we are now trying userlock, we now have this working, has anyone used this or can warn me of any problems.

 

We use it here, it works fine

[jandersen]

Hi all!

 

You will find a detailed competitive analysis (PDF file - 151 Kb) between LimitLogin and UserLock here :

http://www.isdecisions.com/download/whitepapers/UserLock-vs-Microsoft-LimitLogin.pdf

 

Hope it will help!

 

Best/Jean

[fooby]

I found that limitlogon just caused too many problems, we were forever "resetting" the logons of students here. Either it wasnt logging the logoff event or it was just stuffed.

 

fooby

[timbo343]

We use userlock, the only trouble we have is that a department uses laptops and the laptops dont log the kids off correctly so we have to reset them. Thats the only problem but otherwise its great

[MkII]

userlock: £2.21 x 150 concurrent users = £331.50 - our school would never go for that

[jandersen]

Tim,

 

About your problem with UserLock and laptops, and according to my own experience, this occurs when users put their laptops in Hibernate mode without closing their session, or when they close their session when their laptop is not connected to the network any longer.

 

In these cases, UserLock of course doesn't "know" that the session has been closed and will prevent these users to open what it considers to be a new session (if you allowed only 1 session at a time for your users) from another computer.

 

Turnaround: these users should connect again to the network with the same laptop, and UserLock will automatically correct the issue, without any intervention from the administrator.

 

Best/Jean

[apeo]

Going off track abit but just to clarify limitlogin only holds a log of current login sessions only right? That is it doesnt store who logged in where throughout the day?

[jandersen]

You're right Apeo: LimitLogin does not log sessions history.

 

But beyond poor features and installation complexity, the most important problem caused by LimitLogin (in my opinion) are irreversible changes to the Active Directory Schema.

[DMcCoy]

Hmm, it does what its supposed to here and the schema changes are minimal. If you just want to stop simultaneous logins its fine.