****************************************************************** * IBM Netfinity Director Release * * Version 2.12 * * * * readme1.txt April 26, 2000 13:13 * ****************************************************************** *************************************************************************** * Copyright Notice * * * * Copyright 1998, 1999, 2000 by Tivoli Systems, Inc., an IBM Company, and * * IBM. All rights reserved. Tivoli is a registered trademark of Tivoli * * Systems Inc. All other brand or product names are trademarks or * * registered trademarks of their respective holders. * *************************************************************************** *********************************************************************** Trademarks *********************************************************************** The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, Netfinity, Netfinity Director, Universal Managability Services, OS/2, RS/6000, Tivoli IT Director, and Tivoli Management Environment. Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. ActionMedia, LANDesk, MMX, Pentium, and Proshare are trademarks or registered trademarks of Intel Corporation in the United States and other countries. Java and Hot Java are trademarks of Sun Microsystems, Inc. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others. All other brand or product names are trademarks or registered trademarks of their respective holders. *********************************************************************** Purpose of this readme1.txt file *********************************************************************** This readme file provides information about IBM Netfinity Director Release Version 2.12. Please review these notes thoroughly before installing or using this product. For information relating to Tivoli IT Director, see the file readme.txt in this file's same directory. For information relating to the SCO Unixware extensions in a Tivoli IT Director environment, see the file readme.unix in this file's same directory. Please see the IBM Netfinity Director Version 2.11 readme documentation appended below for specific system requirements and any other pertinent informations. For information regarding e-fixes for Netfinity Director, please open URL http://www.pc.ibm.com/support. Releases superseded by this release: NFD 2.11 Patches superseded by this release: This Release of Netfinity Director is based on Tivoli IT Director Maintenance Release 2.12 plus the following e-fixes: e-fix number 1 Patches this release is dependent on: None Database Changes: Several Database Tables were English-only in NFD 2.11. All of these tables now display information in each of the supported national languages. In addition, several Database Tables have been modified. They are: Alert On LAN Settings IBM UM Services Lease Information Port Connections SNMP Agent Configuration System Slots Warranty Cost Release Contents: 1. This README file 2. A full install image of the Netfinity Director Version 2.12 Release level. ****************************************************************** This readme includes the following topics: 1. What's new in this release? 2. Tivoli APARs fixed in this release 3. Applying the Release 4. Special Notes 5. SCO Unixware Support Notes 6. Applicable information from the NFD 2.11 Release Notes ****************************************************************** 1. What's New in this Release? ****************************************************************** Netfinity Director has the following new features and functions: o Microsoft Windows 2000 GA server, console, and agent support o National Language Support for Simplified and Traditional Chinese, French, German, Japanese, Korean, Italian and Spanish ****************************************************************** 2. Tivoli IT Director APARs fixed in this release ****************************************************************** Problems Fixed: Tivoli APAR Abstracts --------------------------------------------------------------------- IY02542 INCREASE THE NUMBER OF COMPONENTS ON RAS IY00660 THERE IS NO DOCUMENTATION IN THE ONLINE HELP ABOUT HOW TO USE IY04309 Need to migrate TWGBackup to ITD 2.11 IY04383 ON A WIN 98 AGENT WITH A 4 GIG HARD DRIVE, THE %USED MONITOR IY04467 LOGITECH MOUSE & KEYBOARD DRIVERS CAUSE BLUE SCREEN NTOSKRNL IY05272 DR. WATSON IN TWGIPC.EXE AFTER UPGRADING TO 2.1 IY05624 MOVING FROM A JET DATABASE TO DB2 THEN BACK TO JET OR SQL IY05820 TWGIPC.EXE TAKES APPROX 20 MINUTES TO START UP IF THE NT IY06206 INVENTORY ON AN AS/400 SYSTEM IN 2.11 SHOWS ALL AS/400 TABLES IY06313 COLOUR CHANGE PROPERTIES FOR THE EVENT LOG ARE NOT RETAINED. IY06412 Allow TWGSHARE to take UNC notation IY06417 WINNT AGENTS WITH PENTIUM 3 PROCESSORS SHOW UP IN INVENTORY IY06503 Cannot override SIMPLE_SEND_TIMEOUT in tcpip.ini IY06505 SYSTEMS RANDOMLY GET PADLOCKED WHEN THE "SECURE YSTEMS"OPTION IY06858 THE INVENTORY VALUE FOR RAM/MEMORY FOR AN OS/2 SYSTEM WILL BE IY06893 TWGMONIT IS TRAPPING WHEN WE MONITORING PROCESSES ON OS/2 IY06894 NT PERFORMANCE MONITOR COUNTER CALCULATING INCORRECT RESULTS. IY06926 ITD 2.1 SERVER CRASHED WITH JAVA EXCEPTION. THERE APPEARS TO IY06987 ITD CAUSES ERROR MESSAGES 500 AND 550 INVALID MAIL USERS WHEN IY07014 Problem with driver over 2G IY07121 INVENTORY SCAN ON IBM TP390 HANGS,RENAME SINGBUS.DLL RESOLVES IY07122 ON NT AGENT THAT USES DHCP, THE INVENTORY SCAN IS REPORTING IY07126 NULLPOINTER EXCEPTION IN TWGINV WHEN SERVER STARTS, DUE TO A IY07240 INVERTORY COLLECTION OF AS/400 AGENT FAILS. IY07263 JVM EXCEPTION: TWGRCCONSOLE INDEXOUTOFBOUNDS IY07282 INVENTORY OF AS/400 DBCS MACHINE RESULTS IN CORRUPTION ON IY07363 PROCESS MANAGEMENT REMOTE TASK EXECUTION DOES NOT ALWAYS IY07454 IN REMOTE COMMAND EXECUTION WITH OUTPUT CAPTURE ENABLED IY07465 WHEN USING RSP FILES TO INSTALL A WIN9X AGENT, LONG DIRECTORY IY07658 SYSTEM VARIABLES IN EVENTSYSVAR.PROP DO NOT SUPPORT BLANKS. IY08004 ITD INVENTORY AGENTS ON NT MACHINES WITH MORE THAN 2G RAM DO IY08021 ON MULTINODE CLUSTERS (>2) AND ON CLUSTERS WITH A LOT GOING IY08127 WHEN REMOTE CONTROLLING AN AGENT,KEYSTROKES AND MOUSE IY08242 JAPANESE ITD CONSOLE DOES NOT DISPLAY ALL WINDOW NT LOG EVENT IY08434 REMOTE CONTROL DEVICE DRIVE TO SUPPORT WINDOW 2000. ****************************************************************** 3. Applying the Release: ****************************************************************** Netfinity Director Version 2.12 Release includes fixes for the Netfinity Director Server, Console and Agents. Since the Netfinity Director Version 2.12 Release CD contains the full product, it can be used to either upgrade existing installations of the Netfinity Director Agents, or for new installations of Netfinity Director Server, Console or Agents. I) FOR NEW INSTALLATIONS OF NETFINITY DIRECTOR SERVER, CONSOLE AND AGENTS Please follow the Netfinity Director Version 2.1 User's Guide, Chapter 3 installation directions. Note that if you plan to use the Default Jet database, stop all Jet DB Applications before starting the installation process for the Netfinity Director Server. II) FOR UPGRADING i) THE NETFINITY DIRECTOR SERVER: 1. Make sure all Director Consoles are logged off. 2. Uninstall Netfinity Director 2.11. 3. If you plan to use the Default Jet database, stop all Jet DB Applications. 4. Follow the Director Server installation directions in Chapter 3 of the Netfinity Director Version 2.1 User's Guide. Note that the format of some Database Tables have changed from 2.11 and 2.12, and a 2.11 Database cannot be reused for 2.12. ii) THE NETFINITY DIRECTOR STANDALONE MANAGEMENT CONSOLE: 1. Stop all Netfinity Director Management Consoles on the system. 2. Uninstall Netfinity Director 2.11. 3. Follow the Netfinity Director Management Console installation directions in Chapter 3 of the Netfinity Director Version 2.1 User's Guide. iii) THE NETFINITY AGENTS FOR OS/2, WINDOWS 9X AND WINDOWS NT Netfinity Director Agents for OS/2, Windows 9x and Windows NT can be upgraded by installing version 2.12 directly over the 2.11 version. It is not necessary to first remove version 2.11. iv) THE NETFINITY DIRECTOR NETWARE MANAGEMENT AGENT 1. Stop the Netfinity Director service by issuing "UNLOAD TWGIPC" on the Netware server. 2. Follow the Netfinity Director Management Agent - NetWare Installation Procedure directions in Chapter 3 of the Netfinity Director Version 2.1 User's Guide. ****************************************** 4. Special Notes ****************************************** NOTE 1: When upgrading to the next level of Netfinity Director, be a new major release or a Release, one needs to manually remove all the class files in the Netfinity Director's install directory's classes subdirectory (%UMS_HOME%\classes). Failure to do so will result in a mixed releases of Netfinity Director, and unpredictable results may occur. NOTE 2: If you encounter problems with Remote Control where keystrokes and mouse movements are not being reflected on the agent, please try the following workaround: On the agent, in Control Panel...Devices, set the KeyEnEx and MouEnEx devices to start Automatically (do not change the KeyEnEx5 and MouEnEx5 devices). Restart the agent. Tivoli APAR IY08127 will address this problem. When the fix is available, the workaround will not be necessary. NOTE 3: When using Remote Control, the Agent machine's screen size will be preserved on the NFD Console machine. Thus, if an Agent with a 640x480 screen size is displayed on a Console with 1024x768, only 640x480 pixels of information will be displayed in the Remote Control window. NOTE 4: The File Transfer application always report a Directory size of 0. NOTE 5: In the File Transfer application, if multiple files are selected, the application only shows the size of the first file. NOTE 6: NFD does not populate the "IPX Address" Inventory table. This table is supported in full-function Tivoli IT Director. NOTE 7: In the File Transfer application, directory replacement (that is, a directory transfer where the source and target directory locations have the same name) results in the existing directory at the target location being deleted and replaced by a copy of the source directory. NOTE 8: The CIM support is available ONLY on the following platforms: - Windows 98 with the addition of the Windows Management Instrumentation (WMI) - Windows 95 with the addition of the Windows Management Instrumentation (WMI) - Windows NT 4.0 (both Workstation and Server) with the addition of the Windows Management Instrumentation (WMI) - Windows 2000 both Professional and Server The ONLY supported version of the Windows Management Instrumentation (WMI) CIMOM in this release is Version 1.5, which is installed by the Netfinity Director installation/setup. Earlier releases of Windows 95 may require you to install Distributed Component Object Model (DCOM) in order to install WMI. DCOM95 is available from Microsoft's website at http://www.microsoft.com. NOTE 9: Opening simultaneous Remote Control sessions to a single agent is not supported. This restriction applies to multiple NFD Remote Control sessions or an NFD Remote Control session and a non-NFD Remote Control session. NOTE 10: When using the Event Action Plan Builder to post to secure News Group, the action does not support a secure News Group Server. NOTE 11: During an uninstall of NFD, the user is given the option of exporting and saving Software Distribution packages. If this option is chosen, the export operation unsigns the packages. These packages cannot then be imported to an NFD server unless they are resigned. NOTE 12: Event Action Plan Filters are case sensitive when entering data. This may cause confusion when editing similar Event Action Plan Filters. NOTE 13: TCP/IP Monitors are not available on Windows 95 and Windows 98 agents. NOTE 14: The Resouce Monitors task will not indicate an error if a recording is exported to a drive that is unavailable, such as a CD-ROM or an empty floppy drive. NOTE 15: When exporting monitor information, the monitor task does not warn the user if the target file already exists. NOTE 16: The File Transfer task will sometimes minimize itself when a "Replace Files?" dialog is answered "No." NOTE 17: No help is available for the "Auto Add" field of the Options>Discover Preferences>Netfinity Director Systems panel. NOTE 18: When upgrading an NFD Agent that does not have NFD Remote Control support already installed, the upgrade procedure will not add NFD Remote Control. When upgrading an NFD Agent that does have NFD Remote Control support, the upgrade procedure will upgrade the Remote Control support as appropriate. If the user wishes to add NFD Remote Control support to an NFD Agent that does not have it, after running the Upgrade Install, run D:\Win32\Install\Files\Nfd\Agent\Winnt\Twgsetup.exe where D: is the device containing the installation package. NOTE 19: In the Resource Monitors Task, the OS/2 monitor for CPU Monitors | Thread Count will always have the value zero. NOTE 20: In the Resource Monitors Task, opening hundreds of Available Resources Folders may result in a system hang. ****************************************************************** 5. SCO Unixware Support Notes ****************************************************************** This section provides information about the Netfinity Director Version 2.12 UNIX Agent. Please review these notes thoroughly before installing or using this product. The Netfinity Director components required to run the UNIX Agent include: - UAgent package for SCO UnixWare 7.1 - Netfinity Director Server Version 2.12 or higher, or Netfinity Director Server Version 2.11 and UNIX Extensions *********************************************************************** This section includes the following topics: UNIX-1. System Requirements UNIX-2. Installation and Configuration Notes UNIX-3. UNIX Agent Operation UNIX-4. Software Defects, Limitations, Workarounds No other documentation on the UNIX Agent is provided. *********************************************************************** UNIX-1. System Requirements *********************************************************************** The complete system requirements for the Netfinity Director servers, consoles, and agents for other platforms are listed in the Netfinity Director User's Guide. The following are additional system requirements for supporting the UNIX Agent. SCO UnixWare 7.1: - 16 MB free space on the /opt mount point - Patch number ptf7441a (This can be obtained directory from the Santa Cruz Operation, Inc., website at http://www.sco.com.) No other UNIX platforms are supported in this release. Each UNIX Agent installs the necessary Java Runtime Environment for its use. The JRE version for SCO UnixWare 7.1 is JRE 1.1.7A. *********************************************************************** UNIX-2. Installation and Configuration Notes *********************************************************************** Netfinity Director Server UNIX Support ----------------------------------------- Netfinity Director Server UNIX support is automatically installed during the Netfinity Director Server installation. Netfinity Director UNIX Agent ----------------------------- SCO UnixWare 7.1 ---------------- 1. Copy the UAgent.pkg.gz package to a temporary directory and unzip the file by executing: gunzip UAgent.pkg.gz 2. Either install the package using 'scoadmin', or, from the temporary directory, type /usr/sbin/pkgadd -d `pwd`/UAgent.pkg where `pwd` is enclosed in reverse quotes. Follow the pkgadd instructions. The agent is installed in the directory /opt/tivoliag. 3. When the installation is complete, the agent begins running automatically, and the system is ready for discovery by a Netfinity Director server. UNIX Agent Security ------------------- UNIX agents are secure by default. Consequently, when they are first discovered by the Netfinity Director server, The middle panel on the Netfinity Director Console shows a lock icon next to the system name. To gain access to the UNIX agent, highlight the desired system(s) on the Console and right-click the mouse to produce the tasks pop-up menu. Click "Request Access," and enter the appropriate user name and password on the dialog. After successfully requesting access, all supported tasks will be available. *********************************************************************** UNIX-3. UNIX Agent Operation *********************************************************************** UNIX Agent Scripts and Executables ---------------------------------- The UNIX agent is installed and configured to start and stop automatically upon rebooting or shutting down the system, respectively. Consequently, no administration or user intervention is required for normal use. The UNIX agent installs into the '/opt/tivoliag' directory; within the 'bin' subdirectory are scripts and executable files that the agent uses to conduct its operations. Other than Genevent, these should not be executed directly by the administrator (root) or users, except under the direction of IBM or Tivoli Support. TWGlaunch -- starts the UNIX agent as a daemon process. TWGend -- shuts down the UNIX agent. RasView -- starts agent logging for diagnosing field problems. This script is for use at the direction of IBM or Tivoli Support. tivhscan.sh -- collects hardware inventory. This script must not be run manually; it is for use by the agent only. Genevent -- This is a sample script that generates events for delivery to the Netfinity Director Servers to which this agent is attached. It may be used by the administrator for test or as a template for user-created events. (See the next section.) The binaries contained in the /opt/tivoliag/bin directory are not to be invoked by the administrator or users. They are for use by the UNIX agent only. Genevent -------- Genevent supports the same parameters as its Win32 counterpart. These include: Parameters Description Required parameters: ------------------------ /TYPE:"type" Dot delimited string (minumum 2 level name) ("UserAppName.Database.Update Record") /TEXT:"text" Free form quoted string ("User application encountered an error") Optional parameters: ------------------------ /DEST:destination Server address format: (protocol::name) default: this station's event server example: TCPIP::TWGSVR1 /SEV:sev Event severity default: Unknown Fatal Critical Minor Warning Harmless Unknown Additional parameters: ------------------------ /STRING:keyword=value String event detail data example: release=director2 /INTEGER:keyword=value Integer event detail data example: returnCode=16 /LONG:keyword=value Long event detail data example: returnCode=70000 For the UNIX agent, the /DEST parameter protocol can only be TCPIP. These parameters can be enumerated from a command line by modifying the sample Genevent script to include no parameters. *********************************************************************** UNIX-4. Software Defects, Limitations, Workarounds *********************************************************************** 1. Discrepancies can be observed between logical partitions enumerated in Inventory and those in Resource Monitors. This behavior is due to the df utility and options used during inventory and is not an error. 2. Task Execution is the only Process Management function supported by the UNIX agents. 3. Task Execution of graphics user interface commands, such as xclock, and commands that require user intervention at the endpoint are not supported by the UNIX agents. 4. Scripts using Perl 4 that are executed using Task Execution may fail immediately after agent installation. To correct this problem, stop and restart the UNIX agent by issuing: /opt/tivoliag/bin/TWGend followed by: /opt/tivoliag/bin/TWGlaunch Perl 5 scripts do not have this limitation. ****************************************************************** 6. Applicable information from the NFD 2.11 Release Notes ****************************************************************** This readme file provides information about IBM Netfinity Director Version 2.11. Please review these notes thoroughly before installing or using this product. This is the Netfinity Director 2.11 release containing: - Server for Windows NT - Agent for Windows, OS/2, Novell - Console for Windows - Softcopy version of the documentation See the documentation for specific system requirements. License Key ----------- You need at least one valid license key to use the product. You can find this on a key card in your packaging. If this is an upgrade version of the product, you need your previous version key in addition to the key found in this packaging. User's Guide ------------ The CD contains the Netfinity Director User's Guide in PDF format. The file is named "director.pdf" located in the docs\xx directory, where xx is the two letter or 4 letter code for your language. This readme file includes any last minute changes to that document. ****************************************************************** This readme includes the following topics: ****************************************************************** 2.11-1. System Requirements 2.11-2. Installation and Configuration Notes 2.11-3. What's new in this release? 2.11-4. Software Defects, Limitations, Workarounds 2.11-5. Additional Notes 2.11-6. Documentation Updates ****************************************************************** 2.11-1. System Requirements ****************************************************************** The complete system requirements are listed in the User's Guide. Listed below are the changes from those documented. The following is important information. Management Console: - Minimum requirement of 55 MB free disk space - 64 MB RAM on Windows NT 4.0 (Workstation or Server with Service Pack 3 or higher) - Requirements for RAM on Windows 95/98 systems remain the same ***************** Database Defaults ***************** Default Database is Now a Jet 4.0 Database (MDAC 2.11) ----------------------------------------------------- In this release of Netfinity Director 2.11 the ODBC drivers were updated to MDAC level 2.11, which is available through Microsoft. This package also updates the Jet Database drivers to version 4.0. When the default database is requested on a new installation of Netfinity Director server 2.11 a Jet 4.0 database is created. This version of the database cannot be viewed using Microsoft Access 97. A Jet 4.0 level database can only be viewed using Microsoft Access 2000. If Microsoft Access 97 is the only version of Access available, and it is desirable to view the Netfinity Director database through Access, then a Jet 3.5 level database can be used. This level of the database can be created through Microsoft Access 97. The database can then be used by Netfinity Director by setting up a ODBC data source for the new database and modifying the file TWGServer.prop to use the new data source. The User's Guide has more information about setting up Netfinity Director to use an existing database. ********************** DMI Support Disclaimer ********************** The DMI support is available ONLY on the following platforms: - Windows 98 with the addition of the Intel DMI Version 2.0(s) Service Provider - Windows 95 with the addition of the Intel DMI Version 2.0(s) Service Provider - Windows NT 4.0 and Windows 2000 (both Workstation and Server) with the addition of the Intel DMI Version 2.0(s) Service Provider. The ONLY currently supported version of the DMISL is Intel's Version 2.0 and 2.0s. ******************************************************************** 2.11-2. Installation and Configuration Notes ******************************************************************** For complete information regarding the installation and configuration of Netfinity Director, see the User's Guide. It is on the CD in the docs\xx directory, where xx is the two or four letter code for your language. The file is named director.pdf. If you are going to have the Intel LANDesk Console on the same machine as a IBM Netfinity Director Management Agent, please install the LANDesk Console first. Installing LANDesk Console on a machine that already has the Netfinity Director Management Agent installed can cause the machine to stop operating. If you have Intel's LANDesk 2.51 or 2.52 installed, and want to install the LANDesk provider, make sure that you run SDCONSOLE (LANDesk's Distributed Console) at least once before installing Netfinity Director. When SDCONSOLE is run the first time, it creates registry keys that are necessary to correctly install the LANDesk provider. Without these keys, the LANDesk Provider Configuration routine does not have the information required to inform the provider of how to launch SDCONSOLE. SDCONSOLE is required for determining topology information. IBM Netfinity Director Windows install and uninstall programs use the TEMP directory. If you have deleted the TEMP directory, the install and uninstall will fail. You need to recreate a proper TEMP directory as indicated by the TEMP environment variable. Consult your Windows documentation if you have questions regarding the proper use of the TEMP directory. If needed, Microsoft Data Access (MDAC) is used by Netfinity Director V2.11 Server install to install and/or upgrade ODBC and its drivers. The MDAC install consists of two steps, with the second step being performed after the system is rebooted and the user logs on. The Netfinity Director Server will attempt to start as soon as the system is rebooted. Since the second step of the MDAC install does not start until the user logs on, the Netfinity Director Server database initialization will fail. You must reboot and log on and then reboot a second time to resolve this situation. ****************************************************************** 2.11-3. What's New in this Release? ****************************************************************** Netfinity Director Server (NT) 2.11 supports Tivoli IT Director 1.2x Management agents, however you should upgrade your 1.2x agents to version 2.11. Please note that you can manage 1.2 agents with the new server, however, the new and improved functions will not be available on the old agents. If you have upgraded your Netfinity Director server from Tivoli IT Director 1.21 to Netfinity Director 2.11, a new software dictionary file is located in the same directory as your existing dictionary file, or \\\Classes\com\tivoli\twg\inventory\. This new dictionary file did not replace the existing dictionary, default.sid, during the upgrade and is named "defaultnew.sid." In order to utilize the additional entries in the new dictionary and keep the modifications that have been made to the existing dictionary, you must run an Netfinity Director software dictionary merge utility against these two files. Your existing file will be backed up and the merged file will be used by the Netfinity Director server for Softwar Inventory. Please consult the Inventory section of the User's Guide to use the import/merge utility, TWGCLI SWDictionaryWriter. Note: Your dictionary file can not be locked during this process. To ensure that the file, default.sid, is not locked, shut down the Netfinity Director server. Once the merge is complete, restart the server. ******************************************************************* 2.11-4. Software Defects, Limitations, Workarounds ******************************************************************* Windows 3.x ----------- Netfinity Director agent is not supported on Windows 3.x. Coexistence with IBM Netfinity Services --------------------------------------- Netfinity Director cannot coexist with IBM Netfinity Services software when running under a NetWare installation. The module name contention may result in Netfinity Director not working correctly. Please unload and remove from the AUTOEXEC.NCF file any statements that do the following : SEARCH ADD sys:netfin LOAD netfbase (netfbase or the path NetFinity has been installed into) Disconnected Network Drives --------------------------- If a console is started while a network drive is disconnected and then later is reconnected, the Install AMP GUI will display the error "The selected drive is not in use" when attempting to list the drive contents. This occurs only on the NT server. Resizing Dialog Boxes with Tables --------------------------------- Dialog boxes that use tables, such as Console Security and AMS Console, may not have the correct initial table column widths. The table columns can be manually resized to fit the screen. Hot Java Browser Limitation --------------------------- In the Channels browser, when viewing a channel that requires authorization, the user will need to enter the username and password twice--once for Netfinity Director's Channels browser and once again for the Hot Java HTML Browser that is used to view HTML pages within the Channels browser. A separate popup window will appear for each. Once a valid password is entered, the popup will not reappear. This problem is due to a limitation with the Hot Java HTML Browser. Some links do not take you to the beginning of the topic. This is a known problem with the HotJava browser. Novell NetWare 4.11 Limitation ------------------------------ The Netfinity Director Agent does not run on a Novell NetWare 4.11 SFT III system. Database Encoding ----------------- Netfinity Director is a poly-lingual product that needs to store and retrieve data from a database for many different locales simultaneously. The current JDBC drivers do not support this feature for DBCS languages. We have encountered JDBC drivers that would not correctly store Unicode values greater than 0xFF and several that would not even allow values greater than 0x7F. This limitation precluded the storage of Unicode characters in the database, and even some characters converted to the locale specific code page. The solution to this problem is to encode some of the strings stored in the database. If the string to be inserted in the database has even one character that exceeds the capability of the JDBC driver, then the entire string is encoded. The characters in the string are checked against a maximum value to determine whether or not to encode the string. The upper limit for non-1252 code page locales is 0x7F otherwise the limit is 0xFF. If any character in the string exceeds the upper limit value then the string is converted to an encoding that is similar to UTF8. The main difference between our encoding and UTF8 is that the 8th bit is never set. Here is the table that describes the encoding. Start End Required Binary Byte Sequence Character Character Data Bits (x = data bits ) ------------------------------------------------------------ \u0000 \u003F 6 00xxxxxx \u0040 \u07FF 11 010xxxxx 01xxxxxx \u0800 \uFFFF 16 0110xxxx 01xxxxxx 01xxxxxx This encoding is very important to know if a third party tool is used to create queries against the database. The returned database string may have been encoded. An encoded string can be detected by looking for a "}" as the first character. This character must be removed before decoding the string. Note that the majority of the information in the database can be represented in code page 1252 and therefore is not encoded using the above scheme. Inserting the following line into TWGServer.prop can turn off this feature. twg.database.encoding = false. The default setting is true, for now. We do not suggest turning off this encoding at this time. Engine Fails to Start on Reboot ------------------------------- Occasionally after initial installation and restart of the Netfinity Director server on Windows NT, the server will fail to start when the machine is rebooted. This is due to the time it takes for the ODBC drivers and services to initialize upon installation. This problem can be detected by viewing the following message in the NT Event Viewer. The message will be in the Application log. Error Message: com.tivoli.twg.engine.TWGDbException: Query Error: java.sql.SQLException: [Microsoft][ODBC Microsoft Access Driver] Unknown If this problem occurs stop and restart the server. This can be accomplished by using the following statements in a command window; net stop twgipc net start twgipc. Memory Constrained Consoles --------------------------- Intermittent JRE (Java Runtime Environment) exceptions may occur when running the Netfinity Director Management Console on systems that are memory constrained, and on some multi-processor systems. This is a known problem with the Windows 32Bit Java Environment documented by Sun. Netfinity Director and Domino Server 4.5 or Later ------------------------------------------ After the installation of the Netfinity Director agent or server on a system that has Lotus Domino Server Version 4.5 or later, the Domino server may experience problems that resemble very poor performance. The Domino Server will not start or stop properly. This is due to an incomplete installation state of the Domino Server. During the Domino Server installation, there is an opportunity to install performance monitors. If the performance monitors for the generic Domino Server are installed, you must run the "notsreg.bat" file in the c:\notes (or wherever you installed the Domino Server) so that the necessary information is registered into the registry. Windows 9x Data Collection ----------------------------------- The Netfinity Director agents running on Windows 9x do not collect data for the IDE Adapter, IDE Device, SCSI Adapter and SCSI Device tables. Software Information Gathered Through OS/2 Syslevel --------------------------------------------------- OS/2 software information that is gathered through OS/2 Syslevel will be collected and displayed in the Inventory task, but cannot be viewed or edited in the Software Dictionary. You may edit these with the TWGCLI task. For details, please see the User's Guide. Remote Control Limitations --------------------------------- HP Model number SK-2501K multimedia keyboard is not supported by IBM Netfinity Director Remote Control. Remote Control does not support double byte character set (DBCS) full screen sessions on Netfinity Director Management agents running the following operating systems: - Windows 95 - Windows 98 - Windows NT Netfinity Director supports DBCS full screen sessions on Netfinity Director Management Agents running under OS/2. If you experience problems using a Logitech Mouse with Netfinity Director's remote control function, you will need to use the Microsoft PS/2 mouse driver that is included as part of the operating system. This is a current limitation of Netfinity Director. Keyboard Support ---------------- Netfinity Director Management Agents running under Windows 95 and Windows 98 do not correctly detect the keyboards installed on agent systems. Instead, these agents use a default keyboard based on the installed language of Netfinity Director Server. If you want to change the default keyboard settings for these systems or if you want to specify a particular keyboard layout for an individual system, you can edit the \Classes\Keyboard.txt file. Instructions for editing the file are included in the file as comments. IBM Netfinity Director supports the following keyboards: - IBM US - IBM France - IBM Germany - IBM Spain - IBM Brazil - IBM Japan - IBM Italian - IBM Korean - IBM Simplified Chinese - IBM Traditional Chinese - NEC PC-9800 Standard Keyboard - NEC PC-9800 106 [PC-9801-116] If you need support for a different keyboard, contact your IBM Netfinity marketing representative. NetWare Notes ------------- When shutting down the Netfinity Director agent on a NetWare server, the modules SECMOD01.SEC and DOSCLLS.NLM are not unloaded automatically. After stopping the Netfinity Director agent, please UNLOAD SECMOD01.SEC to cause these modules to unload as well. Similarly, after running the TWGIPCCF utility to configure the network protocols, the TWGCFSTR.NLM module may not be unloaded. It may be unloaded using UNLOAD TWGCFSTR.NLM with no ill effects. A message may be seen on NetWare 3.x or 4.x server that some resources have not been freed. This is typical, and will cause no other adverse effects. Application Management Console with Hidden Submenu -------------------------------------------------- While looking at an existing Applications Management Package, you may right click on the list of components within the package. A submenu will appear. However, if you right click on the right column, its submenu may be hidden by the adjacent Help panel. To view the submenu and have access to its selections, resize the Help panel until the submenu appears. Extended Tree Shown in Query Window ----------------------------------- The tree displayed in the "Available Queries" panel may extend several pages without any files or folders listed. To see the rest of the components displayed, scroll down to the bottom. CIM Monitors cause Timeouts --------------------------- Monitoring CIM Properties is very system resource intensive for the agent system. If you are using CIM-based monitors, and are experiencing monitor timeouts, reducing the number of CIM Properties being monitored may improve performance. *************************************************************** 2.11-5. Additional Notes *************************************************************** Socks V4 and V5 Support for Console-Server Communication -------------------------------------------------------- The Netfinity Director console supports being configured to utilize a SOCKS V4 or SOCKS V5 compatible firewall to access an Netfinity Director Server. To configure the Netfinity Director Console to utilize a SOCKS V4 firewall, do the following: 1) Open the \\classes\com\tivoli\twg\console\TWGConsole.prop with an editor. 2) Replace the line 'twg.gateway.link.1.initparam=' with a line formatted as follows: twg.gateway.link.1.initparam=* -socksv4addr
-socksv4port For example: twg.gateway.link.1.initparam=* -socksv4addr 146.84.14.254 -socksv4port 1080 If you wish to override the default server logon port (TCP 2033), replace the '*' with a new port number, and change the corresponding parameter in the \\data\TWGServer.prop file by adding the following line: twg.gateway.link.1.initparam= 3) Save the changes, and restart the console (and server, if the \\data\TWGServer.prop file was updated). To configure for a SOCKS V5 firewall, do the following: 1) Open the \\classes\com\tivoli\twg\console\TWGConsole.prop with an editor. 2) Replace the line 'twg.gateway.link.1.initparam=' with a line formatted as follows: a) For unsecured access (a firewall not requiring a userid and password to be used): twg.gateway.link.1.initparam=* -socksv5addr
-socksv5port For example: twg.gateway.link.1.initparam=* -socksv5addr 146.84.14.254 -socksv5port 1080 b) For a user ID/password secured SOCKS V5 firewall: twg.gateway.link.1.initparam=* -socksv5addr
-socksv5port -socksv5userid -socksv5password For example: twg.gateway.link.1.initparam=* -socksv5addr 146.84.14.254 -socksv5port 1080 -socksv5userid myuserid -socksv5password mypassword If you wish to override the default server logon port (TCP 2033), replace the '*' with a new port number, and change the corresponding parameter in the \\data\TWGServer.prop file by adding the following line: twg.gateway.link.1.initparam= 3) Save the changes, and restart the console (and server, if the \\data\TWGServer.prop file was updated). Restricting Valid IP Addresses for Server Logon ----------------------------------------------- The Netfinity Director Server can be configured to restrict the IP addresses from which a logon from an Netfinity Director Console can originate. By default, an Netfinity Director Console can connect to an Netfinity Director Server from any address. By restricting the valid addresses to specific addresses and/or specific address ranges, the server can be made more secure. To restrict the acceptable IP addresses for console logon for a server, do the following: 1) Open the \\data\TWGServer.prop file with an editor 2) Add the following line: twg.gateway.link.1.initparam=* -allowedAddress
-allowedRange where
is an allowed IP address (dotted decimal or host name) is the lower bound of an IP address range of allowed addresses is the upper bound of an IP address range of allowed addresses The line can contain multiple '-allowedAddress' and '-allowedRange' clauses. If you wish to override the default server logon port (TCP 2033), replace the '*' with a new port number. 3) Save the changes, and restart the server If any allowed addresses and/or ranges are specified, then only consoles attempting to connect to the server from one of the allowed addresses will be able to connect. If an attempt to login from a console outside the range of valid IP addresses is attempted, providing a valid user ID and password will not result in an accepted logon. Netfinity Director Database Notes -------------------------- Netfinity Director server on Windows NT offers several database options. The default option uses the Microsoft Jet database. The Jet database allows storing the year portion of a date in either a 2-digit or 4-digit format. The ability to store the year in the 2-digit format will cause certain applications that check for Y2K problems to issue a warning about the database. This warning is not applicable to Netfinity Director's database, because the year stored by Netfinity Director is in the 4-digit format. DB2 Version 6.1 --------------- Netfinity Director 2.11 supports DB2 V.6.1. The required components of DB2 V.6.1 client that must be installed are: - Communications Protocols - ODBC Support - Java Enablement - System Bind Files Due to DB2 V.6.1 packaging considerations, the DB2 Run-Time Client CD does not contain bind files required by Netfinity Director to create a database. The bind files are shipped with the DB2 Administration Client CD. If you have the DB2 Run-Time Client installed, you must install the System Bind Files before attempting to install Netfinity Director. Using the DB2 Administration Client CD, install the system bind files by performing the following actions : - From the "Installation Type" screen, select the 'Custom' install option. - On the "Select Components" screen, select 'System Bind Files' and complete install. Once these actions have been completed, the system must be restarted before installing Netfinity Director Server. If Netfinity Director Server is installed using DB2 Run-Time Client without the System Bind Files options installed, Netfinity Director install will not be able to locate the bind files and will fail. If this problem is encountered and a new database is being created, uncatalog the database on the DB2 client and 'drop' the database on the server. Do not attempt to re-use the database name until you are sure all traces of the database have been removed. Then, using the DB2 Administration Client CD, follow the procedure outlined above to install the System Bind Files. After a restart of the system, uninstall Netfinity Director Server, restart the system, and re-install Netfinity Director Server. Copying or "Ghosting" the Netfinity Director Agent Image ------------------------------------------------- Machines with the Netfinity Director agent on them should not be used as a source machine when "ghosting" or copying it's image in order to set up other machines without doing the following procedures : - Remove the \Tivoli\Data\twgmach.id file from the system. - Within the registry, remove the value for the TWGMachineID key. Genevent /DEST Option --------------------- It is recommended that the user always use the @EventServer keyword in conjunction with the /DEST option when using Genevent. The @EventServer keyword automatically causes the event to be sent to all servers managing the system. Users wishing to use explicit addresses should be aware that the presence of multiple adapters may cause the sending of events to fail. The /DEST parameter will, however, accept the specification of an adapter ordinal as part of the protocol (e.g. NETBIOS3::TWGServer). Running the Windows NT Agent Under a User Account ------------------------------------------------- By default, the Windows NT agent executes under the "SYSTEM" (or "LocalSystem") account, which can result in some limitations due to the lack of network authentication possessed by this account. Specifically, programs executing under the "SYSTEM" account typically cannot access network shares (except those supporting "null" credentials) or other protected network resources. If the Director Agent, or programs executed by the agent, needs to be switched to use a user account, execute the following commands: net stop twgipc twgipcsv -install "" "" "" net start twgipc For the system's local accounts, use "." for the domain name. This command must be issued from an Administrator privilege account, and should refer to an Administrator privileged account (some Director Agent functions will not work correctly from a non-Administrator privilege account). This operation can be used to provide the following capabilities: - Have programs started by Process Manager execute under a network-privileged account by default - Have the Monitor agent and CIM browser gain access to CIM attributes of network objects (such as network drives) - Allow the File Transfer agent to access files on network drives Using Multicast in a Multi-adapter Environment ---------------------------------------------- If you want to use the Multicast function in a multi-adapter environment, the following information is important. The default configuration is to have the first logical interface, TCPIP, run as listen all. This means that we are talking to all the interfaces on only one port. When a multicast message is transmitted, it is transmitted only on that first logical interface. If a user wishes to have the multicast message transmitted on all adapters, the first adapter must be placed into isolated mode. To do so, follow these steps: 1. Stop twgipc by issuing, "net stop twgipc". 2. Create an ASCII file, tcpip.ini, with the following two lines in them: ISOLATED=1 LEGACY = 1 3. Copy this file into the //data/ directory. 4. Restart twgipc by issuing the command, "net start twgipc". If you are running SNA/APPC on Windows 95/98 agents you must modify the Network Time-Out from 15 to 35 seconds in the Network Driver Configuration. NetBEUI Interface ----------------- Special note for Windows NT, 95 and 98 users: The Netfinity Director uses NetBEUI to get the MAC Address for calculating the machine's unique ID, which identifies the agent or server to other servers. Netfinity Director uses the NetBEUI interface to retrieve this information from the operating system. Netfinity Director will still work without this interface installed, but a delay of 2 to 10 minutes may occur. Most Windows NT or 95/98 installs will have the NetBEUI interface installed by default when networking is enabled. Presence Check -------------- The Presence Check utility is designed to establish whether a device is on-line or off-line. The Presence Check can take as long as the network timeout setting to complete. A Presence Check only changes the icon displayed for a managed system if that system is in a different state than the one shown. Padlock in Group Contents ------------------------- In the Group Contents pane, if a system is showing up with a padlock icon, then the server that you are using cannot manage it (and/or another server has secured it). This also means that Inventory information will not be collected on the system, and the system will not show up in any custom dynamic groups. The user may request access to the system by: -Right clicking the icon and selecting Request Access -Provide a valid user id and password when prompted. Storing System User and System Location Data -------------------------------------------- The System User and System Location data for each system must be saved in an ASCII file, TWGUSER.INI in order for it to be read from Netfinity Director's Inventory Browser. There is an empty TWGUSER.INI file on all of your Netfinity Director agents. It can be found in the following directory (depending on the operating system): - Windows NT: \\bin - Windows 95: \\bin - Windows 98: \\bin - OS/2: \ To edit the values in the file, enter the data after the = sign. You will be able to view and use the data after saving the file, and the next inventory collection is performed. Note: if you move this file to another directory, your changes will not be seen by Netfinity Director, and will not appear in the Inventory Data. View...Find Searches Expanded Branches -------------------------------------- In the Resource Monitor console, the View...Find in Available Resources menu option only searches the branches of the attribute trees that have been expanded. If you get a "No match found" error, this either means that there is no attribute which matches the string, or the attribute is on a branch that has not been opened. Viewing Statistics for an Agent ------------------------------- The following apply when you use the Resource Monitor task to view statistics for an agent: - Under Memory Monitors, the Locked Memory and Memory Usage attributes are shown in megabytes, for example, 23.8 indicates 23.8 megabytes. - Under Disk Monitors, the Space Remaining and Space Used attributes are in megabytes, while the Disk Workload attribute is an averaged value of the total megabytes per second of read and write I/O activity. - For OS/2 agents, under OS/2 Swapfile Monitors, the Swap file size and Swap space remaining attributes are shown in megabytes. Socks Client Setup ------------------ If you set up your socks client to access ALL addresses through a SOCKS server, Netfinity Director may have no way of detecting, at the socket level, that you are going through a SOCKS server and you may see slightly inappropriate messages. Online Help ----------- Netfinity Director is based on Tivoli IT Director technology. The online documentation will indicate those functions that are available in IT Director but not in Netfinity Director. A message "object not found" from the online help means that the file containing the help information could not be found. Resizing a help window can cause spacing inconsistency in the help text. Select the Reload button to correct the spacing. Some help windows may blink several times as the help text is being loaded. If the blinking continues, select the Reload button to stop the blinking. Selecting Reload will reset to the beginning of the help window. Screen Resolution ----------------- The minimum recommended screen resolution for properly formatting Netfinity Director windows is 800x600. Software Dictionary Matches --------------------------- The Software Dictionary finds a match for an entry definition only if all associated files for the entry are in the same directory. To locate product suites (such as Microsoft Office) that may not have all applications in the same directory, you can create separate entry definitions for each application in the suite and then create a dynamic group to show all systems found with the specified application files. Use the following steps to create separate entries and a dynamic group: 1. In the Tasks pane of the Management Console, right click on Inventory to display the context menu, then select Edit Software Dictionary to display the Inventory Software Dictionary Editor window. 2. Select File -> New to create a new entry for each associated file that is located in a separate directory. 3. Use the Title and Entry Type fields to identify and classify each entry you create in the inventory software dictionary. You can also fill in the other fields as needed. 4. Below the Associated Files pane, select Add then click OK to specify the file. You are prompted to enter the filename manually or select the file using the file dialog. It is recommended that you use the file dialog to select the file. When you finish selecting the filename, the corresponding attributes are displayed in the Associated Files pane. 5. Select Edit to change any of the attributes. 6. Click on the Diskette icon in the toolbar section of the window to save your entry. You have now created one entry identifying the file (or set of files, if you specified more than one file) corresponding to one application in a single directory. 7. Repeat steps 2-6 for each software dictionary entry you want to create, then click File -> Close to exit the window. 8. In the Groups pane of the Management Console, right click anywhere except on an entry to display the context menu, then select New Dynamic. 9. In the Available Criteria pane of the Dynamic Group Editor window, select Inventory -> Software -> Program Title to display the list of entries from which you can create a new dynamic group. 10. Locate and select the first entry you created and select Add to add the entry to the Selected Criteria pane. 11. Locate the second entry you created and select Add to add it to the Selected Criteria pane. Because multiple entries have been selected, you are prompted by the Choose Add Operation dialog. Select All true (AND) to create a group that applies only if all of the entries you selected are located. 12. Locate and add the rest of the entries you created. For each subsequent entry you add to the Selected Criteria pane, select the "All true (AND)" option when prompted. 13. When you have finished building your group of entries, select File -> Save As from the menu bar and enter the name you want to display in the Groups pane of the Management Console. 14. Close the window and click on your new group in the Groups pane of the Management Console. The agents that meet the search criteria for the software entries you created are displayed in the Group Contents pane. In this case, all entries have to be present on the agent for the agent to be displayed. Automatic Reboot Unattended Installation of an Agent ---------------------------------------------------- Netfinity Director Version 2.11 provides a reboot parameter that enables you to automatically reboot an Netfinity Director managed system (agent) as part of an unattended installation. For unattended installations on Windows platforms, specify reboot after the unattended argument, for example: twgsetup unattended reboot The following example applies to an Netfinity Director managed system that is installed on OS/2: install /R:c:\diragent.rsp reboot NEC PC 9821 Hardware Inventory Support -------------------------------------- Hardware inventory for NEC 9821 systems has the following limitations : - Hardware inventory can collect only keyboard and mouse information for NEC PC9821 Windows 9x agents. - "Interface Type" of mouse is "PS/2" for NEC PC9821 NT 4.0 agents. Action History on the Event Action Plan Builder ----------------------------------------------- The default for Action History log has been changed from 'enabled' to 'disabled'. System Variables within the Event Action Plan Builder ----------------------------------------------------- 'View System Variables' is a new dialog that can be accessed from the 'View' menu in 'Event Action Plans' or 'Event Action Plan Builder'. All the defined System Variables and their values can be viewed as a list in this dialog. To set a System Variable to a different value, first you must select it in the list. Then type in the new value in the input field below the list. Press the 'Update' button when complete. The value in the list should reflect this change. Hidden Columns on Resource Monitor Console ------------------------------------------ After columns have been hidden on the resource monitor console, they can be redisplayed by closing the console and reopening it. Third Party Agent Support ------------------------- Netfinity Director supports several types of third party agents. These agents are developed by organizations other than Tivoli and ship separately from Netfinity Director. These include SNMP, CIM, DMI, and MPM agents. All of these architectures have their own definitions for dealing with text translations. Netfinity Director makes every attempt to exploit those mechanisms whenever possible; however, there are some instances where the expected results may not occur. The following are known restrictions : SNMP Version 1 by definition only supports the 8859-1 character set. This limits the supported languages to those that can be described using that code page. 8859-1 is a single byte character set; therefore, there is no support for Unicode nor DBCS languages. SNMP has no concept of multi-lingual response support. The agent can only respond in its installed language. The CIM standard supports Unicode and is capable of returning text from different languages assuming the translation support is installed on the agent. If a specific language is not installed on the target agent then the CIM agent will respond with its default language, which in most cases is English. At this point in time, the existing CIM agents ONLY respond in English. This limitation is due to early development stages of CIM. DMI supports multi-lingual responses. It supports both 8859-1 and Unicode. Netfinity Director will ask the DMI agent to respond with the appropriate language/code page; however, its ability to respond to that request is limited by its installation. If the corresponding language version support of DMI was not installed, it cannot return the appropriately translated information. Tivoli Management Agents and the NFD Console -------------------------------------------- Systems with the NFD Console and Tivoli Management Agent installed (but no NFD Agent) will NOT have the NFD Agent pushed to them. Customers who wish to have the NFD Agent installed on these systems should perform the manual installation of the NFD Agent when installing the NFD Console. *************************************************************** 2.11-6. Documentation Updates *************************************************************** Inventory Table Addition ------------------------ In Appendix F, "Defining Table Property Files for CIM, DMI, and MIF Data", under section Table Property File Format, a Note should be added under column.X.key : NOTE: This value must be true for one or more columns if multiple rows of data are returned by the managed system. Failure to specify a unique key, made up of one or more columns with column.X.key=true, for the row will result in only one row being stored in the database even though multiple rows of data were returned by the managed system. Also in Appendix F, under the section NLS File Format, the following example is provided: To specify the filter prompt string for "Each True For At Least One" FilterTablePrompt.EachTrueForAtLeastOne.TWGDbUserTable?tableTokenName= translated string for "all true" for this table. In this example, "all true" should be corrected to read "each true for at least one". *************************** End of File ******************************