|
| Home | Product Information | |
Tech Bulletin - 1073
AUDITING A NOVELL® NETWORK
Summary: This technical bulletin describes the steps required to setup the login script and batch files to automatically audit your network stations. You will need to change the example’s drives and mappings to match your network.
The steps required to setup NetKeeper Express or Configuration manager to automatically audit your LAN attached workstations are:
1-Create a NOVELL group called NETKEEPER
2-Modify your System Login Script
3-Create a batch file to run the audit utilities
4-Test the setup
1-Create a NOVELL group called NETKEEPER and add a few members to the group. This will allow you to test the automatic audit functions on just the members of the group. Once you are satisfied that the automatic process is going well, add EVERYONE to the group’s members to enable the audit for all workstations.
2-Modify your System Login Script
Copy information to DOS environment variables
Add the following lines to the beginning of your Login script:
DOS SET FullName = "%FULL_NAME"
DOS SET LoginName = "%LOGIN_NAME"
DOS SET NetAddress = "%NETWORK_ADDRESS"
DOS SET NodeAddress = "%P_STATION"
Modify the Login Script to run the audit batch file
There are two methods to run a program or batch file from the Login Script:
The EXIT method is the preferred method since this method provides more memory available to run the utilities.
Example using the EXIT command
Add the following lines to the END of your login script. (Change the mapping and the drive as needed for your network)
IF MEMBER OF "NETKEEPER"
MAP DISPLAY OFF
MAP ROOT Q:=serv1/sys:apps\nk
DRIVE Q:
EXIT "AUDITHCS.BAT"
END
Example using the EXECUTE (#) command:
Add the following lines to your login script: (Change the mapping and the drive as needed for your network)
MAP DISPLAY OFF
MAP ROOT Q:=serv1/sys:apps\nk
DRIVE Q:
#command /C serv1/sys:apps\nk\audithcs.bat
MAP DISPLAY ON
3-Creating a batch file to run the audit utilities
NetKeeper includes a sample audit batch file, audithcs.bat. The AUDITHCS.BAT file will run the hardware, configuration and software audits. Note that the configuration and software audit are disabled (by the REM command). We suggest that you first setup to audit hardware only until you are satisfied that the audit process is operating correctly. You can modify this file as needed.
@echo off
REM Batch file to run the NetKeeper audit utilities
REM AUDITHCS.BAT
REM DIR *.*
REM PAUSE
REM Sample batch file to test for available memory before running
REM audit
REM You may need to change the RAM requirements, see you user manual
REM This batch file runs config and software audits every 30 days
REM The hardware audit is run daily
REM Run batchram to check the amount of free base memory
batchram
IF ERRORLEVEL 39 GOTO AUDIT1
IF ERRORLEVEL 35 GOTO AUDIT2
REM less than 350K of free memory, don't run audit
SET >> LOWMEM.LOG
GOTO END
:AUDIT2
REM at least 350K of free memory, setup some virtual memory
SET CLAVM0=C:\,128
:AUDIT1
REM at least 400K of free memory
HARDADT [EF=FullName
REM CFGADT [NO=30
REM SOFTADT [NO=30
GOTO END
SET CLAVM0=
:END
REM Change the next line to delete the mapping to the NetKeeper
REM directory
MAP DEL Q:
4. Test the setup
Note: Insure that you have at least two stations logged into the network with supervisor privileges. If you create an invalid login script you could lock yourself out of the network since you can’t login. Having a second station already logged in with supervisor privileges will let you correct the login script since you are already logged into the network.
The hardware audit should run as you login.
Troubleshooting:
If the hardware audit won’t run or you get errors try:
Step 1: Open a command (DOS) prompt and make the NetKeeper directory (where you installed the program) the default directory. Example:
Q:\PUBLIC> cd \apps\nk
Q:\APPS\NK>
Step 2: Run the hardware audit from the command line in manual mode. Example:
Q:\APPS\NK> hardadt [m
If the utility HARDADT.EXE runs, then the problem is either in the batch file or in the login script. Check that the file HARDADT.EXE is in the NetKeeper directory by running a directory. Example:
Q:\APPS\NK> dir hardadt.exe
Volume in drive Q is SYS
Directory of Q:\APPS\NK
HARDADT EXE 328,544 04-28-97
5:43a
If the file is not in the directory (FILE NOT FOUND) then you may be in the wrong directory or the HARDADT.EXE file was not installed properly.
Step3: Run the audit batch from the command line. Example:
Q:\APPS\NK> audithcs.bat
The batch file should run without errors.
Note: You may get an error when the MAP DEL Q: line is executed, this is OK here.
If the batch file does not run:
Check that the BATCHRAM.EXE file is in your NetKeeper directory.
Check that you have sufficient rights in the directory
Check that you have the correct version of the audit utility for your network:
For Novell networks the version of the audit utility should include the letters NV
For netbios networks (NT, LAN Man, OS/2, Lantastic) the version of the audit utility should include the letters MS
For Vines networks the version of the audit utility should include the letters VI
For all other networks the version of the audit utility should include the letters NN
Step 4: Run the batch from the login script.
To run the audit from the login script, logoff the network and reboot your machine. Then log back in.
If the batch won’t run:
If you get a "File not found error", you may not be moving the NetKeeper directory before running the batch file. Uncommenting (remove the REM keyword) the 4th and 5th lines of the audit batch will display the directory from which you are executing the batch. The directory should be the NetKeeper directory.
You may not have enough free base memory to run the batch using the # (EXECUTE) method. Use the EXIT method instead.
Notes:
At the end of the batch file you may need to switch back to a different drive before deleting the map to the NetKeeper directory.
Make the AUDITHCS.BAT read only and hidden to prevent accidental deletion