Re: Please Help

Hello,

Active Directory is a very good solution for setting up centralized
authentication. You join computers to a domain, and you have a domain
controller that handles authentication for the computers in the domain.
Information about authentication can be collected from the domain
controller.

Logon and logoff are a little difficult with Active Directory. Active
Directory stores only the last logon information on an attribute for the
user object in Active Directory. It does not typically store the last
logoff. Most people will choose one of the following two solutions in an
Active Directory environment:

1) Use the Event logs.
Make sure that you use group policy to enable auditing to the desired level.
Once enabled you can look at the Security event logs to determine logon and
logoff. This can be time consuming and not very practical. Also, if you
have more than one domain controller, you have to look at the event logs on
each domain controller because the information is not replicated (or copied)
to each domain controller. Some people will implement special scripts to
copy the event logs into a database so it is more convenient to query the
logs.

2) A more clean solution would be to use a third party software tool that
runs as a service on your Domain Controllers. This service would monitor
logon and logoff events and provide its own reporting mechanism.

There are other authentication solutions besides Active Directory. Some of
them are more secure than others, and some of them might provide better
logon and logoff reporting.

Good luck in your search.

--
Ken Aldrich
DSRAZOR for Windows
Visual Click Software, Inc.
www.visualclick.com

"ankit ." <ankit.jgec@xxxxxxxxx> wrote in message
news:f0336c1f-0c7c-4d5d-9f6f-ede3dd6a8efe@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am a student of engineering college in India. In our computer lab,
our professor wants to save a log of each and every student(i.e their
logon time, logoff time, their roll no.).

For this we proposed a solution that the authentication of the user
should be done at remote computer for logging into local computer i.e.
we want a server that will authenticate a user for logging into local
computer.

Can anyone help us, what to do and how?

Is active directory useful in this case.

Ankit


.

Relevant Pages

  • Re: Machine Authentication not working with wireless clients and I
    ... after many hours with tech support at Microsoft and Aruba we finally ... Authenication-Methods-802.1x,my controller had a checkbox set for inner eap ... authentication, just the same error as before, about invalid account. ... What I would do is create a group of wireless enabled computers. ...
    (microsoft.public.internet.radius)
  • RE: Domain Controller Hardware Failure, remove from AD
    ... to know how to remove a crashed and decommissioned domain controller from ... we use the Active Directory Installation Wizard for ... demoting a domain controller to a member server. ... Settings object that exists as a child of the server object in Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: AS5400 configuration help
    ... Also why don't you try local authentication first. ... controller E1 7/0 ... interface FastEthernet0/0 ... dialer rotary-group 1 ...
    (comp.dcom.sys.cisco)
  • Re: LDAP?
    ... Your suggestion on integrating Active Directory and MS Access sounds good. ... >>If you mean you want to try and integrate it with Access security, ... > adopted to use any sort of authentication method you choose, ... then launches the real database and logs into the Access ...
    (microsoft.public.access.security)
  • Re: "The remote procedure call was cancelled" - child domain replication error
    ... > "Active Directory Installation Wizard ... > from the remote domain controller ROOT-PDC-01.COMPANY.COM. ... > installed DNS for me. ...
    (microsoft.public.windows.server.active_directory)