====================================================================== = LCCM 2.5.1 Service Pack 4 = = October 20, 2000 = = = = Welcome to LANClient Control Manger (LCCM) Service Pack 4. This = = file contains information about installing and using Service Pack = = 4 (SP4). = ====================================================================== (c) Copyright IBM Corp. 2000 All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ====================================================================== CONTENTS ====================================================================== This file contains the following sections: 1.0 What is in this Service Pack 2.0 How to install the Service Pack 3.0 How to use the new DiffTool with Office 2000 4.0 How to uninstall LCCM 2.5.1 and/or Service Pack 4 5.0 Known problems with DiffTool 6.0 Large Partition support for the FAT32 and NTFS file systems 7.0 Using LCCM to install Windows 98/NT Service Packs 8.0 Instructions for setting up the redirection capability in LCCM 9.0 Using System Migration Assistant (SMA) with LCCM 10.0 Notes about Installing Universal Manageability Services (UMS) 11.0 Notes about Deploying Clients into a Domain 12.0 Trademarks ====================================================================== 1.0 WHAT IS IN THIS SERVICE PACK: ====================================================================== All LCCM service packs are cumulative. Thus, Service Pack 4 contains all fixes and updates from prior Service Packs (1, 2 and 3) and Patches (1). It is sufficient to install just Service Pack 4 to receive all changes mentioned in this file. Many of the following modifications have resulted in changes to LCCM's graphical user interface and to its language strings. If you upgrade a Japanese LCCM installation with this service pack, everything will work fine, but many of the user-interface windows and strings will be displayed in English (instead of Japanese). 1.1 Functional Enhancements in Service Pack 4: ---------------------------------------------------------------------- 1. Built-in support for installing UMS 2.12 with LCCM wizard- generated profiles is added. 2. If you install UMS application using LCCM with Service Pack 4, the following entry has been added to the ums.iss file: [NfDReqAuth] Result=1 The Result parameter controls whether authorization is required for a user to have remote access to the computer. The options are: 1 Yes, require authorization for a user to have remote access to the computer. 0 No, do not require authorization for a user to have remote access to the computer. 3. Two new utilities (LCCMPREP.EXE and ADDDOM.BAT) are added to assist LCCM administrators in making some required manual configuration changes when deploying clients into a domain. 4. Support for installing Windows 2000 Service Pack 1 has been added as part of the Windows 2000 unattended installation profile. 5. Support for new IBM systems and network adapters. See the updated Compatibility and Configuration Guide on the IBM web page (http://www.pc.ibm.com/us/desktop/lccm/compat.html) for a complete list of supported hardware. 1.2 Fixes in Service Pack 4: ---------------------------------------------------------------------- 1. There is no longer an error, when importing the client database from a previously exported copy. 2. The client hang in SCANNT.EXE on certain ThinkPad models that was introduced in Patch 1 no longer occurs. 3. LCCM will now clone DNS parameters on Windows 95, Windows 95 OSR2, Windows 98, and Windows 98 SE systems. After installing Service Pack 4, you must create new profiles for this fix to be in effect. However, you do not have to re-create your clone images. 4. Service Pack 4 enables unattended install for the following language versions of Windows 2000: - German - Dutch 5. When LCCM is installed on a server that is not a domain controller, some user permissions are not set up correctly. Installing Service Pack 4 corrects these problems. 6. SCRUB.EXE no longer displays write-error messages at the client. You should replace all copies of SCRUB.EXE with the version in Service Pack 4. 7. SCANNT.EXE is modified to handle scan questions correctly: - If scan is interactive, display ONLY the responses to the scan questions in the "Client Details" notebook. Do not alter the "OWNERDATA" information in the ASSET ID chip. - If scan is non-interactive (the default), then populate the "Client Details" notebook by putting the "LOCATION" from the "OWNERDATA" group into the "Client Details" "Location" box, and the other four fields from the group into the "Client Details" "Contact" box. 8. DIFFTOOL.EXE now handles certain multiple-application installs correctly. 1.3 Known Issues in Service Pack 4: ---------------------------------------------------------------------- 1. LCCM does not display video adapters for some OEM systems. However you can modify VIDEO.LST file in the LCCM directory, and tailor it to your own need. 2. When Service Pack 4 is installed, a problem occurs when an attempt is made to use Partition Magic scripting to resize a partition as part of an LCCM deployment. Use the following workaround: If the mouse driver is in the shared directory that contains the Powerquest files, delete or rename the mouse.com file. LCCM will ultimately use the utilities in script (rather than interactive) mode, so the mouse driver is unneeded. 3. The computer name to be installed with Windows 2000 must begin with an alphabetic character. If it is numeric, the installation of that client will halt during setup with a warning. 4. On the LCCM Server, the Progress and Errors window will report status of clients that are being processed. This status may incorrectly report what setup stage that a given client is in when performing a Windows 2000 unattended install. This will not affect the installation of the clients. Please wait until each client is fully installed. 5. Some modifications made in SP3 or SP4 will not apply to your current Windows 95, Windows 95 OSR2, or Windows 98 unattended install profiles. To benefit from these modifications, create a new profile that uses the same operating system, and select the 'Use existing operating system files' box. This will update all existing profiles that use that operating system image. 6. The new maximum-size partition enhancements have some limitations when used with Rapid Restore: RPL protocol - The maximum size of the boot partition is 2040 megabytes (unchanged in Service Pack 4). PXE protocol - Windows NT 4.0 - If the hard disk is bigger than 15.6 gigabytes, then the true maximum size (7.8 gigabytes) is allowed. - If the hard disk is smaller than 15.6 gigabytes, then the maximum size of the boot partition is 2040 megabytes (unchanged in Service Pack 4) - Windows 2000 - The maximum size is approximately half the size of the hard disk in all cases. 7. When you create a Windows NT 4.0 (Server or Workstation) profile with a static IP address that contains a zero in the second or third octet, you get a dialog box informing you that the IPAddress key has an invalid IP address. Click OK and the IP address is now accepted. This problem has been fixed in the Tcpcfg.dll (may also be called Tcpcfg.dl_) file contained in Windows NT 4.0 Service Pack 2.0 and later service packs. To work around this issue: 1. On the LCCM server, rename the Tcpcfg.dll/Tcpcfg.dl_ file to Tcpcfg.org. This file is located in the \LCCM\CLNTFILE\NT4WKS\ENG and \LCCM\CLNTFILE\NT4SRV\ENG (or the appropriate language) directories. 2. Copy the Tcpcfg.dll/Tcpcfg.dl_ file from the latest service pack into the \LCCM\CLNTFILE\NT4WKS\ENG and/or \LCCM\CLNTFILE\NT4SRV\ENG directories. 8. During installation of SP4, do not click the Finish button more than once. If you do so, the LCCM server may appear to hang, with a blank screen that contains only the mouse pointer. To recover, press the Ctrl-Alt-Del keys simultaneously and then select "Shutdown". 9. When the LCCM server is set up with a multihomed (Ethernet/Token ring) configuration, if you flash the client's Token ring adapter to the current PXE 2.0 level and then scan the client, the scan will hang. You must flash the Token ring card with the current PXE 1.0 level only. However, PXE 2.0 will work when the Token ring is not in a multihomed environment. 10. When installing UMS and/or other applications along with unattended installation, be sure to verify that your primary partition will be large enough to accommodate both the applications and the operating system. 11. When you perform an unattended installation of Japanese Windows 98 SE, the first time you restart the client machine a message will be displayed stating that the file C:\windows\system\mfc42.dll is being replaced. Click OK, and the operating system will function normally. 1.4 Updates from Patch 1 ---------------------------------------------------------------------- 1.4.1 Fixes in Patch 1: ---------------------------------------------------------------------- Patch 1 replaces a few files in order to fix the following: - Some problems that were discovered after SP3 was released. - Some Windows 2000 enabling for versions that were released after SP3 was released. Patch 1 fixes these things: 1. Cloning Windows 98 or Windows 95 OSR2 under RPL no longer fails in the IMAGE.BAT file (missing label NEXT). 2. Cloning Windows 98 or Windows 95 OSR2 no longer fails when maximum size partition plus a Rapid Restore partition are selected. 3. Client computer no longer hangs during scan. 4. Client computer no longer hangs on FDISK step during an operating-system deployment. 5. Unattended install of non-English Windows 2000 is now enabled. The changes in Patch 1 have been tested with the following language versions of Windows 2000: English LCCM version: - Brazilian Portuguese - Danish - French - Italian - Norwegian - Spanish - Swedish Japanese LCCM version: - Japanese Chinese-enabled English LCCM version: - Simplified Chinese - Traditional Chinese 6. Installing Universal Manageability Services (version 2.12) on Windows 2000 is now enabled in the Profile Wizard. 7. Installing Universal Manageability Services with fewer than 4 options will now create a client that Netfinity Director can discover. 8. Installing Universal Manageability Services no longer results in a message box presented at the LCCM client. 1.5 Updates from Service Pack 3: ---------------------------------------------------------------------- 1.5.1 Functional Enhancements in Service Pack 3: ---------------------------------------------------------------------- 1. Profile wizard now supports unattended installations of Windows 2000 Professional, Windows 2000 Server, and Windows 2000 Advanced Server. 2. Profile wizard now supports unattended installations of Windows 98 with the latest Windows 98 service packs (tested with Service Pack 1) and Windows 98 Second Edition. 3. Profile wizard now supports the latest Windows NT 4.0 service packs (tested with Service Packs 3, 4, 5, and 6a) as part of its unattended installations of Windows NT 4.0 Server and Windows NT 4.0 Workstation. 4. DOS version replaced with DOS-2000 level plus a few additional extensions that support large partitions. 5. Profile wizard partition size limits are increased: Windows NT 4.0 - allows true maximum-size NTFS partition - allows fixed-size NTFS partition between 400 and 2040 megabytes (not changed by Service Pack 3) Windows 98 and Windows 95 OSR2 - allows true maximum-size FAT32 partition - allows fixed-size FAT32 partition of any size (minimum is 512 megabytes) Windows 2000 - allows true maximum-size NTFS or FAT32 partition - allows fixed-size NTFS or FAT32 partition of any size (minimum is 1800 megabytes) - allows fixed-size NTFS partition between 1800 and 8400 megabytes when the 2-partition option is selected 6. Profile wizard now allows FAT32 partitions for clone installation and unattended installations of Windows 95 OSR2, Windows 98, Windows 98 Second Edition profiles, and for unattended installations of Windows 2000 profiles. 7. Bootstrap program now has built-in support for remote TFTP servers. This allows the DOS boot images to be stored on remote file servers in a Wide Area Network environment (details in section 7.0). 8. Coexistence with Microsoft Windows 2000 DHCP servers. 9. Support for new IBM systems and network adapters. See the updated Compatibility and Configuration Guide on the IBM WEB page (HTTP://www.pc.ibm.com/us/desktop/lccm/compat.html) for a complete list of supported hardware. 10. Profile wizard now supports installing IBM Universal Manageability Services (UMS) Version 2.11 as part of an unattended installation profile. 11. Removed Universal Management Agent support from the profile wizard (UMS is its replacement). 12. Profile wizard now supports built-in integration with IBM System Migration Assistant Version 2.1 (SMA). You can download SMA from the IBM WEB page (HTTP://www.pc.ibm.com/us/software/sysmgmt/products/sma). 13. DiffTool now supports Windows 2000 Professional, Windows 2000 Server, and Windows 2000 Advanced Server. 14. DHCP and BINL service have been updated for coexistence with IBM Universal Manageability Services (UMS) when UMS is installed on the LCCM Server. NOTE: Uninstalling SP3 does not remove this new DHCPSD.EXE file, because you would get a Dr. Watson error (the first time you started the back-level DHCPSD.EXE) and it would lose knowledge of all active IP leases. 15. Network driver now installed during NT unattended installations on the following IBM machine types: 6584, 6594, and 6867 (requires NT Service pack 4 or later in the profile). 16. We added a sample file, \LCCM\OPTIONS.INI, that contains examples of some options that you can modify to override the standard LCCM configuration. OPTIONS.INI is not actually used in LCCM. It merely contains prototypes of statements that you can use in an \LCCM\LCCM.INI file. To change an option in your LCCM configuration, shut down LCCM and create a file named \LCCM\LCCM.INI. Add the option you want to change to that file. Then restart LCCM. 17. The NETWORK.LST, MACHINE.LST, and VIDEO.LST files are all replaced, in order to support new hardware and to correct some errors. If you modified any of these files, you can find your old versions in the \LCCM\Uninstall_SvPk directory. 1.5.2 Fixes in Service Pack 3: ---------------------------------------------------------------------- 1. Bootstrap Program now performs a DHCPRelease to the DHCP server when booting to the local drive. 2. Update to fix RPL with the IBM PCI Token-Ring Adapter Family in machines with a processor speed greater than 400Mhz. 3. Bootstrap program modified to reduce the number of multiple "Attaching to server" messages and the number of time outs that cause multiple reboots. 4. Intermittent client processing delays, with 'Configuring client boot environment' message displayed in the Progress and Errors window, no longer occur. 5. IBM ThinkPad computers with AssetID now work with LCCM. 6. Prevent client from stopping with error 2224 when using 'administrator' or 'guest' as the client's userid. 7. AIAREAD.EXE and AIAWRITE.EXE now use 'GATEWAY' (instead of 'IPGATEWAY') for the gateway address, as documented in the LCCM Training and Procedures Guide. 8. AIAREAD.EXE no longer appends 1 to 'GATEWAY' when returning the gateway address. 9. Modifications to GO.BAT and GO_D.BAT files allow Windows NT and manual Windows 2000 profiles to be processed concurrently. 10. You can now stop a client in the middle of processing, and then either reprocess it or assign it to another profile and process it with out getting the 'Unable to write flags for the client' error. 11. DiffTool no longer gives invalid error message about not being logged on as an administrator. This fixes an error introduced in LCCM Service Pack 1. 1.6 Updates from Service Pack 2: ---------------------------------------------------------------------- 1. TFTP Service settings have been updated so that file system access is restricted to the directory in which the TFTP Service files are installed. 1.7 Updates from Service Pack 1: ---------------------------------------------------------------------- 1. DiffTool now has support for Microsoft Office 2000* Professional. 2. IBM Intermediate Support Driver will support multiple fault tolerant network adapters. ====================================================================== 2.0 HOW TO INSTALL THE SERVICE PACK ====================================================================== 2.1 Prerequisites: ---------------------------------------------------------------------- - LCCM Version 2.5.1** (English, Simplified Chinese, Traditional Chinese, or Japanese versions). - Administrator privileges on the LCCM server. - LCCM Server must have at least 60 MB of free disk space. 2.2 Pre-installation: ---------------------------------------------------------------------- - The LCCM server application must not be running. 2.3 Installation: ---------------------------------------------------------------------- If you already have Service Pack 1,2 or 3 installed, you can install Service Pack 4 over it without needing to uninstall. 2.3.1 To Install LCCM Service Pack 4: ---------------------------------------------------------------------- 1. Download LCCMSP04.exe from the IBM Web site. 2. Run LCCMSP04.exe. 3. If you are asked about replacing files in a TEMP directory, answer "Yes to All". 4. Allow the computer to restart. 2.3.2 To replace the IBM Intermediate Support Driver: ---------------------------------------------------------------------- Do this only if you have not already done this when you installed LCCM 2.5.1 Service Pack 1, 2 or 3, or retrieved and installed the IBM Intermediate Support Driver update file from the IBM Web site. 5. Uninstall current IBM Intermediate Support Driver (Wedge) driver from Control Panel...Network...Protocols~*. 6. Reboot the computer as requested by Windows NT*. 7. Go to Control Panel->Network->Protocols, click 'ADD' to install the new Wedge driver. 8. In the protocol dialog box, click 'Have Disk...'. 9. Fill in the local path of your LCCM Wedge directory, click 'Continue'. Example: C:\LCCM\WEDGE. (note: The new driver files were copied into that directory.) 10. Click 'Continue' to accept IBM Intermediate Support Driver option. 11. Click OK to reboot. ====================================================================== 3.0 HOW TO USE THE NEW DIFFTOOL WITH OFFICE 2000* ====================================================================== To successfully deploy Office 2000* using DiffTool, you must follow the procedure outline below: 3.1 Prepare donor system: ---------------------------------------------------------------------- 1. Roll out the desired operating system on the machine. 2. Set up the system so that the Office 2000 CD will not autostart. There are several ways to do this: . Access the Office 2000 CD via a network shared CDROM drive on a remote system. . Put the Office 2000 CD in the local CDROM drive before you perform the operating system rollout (in step 1 above) . Modify the system's settings to prevent CD autorun. . NT Registry: change the value of HKLM\SYSTEM\CurrentControlSet\Services\Cdrom\Autorun to 0. . Windows 98: go to System Properties, Device Manager page, and uncheck "Auto insert notification" item. 3. Logon to make sure everything is functioning properly. Warning: The Office 2000* Installation/Welcome window must not start before DiffTool starts. If the Office 2000 Installation/Welcome window starts first, the DiffTool image of the donor machine will not be complete correctly. Office 2000* will not operate correctly on the target systems. 3.2 Prepare for Office 2000* DiffTool image: ---------------------------------------------------------------------- 1. Make sure you logon to the donor system with an identity that has administrator privileges on the LCCM server. 2. If you had shared the Office 2000* CD on a remote computer, connect to that share point. 3.3 Create an Office 2000* image: ---------------------------------------------------------------------- 1. Run DiffTool, and install Office 2000* via DiffTool. 2. Answer Office 2000 setup questions per your system's requirement. 3. Office 2000* will start copying files to the system. 4. Click the 'Ignore' button in the popup window 'Microsoft Office 2000 Files In Use'. Note: The 'Microsoft Office 2000 Files In Use' window shows up about 50% into copy file phase. It is important that you click the 'Ignore' button so Office 2000* doesn't terminate DiffTool while it is collecting data from the system. In the event you did click 'Cancel' by mistake, you must restart the entire DiffTool processes from section 3.1. 5. Do not reboot the client (donor) machine after Office 2000 finished. Click the 'NO' button in the 'Installer Information' window to prevent Office 2000* from rebooting the machine. 6. Click the 'Finish' button in DiffTool window to close everything properly. 3.4 Apply the Office 2000* DiffTool image: ---------------------------------------------------------------------- 1. From the LCCM server, create an unattended install profile that includes the Office 2000* image. 2. Select a target machine and roll out that profile. 3. After the status on LCCM server for the target machine changed to "process completed...", reboot the target machine, and logon as the administrator to complete the Office 2000 installation process. ====================================================================== 4.0 HOW TO UNISTALL LCCM 2.5.1 AND/OR SERVICE PACK 4 ====================================================================== 4.1 Removing LCCM 2.5.1 Service Pack 4 only: ---------------------------------------------------------------------- 1. Click the 'Add/Remove' program icon in Control Panel window. 2. In the Add/Remove Programs window, highlight 'LANClient Control Manager 2.5.1 with SP4'. 3. Click the 'Add/Remove' button at the bottom of the window box. 4. Answer 'YES' to enter into the LCCM uninstall program. (This will NOT automatically uninstall all of LCCM.) 5. A popup window will ask whether you want to remove the entire LCCM package or just the Service Pack. Answer 'NO' to remove only the service pack. 6. If you have installed the upgraded IBM Intermediate Support Driver, you now need to reinstall the original version. (Note: The original driver files are restored to the LCCM\WEDGE directory.) 7. Uninstall of Service Pack 4 is complete. 4.2 Removing the entire LCCM 2.5.1, including Service Pack 4: ---------------------------------------------------------------------- 1. Click the 'Add/Remove' program icon in Control Panel window. 2. In the Add/Remove Programs window, highlight 'LANClient Control Manager 2.5.1 with SP4'. 3. Click the 'Add/Remove' button at the bottom of the window box. 4. Answer 'YES' to enter into the LCCM uninstall program. 5. A popup window will ask whether you want to remove the entire LCCM package or just the service pack. Answer 'YES' to remove the entire product. 6. Answer the uninstall questions as appropriate to your situation. 7. Uninstall will remove LCCM and ask you to reboot the machine. 8. Answer 'Yes' to complete the final step of the uninstall. Note: You can find a more detailed description on how to install/uninstall IBM Intermediate Support Driver in 'LCCMPath\wedge\read.me'. Alternatively, you can consult the online User Guide, at http://www.pc.ibm.com/us/desktop/lccm/index.html or the Training and Procedures Guide for details on how to install IBM Intermediate Support Driver. ====================================================================== 5.0 KNOWN PROBLEMS WITH DIFFTO0L ====================================================================== For Office 97 on Traditional Chinese Windows NT* Server SP4: On the target machine's desktop, the Office Toolbar shows a link to "Open Office Document". The link doesn't work. It will cause an access violation. There is no work around for this problem, we recommend not using the link until a better solution is found. The installation also places two short cuts on the desktop to allow the user to install IE 3.02 and a punctuation package. These items require the Office 97* CD to be present in the local system to install properly. Or, change the path to the short cut to where the CD is being shared. For Office 2000* on all Windows Operating Systems: It is recommended that you install all Office products using their built-in unattended installation support. There are several intermittent problems using Difftool with the Office family of products. ====================================================================== 6.0 LARGE PARTITION SUPPORT FOR FAT32 AND NTFS FILE SYSTEMS ====================================================================== 6.1 New support files introduced in SP3 are: ---------------------------------------------------------------------- - \\LCCMSERVER\LANC$$\LCFDISK2.EXE - \\LCCMSERVER\LANC$$\FDISK32.COM - \\LCCMSERVER\LANC$$\FORMT32N.COM Please be aware that post-SP3 profiles will not work if the user were to UNINSTALL SP3. 6.2 Support files left behind to handle the pre-SP3 profiles are: ---------------------------------------------------------------------- - \\LCCMSERVER\LANC$$\LCFDISK.EXE - \\LCCMSERVER\LANC$$\FDISK32.EXE - \\LCCMSERVER\LANC$$\FORMAT32.COM 6.3 These files are replaced (or added) in SP3: ---------------------------------------------------------------------- - \\LCCMSERVER\LANC$$\DEFAULTS\FAT16.LCP - \\LCCMSERVER\LANC$$\DEFAULTS\FAT32.LCP - \\LCCMSERVER\LANC$$\DEFAULTS\95_2_CL.LCF - \\LCCMSERVER\LANC$$\DEFAULTS\95_2_UN.LCF - \\LCCMSERVER\LANC$$\DEFAULTS\98CL.LCF - \\LCCMSERVER\LANC$$\DEFAULTS\98UN.LCF - \\LCCMSERVER\LANC$$\DEFAULTS\W2KUN.LCF 6.4 How to create a manual profile using the new files: ---------------------------------------------------------------------- To create manual profiles with SP3 that can take advantage of large partitions with FAT32, you will need to use the new FDISK32.COM and FORMT32N.COM mentioned above. The steps are as follows: 1. Create your manual profile as you normally would with LCCM 2.5.1. 2. Add a client parameter to your profile called "LCCMFAT32". Assign it a value of '1'. 3. Edit the preload file (*.lcp) which contains the disk partition preparation commands. 4. Add the FDISK32.COM command here. If there are any current FDISK.COM or FDISK32.EXE commands in this file, you need to replace them with the new FDISK32.COM command. FDISK32.COM has the following usage: FDISK32 [/STATUS | d /PRI:n | d /EXT:n | d /LOG:n | d /MBR] /STATUS Displays the status of the fixed disk drive d Physical drive number (1,2,...) n Size of partition in megabytes /PRI Create a primary drive /EXT Create an extended partition /LOG Create a logical drive within an extended part. /MBR Write a new Master Boot Record 5. Process the profile normally. If you have properly set up the LCCMFAT32 client parameter, the LCCM processing batch files (lcproc.bat & lcprocd.bat) will automatically format the drive using the "FORMT32N.COM" format program. Examples of FDISK32.COM command: ------------------------------------------------------------------ The following command line will create a primary partition on the first hard drive. Logical drive "c:" will be assigned to it and it will be 3000 MB in size. FDISK32 1 /PRI:3000 The following command lines will create an extended partition on the first hard drive. The first command creates the partition. The second commands assigns that partition the next available Logical drive letter. It will be 4000 MB in size. FDISK32 1 /EXT:4000 FDISK32 1 /LOG:4000 ====================================================================== 7.0 USING LCCM TO INSTALL WINDOWS 98/NT SERVICE PACKS ====================================================================== The LCCM Profile wizard now supports installing Service Packs as part of an unattended installation of Windows 98, Windows 98 Second Edition, and Windows NT 4.0 Workstation and Server. Currently, the following Service Packs have been tested. - Windows 98 Service Pack 1 - Windows NT 4.0 Service Packs 3, 4, 5, and 6a After this LCCM Service Pack is released, Microsoft may create more Service Packs for these operating systems. Provided these Microsoft Service Packs behave similarly to their predecessors, support can easily be added to LCCM by modifying configuration files after LCCM Service Pack 4 is installed. 1. Edit the file "IMGWIZ.TPL". It can be found in your LCCM installation directory in the "CLNTFILE\IMGWIZ" subdirectory. 2. Increment the "Num=" count in one of the following sections depending on which operating system you wish to add the new Service Pack to: [NT Service Pack], [W98 Service Pack], or [W98ED2 Service Pack]. 3. In this section, the following keys need to be added: NameX = VerX = (NT Only) CmdX = The current file has examples for all of the current Service Packs that are supported. Note that "VerX" is usually equal to the Service Pack number X 256. I.E. For Service Pack 2, Ver2=512. ====================================================================== 8.0 INSTRUCTIONS FOR SETTING UP THE REDIRECTION CAPABILITY IN LCCM ====================================================================== 8.1 Setting up the LCCM Server ---------------------------------------------------------------------- 1. On your LCCM Server, create an OPTIONS.TXT file using notepad (or your favorite text editor) in the \IBMTCPIP directory. 8.1.1 Syntax of OPTIONS.TXT ---------------------------------------------------------------------- Each line in the file can have one the following syntax formats. The size of the options.txt file is limited to 64K. Note that the # is a command used for making comments. SUBNET;TFTP_SERVER_IP;PATH; SUBNET;TFTP_SERVER_IP; SUBNET;TFTP_SERVER_IP;; # SUBNET;TFTP_SERVER_IP;PATH; --------------------------- This format is used to change the subdirectory path where the DOS image files(PROFX, PROFS, and PROFN) are stored on the redirection TFTP server to something other than where they were located on the LCCM server. 'Path' in the syntax is the location of the PROFS, PROFX or PROFN files on the TFTP server. Complete the path with a backslash or forwardslash as appropriate depending on the TFTP server (e.g., NT or Linux) SUBNET;TFTP_SERVER_IP; ---------------------- This format is used if the DOS image files (PROFX, PROFS, and PROFN) are stored in the same subdirectory on the redirection TFTP server as they were on the LCCM server. The default directory during an LCCM install is C:\IBMTCPIP\. SUBNET;TFTP_SERVER_IP;; ----------------------- This format is used to make the path blank. This is useful when the TFTP server is a Linux/Unix machine and the PROFS, PROFX and PROFN files are in the /tftpboot directory. # Comment ---------- Any sentence that begins with a # is treated as a comment. Note: There should not be any spaces in the lines in the file. Any blank lines are ignored. If the syntax of a line is not proper, then that particular line is ignored and the next line is scanned. Important: Hit the Return/Enter key at the end of every line, including the last one when creating the OPTIONS.TXT file. 8.1.2 Example of an OPTIONS.TXT file ---------------------------------------------------------------------- # this line is a comment 9.42.0.0;9.42.2.1;C:\TEMP\; 9.52.0.0;9.52.1.2;; 10.2.0.0;10.2.5.6; 8.2 Setting up a redirection TFTP server ---------------------------------------------------------------------- 8.2.1 Windows NT setup ---------------------------------------------------------------------- Open the DOS prompt on the computer you want to set up as the TFTP server. Enter the following commands. # In the following command, 1.2.3.4 is the IP address of the # LCCM server (or you could also use the machine name of # the LCCM server.) NET USE X: \\1.2.3.4\LCCM$TCP MD C:\IBMTCPIP # In the following, there is a space between X:\ and C:\ XCOPY /S X:\ C:\IBMTCPIP CD C:\IBMTCPIP # In the following, there should be a space between every # argument. TFTPD32 -cmd -k 8 -v 2 -r -d C:\IBMTCPIP # To run TFTP as a service, enter the following command instead # of the previous one: TFTPD32 -install -k 8 -v 0 -r -d C:\IBMTCPIP 8.2.2 LINUX setup ---------------------------------------------------------------------- Everything in this section is case-sensitive. Please enter it exactly as shown. 1. Make a directory called /tftpboot. 2. Place the PROFS, PROFN and PROFX files in the /tftpboot directory. Be careful about case sensitivity (e.g., file names must be upper-case)! 3. Open the /etc/inetd.conf file. 4. Go to the line that talks about TFTP and make it the following: tftp dgram udp wait root /usr/sbin/tcpd in.tftpd /tftpboot. Note: All that we are doing is removing the "#" from the beginning of the line and adding /tftpboot to the end. 5. Save the file. 6. Reboot the machine or restart the inetd service. ====================================================================== 9.0 USING SYSTEM MIGRATION ASSISTANT (SMA) WITH LCCM ====================================================================== 9.1 How it works ---------------------------------------------------------------------- If you create an SMA profile using System Migration Assistant Version 2.1, you can deploy that profile automatically with an LCCM wizard generated profile. In the LCCM profile wizard, select the option to include SMA as part of the profile. At client assignment time, you will need to provide the full UNC path and filename to wherever you have stored the SMA file. 9.2 Known issues ---------------------------------------------------------------------- Some SMA personality settings are specific to the user that is logged on when the settings are captured. These include "Wallpaper", "Colors", "Desktop Icons", and all other settings that have to do with desktop appearance. These settings will not transfer to the client target system. However, all connectivity settings and data files should transfer without problems. ====================================================================== 10.0 NOTES ABOUT INSTALLING UNIVERSAL MANAGEABILITY SERVICES (UMS) ====================================================================== 10.1 Requirements ---------------------------------------------------------------------- - Processor: Pentium 200 or higher. - Memory: 32 MB RAM minimum, 64 MB recommended for full install. - Internet Explorer 4.01 or later is required. - Microsoft NT Service Pack 4 or later is required. - Universal Manageability Services version 2.12. 10.2 Known Issues ---------------------------------------------------------------------- 1. After installing UMS with Windows NT 4.0 or Windows 2000, the first user to log on to the system MUST have administrator privileges, so that UMS can finish configuring the system. 2. Unattended install fails on Japanese, Chinese Traditional, and Chinese Simplified because UMS attempts to overwrite files. To continue and finish the setup, click the "No to all" button every time a window pops up. This will happen several times, but the install will finish and work correctly. 3. Some machines are not supported by UMS. If this seems like a problem, check the master.ini file in the UMS directory and check if the four digit machine model number exists anywhere in the list. If it does, the machine is supported. If the model number is not present in master.ini, UMS does not support that machine, and cannot be installed. 4. In order to perform an unattended installation of UMS that includes SNMP support, you must select SNMP support when building the client profile, then edit the .LCA file for each profile, located in C:\LCCM\CLNTFILE\PROFILE\PROFxxx.LCA (for example, PROF001.LCA). For Windows NT Server, add the following information to the .LCA file: [Network] InstallServices = SelectedServicesList [SelectedServicesList] SNMP = SNMPParameters [SNMPParameters] For Windows 2000 Server, add the following information to the .LCA file: [NetOptionalComponents] SNMP = 1 [SNMP] 5. UMS DMI support defaults to Desktop as the type of information to be returned. To change this option in the profile to either Server or Mobile, edit the file SETUP.ISS located in C:\LCCM\CLNTFILE\PROFILE\PROFxxx\UMS\EN (or appropriate language directory). In the file SETUP.ISS you will find the following lines: ;DMI machine type ;Options: Server ; Mobile ; Desktop [DMI] DMIType=Desktop Change the line DMIType=Desktop to either DMIType=Server or DMIType=Mobile, depending on the information you want to have returned. ====================================================================== 11.0 NOTES ABOUT DEPLOYING CLIENTS INTO A DOMAIN ====================================================================== 11.1 Configurations ---------------------------------------------------------------------- A common situation is to deploy Windows NT 4.0 or Windows 2000 workstations and servers as members of a domain and to deploy Windows 95 and Windows 98 workstations that will log on to a domain. In some cases, you will need to do some manual configuration on your servers to make this work. Configuration 1: LCCM is installed on a Primary Domain Controller (PDC) or on a Backup Domain Controller (BDC). The target computers are deployed into the same domain as that of the LCCM server. In this case, no manual configuration is needed. Configuration 2: LCCM is installed on a Stand Alone (SA) server. The target computers are deployed into the same domain as that of the LCCM server. In this case, you should use LCCMPREP.EXE and ADDDOM.BAT as described below. Configuration 3: LCCM is installed on a PDC, BDC, or SA. The target computers are deployed into a different domain from that of the LCCM server. In this case, you should use LCCMPREP.EXE and ADDDOM.BAT as described below, and you will need to modify the LCA file for each appropriate profile and may need to establish trust relationships between the LCCM server's domain and the target domains. 11.2 New LCCM Utilities ---------------------------------------------------------------------- Two utilities are provided with this service pack to assist in this configuration. After installing Service Pack 4, they will be in the C:\LCCM directory (i.e., in the directory into which you installed LCCM). You must run these programs with administrator privileges. 11.2.1 LCCMPREP.EXE ---------------------------------------------------------------------- LCCMPREP.EXE is the utility for preparing the target domain (into which clients will be deployed). It is best run on a domain controller for the target domain. This creates the user and group accounts necessary for LCCM clients to be correctly validated and to be installed into that domain. The following options are supported: LCCMPREP [/P] [/R] /P ... For PXE Support /R ... For RPL Support At least one option must be specified, and both options can be specified at the same time. 11.2.2 ADDDOM.BAT ---------------------------------------------------------------------- ADDDOM.BAT is used to configure the LCCM server, and must be run on the LCCM server only. Do NOT run this batch file on any domain controller unless both of the following are true: - That domain controller is also the LCCM server. - You are deploying clients into a domain other than the one which is controlled by the LCCM server. The following options are supported: ADDDOM [P] [R] domain1 [domain2 ...] P ... For PXE Support R ... For RPL Support At least one parameter "P" or "R" MUST be specified. Both may be specified on the same line. At least one domain name must also be specified. The domains to be processed should be listed on the command line. Domain names should be separated by single spaces. The LCCM server's domain MUST be specified, whether or not other domains are also specified. You must have established any necessary trust relationships beforehand. Trust relationships are only necessary if clients deployed in the target domain will need to access domain resources in the LCCM server's domain during deployment (for example, if the installation files sharepoint has been changed and is on a domain resource, rather than on the LCCM server). On a standard LCCM installation, where all sharepoints are on the LCCM server, there should be no need to establish trusts or to specify target domains, though the ADDDOM.BAT must always be run on the LCCM server, specifying the LCCM server domain on the command line. Messages are logged to LCCMDOM.LOG. We suggest that you examine LCCMDOM.LOG to be sure that all target domains are correctly enabled for service by the LCCM server. The reason for failure to enable any domain will be in this file. 11.3 Procedures ---------------------------------------------------------------------- The steps are as follows: 1. Configuration 2 and configuration 3: On a domain controller for the domain(s) into which you wish to deploy clients, run the LCCM utility LCCMPREP.EXE. 2. Configuration 3: Establish a trust relationship between the LCCM domain (as the trusting domain) and each target domain (as the trusted domain). Trust relationships are only necessary if clients deployed in the target domain will need to access domain resources in the LCCM server's domain during deployment (for example, if the installation files sharepoint has been changed and is on a domain resource, rather than on the LCCM server). On a standard LCCM installation, where all sharepoints are on the LCCM server, there should be no need to establish trusts or to specify target domains to the ADDDOM.BAT file, except as noted below. 3. Configuration 2 and configuration 3: Run the LCCM utility ADDDOM.BAT on the LCCM server, specifying the LCCM server's domain for processing. You may specify other domains, if the necessary trust relationships have been established. ADDDOM.BAT must ALWAYS be run on the LCCM server, specifying the LCCM server domain on the command line. 4. Configuration 3: Add the following line to the [Network] section of the LCA file for the appropriate LCCM profile. CreateComputerAccount=, This account does NOT have to be an administrator account. We would suggest that you create an account for this special purpose. The only right that the account NEEDS is "Add Workstations to Domain". This will limit security exposure. ====================================================================== 12.0 TRADEMARKS ====================================================================== The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM LCCM Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. ========================== END OF DOCUMENT ==========================