Start the installation from the i5/OS console
To install Windows 2000 Server or Windows Server 2003 on iSeries™, you need
*IOSYSCFG, *ALLOBJ, and *JOBCTL special authority. You must have your Windows
server license key available. In most cases, it is printed on the back of
the installation CD jewel case.
- When performing an installation type of *FULL, place the installation
CD in the iSeries server optical drive (unless you plan to use an image of the
installation CD).
When performing an Install type of *BASIC, place the ServerGuide™ CD in the attached xSeries® server CD-ROM drive.
- Use one of the following methods to begin the installation:
- If the Install Windows server (INSWNTSVR) command generated by the Windows
server installation advisor is available:
- Call QCMD at the i5/OS™ command line to start a command entry prompt and
select F11=Display Full.
- Paste the INSWNTSVR command generated by the Windows server installation
advisor at the i5/OS command line and press Enter to run the command.
- The installation starts and can take up to an hour. You may be prompted
to enter additional information. Afterward, go to Continue the installation from the integrated Windows server console.
- Otherwise, begin the installation at the i5/OS command line by typing INSWNTSVR and
pressing F4 to prompt the command. Type the values from the Installation worksheet for i5/OS parameters in
each of the following fields:
- In the Network server description field (see Network server descriptions for
more information), type the server name from the Installation worksheet for i5/OS parameters and
press Enter.
- In the Install type field, type the value
(*FULL or *BASIC) that you filled out in the Installation worksheet for i5/OS parameters.
- In the Resource Name field, type
the information that you filled out in the Installation worksheet for i5/OS parameters.
- Choose the Windows server version you want
to install; press Enter.
Note:
Windows Server 2003 is required for
iSCSI attached servers.
- If you want to install the server from a stored image instead of the physical
CD, specify the path to that image in the Windows
source directory field.
- In the Install option field, use the default
*INSTALL.
- If you want the installation to configure TCP/IP properties
for any network adapters installed in the iSeries which will be controlled by the new
integrated server, specify the Windows TCP/IP configuration values from the Installation worksheet for i5/OS parameters. Otherwise, skip this step and use the default value *NONE.
- To install and configure an optional virtual Ethernet port, specify the
Windows TCP/IP configuration values for the Virtual Ethernet port field from
the Installation worksheet for i5/OS parameters.
- Type the values from the Installation worksheet for i5/OS parameters in these
fields:
- TCP/IP local domain name
- TCP/IP name server system
- Server message queue
- Library
- In the Event log field, specify
which event log messages you want i5/OS to receive from the server.
- In the fields for the Server storage
spaces, type the values from the Installation worksheet for i5/OS parameters:
- Specify values for the Install source size and System size fields or select
the default *CALC to allow the system to calculate the minimum size.
- If you want to choose a different auxiliary storage pool (ASP) for the
install source and system drives, specify it in the corresponding element
of either the Storage space ASP or Server storage ASP device fields.
- For system drives up to 32 GB, in the Convert to NTFS field, you can specify *NO to leave the integrated server's system drive formatted
with the file allocation table (FAT32) file system. Otherwise, use the default
of *YES to convert the system drive to the New
Technology File System (NTFS) during the installation. For information that
might help you decide, see Comparison of FAT, FAT32, and NTFS file systems. The INSWNTSVR
command automatically converts system drives larger than 32 GB to NTFS if
necessary.
- Optional: Specify either a Windows workgroup
or domain in the corresponding To workgroup or To domain parameters.
- Optional: Specify the name of the user who holds
the Windows server license you are installing in the Full Name field.
- Optional: Specify the name of the organization that
holds the Windows server license you are installing, in the Organization field.
- In the Language version field, specify *PRIMARY to have the IBM® i5/OS Integrated Server Support use your primary
language. To prevent problems with predefined names that cannot be enrolled,
make sure that the integration licensed program and Windows server will be
using the same language. If you need to know which languages the command
supports, look at Supported language versions.
- In the Synchronize date and time field, specify *YES to have i5/OS synchronize the date and time with the
integrated server every 30 minutes. If you want i5/OS to synchronize the date and time with
the integrated server only when you vary it on, type *NO.
- In the Propagate domain user field, specify
if this server should be used to propagate and synchronize users to the Windows
domain or active directory.
- In the Windows license key field, specify
the CD key that Microsoft® has provided, including the
dash. In most cases, you can find this CD key printed on the back of the
Windows installation CD jewel case.
- In the License type field, specify the type
of Windows server license that you purchased.
- If you specified *PERSERVER in the License type field, then in the Client licenses field, specify the number of client licenses that you purchased.
- Enter the Terminal services options to install
in the Terminal services field.
- In the Restricted device resources field,
type the value from the Installation worksheet for i5/OS parameters.
- In the Shutdown timeout field,
specify the integrated server's shutdown time-out value in minutes. This is
used to limit the amount of time that the integrated server's operating system
is given to shut down before the server is varied off.
- If you are installing an IXA attached or IXS server, continue
to step 34 and fill out additional parameters. If you
are installing an ISCSI attached server, type the values for the iSCSI parameters
from the Installation worksheet for i5/OS parameters in the following fields:
- Activation timer
- Communications message queue
- In the Storage path field, specify the name of the Network server host adapter
to use for iSCSI storage communications. For more information, see Network server host adapters.
- In the Virtual Ethernet path field,
enter the name of one or more Network server host adapters to use for iSCSI
LAN communications.
- Specify at least one value for the *VRTETHPTP port and any additional
ports specified above for the Virtual Ethernet port field.
- Optional: Specify the Shutdown TCP port and the Virtual Ethernet control
port.
- Enter an existing network server configuration name for the
following fields or select the default values.
- Remote system NWSCFG
- Service processor NWSCFG
- Connection security NWSCFG
Press Enter.
- Enter the IP Security (IPSec) rule to use:
- For an existing Connection security NWSCFG:
- Specify the configured security rule to use the IP security rule field.
- Press Enter.
- For a defaulted Connection security NWSCFG:
- Specify the default IP Security (IPSec) rule to use in the Default IP
security rule field
- Press Enter.
- If prompted, enter service processor configuration information
from the Installation worksheet for i5/OS parameters in these fields, when using the defaulted Service processor NWSCFG name:
- In the Initialize service processor field:
- a. When initializing the service processor is any value other than *NONE,
enter a Component and Compare value for the SP certificate identifier field.
- Select the unicast option to use in the Enable unicast field:
- Enter value(s) for the Enclosure identifier field when not using unicast,
specify a value for the Serial number and optional Manufacturer type and model.
- When using unicast, specify a value for the Service processor name field
or enter an IP address in the SP internet address field.
- When using the defaulted Remote system NWSCFG name and when initializing
the service processor is any value other than *NONE, specify the SP authentication
values for User name and User password.
- If prompted, enter remote system configuration information
from the Installation worksheet for i5/OS parameters in these fields, when using the defaulted Remote system NWSCFG name:
- In the Remote system identifier field, specify
one of the following:
- Use the serial number identified by the Enclosure identifier field of
the Service processor NWSCFG.
- Specify a value for the Serial number and optional Manufacturer type and
model for the Remote system identifier field.
- In the Delivery method field, enter the method
used to configure the remote system.
- In the CHAP authentication field, enter the
Challenge Handshake Authentication Protocol (CHAP) values used to authenticate
the remote system.
- In the Boot device ID field, identify the
iSCSI adapter used to boot the remote system. Use the default value *SINGLE
if there is only one iSCSI boot device in the remote system.
- When using a *DYNAMIC Delivery method, optionally specify any additional
options in the Dynamic boot options field.
- In the Remote interfaces field, enter values
for the interface used in the remote system.
- In the SCSI interface field, enter values
for the SCSI function, including:
- The SCSI Adapter address
- The SCSI Internet address
- The SCSI Subnet mask
- Optional: Enter the SCSI Gateway address
- The iSCSI qualified name or allow the system to automatically generate
the address by entering *GEN.
- In the LAN interface field, enter values for the LAN function, including:
- The LAN (TOE) Adapter address
- The LAN Internet address
- The LAN Subnet mask
- Optional: Enter the LAN Gateway address
-
Filling out additional parameters allows you to do the
following things:
- Install a keyboard type on the integrated server other than the default.
(Valid keyboard style identifiers are listed in the TXTSETUP.SIF file in
the I386 directory of the Windows server installation source.)
- Use your own IP addresses for the point to point virtual Ethernet.
- Use an NWSD configuration file. See Network server description configuration files.
- Configure a new or existing Windows Cluster configuration.
Provide any other information that seems relevant for your needs
and press Enter.
The integrated Windows server starts to install. The second stage of the
installation process is Continue the installation from the integrated Windows server console. The process will take approximately
1 hour, depending on your hardware configuration.