Networks

Ask something
Discussion Locked

login script pull usr info to MS access

0 helpful
2 replies

by skuehner

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I work in a large call center and trying to locate the phone reps is a bear. The pc names are base on drops, and so i would like to find/create a script that will pull the %username% and %computername% everytime a user logs into a pc and posts that data into a database of some sort. Any ideas?

2 replies

by bfilmfan

Microsoft thoughtfully provides a security log where this information can be recorded on a domain controller in Active Directory environment.

You didn't state what OS the users are using on the desktops or what OS your login server is using. LDAP compliant databases can have that information tied to the user's accounts.

If you are an all AD environment, you can easily use the security log or a security event monitoring service such as MOM, Quest, NetIQ, etc to have a searchable database, which can all be SQL-based. A SQL database would be more robust and fault-tolerant than an Access database.

by mm212

This will provide much more information than you are looking for, but it will get the job done.

Download gpresult from Microsoft at http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/gpresult-o.asp . Be sure to remove any spaces that may have krept in and be sure to use the entire link if it wraps. Add a batch file to the OU(s) logon script which contains:

ipconfig>\\server\gporesults\%computername%.txt
set l>>\\server\gporesults\%computername%.txt
\\server\sysvol\domain\scripts\gpresult /v>>\\server\gporesults\%computername%.txt

Replace server and domain with the appropriate names/paths for your network.

This has every machine create a file in one folder corresponding to their computer name. You could also make this by user name if you wished, but if they log on to more than one workstation, it would be overwritten.

In this file it gives the results from an ipconfig command, the server that authenticated them, and the results of the gpresult tool. I put this into play and I love the results. It has help track down numerous problems.

The /v after gpresult causes it to run in verbose mode. This gives each and every policy setting, registry entry and script and what policy they got it from. The largest file I see using this method is 36KB on a machine with many settings applied. Most are between 20 and 30KB. There are other switches you can use that will provide less information if you wish.

This discussion is closed to new replies.