README IBM LCCM Version 2.5.1 for Windows NT Server 4.0 --------------------------------------------------------------------------- This document contains important information on installing IBM LCCM version 2.5.1. It includes essential information for users upgrading from earlier versions. You should read this document and follow the instructions carefully. LCCM Forum: For new and advanced users of LCCM, an LCCM Forum Website is available. This Forum is monitored by IBM personnel and will discuss and answer many of the common questions relating to LCCM and its implementation. The Forum is accessible from the LCCM home page at: http://www.pc.ibm.com/us/desktop/lccm/index.html Specified Operating Environments: The specified operating environments for LCCM are those supported by the compatibility test results for a variety of hardware and software combinations. The test reports are accessible from the World Wide Web at http://www.pc.ibm.com/us/desktop/lccm/index.html. This Web Page will be updated as additional test cases are completed. IMPORTANT: Before using LCCM, check the compatibility test results and browse the rest of the LCCM Web Site for additional information and tips concerning the installation and use of LCCM. Pre-install Considerations: Before continuing, review the latest installation notes for changes or tips on the World Wide Web at: http://www.us.pc.ibm.com/desktop/lccm/index.html. It is recommended LCCM be used with supported Network Adapter Cards only. Should you wish to utilize the IBM 10/100 Etherjet PCI adapter with Wake-on-LAN in Docking Stations, then you must re-flash this adapter with the latest ETPFLSH2.EXE V3.10 boot disk. This updated microcode can be obtained from the World Wide Web at http://www.networking.ibm.com/support and is located under 'IBM 10/100 Etherjet PCI Management Adapter'. We recommend that you update your Thinkpad systems to the latest BIOS level with microcode obtained from the ETPFLSH2.EXE V3.10 page. For the latest listing of Network Adapter cards supported by LCCM 2.5.1 see :\LCCMINST\CLNTFILE\NETWORK.LST This is because LCCM will automatically scan and therefore only recognize and configure supported Network Adapter cards. To use unsupported cards you will have to make the necessary correct entries into both NETWORK.LST and LCCM's Default Directory files according to your Card Manufacturers documentation. This is particularly important for an Unattended NT Install. For further details see the Training and Procedures Guide "Installing Network Adapter Device Drivers". If you have a non-IBM device that is on Windows 95, Windows 95 OSR2 or Windows 98 Hardware Compatibility List then the device can be auto-detected by the Windows operating system. Alternatively you can edit the answer file (.LCA) which you can find at :\LCCM\CLNTFILE\DEFAULTS\XXXX.LCA and for example add the line "netcards=" to install a network adapter card. Note: LCCM does not support dual Ethernet and Token Ring environments. Server Prerequisites: 1. Windows NT Server 4.0 - Service Pack 4, must be installed on your server. You can obtain Service Pack 4 directly from the "downloads" section of the Microsoft NT Server homepage (http://www.microsoft.com/ntserver), or you may obtain it from your Microsoft supplier, or from the IBM Server Guide CD set. It is recommended that NT Server 4.0 and Service Pack 4 be installed on a primary DOS partition of at least 512Mb, with LCCM 2.5.1 installed on a secondary partition. The reason for installing LCCM on a secondary partition is to allow sufficient disk space for copying operating system images to your server. 2. If you intend to use LCCM to install operating systems on your clients, such as Windows NT 4.0 Server, Windows NT 4.0 Workstation, Service Packs ( e.g. Service Pack 4 for Windows NT 4.0), Windows 98, Windows 95 OSR2 or Windows 95, you need to reserve sufficient hard disk space for LCCM to make images of the applications you want to install. It is recommended that you allow a minimum partition size of 512Mb for each operating systems, including service packs and applications. 3. It is recommended that the file system on your server be configured as NTFS. This allows you to ensure the security of your server directories. 4. The server's computer name cannot contain embedded spaces. 5. The minimum physical memory requirement for an LCCM Server is 128Mb. 6. The recommended default pagefile size is 129MB (RAM plus 1MB). To change your default pagefile size: a) In Windows NT's Control Panel, double-click on System. b) Click on the Performance Tab. c) Under Virtual Memory double-click on the Change button. d) Then specify your pagefile size. e) Press OK. 7. When processing or scanning, LCCM requires two Windows NT licenses for each client computer being processed concurrently. You will be asked to provide the number of licenses required during the Windows NT Server installation. 8. If you intend to use DHCP/PXE clients, the available IP addresses must be equal to, or exceed, the maximum number of potential LCCM clients. Set Lease times to periods longer than the longest processing function of LCCM (potentially a large image download). You can limit the number of clients that will be processed at any single time within the LCCM program from the Processing page of the LCCM Defaults notebook. To add additional Windows NT licenses, use the Windows NT License Manager feature, which is accessible through the Administrator Tools (Common) Program. 9. The DLC (for RPL), NetBEUI (for RPL) and TCP/IP (for RPL or DHCP/PXE) Protocols must be installed as appropriate. Also, if you intend to install LCCM RPL support, the Remoteboot Service must be installed and the Fix Security program must be run. To install these, carry out the following: a) From the Windows NT Control Panel, double-click on Network. b) Click on the Protocols tab and verify that the following protocols are installed: DLC Protocol NetBEUI Protocol TCP/IP Protocol If any of these protocols are missing, add them now. c) Click on the Adapters tab and verify that you have records for all adapters you will be using in your server. d) Click on OK to close the Network Window. If you receive a message to restart Windows NT, click on No; DO NOT RESTART it at this point. e) From the NT Control Panel, select Services. f) Highlight Remoteboot Service. g) Click on Startup. h) In the Startup box, click the Automatic radio button. i) Click on OK. j) Click on Start to start the Remoteboot Service. k) Close the Services window. l) Shut down and restart Windows NT Server. 10. Use the following procedure to start Remoteboot Manager and verify that the Remoteboot Service has been installed and configured correctly. This step is provided to verify the correct operation of the Remoteboot Service, which is required to operate RPL clients. First ensure your client computers are configured as RPL clients. To configure client computers with onboard BIOS, as RPL clients do the following: a) Enter your client computers BIOS by pressing F1. b) Select Automatic Power Management by using the up and down arrow keys. c) Select Automatic Power On. d) Select Wake On LAN. e) Ensure Wake On LAN is enabled, instructions on how to change options are given at the bottom of the screen. f) Press the Escape button to exit. g) Select Startup Options. h) Select Startup Sequence. i) Ensure that your first drive has been enabled as Network, your second drive as Floppy and your third drive as Hard Disk. Instructions on how to change options are given at the bottom of the screen. j) Press Escape to exit the BIOS after saving the changes or new settings as appropriate. Note: that if your BIOS is integrated in a Network Card, you will have to ensure that you have the correct BIOS, you may have to use your Flash BIOS diskette for this (refer to your card manufacturers documentation). Your Flash BIOS diskette will also allow you to change the configuration for your BIOS to RPL, select the appropriate option from the menu. To connect one or more client computers to the LAN and start them. a) From the Windows NT desktop, open a DOS Window and start Remoteboot Manager by typing RPLMGR. b) The Remoteboot Manager starts. If you are instructed to create a Profile, click on OK to continue. For each client computer attempting to RPL, you will see the MAC address displayed in the column labeled Workstation Name, there will be nothing in the In profile column, and each MAC address will have information in the Description column. If this is the case, the Remoteboot Service has been correctly installed. c) From the Remoteboot Manager task bar, select Configure, then click on Fix Security, answer Yes to the resulting pop-up message. d) From the Remoteboot Manager task bar, select Configure again, and then click on Check Configurations. Answer Yes to the resulting pop-up message. e) Close (do not minimize) Remoteboot Manager. You are now ready to install the IBM LCCM program. -------------------------------------------------------------------------------------------- Upgrading from Version 1.0 or 1.1: Upgrading to version 2.5.1 from either version 1.0 or 1.1 is not supported. You must remove all earlier versions of LCCM before installing version 2.5.1. To uninstall your current version of LCCM, carry out the following steps: * Uninstall Previous Versions of LCCM 1. This first step is only required if you are uninstalling/re-installing version 2.0 of LCCM. Earlier versions (1.0, or 1.1) do not use the Intermediate Support Driver. From the Windows NT Desktop, click on the Start button and select Settings -> Control Panel -> Network -> Protocols. Highlight the IBM Intermediate Support Driver and click on Remove. 2. From the Windows NT Desktop, click on the Start button and select Settings -> Control Panel -> Add/Remove Programs. Highlight LANClient Control Manager and click on the Add/Remove button to uninstall the program. LCCM and all of its installed components will be removed from your system. When asked if you want to remove shared files, click on Yes. The existing folder where you originally installed the product will not be deleted. This is because the folder will still contain some user-created data-files. Make sure you have these files saved in a separate folder and then delete the original LCCM installation folder, and all sub-folders and remaining files. Upgrading from Version 2.0: Note: only version 2.0, build 297uw.nt can be successfully upgraded to Version 2.5.1. From the main menu, click on Help -> About. The build level will then be displayed on the Title bar of the Welcome screen. After ensuring that your current version of LCCM 2.0 is installed and working properly on your LCCM Server and that there are no current versions of LCCM 2.0 running on your Server or on Remote Consoles connected to your LCCM Server. 1. Run the SETUP.EXE program, which you will find in the :\LCCMINST\NT Directory, where LCCMINST is the temporary LCCM install directory you created after downloading and uncompressing LCCM 2.5.1. At the Welcome Screen press Next -> Select a language option and press Next -> Accept the IBM License Agreement by selecting I Agree -> Select Perform Server installation (including workstation files) as it is the only option currently supported. 2. The Previous Detected Version screen displays whether you have LCCM version 2.0, build 297uw.nt installed: If you do not have the supported version of LCCM 2.0, error messages giving the version of LCCM currently installed and the appropriate course of action will be displayed. 3. The Location of Backup Files screen displays the path and BACKUP directory of copied control files from your LCCM 2.0 installation. If you made changes to default .LST files in your LCCM 2.0 installation (e.g.Network.lst), check whether these changes are required in the corresponding LCCM version 2.5.1 files, as LCCM 2.5.1 supports a wider range of hardware. 4. At the Installation complete screen press OK to confirm that the upgrade has completed successfully. 5. If you used the IBM DHCP service with LCCM 2.0, you must now upgrade the IBM Intermediate Support Driver. To install IBM's Intermediate Support Driver do the following: a) From the Windows NT desktop, click on Start, Settings and Control Panel. b) Double-click on Network. c) Select the Protocols tab, click on Add and then Have Disk. d) In the Path box, enter :\LCCMINST\NT\WEDGE and then click on OK. e) The Select OEM Option box will be displayed. The IBM Intermediate Support Driver will be highlighted. If not (you have entered the wrong pathname), check the pathname you entered in step d and retry. Click on OK to install this driver. You will be returned to the Network Setup window. Click on Close to exit. f) Shutdown and restart your server at this point. The new driver will be loaded as the server restarts. Upgrading from version 2.5: Note: only version 2.5, build 990119 can be successfully upgraded to Version 2.5.1. From the main menu, click on Help -> About. The build level will then be displayed on the Title bar of the Welcome screen. After ensuring that your current version of LCCM 2.5 is installed and working properly on your LCCM. Server and that there are no current versions of LCCM 2.5 running on your Server or on Remote Consoles connected to your LCCM Server. 1. Run the SETUP.EXE program, which you will find in the :\LCCMINST\NT Directory, where LCCMINST is the temporary LCCM install directory you created after downloading and uncompressing LCCM 2.5.1. At the Welcome Screen press Next -> Select a language option and press Next -> Accept the IBM License Agreement by selecting I Agree -> Select Perform Server installation (including workstation files) as it is the only option currently supported. 2. The Previous Detected Version screen displays whether you have LCCM version 2.5, build 990119 installed: If you do not have the supported version of LCCM 2.5, error messages giving the version of LCCM currently installed and the appropriate course of action will be displayed. 3. The Location of Backup Files screen displays the path and BACKUP directory of copied control files from your LCCM 2.5 installation. If you made changes to default .LST files in your LCCM 2.5 installation (e.g.Network.lst), check whether these changes are required in the corresponding LCCM version 2.5.1 files, as LCCM 2.5.1 supports a wider range of hardware. 4. At the Installation complete screen press OK to confirm that the upgrade has completed successfully. 5. If you used the IBM DHCP service with LCCM 2.5, you must now upgrade the IBM Intermediate Support Driver. To install IBM's Intermediate Support Driver do the following: a) From the Windows NT desktop, click on Start, Settings and Control Panel. b) Double-click on Network. c) Select the Protocols tab, click on Add and then Have Disk. d) In the Path box, enter :\LCCMINST\NT\WEDGE and then click on OK. e) The Select OEM Option box will be displayed. The IBM Intermediate Support Driver will be highlighted. If not (you have entered the wrong pathname), check the pathname you entered in step d and retry. Click on OK to install this driver. You will be returned to the Network Setup window. Click on Close to exit. f) Shutdown and restart your server at this point. The new driver will be loaded as the server restarts. Installing IBM LCCM Version 2.5.1: 1. Download the IBM LCCM compressed file from http://www.pc.ibm.com/us/desktop/lccm/index.html, to your Windows NT machine. 2. Uncompress the downloaded file to a temporary directory (e.g. D:\LCCMINST) that you have created. 3. If you intend to install LCCM using DHCP/PXE you must install IBM's Intermediate Support Driver now. To install IBM's Intermediate Support Driver do the following: a) From the Windows NT desktop, click on Start, Settings and Control Panel. b) Double-click on Network. c) Select the Protocols tab, click on Add and then Have Disk. d) In the Path box, enter :\LCCMINST\NT\WEDGE and then click on OK. e) The Select OEM Option box will be displayed. The IBM Intermediate Support Driver will be highlighted. If not (you have entered the wrong pathname), check the pathname you entered in step d and retry. Click on OK to install this driver. You will be returned to the Network Setup window. Click on Close to exit. f) Shutdown and restart your server at this point. The new driver will be loaded as the server restarts. 4. Run the SETUP.EXE program, which you will find in the :\LCCMINST\NT \ Directory. 5. The LCCM Installation program will begin and the Welcome to the LANClient Control Manager Setup Program screen will be displayed. Select Next to continue with the setup program or Cancel to exit from the setup program. 6. Select the language option that you want to use and then select Next. 7. If you accept the terms and conditions of the license agreement, select I Agree to continue with the setup program. 8. Select the installation environment for your LCCM installation. Select Perform Server installation (including workstation files) if you want to install the server component of LCCM. Select Perform Remote Workstation installation only if you want to install the administrator's console component. You must have a current and working LCCM Server present on your network, for your remote console to work, and because you will be asked to enter the name of your LCCM Server. 9. Select the type of LCCM installation you want to install. There are two ways to install the LCCM program; typical or custom. A typical installation will install LCCM according to defaults based on information that the LCCM setup program has detected about your computer. A custom installation will step you through every decision that LCCM requires for a successful installation. At this point you have some decisions to make: a) If you select Perform Server installation (including workstation files) you will then have the option of selecting either a Typical installation or a Custom installation. Select this option if you are using the server's keyboard and monitor as the administrator's console (See Custom Installation and Typical Installation from the Training & Procedures Guide). b) If you select Perform Remote Workstation installation only, LCCM will lead you through the installation. Select this option if you want to run LCCM on a client computer (See Installing LCCM on Another Computer and Remote Workstation Installation from the Training & Procedures Guide). You must also make sure that the prerequisites below are followed: * LCCM must already be installed on the server using all required functions (DHCP/PXE support, RPL support, or both). * Do not re-install IBM DHCP/PXE Support during the Perform Remote Workstation Installation option. This support will already be operating on your server. * Remember that you must be logged on with administrator privileges in order to install the product. ----------------------------------------------------------------------------------------------------- Training & Procedures Guide: It is strongly recommended that you print off and consult the Training and Procedures Guide that you have downloaded along with LCCM 2.5.1. In particular please read Chapter 2 Installing LCCM in conjunction with this README.TXT for complete details about installing and running LCCM. After Installing LCCM: If you are using LCCM with RPL clients (this is not necessary for DHCP/PXE clients), for every type of adapter you are using on your LAN, you must add an identifying line to the file :\LCCMINST\NETWORK.LST. This file is used by LCCM to store information about adapters on your LAN. For additional information, see "Installing Network Adapter Device Drivers" in the Training and Procedures Guide, or consult the Online User Guide. A list of supported adapters is provided on the World Wide Web at: http://www.pc.ibm.com/us/desktop/lccm/index.html To clean up redundant files, in order to save disk space, delete the following: 1. The compressed LCCM file that you downloaded from the World Wide Web. 2. LCCM's temporary install directory (e.g., :\LCCMINST) Important Information if you are using a LAN Router. If you are using LCCM in a RPL environment, the LCCM server must be on the same LAN segment as the clients you will be controlling. LCCM does not support the use of routers in a RPL environment. If you are using LCCM in a DHCP/PXE environment, routers are supported and the LCCM server can be located anywhere within the network. For details, refer to the LCCM Version 2.5.1 Training and Procedures Guide. This guide is accessible from the following Web address: www.pc.ibm.com/us/desktop/lccm/index.html WINS Name Resolution: LCCM does not require WINS to invoke name resolution if your client computers reside on the same domain as your LCCM server. In this case name resolution is facilitated by NBUtil. Note that NBUtil is not compatible with WINS. Utilities Installed with LCCM: The following utility programs can be found in the :\LCCMINST\CLNTFILE directory: * IDVIEW This utility can locate Plug-and-Play numbers across your network. * WATCHDOG This utility can be used to automatically reboot clients, after a specified time, that have not responded to such functions as Scan or Image Download functions. * WINWAKE This utility can be used to power on clients remotely, using Wake on LAN. Consult the Online User Guide, or the Training and Procedures Guide for details of using these utility programs. ------------------------------------------------------------------------------------------------ LIMITATIONS: 1.LCCM version 2.5.1 will support both PXE1.0 and PXE2.0. The LCCM/DHCP/PXE code on the LCCM server has been upgraded to support PXE2.0 clients, existing IBM 16/4 Token Ring PCI Adapter 2 with wake-on-LAN network cards must be flashed with the latest level of micro code in order to continue working with the new level of code within the LCCM server. The latest micro code can be downloaded from the web site http://www.networking.ibm.com/support. ------------------------------------------------------------------------------------------------ - Licensed Material - (C) Copyright IBM Corp. 1996, 1999 All rights reserved. - U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. END OF DOCUMENT