ManageWise 2.1 Configuration and Usage Tips
Articles and Tips: article
Novell Consulting Services
01 Jan 1997
Since this AppNote was written in Australia, it retains the original British spelling used by the author.
Provides tips on how to configure the ManageWise 2.1 console and NetExplorer server in new ways to customize the product's functionality.
Novell's ManageWise is a powerful network management application that allows you to manage NetWare and MS Windows NT servers, as well as user workstations. The base product also includes traffic analysis, virus protection and inventory management capabilities. However, there are instances where you might not want the full functionality of ManageWise available to certain users. For example, you may want to reduce the functionality available to the network operator on the night shift, or restrict a junior operator's ability to access the routers and reconfigure the backbone.
This AppNote provides some tips on how you might configure ManageWise to make it more useful. You will learn how to configure the ManageWise console and NetExplorer server in new ways to customise the available functionality and enhance system operations. Specifically, this AppNote describes:
How to configure the NetExplorer server to limit visibility to certain part of the network (scoping) or restrict visibility to certain devices (exclusion)
How to limit access to NetWare servers or desktops, or to features such as MIB browsing
How to set up ManageWise so that different operators access different levels of functionality on the same physical ManageWise console
Miscellaneous configuration and usage tips for ManageWise
This AppNote assumes familiarity with ManageWise and basic network management concepts.
For a discussion of how to integrate ManageWise with Unix-based enterprise management systems such as HP's OpenView, IBM's SystemView and Sun's SunNet Manager, see "Extending ManageWise for the Challenges of the Enterprise," Novell Application Notes, July 1996, p. 5.
ManageWise 2.1 Components
ManageWise 2.1 is the latest in a long line of network management products from Novell. It provides comprehensive management information about the NetWare environment. The ManageWise suite includes:
The ManageWise 2.1 Console, an MS Windows application that runs on Windows 3.1- and Windows 95-based PCs
The NetExplorer Server, a network discovery server
Management agents, server management software that runs on NetWare and Windows NT servers
NetWare LANalyzer Agent, a remote network analysis agent
The ManageWise 2.1 platform is also capable of integrating "snap-in" products from other vendors. These third-party products can take advantage of the functionality provided in the base ManageWise product.
NetExplorer Server Configuration
The NetExplorer server is an integral part of a ManageWise system. It is responsible for the discovery of information relating to devices in the network. Information discovered by the NetExplorer server is transferred to the ManageWise console when the NetExplorer Manager process on the ManageWise console requests it.
In a help desk environment, it is possible for up to ten ManageWise consoles to obtain information from a single NetExplorer server. (Check with your local Novell sales office for licensing details if you decide to run multiple ManageWise consoles.)
Scoping versus Exclusion
There are two concepts within the NetExplorer discovery process which need to be understood: scoping and exclusion. In a large network, there may be more than one network management centre and each may be responsible for a given geographical region. Information relating to devices in these regions can be directed at the designated network management centre and the management consoles contained therein. The discovery of devices in these regions can be controlled.
The ability to determine how much of the network is discovered is known as scoping. ManageWise is able to scope the network for both IPX and IP networks. There may be devices in the network which for some reason it is not desirable to obtain information about. These devices can be excluded from the discovery process. ManageWise supports both IP and IPX exclusion. Scoping can work with or without exclusion, and exclusion can work with or without scoping.
Sometimes organisations might want to exclude NetWare servers, or other devices, especially when the ManageWise consoles are being used for desktop application support. Below, we will look at ways in which the ManageWise console can be set up to display servers but not allow any management of those servers.
Note: If you are proposing to implement exclusion,make sure you have installed the latest patchesforManageWise 2.1. A patch called MW01A.EXEis required for the NETEXPLOR.NLM.This patchfile can be obtained from the Novell SupportConnection page on the World Wide Web at http://support.novell.com.
Implementing Bulk Scoping Addresses. If you decide to implement scoping on NetExplorer servers, it can be a tedious process to enter the addresses of each segment. An alternative is to use a text editor and edit the SYS:NMDISK\NXP.INI file. You can enter bulk IP or IPX addresses straight into the NXP.INIfile, one entry per line, as shown in the examples below.
For IP network scoping, add a section like this:
[IPRedundantRouters] 126.96.36.199 188.8.131.52
For IPX network scoping, add a section like this:
[IPXScopingNets] 0101f2dd,FFFFFFFF 0101f2ee,FFFFFFFF
Implementing Bulk Exclusion Addresses. If you have bulk addresses to be excluded, you can add them through a text editor straight into the SYS:NMDISK\NXP.INIfile.
For IP address exclusion, add a section like this:
[SNMPIPNoAccess] 184.108.40.206 220.127.116.11
For IPX address exclusion, add a section like this:
[SNMPIPXNoAccess] 0101f2d5 0101f2d6
Exclusions Can Affect Discovery
If you exclude the addresses of NetWare servers, it can affect the discovery of workstations and printers. NetExplorer normally discovers which devices are attached to a server; if a server is excluded for IPX and IP, devices may not be detected correctly. If the NXPLANZ process is running and the NetWare LANalyzer Agent is running on the server, it can detect the workstations through their MAC addresses.
Normally, a NetExplorer server runs NetExplorer processes for IP, IPX and LANalyzer discovery. If there is no IP in the network, you can disable NXPIP.NLM in the SYS:SYSTEM\NETXPLOR.NCF file. Some routers and hubs only support management over IP, so while there may not be any servers or workstations actually running IP, NXPIP.NLM could be kept to help discover the network infrastructure. Apple Macintosh computers running the AppleTalk protocol will be discovered through NXPLANZ.NLM in conjunction with the NetWare LANalyzer Agents, loaded on the NetWare server that is located on the same segment as the Macintosh computers.
Adding Community Strings for NetExplorer Discovery
NetExplorer uses SNMP community strings as part of its discovery process. If NetExplorer does not know the community string for a router, the discovery process might take longer or may be incomplete for networks attached to that router. Ideally, all SNMP community strings should be known by NetExplorer.
To check this, go to the NetExplorer server and access the NXPCON screen. Check in the SNMP | View Discovered Community Names window. For each address with a Community name of <UNKNOWN<, you should endeavor to find out the community name associated with that device. Default community strings are <public<, so if a device shows as <UNKNOWN< it is likely that the string has been changed or the device is unmanageable via SNMP.
Once a new community string has been determined, it can be added to the list on the NetExplorer server through the NXPCON screen by choosing SNMP | Edit Community Name List.
Once added, SNMP options (and Discovery Schedule options) can be dynamically invoked without having to restart the NetExplorer process by running the Activate Changes option from the NXPCON screen.
Dynamically Updating Currently Logged In Users
The information stored for a network object is recorded at the time the object is discovered by NetExplorer. The information is stored in the database object, in the System Information | System Name field. This information is displayed along with the object in the Internetwork map.
It is possible to have the currently logged in user recorded for the workstation in the ManageWise database. To do this, add the following section to the SYS:NMDISK\NXP.INI file:
Controlling the Trap Process
All NetWare servers have the ability to send SNMP Trap messages to any IP or IPX device defined in that server's SYS:ETC\TRAPTARG.CFG file. NetWare servers can send traps over IP or IPX. The addresses in the TRAPTARG.CFG file will be read at the time SNMP.NLM is loaded.
Dynamic Additions to the TRAPTARG List. If the NetWare server is running the ManageWise agent, one of the NLMs will detect ManageWise consoles advertising 0x26A SAPs. The FINDNMS.NLM module dynamically adds the address of any console advertising 0x26A to the list it statically read from the TRAPTARG.CFG file when SNMP.NLMwas loaded.
There are several ways to control this process:
Editing the ManageWise agent. You can prevent FINDNMS.NLM from loading by commenting it out in the SYS:NMDISK\NMA2.NCF file. FINDNMS.NLM is the first module loaded in this file. Add a "#" or ";" character in front of the LOAD FINDNMS.NLM statement to prevent it from loading.
Switching off 0x26A SAPs at the ManageWise Console. It is possible to stop the ManageWise console from broadcasting SAPs. At the ManageWise console, select Configure | Global Preferences | System Options. Deselect "Receive NetWare Server Alarms" to stop sending the SAPs. (This parameter is also located in the C:WINDOWS\NMS.INI file as SapBroadcast=0 to disable and 1 to enable SAP broadcasts from the ManageWise Console.)
Filtering 0x26A SAPs at the router. If you have a number of consoles in a help desk environment, it may be easier to simply filter the outgoing 0x26A SAPs at the router. This way, if someone accidentally switches SAP broadcasts back on, they will not get past the router.
NetWare LANalyzer Agent Tips and Tricks
LANalyzer Agent Uses TRAPTARG.CFG. The NetWare LANalyzer Agent also uses the TRAPTARG.CFG file and responds to the 0x26A SAPs as well. The syntax for the load command is as follows:
load LANZCTL trapreg=1
If trapreg is set to 1, it causes SNMP traps to be sent to management consoles advertising themselves as 0x26A on the network, as well as to stations listed in the TRAPTARG.CFGfile.
Omitting the trapreg parameter or setting it to 0 causes traps to be sent only to those stations listed in the TRAPTARG.CFGfile.
Moving a Server. If you want to move a server from one segment to another, you need to delete the LANalyzer Agent Configuration file and let it get "rediscovered" at its new location. Here's how to do this:
Unload the LANalyzer Agent by running ULANZ.NCF (the unload NCF file) at the server console.
Delete the SYS:LANZ\LANZ.CFGfile.
After you have moved the server to the new segment, load the LANalyzer Agent by running LANZ.NCF.
As a precaution, let the agent run for 10 minutes and then unload it. (The LANZ.CFG file will be zero bytes in length until the agent is unloaded. The file is written to disk when LANZCTL.NLM is unloaded as part of ULANZ.NCF.)
Rerun the LANZ.NCFfile; the LANZ.CFG file will not change again.
Limiting the RAM Available to the LANalyzer Agent. By default, the NetWare LANalyzer Agent will reserve 2 MB of RAM for LANalyzer packet trace files. This may be more memory than you want to dedicate to this task. The minimum that is recommended to be allocated for this purpose is 512 KB of RAM, which will typically enable about 120 to 150 packets to be captured on an Ethernet segment.
To change the amount of memory available to the LANalyzer agent, use the following command:
load LANZMEM bound=KB age=HHH
The bound=KB parameter is the upper limit on memory that can be allocated dynamically by the NetWare LANalyzer Agent. Increasing this number allows you to create larger packet capture buffers and maintain data for inactive stations for a longer period of time. Decreasing this value reduces the amount of memory that can be used by NetWare LANalyzer Agent. This leaves more memory for the other server tasks.
The NetWare LANalyzer Agent automatically purges data for inactive stations as the memory bound is approached. This allows NetWare LANalyzer Agent to adjust to the memory that is available to it dynamically. If the bound is low, purging occurs frequently, saving only data for stations that have been recently active on the network. If this happens, a message appears on the system console indicating that not enough memory has been allocated to NetWare LANalyzer Agent.
Top N Stations Sort. ManageWise has a feature where the NetWare LANalyzer Agent can remotely sort (at the agent rather than at the console) the most active devices on a monitored segment. This activity might be for Packets In, Packets Out, Bytes In, Bytes Out, or Errors. It is possible to have more than one concurrent sort being undertaken on a LANalyzer Agent at any given time. By controlling the number of concurrent sorts, you can control the amount of RAM that will be used for this task.
This feature is accessed by highlighting a managed segment's Dashboard, then from the pull-down menu selecting Configure | Active Window. Each option you select constitutes one Top N Stations Sort.
In the LANZ.NCF file, adjust the following load command:
LOAD LANZSM topn=N
where N is the number of concurrent Top N Station sorts that are allowed by NetWare LANalyzer Agent.
Handling Deliberate Duplicate IP Addresses. If you deliberately have duplicate IP addresses on some segments, you may receive a flood of "Duplicate IP Address" alarms. If you have applied the MW01A.EXE patch, you can add a parameter to the LANAlyzer Agent NCF file to stop these alarms from being sent.
If you want to disable multiple IP traps, open the SYS:SYSTEM\LANZ.NCFfile and set the DUPIP parameter as follows:
LOAD LANZSM DUPIP=0
If the DUPIP parameter contains a non-zero value (or if the parameter is not specified), duplicate IP traps will be generated.
ManageWise Console Configuration
The ManageWise console is not designed to be pulled apart. The console does not have out-of-the-box configuration functionality to get different views of data, nor are the menu options which are available in ManageWise generally configurable. The only way a ManageWise console may look different is if different third-party applications are integrated with it. However, the console may display different custom maps or internetwork maps, depending on the way the information has been configured and which NetExplorer server the console is using.
There are two files that control what is available on the ManageWise console: C:WINDOWS\NMS.INI and C:MW\NMS\OLF\BUILTIN.OLF. This section gives tips on how to configure these files to modify the ManageWise console configuration.
Note: Before trying these tips, make sure you have backup copies of the NMS.INI andBUILTIN.OLF files.If ManageWise will not start, restore the backup copies of thesetwo files and try again.
The NMS.INI File
The C:WINDOWS\NMS.INI file has a section called [map] which identifies the modules to be run at the console. A sample NMS.INIfile is shown below:
[map] ;************************************************ ; NETWARE MANAGEMENT SYSTEM CONSOLE TASK ;************************************************ ; A. NMS CONSOLE GLOBAL OPTIONS: ;=============================== ;-----------------Do not change the following lines-------- AutoExecute=snmpsrv,n-shell alarmmanager Modules=nmm,nsm,dds,rmon,rsm,hsm,SFT3,nma,oldnma,IPXWS,IPWS,UnixWare,\ Printer,nmsaamgr,nwconn,netxplor,LDTOOLS RunModules=nmm,nsm,dds,rmon,rsm,hsm,SFT3,nma,oldnma,IPXWS,IPWS,\ UnixWare,Printer,nmsaamgr,nwconn,netxplor,LDTOOLS DllPath=C:\MW\NMS\bin OlfPath=C:\MW\NMS\olf AppIcon=C:\MW\NMS\bin\map.ico
If you remove the Modules and RunModules that are not required from this section of the NMS.INI file, those options will not be executable at the console. The modules and their corresponding options are as follows:
NetWareServices Manager (instrumentation of NetWareservers)
RemoteMonitoring (the NetWare LANalyzer Agent managerwithin ManageWise)
RouterServices Manager (the MIB I and II routermanagement interface)
HubServices Manager (the interface for managingHSM-compliant hubs)
NetWareSFT III server management
NetWareManagement Agent management (needed to manageNetWare servers)
SupercededNetWare Management Agents 1.5 and 2.0-specificfeatures
NetWarefor SAA Services Manager programs
If a console is to be denied the ability to access NetWare servers, the following components could be removed from this list: nsm, rmon, rsm, hsm, sft3, nma, oldnma, nmsaamgr, and nwconn.
A ManageWise console could be denied access to desktop management by excluding the LDTOOLS Module and RunModule.
Changing Icon Sizes and Spacing. Have you just bought a 17-inch monitor for your ManageWise console and you still can't display the whole network on one screen? The Configure | Global Preferences lets you change colors and fonts but not distances between icons. By editing the NMS.INI file, you can change the distance between icons on the internetwork map and segment maps. Follow the instructions for each of the Vertical and Horizontal Object Spacing parameters. Try setting them to the minimum value, then restart the ManageWise Console. If the objects are too close together, incrementally increase the distance to suit your preference.
You can also set the object name to be truncated or wrapped to a second line by setting the Internetwork Map or Custom Map Truncate Object Name equal to 0 for wrap or 1 for truncate.
Internetwork Display on Startup. It is possible to have the internetwork map automatically open on startup by setting Start Internetwork Map = 1 in the NMS.INI file.
The BUILTIN.OLF File
This file is used to determine which of the pull-down menu options will be displayed in the ManageWise console.
If access to NetWare servers, routers and hubs and packet filtering is to be denied, the following lines could be commented out:
;IDM_VW_NW_SERVERS = 330 ;IDM_VW_PRINT_SERVERS = 331 ;IDM_VW_ROUTERS = 332 ;IDM_VW_HUBS = 333 ;IDM_VW_FILT_PACKETS = 337 ;IDM_VW_GOTO_PACKET = 338 ;IDM_CFG_RTTREND = 339 ;IDM_VW_ABOUT_DECODES
If the server performance trending and hub trending is to be denied, the following lines could be commented out:
;IDM_PF_NW_SERVER_TRENDS = 405 ;IDM_PF_NW_SERVER_THRESH = 406 ;IDM_PF_ROUTER_INTERFACES = 407 ;IDM_PF_HUB_TRENDS = 408 ;IDM_PF_HUB_STATS = 409
If SNMP MIB browsing is to be denied, the following lines could be commented out:
;IDM_CFG_SNMP_OPTIONS = 469 ;IDM_SNMP_MIB_BROWSER = 551 ;IDM_SNMP_MIB_COMPILER = 552 ;IDM_SNMP_TRAP_INTEGRATOR = 553
Help files and context sensitive help files could also be commented out in this manner also. These references are further down in the BUILTIN.OLFfile.
The SNMPMIBS.BIN File
ManageWise has the ability to integrate MIBs (Management Information Bases) from many vendors, and to use those MIBs to manage objects in the network. ManageWise includes a MIB Compiler and a MIB Browser. MIB files are stored ready for compilation in the C:MW\SNMPMIBS\CURRENT directory. Files in this directory are compiled by the MIB Compiler; the resultant files are stored in the C:MW\NMS\BIN directory as SNMPMIBS.BIN. Unique combinations of MIBs could be compiled in this manner, simply by determining which *. MIB files are copied into the C:MANAGEWISE\NMS\SNMPMIBS\CURRENT directory. The SNMPMIBS.BIN file could be copied to the operator's console, at login time, and stored in the C:MANAGEWISE\NMS\BIN directory.
Limiting MIB Functionality. The MIB Compiler program is called MIBC.EXE and it is stored in the C:MW\NMS\BIN directory. This program can be run separately from ManageWise. It is possible to remove this program from the operator workstations to eliminate the users' ability to compile MIBs themselves.
You might want to limit a user's ability to access MIBs completely. To do this, first remove all MIBs from the C:MW\NMS\SNMPMIBS\CURRENT directory. Then run the MIB compiler; a 275-byte SNMPMIBS.BIN file will be created in the C:MW\NMS\BIN directory. If the user then tries to run the MIB Browser, the following error message will appear:
Error in the current MIB bin file, no objects exist... re-compilation may be necessary!
The NMS.HLP File
ManageWise has a very comprehensive Windows Help system. The help files are usually stored in the C:MW\NMS\HELP directory. The main file is NMS.HLP. If you are looking at limiting the visibility of these files, you may want to create a cut-down or zero-information help file using one of the Windows Help editors and compilers.
For example, you could create a limited-information version of NMS.HLP so that users have less information to search. This version could then be copied to the user's MW\NMS\HELP directory to replace the full-functionality NMS.HLP.
Different Configurations for Different Console Operators
Given the above configuration options, it is conceivable to have different configurations for a number of operators. The NMS.INI, BUILTIN.OLF, SNMPMIBS.BIN (and optionally the NMS.HLP) files could be customised for different individuals based on their skills and responsibilities. These files could be copied to the various directories before the operator launches the ManageWise application. A set of these files, with minimal or no functionality, could be copied back when the operator finishes using the console.
Minimising ManageWise Console Functionality
From a ManageWise console, a user can perform many operations without being logged in or authenticated to the network. An SPX connection to the NetExplorer server is all that is needed in order to update the console's internetwork map and object database. To stop this update from occurring, a combination of changes to the BUILTIN.OLF and NMS.INIfiles is necessary.
Launching ManageWise with NAL
The Novell Application Launcher (NAL) can be used to gain access to the ManageWise application. The four files described above could be copied to the ManageWise console before launching the application with NAL. Upon completion, NAL could copy a set of minimal-functionality files back to the ManageWise console as part of the application shutdown phase. This would effectively secure the console from anyone who tried to run ManageWise without logging into the network.
Miscellaneous ManageWise Tips
ManageWise in a Non-NDS Environment
Not every site has upgraded to NetWare 4 yet, so in a non-NDS environment you could limit ManageWise's functionality for different users at user login time. You could have different profiles, or levels of functionality. For each profile you could store a set of the customised files in a particular directory. The users could be assigned membership in different groups, depending on the level of functionality you want to give them. Examples of these groups could be Desktop, Servers, Routers or Inventory. The system login script for these groups could be similar to the following:
IF MEMBER OF DESKTOP BEGIN COPY SYS:\GROUPS\DESKTOP\NMS.INI C:\WINDOWS COPY SYS:\GROUPS\DESKTOP\NMS.HLP C:\MW\NMS\HELP COPY SYS:\GROUPS\DESKTOP\BUILTIN.OLF C:\MW\NMS\OLF COPY SYS:\GROUPS\DESKTOP\NMS.HLP C:\MW\NMS\HELP END IF MEMBER OF SERVERS BEGIN...
When a ManageWise session is terminated, you could get the user to run a batch file named something like MWCLOSE.BAT which would copy the minimal configuration to the console, thereby securing the console. An example of such a batch file is shown below:
COPY SYS:\GROUPS\SHUTDOWN\NMS.INI C:\WINDOWS COPY SYS:\GROUPS\SHUTDOWN\NMS.HLP C:\MW\NMS\HELP COPY SYS:\GROUPS\SHUTDOWN\BUILTIN.OLF C:\MW\NMS\OLF COPY SYS:\GROUPS\SHUTDOWN\NMS.HLP C:\MW\NMS\HELP IF EXIST C:\MW\NMS\BIN\MIBC.EXE DEL C:\MW\NMS\BIN\MIBC.EXE IF EXIST C:\MW\NMS\BIN\SMUT.EXE DEL C:\MW\NMS\BIN\SMUT.EXE IF EXIST C:\MW\NMS\BIN\NMSCRON.EXE DEL C:\MW\NMS\BIN\NMSCRON.EXE
For groups that are not to have access to the desktop management or virus protection features, you could selectively copy on startup, and remove on shutdown, all files from the C:MW\LDT and C:MW\LDVPdirectories.
There are other files you may want to delete. This example just shows one method for how you could approach it.
Controlling Access to ManageWise Utilities
The standard installation of ManageWise includes a number of utilities that you may want to control access to depending on the functionality you want to provide to your users. Likewise, you may want to remove some of these utilities from the ManageWise program group under Windows.
NMSCRON.EXE. The NetExplorer Manager process runs on a ManageWise console. It is launched from the LOAD command in C:WINDOWS\WIN.INI. (See also N-SHELL.EXE NetExplorer.)
MIBC.EXE. The MIB Compiler program can run be run independently from ManageWise. It is stored in the C:MW\NMS\BIN directory and probably should only be made available to the ManageWise administrator.
MTB30.EXE. The Multimedia Toolbook is used with ManageWise Scenarios stored in the C:MW\NMS\HELP directory. When the program is launched from within ManageWise, it is via N_MTBRUN.EXE in the C:MW\NMS\BIN directory.
N_DBADMN.EXE. The ManageWise Database Administration tool is run from the Database Administration Tool icon in the Windows ManageWise Program Group or Folder. The file resides in C:MW\NMS\BIN and should only be made available to the ManageWise administrator.
N_DB5TO6.EXE. The Btrieve Version 5 to 6 Upgrade Utility is used when the ManageWise database is upgraded from ManageWise 2.0 to ManageWise 2.1. It should only be run at the time the database is being upgraded and should not be left on any ManageWise consoles. Once the database is upgraded, remove this utility from the C:MW\NMS\BIN directory and do not run it again.
N_DBGINI.EXE. The ManageWise Debugger Initialization program is used sparingly by developers and Novell Technical Support for debugging problems. It should be removed from C:MW\NMS\BIN and only run when advised by Novell Technical Support.
N-SEGCON.EXE. The ManageWise Segment Consolidation Utility is run from the Segment Consolidation Tool icon in the Windows ManageWise Program Group or Folder. The file resides in C:MW\NMS\BIN and should only be made available to the ManageWise administrator.
N-SHELL.EXE. This is the ManageWise Console. For the ultimate control, you could stop the console from launching by removing this file from the C:MW\NMS\BIN directory.
N-SHELL.EXE. The NetExplorer Manager process runs on a ManageWise console. It is launched from the NetExplorer Manager icon in the Windows ManageWise Program Group or Folder. The file resides in C:MW\NMS\BIN and should only be made available to the ManageWise administrator or the master console designated to update the NetExplorer data.
NMAINST.EXE. This is the NetWare Management Agent Installation program. You could delete this from the C:MW\NMS\BIN directory on all but the ManageWise administrator's console.
SNMPSRV.EXE. The SNMP Data Server Process is an iconised process that is automatically launched when the ManageWise console is launched. It is the SNMP Trap Manager component and adds the records to the TRAP database. This program only needs to exist on consoles acting as trap managers.
Shutting Down the NetWare Server
When shutting down a NetWare server, it is advisable to perform an orderly shutdown. Most of the ManageWise components have an Unload NCF file. These could be combined to create a DWN.NCF file to be run instead of the usual DOWNcommand for a server.
The DWN.NCFfile could have the following components:
UNNMA2(Note the syntax - it has an extra N in it) ULANZ(If the server is running LANalyzer agent) UNXP(Only if the server is the NetExplorer server) UNLOAD GTREND REMOVE DOS(If you want the server to auto-reboot) DOWN
There are many ways to configure and enhance a ManageWise system. This Application Note has highlighted some of the ways we have found to tweak ManageWise to make it even more useful.
A follow-up AppNote will highlight some of the ways that the Virus Protection, Desktop Management and Inventory Management features can be optimised.
* Originally published in Novell AppNotes
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.