ForeFront Software Inc. Lan Configuration Facility (LCF) Technical Information ======== OVERVIEW ======== In 1990, the Royal Bank of Canada selected OS/2 as its primary workstation and server operating system. All of the bank's new mission critical applications are developed under OS/2 and the large majority of servers are currently OS/2, including those in its 1,700 branches. Over the next 3 years the bank plans to have 75% of its DOS workstations migrated to OS/2. As well, the bank has upward of 1,200 developers, 1/3 of which use OS/2. The enormous cost associated with installing and configuring all of these OS/2 systems lead to the bank's development of the LCF. With the LCF, OS/2 mission critical workbenches can be customized and thoroughly tested at the development center and then distributed outward from there. This creates systems which can be maintained and supported in a cost effective manner. In late 1992, ForeFront Software was established to bring the LCF to market. ======== FEATURES ======== * An administrator can customize packages for later installation over the LAN. * Packages are stored in a central library at the LCF code server (the code server is simply an OS/2 workstation, it need not be a network server). * Packages are composed of files and directories and can consist of operating systems (OS/2 or DOS), products (Windows) and applications. * An administrator can push packages to unattended workstations running on the LAN (these workstations must be running OS/2). * An administrator can create scripts to enable users to install and configure the packages. The scripts can be set up to prompt the user for input or to work without any prompting at all. * A user can run the scripts to pull packages from the code server library. The script/package combinations are selected from simple pull-down menus. * User preferences can be stored at the code server and used to customize the desktop at installation. * The package can be customized based on the specific features of the machine it is installed on. * The installation of an OS/2 package can be done from a two diskette "seed system" when necessary. This is used when the target system does not yet have OS/2 on it such as in recovery after a disk failure. * Scripts can be run on unattended remote workstations to perform administration tasks such as virus detection or auditing. ======== BENEFITS ======== SPEED * Installation can be done at LAN speeds. EASE OF USE * Users can install software without having to deal with the complexity of installation programs. They need only pick from a menu and start the installation process. All the necessary installation tasks were performed when the package was created. * Developers and support staff can pull specific workbenches for problem re-creation and regression testing. STANDARDIZATION * Systems and applications can be tailored to company standards and made readily available to users. SUPPORT * Pre-tested and customized packages are easier to support and maintain. * The packages can be pre-tuned by an expert. The script can be used to select file systems, position and size the swap file, print queues, etc., as well as set desktop options. * Automatic customization to user preferences saves user time and minimizes user resistance to the installation of new releases and maintenance. * The ability to run a script on remote workstations can be used to centrally execute virus checking, auditing and most other LAN administration programs. RECOVERY (DISASTER RECOVERY) * Critical workstations such as servers and gateways can save their operating systems and other software as packages for quick restoration in case the hard disk ever needs replacing. COST SAVINGS * Systems can be configured in ways which are impossible with the regular installation program. For instance, a package can be customized where parts of the regular system, such as help folders and the tutorial, are stored at a LAN server to minimize each workstations disk usage. OTHER * Software does not have to be CID enabled to be distributed, installed and configured by the LCF. ===================== OPERATING ENVIRONMENT ===================== HARDWARE REQUIREMENTS LCF Code Server - Minimum 8 MB of main memory. - 1 MB of hard disk space plus an amount equal to the size of the images being stored. Images are not compressed. LCF Client (Target Workstation) - Requirements dictated by software being installed. - OS/2 2.0 install requires 6 MB of main memory. LCF Agent - 500K hard disk space. SOFTWARE REQUIREMENTS LCF Code Server - OS/2 2.x with REXX support installed. LCF Client - OS/2 2.x LCF Agent - OS/2 2.x NETWORKING REQUIREMENTS All Components NetBIOS (available with Lan Requester 1.3, Extended Service 1.0, Novell Requester, etc.) ================================ ForeFront Software Inc. 2202 2 Ave. NW Calgary, Alberta Canada T2N 0G9 (403) 531-2160 Fax: (403) 270-0372 CompuServe: 73110,722