Jump to content

jandersen

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

0 Neutral

About jandersen

  1. 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.
  2. 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
  3. 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
×
×
  • Create New...