INCLUDE COMPUTERS THAT HAVE PREVIOUSLY BEEN AUDITED
Uncheck this option to only query for computers that do not exist in the Mouse Tracks database.

LDAP Query or Hostname
Examples:
LDAP://DC=yourdomain,DC=com
Retrieves all computers from the yourdomain.com domain

LDAP://MYLDAPSERVER
Retrieves all computers listed on the MYLDAPSERVER server

LDAP://OU=IT,DC=hq,DC=yourdomain,DC=com
Retrieves computer from the IT organizational unit in the domain hq.yourdomain.com

LDAP://OU=Accounting,OU=Finance,DC=hq,DC=yourdomain,DC=com
Retrieves computers from the Accounting organizational unit contained within the Finance organizational unit in the domain hq.yourdomain.com

WRKSTA-011
The specific hostname "WRKSTA-011" will be returned.

Comments:
The order of the items is important. For example if you have an Organizational Unit Named Accounting that contains the Organizational Units Accounts Payable and Accounts Receivable you would need to list the end node of the tree first and work your way up. The valid order for the tags is OU, then DC.

(correct)
LDAP://OU=Accounts Payable,OU=Accounting,DC=yourdomain,DC=com

(incorrect)
LDAP://OU=Accounting,OU=Accounts Payable,DC=yourdomain,DC=com

NUMBER OF AUDITS TO RUN CONCURRENTLY
To speed up the auditing, MT Audit allows the execution of audits on remote computers to run asynchronously. You can throttle this value by choosing how many audits can be running at the same time. Valid values are 1 through 10. Due to the page locking mechanics of the Jet Database Engine we recommend keeping this value no higher than 4 if you are storing your data in Access.

AUDIT OR EXCLUDE
The 2nd page of the Wizard Form will show you a list of computers that will be audited. By default newly discovered computers will default with the value of 'Audit'. If you wish to exclude certain computers from being audited select 'Exclude' from the drop down list. MT Audit will remember which computers are excluded so you won't need to repeat this step when reauditing.

AUDITING
Pressing the 'Audit' button will initiate the Audit Process. A grid view is then displayed showing you the current progress of the audit for each computer.

RUNNING MTAUDIT.EXE THROUGH THE COMMAND PROMPT
1. Create a new batch file (e.g., audit.bat)

2. Enter the Following Command in your batch file…
C:\Program Files\Gritware\Mouse Tracks 2009\MTAUDIT\MtAudit.exe LDQ=LDAP://YourLDAP REAUDIT=TRUE CONCURRENT=5 EMAIL=myemail@mycompany.com

Option	Comments
LDQ	A valid LDAP Query string or the hostname of a single computer
REAUDIT	Valid Values are True, False, 0 or 1
CONCURRENT	Number of audits to run concurrently (valid values 1-10)
EMAIL	If an email address is supplied a summary report will be mailed to this address upon completion of the audit. For this option to work make sure you have configured the Email Settings from the Mouse Tracks Windows Client by choosing the Tools--Configure Mouse Tracks--Help Desk Tab--Configure Email button.

3. Save the batch file

4. Create a scheduled task to run this batch file. See How To Schedule Tasks in Windows XP for additional help. Be sure to run the task with a domain user account that has administrative privileges to these remote computers.

IMPORTANT
MTAUDIT.EXE can only be run from a computer that has the Mouse Tracks Windows Client installed. If you want to setup the scheduled task to run on a server you will need to install the Mouse Tracks Windows Client on that server. After installing the Mouse Tracks Windows client on your server be sure to run Mouse Tracks once to configure the database connection.

TROUBLE SHOOTING
If you're having trouble auditing computers verify that they have the Remote Registry Service running. To test this open regedit and try to connect to the computer's registry. If you are unable to connect MT Audit will be unable to connect as well.

Verify that the Windows Management Instrumentation Service is not disabled on your remote computers.

If you have Windows Firewall enabled on Windows XP or Windows Vista by default MT Audit will be unable to connect to these computers. To enable remote administration through the Windows firewall on a computer open a command prompt on the computer and type "netsh firewall set service RemoteAdmin".

You can enable remote administration through the firewall for your entire domain by editing the group policy for your domain. Open the group policy editor in Windows Server 2003 and browse to Computer Configuration--Administrative Templates--Network--Network Connections--Windows Firewall--Domain Profile. From here you will see "Windows Firewall: Allow remote administration exception". Configure this option to be enabled. To activate this policy choose start--run then type gpupdate. This policy may take up to 15 minutes to propagate to your domain computers.

Verify Reverse DNS lookup is correct.
Open a command prompt and type ping -a <IP ADDRESS>

The first line of the response will be "Pinging <COMPUTER NAME>"

If the "COMPUTER NAME" is incorrect for the given "IP ADDRESS" there is a reverse DNS lookup issue that must be resolved.