This information in this section should be used in place of the Completing A Factory Installation on MQuads section in the Installing Windows NT manual.
There are three phases:
On-site installation which completes the installation of Windows NT 4.0 with specific customer-supplied data.
Customization Part 1 which occurs at the first logon following completion of installation.
Customization Part 2 which consists of normal Windows NT initial system setup, product installation, and administrative actions.
The following steps constitute the first phase of customer-site installation. When the pre-installed system is booted for the first time, Windows NT GUI Mode Setup is entered unconditionally. This pre-installed WINDOWS NT system includes:
The boot drive initialized as an NTFS partition of approximately 8032 MB (maximum) with the remaining boot drive space being unpartitioned and unformatted.
Windows NT 4.0 installed in a directory called WINNT4 in this partition.
Sequent custom HAL for NUMA-Q 1000 installed.
Necessary additional device drivers installed.
A Sequent directory containing Sequent drivers, services, and tools.
Temporary directories needed to complete on-site installation.
On-site Installation (GUI Mode Setup) involves a combination of automated and manual steps. Steps marked with an (A) indicate data is supplied automatically. The supplied data is shown in parentheses. Installation does not pause at these steps and there may or may not be any visible indication of the step. Steps marked with a (U) indicate the user must supply information or a response. These steps cannot be automated because their inputs vary by customer. On-site installation should not be started until all the required customer information is available: user name, organization name, product certificate number, computer name, computer role, domain name (if needed), and time, date, and time zone to use.
(A) Confirm hardware during setup (Yes)
(A) Keyboard and Keyboard Layout (as detected)
(A) Pointing device (as detected)
(A) Video drivers (unattended - installs the ATI adapter drivers)
(A) SCSI drivers (as detected)
(A) Network installation (unattended - installs the Adaptec ANA62044 adapter drivers)
(A) Network Protocols to install (TCP/IP only)
(A) Network Services to install (basic only)
(A) Internet Information Server install (No - can be installed as part of EE optional products)
(A) Modem Parameters (none - must be done later)
(A) Video settings (pre-set values for pixel depth, horizontal and vertical count, refresh rate)
(U) End User Licensee agree/disagree (customer must agree)
(U) User Name
(U) Organization Name
(U) Product ID (Windows NT certificate number)
(U) Computer Name
(U) Computer Role (Stand alone server, PDC, BDC)
(U) Domain name if not a stand alone server (may be preceded by an error message)
(U) Time zone and date/time settings
(U) Pause before network install and startup (to verify connected to network)
(A) License mode (defaults to 'per seat', can be reset later)
(A) Skip welcome wizard (Yes)
(A) Skip Administrator password wizard (Yes)
(A) Service Pack 5 install (done automatically by command at end of setup)
(A) Sequent driver and service installation (done automatically by command at end of setup)
(U) Review setup log file (may choose to review or not)
(U) Reboot
When the system is rebooted following the previous installation steps, and Administrator is logged on (no password at this time), the Enterprise Edition Installer is automatically started. This installer will perform two main functions: make final changes to the boot images including changing the name and removing the memory limitation; and allow the installation of the Enterprise Edition components.
This first boot boots an image that claims to be "Windows NT Server", not "Windows NT Server, Enterprise Edition", and limits memory usage to 256 MB. The EE installer will indicate that changes are being made to the boot information via a message box containing a length message. Choose OK (the only choice available). This message box will not appear again.
Following the above, the Windows NT EE Installer indicates that it is about to run. A check box controls whether the Installer will automatically start again on the next boot. Since we are not ready to run the EE Installer to install components, this box should have its check mark removed. Then the EE Installer should be exited by choosing Exit. Ignore the warnings about installation being incomplete. We will return to these steps later.
It is recommended that IBM NUMA-Q field personnel perform this first logon and immediately follow it by exiting the EE Installer, shutting down, and rebooting Windows NT. This second boot will have the correct boot image name and will have access to all the installed memory.
At this point the final version of Windows NT 4.0 Enterprise Edition, Service Pack 5 for NUMA-Q 1000 is running with full access to all system resources. However, there are many things left to do before the system becomes a production machine. If IBM NUMA-Q personnel are still involved at this time they will need to work closely with customer personnel since most of the further customization will be driven by the customer's needs. The sequence below is reasonable but, in most cases, there is no requirement that it be followed. Some of these steps will require the Windows NT EE CD-ROMs.
Verify time zone, date, and time. Although these should have been properly set during the on-site installation, they should be verified with the customer before other installation steps are initiated. Note that some customers may not want to use the local time or local time zone.
Set regional settings. This would include number formats, date and time formats, and currency settings.
Perform IBM NUMA-Q-specific installation steps. If there are Sequent drivers and/or services that have not yet been installed or configured, that should be done now. If there are specific Sequent environment or registry settings required, they should be set now.
Complete network setup. The system is shipped with one or more Adaptec 4-port cards. The driver for this card has been installed and at least one of the ports has been configure to obtain an address via DHCP. If there is no DHCP server available, you will already have seen DHCP error messages. Each port needs to be set to either use DHCP or have a hard-coded TCP/IP address. If there are non-Adaptec adapters in the system, they should be installed and configured at this time. If protocols in addition to TCP/IP are desired they should be installed now and port bindings set or updated. A reboot may be required at this point to implement the network changes.
Join domain or workgroup or establish trusts. If the computer is to be a member of a domain or a workgroup, it should join it at this time. If the computer is a controller, it may be time to establish trust relationships with other domains.
Update Event Log settings. The event log settings need to be visited to establish or change behavior for log filling and wrap rate. In addition, if security events are to be collected, auditing needs to be turned on.
Update existing users, add new users. The 'administrator' user has been installed with NO password. A password should be added to administrator. The 'guest' account should be disabled or restricted as desired, and a new password should be assigned if needed. Additional users, such as role-based administrators, backup accounts should be added. Specific user permissions should be set or changed as needed.
Update local video, keyboard, and mouse settings. There are probably no changes needed since these are secondary on a server. It may be desirable to set a screen background and to set the screen-saver, possibly with security lockout. Create one or more partitions from the unpartitioned space on the boot drive. The boot drive will contain unpartitioned space following the boot partition. If you want to use this space (say for dump support, application installation, etc.) you should create one or more partitions using the disk administrator tool.
Complete disk setup. Disks other than the boot disk (including any partitions created above) may need any or all of the following: partitioning, formatting, assigning or changing file system, establishing mirrors, building stripe sets, and assigning disk letters.
Resize and/or allocate additional page files. The default page file on C: is probably inadequate for all NUMA-Q 1000 configurations and needs to be adjusted. The customer may want to allocate additional page files on other drives for performance reasons. Guidelines for page file size are not yet available.
Adjust crash dump options. Although the default options are fine, the customer may want different settings (such as auto-reboot off). Crash dumps should be enabled (this is the default) and the dump should be written to a location big enough to accommodate all of physical memory. Initially, the target file is on the root disk in the Windows NT root directory: thus this disk should have free space that exceeds the size of real memory. The dump file could also be pre-allocated at an appropriate size although we are offering no tool to accomplish this.
Install remote and local printers. Identify and install local printers, including their drivers and control applications, which are to be controlled by this server. Install remote printers that local applications will want to use for printing.
Set COM ports, install modems. If changes in the COM port settings are needed, they should be done now. If the system will have modems for remote serial access, they should be installed before any services that will want to use them.
Install additional Windows NT Services. The streamlined installation process does not install various services that might be commonly used. These include DHCP, RAS, SNMP, DNS, WINS, TCP/IP simple services, TCP/IP printing, and network monitor, for example. Once installed, most such services will require additional configuration.
Install and tailor Internet Explorer. IE 2.0 is pre-installed. IE 3.02 is available on the distribution CDs and can be installed with the Enterprise Edition Installer (see Install and tailor Enterprise Edition components below). However, IE 4.01 is recommended to achieve Y2K compliance. IE 4.01 is available on the Service Pack 5 CD as a Service Pack. Insert the CD and click on the IE Service Pack line and the Intel installation line.
Install the Data Access Components Service Pack. Insert the Service Pack 5 CD and click on the Data Access Components Service Pack line and the Intel installation line.
Install and tailor DBMS software. DBMSs should generally be installed before applications that depend on them. For example, MSMQ and MTS depend on SQLServer 6.5. If the customer also wants to install SQLServer 6.5, it makes sense to install it before installing applications that use it. Otherwise MSMQ and MTS will install a private version of SQLServer. If ODBC is to be used by any applications, it may need tailoring now.
Install Internet Information Server. If you plan to run IIS, install the base version (2.0) included with Windows NT 4.0. There is an icon on the server's desktop to perform this install. The Windows NT CD-ROM disk 1 is needed to complete this install. You must install this version of IIS if you intend to use the upgrade (to 3.0) included with Windows NT Enterprise Edition.
Install and tailor Enterprise Edition components. In addition to Internet Explorer the Enterprise Edition components include: MTS (Microsoft Transaction Server), MSMQ (Microsoft Message Queue Server), MSCS (Microsoft Cluster Server), IIS (Internet Information Server) Upgrade from 2.0 to 3.0, FrontPage 97. Use the Enterprise Edition installer to choose and install these components as desired. The Enterprise Edition Installer can be found from the Start menu under Programs; Administrative Tools. Enterprise Edition CD 1 will be needed. If SQLServer 6.5 is to be present at the site, it should have been installed first. MSMQ and MTS use SQLServer 6.5 and will install a private version if it is not already present. The Enterprise Edition Installer can be found from the Start menu under Programs; Administrative Tools. Enterprise Edition CD 2 will be needed.
Reinstall Service Pack 5. Service Pack 5 should be reinstalled after the above components have been installed. This can be accomplished via the command "C:\SRV_PACK\SP5\sp5i386 -n" where -n suppresses the creation of an uninstall directory. An uninstall directory is not of much use at this point since the underlying system is already at the SP5 level. Service Pack 5 can be reinstalled as often as needed.
Install additional service packs and features. The Service Pack 5 CD that comes with your system contains additional service packs and features that you may want to install. These include Internet Explorer, Microsoft WBEM, Microsoft Site Server Express, and Data Access Components Service Packs. More information is available in the NTSP5.htm file on the CD.
Change driver and service start options. If there are drivers or services that should not be started automatically, or that should be but are not, or that have ordering dependencies, they should be adjusted now.
Install and tailor management tools. Management tools or services that will be used, such as SNMP, should be installed before applications.
Install and tailor server applications. Applications should generally be installed last so that all the services they depend on can be located. These would include BackOffice components such as mail server(s), web server(s), as well as custom applications, etc.
Set folder and file sharing. If there are to be shared files on the server, the sharing options at the appropriate locations need to be set. If the folders to be shared do not exist, they should be created (and loaded) first.
Set performance options. If there are specific settings that are used to improve performance, they should be applied now.
Enable 3 GB application addressing. If you plan to use the 3 GB application addressing option, update boot.ini to include the required option: /3GB. You may want to have boot images that contain the option and omit the option for maximum flexibility when troubleshooting. See the "Enabling 4GT Support in Your Applications" topic in the readme.doc file located at the root of the Enterprise Edition CD-ROM, disk 1.
Create Emergency Repair Disk. Create the Windows NT emergency repair floppy disk using the rdisk.exe utility. This disk should be kept available for repair use and should be updated periodically, especially whenever the disk configuration is changed.