ClearPath IX Systems Installation and Configuration Guide

ClearPath IX Systems Installation and Configuration Guide ClearPath IX Systems Installation and Configuration Guide

public.support.unisys.com
from public.support.unisys.com More from this publisher
24.12.2012 Views

Installing Windows NT Server 4.0 (DR/2) Table 6–1. Windows NT Server 4.0 Installation Checklist √ Media or Information Required 6.2. Steps to Take If Windows NT Is Preloaded Media needed: A blank diskette for creating an emergency repair disk. Information needed: Name and Organization screen Name __________________________ Organization _____________________________ Determine the name of the user (for example, the administrator) and organization responsible for the node. Registration screen Windows NT Registration Number: The Windows NT registration number is found on a Certificate of Authentication provided with the installation media. Server Type screen Have the client determine the Windows NT Server type: − Primary Domain Controller (PDC) Directly maintains security and user account information in the master copy of the domain’s directory database. − Backup Domain Controller (BDC) If BDC is selected, the PDC must be accessible on the LAN during setup of the BDC. The BDC maintains a replicated copy of the directory database maintained by the PDC. Can be promoted to serve as a PDC. − Member Server (default recommendation) Member (stand-alone) server mode is recommended in the following circumstances: If the server is to perform time critical tasks and the site does not want it spending time authorizing domain logon attempts or receiving synchronized copies of the domain’s directory database. If the site wants this server to have a different administrator or different user accounts from the rest of the servers in the domain. A member server can participate in a domain, although that is not required. This document describes installation procedures for a member server only. For more information about domain planning, refer to Microsoft Windows NT Server Version 4.0 Concepts and Planning. continued 6–2 Version 009B (Web Only) 7850 5104–009

Installing Windows NT Server 4.0 (DR/2) Table 6–1. Windows NT Server 4.0 Installation Checklist √ Media or Information Required 6.5. Installing and Configuring Windows NT Server 4.0 Media needed: • Setup diskettes—labeled “Microsoft Windows NT Server Setup Disk x” (where x is 1, 2, and 3) • Windows NT CD-ROM—labeled “Microsoft Windows NT Server” • RAID drivers diskette—labeled “NT 4.0 Supplemental Drivers Diskette" • Video drivers diskette—labeled “NT 4.0 Supplementary Drivers Diskette” • Blank 3-1/2 inch diskette (label this diskette “Emergency Repair Disk”) • DR/2 drivers diskette—labeled “Mylex Solution Software Kit 2.01 NT/NW Drivers Diskette" 6.5.2. Configuring Windows NT Server 4.0 Information needed: Name and Organization screen Name __________________________ Determine the name the site wants identified with the Windows NT node (for example, the administrator’s name or the Windows NT owner name). Organization _____________________________ Determine the organization name the site wants identified with the Windows NT node. Registration screen CD-KEY ______________________________________ To register Windows NT, you need the key number printed on a label on the back of the Windows NT CD-ROM jewel case or on the Certificate of Authentication. SNMP Properties screen System administrator name __________________________ Phone number __________________________ Location (room number) __________________________ Date/Time Properties screen; Time Zone tab screen Time zone at the site _____________________________ Daylight saving time: If daylight saving time is being used, check the check box provided on the Time Zone tab screen. 7850 5104–009 Version 009B (Web Only) 6–3

Installing Windows NT Server 4.0 (DR/2)<br />

Table 6–1. Windows NT Server 4.0 <strong>Installation</strong> Checklist<br />

√ Media or Information Required<br />

6.2. Steps to Take If Windows NT Is Preloaded<br />

Media needed: A blank diskette for creating an emergency repair disk.<br />

Information needed:<br />

Name <strong>and</strong> Organization screen<br />

Name __________________________<br />

Organization _____________________________<br />

Determine the name of the user (for example, the administrator) <strong>and</strong> organization responsible for<br />

the node.<br />

Registration screen<br />

Windows NT Registration Number:<br />

The Windows NT registration number is found on a Certificate of Authentication provided with the<br />

installation media.<br />

Server Type screen<br />

Have the client determine the Windows NT Server type:<br />

− Primary Domain Controller (PDC)<br />

Directly maintains security <strong>and</strong> user account information in the master copy of the<br />

domain’s directory database.<br />

− Backup Domain Controller (BDC)<br />

If BDC is selected, the PDC must be accessible on the LAN during setup of the BDC.<br />

The BDC maintains a replicated copy of the directory database maintained by the PDC.<br />

Can be promoted to serve as a PDC.<br />

− Member Server (default recommendation)<br />

Member (st<strong>and</strong>-alone) server mode is recommended in the following circumstances:<br />

If the server is to perform time critical tasks <strong>and</strong> the site does not want it spending time<br />

authorizing domain logon attempts or receiving synchronized copies of the domain’s<br />

directory database.<br />

If the site wants this server to have a different administrator or different user accounts<br />

from the rest of the servers in the domain.<br />

A member server can participate in a domain, although that is not required.<br />

This document describes installation procedures for a member server only. For more information about<br />

domain planning, refer to Microsoft Windows NT Server Version 4.0 Concepts <strong>and</strong> Planning.<br />

continued<br />

6–2 Version 009B (Web Only) 7850 5104–009

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!