User log files over a network

[MattGaff]

Reletively new to this, I wanted to know how feasable it is to create user log files for users over a network.

Each time somebody logs in, I would like the log file to display information such as time of log in, machine logged into and the software installed on the machine.

Is this do-able with all tools already available (i.e. dont have to install specialist software)?

Users are logging onto a network controlled by windows server 2003

[sicarie]

Reletively new to this, I wanted to know how feasable it is to create user log files for users over a network.

Each time somebody logs in, I would like the log file to display information such as time of log in, machine logged into and the software installed on the machine.

Is this do-able with all tools already available (i.e. dont have to install specialist software)?

Users are logging onto a network controlled by windows server 2003

I'm guessing you're speaking of someone logging into the domain. I'm not sure what your setup is (or what the default is anymore, it's been a few years), but I would recommend looking at the logs on the DC. (Right-click My Computer, Click Manage, and go to Event Viewer. Those should show your logs.)

There are ways to change the logging levels through Start, Control Panel, Administrative Tools, Local Security Policy, Local Policies. I'm pretty sure that will catch the logons to the domain (by altering the 'Audit Logon Events' in the Audit policy), but as this is a Win2k3 question, I'm going to move it over to the Windows Forum where our knowledgeable Windows members will probably be better able to either correct me, or give even more information in the rare event that I'm right. (The Windows Forum admins can move it back if it comes out that this is a syslog question or something of the sort.)

Best of luck

[bartonc]

There are ways to change the logging levels through Start, Control Panel, Administrative Tools, Local Security Policy, Local Policies. I'm pretty sure that will catch the logons to the domain (by altering the 'Audit Logon Events' in the Audit policy), but as this is a Win2k3 question, I'm going to move it over to the Windows Forum where our knowledgeable Windows members will probably be better able to either correct me, or give even more information in the rare event that I'm right.

That's exactly what I would have suggested (although I'm no W2K3 expert, that's right for on XP Pro).