Applies to IBM Suite, IBM Enterprise Suite APAR IC24355 TITLE: Inventory Scanner Update PRODUCT: LANDesk(R) Management Suite 6.1 COMPONENT: Inventory REVISION: I DATE: 22-Mar-99 ------------------------------------------------------------------------ INTEL TERMS AND CONDITIONS: The copyright laws of the United States and international copyright treaties protect the software files enclosed in this self-extracting file ("FILE"). This FILE contains software files that are intended to replace or otherwise run with commercially available versions of Intel software products. You may, without charge, use copies of the files contained within the FILE for their intended purposes to update legally obtained, commercially available Intel software; provided you do NOT (1) distribute the FILE in any form, as part of, or in combination with any other software or hardware product without the prior written consent of Intel Corporation, (2) change or omit any proprietary rights notice appearing on or in the FILE. EXCEPT AS RESTRICTED BY LAW, THE SOFTWARE PROGRAMS CONTAINED IN THE FILE ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, TITLE OR FITNESS FOR A PARTICULAR PURPOSE. ------------------------------------------------------------------------ ABSTRACT: THIS ARCHIVE CONTAINS FILES WHICH HAVE NOT BEEN FULLY REGRESSION TESTED BY INTEL. THE ISSUES OUTLINED IN THIS TEXT HAVE BEEN CORRECTED AND TESTED, AND THE FILES IN THIS ARCHIVE ARE FULLY SUPPORTED BY INTEL, HOWEVER, THEY ARE CONSIDERED "PRE-SERVICE RELEASE." INTEL MAKES NO WARRANTY AS TO PROBLEMS ARISING AS A RESULT OF INSTALLING THESE FILES. Resolves several issues and enhancements to the inventory scanners for LANDesk(R) Management Suite 6.1. This file replaces SC61_3 and includes updates to SC61_3. ------------------------------------------------------------------------ CONTENTS: BIOS.DOC 12,935 17-Jun-98 02:33p ENUCST16.DLL 8,208 21-Jul-98 02:06p ENUCST32.DLL 47,104 21-Jul-98 01:51p FIXMEM.SQL 1,084 07-Jul-98 04:01p INV16.EXE 119,808 14-Oct-98 03:09a LDCSTM16.EXE 109,264 21-Jul-98 03:22p LDCSTM32.EXE 52,736 17-Jul-98 04:05p LDISCAN.EXE 268,920 14-Oct-98 02:05a LDISCAN2.EXE 154,271 22-Oct-98 11:38a LDISCN32.EXE 251,904 14-Oct-98 11:05p WLDISCAN.EXE 298,496 14-Oct-98 03:22a YGREP32.DLL 72,704 05-May-98 11:23p YGREPD16.DLL 45,008 27-May-98 04:17p In order to properly implement patches, we have changed our date/time stamp on update files. Because of this, you may find that this file has an older date than what is currently on your system. Please verify the revision number instead of the date when applying the patch. ------------------------------------------------------------------------ CHANGES Changes from SC61_3 to SCANNER: Updated LDISCAN.EXE, WLDISCAN.EXE and INV16.EXE. Changes from SC61_2 to SC61_3: Update LDISCN32.EXE. Changes from SC61_1 to SC61_2: Updated LDISCAN.EXE, INV16.EXE, WLDISCAN.EXE and LDISCAN2.EXE. ------------------------------------------------------------------------ INSTALLATION INSTRUCTIONS: 1. Copy LDISCN32.EXE, INV16.EXE, YGREP32.DLL, LDISCAN.EXE, WLDISCAN.EXE, YGREPD16.DLL, LDISCAN2.EXE, ENUCST16.DLL, ENUCST32.DLL, LDCSTM16.EXE and LDCSTM32.EXE to the LDLOGON directory of the core server. 2. Edit the client configuration .INI and .IN# files to copy YGREP32.DLL and YGREPD16.DLL to clients. These files on Client Deployment Service Centers will also need to updated, either by reconfiguring them or copying the files to them. The following line needs to be added to the NTSTACFG.INI and NTSTACFG.IN# files: (NOLOGON)FILE16=YGREP32.DLL This needs to be added to the [Inventory Scanner Files] section. The following line needs to be added to the 95STACFG.INI and 95STACFG.IN# files: (NOLOGON)FILE17=YGREP32.DLL This needs to be added to the [Inventory Scanner Files] section. The following line needs to be added to the CLNTCFG.INI and CLNTCFG.IN# files: ADDFILE12={%DTM_LDCLIENT_DIR}\LDCLIENT, YGREPD16.DLL This needs to be added to the [INV:16TONW] and [INV:16TONT3] sections. This will enable the new YGREP32.DLL file to be copied to clients when they are configured and to Service Centers. 3. For the new BIOS scanning to take effect, you will need to download Revision 8.07a or later of the LDAPPL.INI and copy it to the LDLOGON directory of the core server and all Service Centers. For instructions on how to edit this new [BIOS Info] section of the LDAPPL.INI, see BIOS.DOC enclosed in this patch file. 4. Either copy the files to the clients, or reconfigure them. 5. After all clients' scanners have been updated that point to the core server, execute FIXMEM.SQL. This is an SQL script that will correct a problem where the class MEMORY was used in 2 different locations by the scanners, which is not allowed by the database. As always, backup your database before performing any maintenance, as Intel is not responsible for any damage caused by this BETA script. It is possible to run this script repeatedly if an older scanner sends the information after the script has been run once. ------------------------------------------------------------------------ SYMPTOMS ADDRESSED: Symptom On computers with a network adapter that supports DMA, an invalid scan file would be generated. Solution Apply WLDISCAN.EXE, INV16.EXE and LDISCAN.EXE dated 14-Oct-1998 or later. Symptom On a computer with a NetBIOS layer loaded, but not a complete NetBIOS layer, the scanner would generate an error. The error would occur even if you did not want the scanner to run on NetBIOS. Solution Apply LDISCAN.EXE dated 14-Oct-1998. Symptom On Computers with a Modem and a Port of Unknown, a second modem listed as %d would be created in the inventory. Solution Apply LDISCN32.EXE dated 14-Oct-98. Symptom On Compaq computers without DMI, the Firmware Revision was not correct. Solution Apply LDISCAN.EXE dated 14-Oct-1998 or later and WLDISCAN.EXE and INV16.EXE dated 21-Oct-98 or later and LDISCAN2.EXE dated 14-Oct-98. Symptom On computers with certain versions of Matrox video drivers, the scanner would Dr. Watson. Solution Apply LDISCN32.EXE dated 14-Oct-98. Symptom On Compaq computers with DMI installed, the system name of the computer (e.g. Compaq Deskpro 4000) would not be correctly retrieved. Solution Apply LDISCN32.EXE dated 14-Oct-98. Symptom In certain circumstances, CDROM information was not being correctly retrieved. Solution Apply LDISCN32.EXE dated 14-Oct-98. Symptom Dell specific information, such as Serial Number, was not being retrieved. Solution Apply LDISCN32.EXE dated 15-Sep-1998 or later. This information is gathered via DMI, so the DMI service layer and a DMI BIOS must be installed on the computer. Symptom If a directory was close to the limit (about 80 characters), the scanner would incorrectly generate the software package information in the scan file. These invalid fields would cause the DataMart utility not to move any Software information. Solution Apply LDISCAN.EXE dated 27-Aug-1998 or later. Symptom If the scanner is run from a Windows NT logon script on Windows 95, the login name field is not filled in correctly. Solution Apply LDISCN32.EXE dated 14-Oct-98 and INV16.EXE dated 22-Jul-1998 or later. Symptom On Windows 95 computers with a Dial-Up Adapter and regular network adapter installed, the scanner would report the MAC address as the Dial-Up Adapter address instead of the network adapter MAC address. Solution Apply LDISCN32.EXE dated 14-Oct-98. One side-effect of this is that computers that have no network card will still show as having a NIC Address, although no other Network information will be present. Symptom The Intel Inventory Server service would unload with the following error in the Event Log: Violation of UNIQUE KEY constraint 'UQ_LD_MASTERATTRIBUTE_1__10': Attempt to insert duplicate key in object 'LD_MASTERATTRIBUTE'. Command has been aborted. . Cause The OS/2 inventory scanner was sending a scan file that had incorrect syntax. This would only happen on computers with an EISA motherboard and at least one EISA card. Solution Apply LDISCAN2.EXE dated 14-Oct-98. Symptom It is possible for a user to cancel out of the Custom Forms application without filling out forms. Solution Apply LDCSTM32.EXE dated 17-Jul-98 or later and ENUCST32.DLL dated 21-Jul-98 or later for Windows 95 or Windows NT computers. For Windows 3.x, apply LDCSTM16.EXe and ENUCST16.DLL dated 21-Jul-98 or later. There is also a new switch that needs to be used. To not allow the user to close the form without filling it out, use the /FE switch. Symptom If a network card is scanned that uses shared memory, a class name of Memory would be created under Network - Shell Driver. If you then looked at certain dialogs in the management console, such as the query dialog, the class Memory and class Network - Shell Driver - Memory would share all of the same attributes and sub-classes. Cause It is invalid for the inventory database to have duplicate class names, so the Network - Shell Driver - Memory class has been renamed to Network - Shell Driver - SD Memory. Solution Apply LDISCAN.EXE, INV16.EXE and WLDISCAN.EXE dated 07-Jul-98 or later. Also execute FIXMEM.SQL after all of the clients' scanners that point to this database have been updated. Symptom If LDISCN32 is run and the BIOS text string file does not exist, the scanner would Dr. Watson. Solution Apply LDISCN32.EXE dated 14-Oct-98. Symptom If LDISCN32 is run and the INV16.DAT file is not available and certain information is in the LDAPPL.INI file, the scanner would Dr. Watson. Solution Apply LDISCN32.EXE dated 14-Oct-98. Symptom On Windows 95 computers, most frequently with Toshiba laptops, the scanner would GPF in MFC42.DLL or KERNEL32.DLL. Solution Apply LDISCN32.EXE dated 14-Oct-98. Symptom The 32 bit Windows scanner would not retrieve the ROM Family field from Compaq BIOSes. This item is needed to determine Year 2000 Compatibility. Solution Apply INV16.EXE dated 15-Jun-98 or later. Symptom Certain BIOS information, such as BIOS version, is usually not retrieved. Cause Many items of BIOS information, such as BIOS version, are not available with standard BIOS function calls. Most BIOS vendors, and hardware manufacturers, store this information differently, if it is stored at all. Solution Apply LDISCN32.EXE dated 14-Oct-98 and INV16.EXE dated 15-Jun-98 or later, LDISCAN.EXE dated 23-Jun-98 or later, or WLDISCAN.EXE dated 25-Jun-98 or later and YGREPD16.DLL dated 27-May-98 or later . Also get Revision 8.07a or later of the LDAPPL.INI file. Symptom LDISCN32 could not be used reliably in an environment where multiple users run it from the same directory. Cause A component of the 32 bit scanner, INV16.EXE which scans for certain BIOS information Windows NT will not let a 32 bit application access, creates a temporary file always called INV16.DAT. If multiple users ran LDISCN32 from the same directory at the same, incorrect information could be added to the scan for one of the systems. Solution Apply LDISCN32.EXE dated 14-Oct-98 and INV16.EXE dated 15-Jun-98 or later. Symptom When logging into NetWare and running the scanner via the login script on Windows 95 with Novell Client 32, the login name field would be blank. Cause LDISCN32 used a Windows call to determine what the user's login name is. With Client 32 this could would not work correctly during the login process, but would work fine after the user had finished logging in. Solution Apply LDISCN32.EXE dated 14-Oct-98. Symptom Certain configuration files would not appear in the database. Typically, all but one of the configuration files scanned for would be in the database. Solution Apply LDISCAN.EXE dated 23-Jun-98 or later. Symptom The LDISCAN.CFG file, containing the DEVICE ID of the computer, could only be located at C:\. This meant that any machine that could not write to C:\, such as if the drive did not exist or the user did not have rights to, would generate a new DEVICE ID everytime the scanner is run. This would cause a new entry in the database for the same computer. Solution Apply LDISCN32.EXE dated 14-Oct-98. A new option was added to the command line for the scanner, /E=. The environment variable points to the path, drive letter and directory, where the LDISCAN.CFG file is to be kept. For example, on a Windows 95 computer a statement is added to the AUTOEXEC.BAT that is SET LDMS=F:\USERNAME, indicating that the LDISCAN.CFG for this machine should be located in the F:\USERNAME directory. The command line for the inventory scanner would now include /E=LDMS. If there is no /E used, then the scanner will default to C:\ for the location of LDISCAN.CFG. ------------------------------------------------------------------------ TRADEMARKS LANDesk is a registered trademark of Intel Corporation. *Other products and corporate names may be trademarks of other companies and are used only for explanation and to the owners' benefit, without intent to infringe. Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein.