Sending your data

On occasion we will require your Match-IT data to diagnose a non-trivial configuration issue. There are a number of ways that you can get your data to us:-

On CD

You can optionally omit the file called matchasa.tps from your transfer or zip file; this usually saves quite a lot of space and is only required if we are looking into an auditing problem.

Installing and running a script

We will occasiionally send you a script to perform a specific task. You can install and run that script by following the instructions below:-

These instructions apply to versions of Match-IT supplied after 17 Jan 2007

Step 1 - Save the script

We will send the script as an email attachment. Save it to your Match-IT configs folder on the server. For example m:\match_it\configs or just m:\configs.

Step 2 - Install the script

Use the Processes+GoAnywhere menu and execute the DR module process called "Install script". Use the [...] next to the script name to locate and select it. Tick both checkboxes (they will usually be ticked anyway) and make sure the language is set to "lua" (enter "lua" if not). Click the install button. This will install the script and then fire off the list of installed scripts.

Step 3 - Execute the script

After clicking the [Install] button Match-IT should have fired up the list of installed scripts and auto-located to the one you just installed. Having checked the correct script is selected click the [Execute] button to run it.

Running the script again/later

If you installed the script but did not run it or want to run the script again you can do so at any time by using the Processes+GoAnywhere menu and executing the DR module process called "Scripts". Select your script and click the [Execute] button.

Diagnostics

Match-IT makes extensive use of a computers's resources and may uncover previously undetected problems. If you are having problems with a particular computer please consider the items below.

Event viewer

Start the Computer Management applet from the Administrative Tools section of your Control Panel and open the Event Viewer branch of the tree. Check the various log lists for evidence of a consistent problem.

Server

Always try restarting the server first.

Restart

Restart the computer. If possible, physically turn it off rather then just doing a Windows restart operation.

Other programs

Close all the programs running (open) on the computer (including My Documents etc).

Virus checking

Make sure that a virus checker on the computer - especially a memory-resident one - is not checking items in the Match-IT folder - which will reside on your server. The Match-IT data files do not need to be checked and the executables are checked by Match-IT itself. Running a real-time virus checker on the Match-IT folder can seriously affect performance and ultimatly end in a crash due to Windows not handling network timeouts elegantly.

Background programs

Try running Match-IT in a simple software environment to minimise the possibility of unexpected conflicts with other programs. Remove all memory-resident programs (bottom right of your screen) that are not absolutely essential: iTunes, Messenger, Skype, spam filters, virus checkers, spyware detectors etc.

Windows components

Try turning off all non-essential Windows components: Firewall, screen saver etc.

Printer and Fax

Make sure all your printer and fax drivers are up to date and that you can print test pages. Do the same for any other hardware connected to the computer.

Removable devices

Remove all non-essential devices connected to the computer: iPods, memory sticks etc.

More virus checking

If you are running a memory-resident virus checker on the computer (likely), configure it to ignore these local files:-

• c:\windows\win.ini
• c:\documents and settings\user\application data\*.set

Where user is a Windows user name. Do this for all Windows users that will run Match-IT.

Network

Get your hardware/systems engineer to perform a check on the network. Badly configured networks and faulty network cards are relatively common. Speed and packet-loss tests are a good start.

Motherboard memory