|Home | Product Information ||
TECHNICAL BULLETIN - 1063
Auditing a Server
This technical bulletin describes the steps needed to audit a server from a local workstation and store the audit data as a separate station. You can audit your server from a workstation and store the results attached to the workstation's data simply by adding a line to your software audit script (for instance m:\*.* /s). This bulletin describes a technique by which you attach the software audit data to an equipment record that you entered. This is an advanced technique. You must know how to operate your Network and how to audit software with NetKeeper before using the enclosed techniques.
To audit your server using the simple technique described above, see your NetKeeper manual under Software Audit Scripts.
You can audit a network server's software from any workstation on the network. You can not, however, run a hardware audit on the server from a remote workstation. To perform a full hardware audit of the server you need to boot the server as a station. Since the hardware audit program performs low level hardware tests, you will likely crash the server if you perform a Hardware audit on a running server.
Software audit of a network server
NetKeeper can perform a software audit a local or a remote server. To audit the server you sufficient rights to access the entire server. The Network supervisor has rights to audit the entire server or can assign full rights to another user.
Steps to perform a quick audit of a network server on you LAN or WAN.
Steps in detail
1-. Obtain the server's name. Use your network's utilities to get the server's name.
2-. Find the server's serial number, location and network address. Create an equipment record for the server and enter the server's name into the login name and the user's name. This is useful for reports. Next enter the server's Serial Number, location and network address. Note that NetKeeper records both network number and node number. The network number is used on only some networks (most notably Novell®). The node number is used by all networks and is generally the NIC (Network Interface Card) burned in address. If your network is set up using locally administered addresses, use this identifier for node number. Enter any additional data you need to store about your server and save the equipment data.
3-. Start NetKeeper Configuration Manager and enter the server's software audit script. Enter the audit script into a configuration element. To enter a configuration element select Configuration/Manager from the main menu, then ELEMENTS and press INSERT. (For additional details see your NetKeeper Configuration Manager manual under ELEMENTS). Under the element's data name, enter something like "Software audit script, SERVER1". Accept the defaults for the remaining fields. Enter SCRIPT under FILE. The audit script is entered in the DATA area. A server's software audit script is usually very simple, for example :
m:\*.* /s /EX=EXE /EX=BAT /EX=COM
The line above audits drive m: all files with extensions EXE, BAT and COM. For additional information about software audit scripts, see your NetKeeper manual under SOFTWARE AUDIT SCRIPTS.
Save the configuration element and then retrieve it back. On the upper right hand corner you will see a number. This is the element's number. Write it down we will need it later.
4-. Write a batch file to run the audit. An example follows :
SAMPLE.BAT- Sample server audit batch
|2||REM Sample batch file to test for available memory before running audit|
|3||REM You may need to change the RAM requirements, see you user manual|
|4||IF exist LOCKNK.TXT GOTO END|
|6||IF ERRORLEVEL 39 GOTO AUDIT2|
|7||IF ERRORLEVEL 35 GOTO AUDIT1|
|8||REM less than 350K of free memory, don't run audit|
|9||SET >> LOWMEM.LOG|
|12||REM at least 350K of free memory|
|15||REM at least 390K of free memory|
|20||SOFTADT [NU=XX [EU=SERVNAME [EI=IDNUM [EA=NETNUM [EN=NODENUM|
The above batch is a variation of the SAMPLE.BAT batch file from your Netkeeper Manual. Lines 16-20 changed to load data into the DOS environment and then use the data entered into the environment variables to audit the server. Make sure that the data you load into NETNUM and NODENUM match exactly the entries in the equipment record. This is very important as NetKeeper uses the combinations Network Number and Node Number to identify the station, server and the audit data. DOS environment data is assigned in lines 16-19. The data shown is for example only, change the entries to the right of the "=" sign to match your data.
Line 20 performs the audit. The command line parameter [NU specifies the configuration element that contains the software audit script. This option overrides the default audit script and the audit script in swscript.ini. Replace the XX with the element number you recorded in step 3.
5-. Run the audit batch file to audit the server.
HINT: You can also attach the batch to an entry in your REPORTS AVAILABLE list. The REPORTS AVAILABLE list is really a list of batch files and programs that can run reports or any other task. To execute the server audit from the REPORTS AVAILABLE list, add a REPORT DATA form. Under description enter "Software Audit -- Audit SERVER1 batch file". Set BATCH FILE to "Y" and enter the batch file's full path under REPORT DEFINITION. All other entries are optional. To run the audit highlight the entry from the list and press RUN.
Return to Tech Bulletin Menu