Starting Windows Server 2003 installation from OS/400

Although this section is written for a *FULL type of installation, you can also use it for a

*BASIC type. Notice that some parameters in the INSWNTSVR command are not required for a *BASIC installation. Refer to Table 2-4 on page 41 to determine which parameters apply to

*BASIC and *FULL installations.

Note: When we used the wizard, selecting Windows .NET server as our Windows version, the final command contained the parameter WNTVER(*WIN2002), which must be changed to WNTVER(*WIN2003). This error may or may not have been corrected by the time you use it.

The installation of Windows Server 2003 on an IXA or IXS is performed in two phases.

Phase one runs on OS/400 and is triggered by the INSWNTSVR command, which you run from a green screen. During phase one, these tasks are performed:

*FULL installation

– A network server description (NWSD) that contains a description of the Windows integration environment, and associates the IXA or IXS hardware resource name with Windows Server 2003, is created.

– Network server storage spaces for the Windows Server 2003 system drive (C:) and install source drive (D:) are created in the specified auxiliary storage pool.

– The contents of the \i386 directory and its subdirectories are copied from the Windows Server 2003 installation CD-ROM or IFS to the D: drive.

– Programs, files, and device drivers specific to Windows Server 2003 running on the IXA server or IXS are copied into a directory named \i386\$OEM$ on the D: drive.

– An UNATTEND.TXT file that contains the Windows Server 2003 information entered in the INSWNTSVR command and that allows for an almost unattended installation of Windows Server 2003, is created.

– TCP/IP on OS/400 is started, if it is not already active.

– The network server description is varied on to start the DOS mini-boot image on the C:

drive. The AUTOEXEC.BAT file on drive C: contains the necessary statement to start the unattended installation of Windows Server 2003. If you watch the Windows Server 2003 console, you see the normal PC boot process, followed by DOS starting, and then the first stage of a standard Windows Server 2003 installation.

*BASIC installation

– A network server description (NWSD) that contains a description of the Windows integration environment, and associates the IXA or IXS hardware resource name with Windows Server 2003, is created.

– Network server storage spaces for the Windows Server 2003 system drive (C:) and install source drive (D:) are created in the specified auxiliary storage pool.

– Programs, files, and device drivers specific to Windows Server 2003 running on the IXA server or IXS are copied into a directory named \i386\$OEM$ on the D: drive.

– TCP/IP on OS/400 is started, if it is not already active.

– The ServerGuide installation process creates an UNATTEND.TXT file that contains the Windows Server 2003 information entered in the INSWNTSVR command and that allows for an almost unattended installation of Windows Server 2003.

– The ServerGuide installation process starts the DOS mini-boot image on the C: drive.

The AUTOEXEC.BAT file on drive C: contains the necessary statement to start the unattended installation of Windows Server 2003. If you watch the Windows Server 2003 console, you see the normal PC boot process, followed by DOS starting, and then the first stage of a standard Windows Server 2003 installation.

Phase two runs on the integrated Windows server. It consists of four stages called modes, which comprise the normal Windows Server 2003 installation process. The first three modes are completely unattended, while the fourth mode requires input from the Windows Server 2003 console:

Mode 1 – Character mode: All files necessary to complete the setup process from the D:

drive to a temporary directory are copied. The disk image is also prepared for the next phase of the installation. The server restarts.

Mode 2 – Text mode: All files required to create the server from the temporary directory to the installation folders are copied. The server restarts.

Mode 3 – Convert mode: The Windows Server 2003 installation partition is converted from the default FAT format to NTFS if CVTNTFS(*YES) was specified in the INSWNTSVR command, or if the size specified for the system drive in the INSWNTSVR command is 2048 MB or greater. The server restarts, and TCP/IP on OS/400 is started (if it is not already active).

Mode 4 – GUI mode: The Windows Server 2003 console prompts for additional information required to complete the installation.

During a *FULL installation, if the INSWNTSVR command fails before mode 4, OS/400 attempts to do a cleanup and removal of these objects created during installation:

Network server description

C: and D: drive network server storage spaces

Line descriptions

TCP/IP interface for the point-to-point Virtual Ethernet LAN

Message queue (if specified)

In this case, you must restart the installation from the beginning. Before you attempt another installation, ensure that all of these objects are really deleted.

Again, for a *FULL type of installation, if the Install Windows Server command (INSWNTSVR) fails during mode 4 (which is when the network server description is varied on, and Windows Server 2003 is started in GUI mode for the first time), the OS/400 side of the installation is complete. In this case, OS/400 does not attempt to clean up. All you have to do is sign on to Windows Server 2003 and attempt to complete the installation. (You may need to vary the NWSD off then on again from a green screen session first). If you are still unable to recover, uninstall the server and start again.

You are now ready to start the installation of Windows Server 2003 on the IXA server or IXS.

Make sure you:

Have filled out the worksheet in Table 2-4 on page 41 so that you have all of the necessary information in front of you.

Sign on to OS/400 with a profile that has *IOSYSCFG, *ALLOBJ, *JOBCTL, and

*SECADM special authorities.

To start the installation, follow these steps:

1. When performing a *FULL installation, ensure that the iSeries CD-ROM drive is varied on.

Insert the Windows Server 2003 installation CD-ROM (if you are not installing from a directory in the IFS).

2. To make sure that there is no network server description currently using the hardware resource on which you want to install, enter this command:

WRKCFGSTS *NWS

Time required: As a guide, the time required from when you have filled out all of the parameters on the INSWNTSVR command and press Enter, to the point where the basic Windows Server 2003 is installed, varies between 40 and 60 minutes. If you are installing on the latest hardware, installation takes around 40 minutes, but installing on older hardware takes longer. This time does not include any customization tasks (such as promoting the server to a domain controller) or completing the post-installation tasks.

Check the resource name of any varied on network server descriptions and vary off if necessary.

3. To install Windows Server 2003, verify that you have access to a user profile with the necessary authority (*IOSYSCFG, *ALLOBJ, *JOBCTL, *SECADM) to perform the installation.

Sign off your current session, then sign on again with the user profile used to perform the installation. Signing on again starts a new job log that captures the installation process.

4. Change the OS/400 QSYSOPR message queue delivery mode to something other than

*BREAK so that the installation is not interrupted using the Change Message Queue command (CHGMSGQ).

5. If you completed the Windows server installation advisor wizard and it built an installation command string for you, follow these steps:

a. Go to the browser session and highlight the command string.

b. Click Edit→ Copy.

c. On the command line of your green screen session, type call qcmd and press Enter.

d. Press the F11 key to expand the command entry to full screen.

e. Click Edit→ Paste. This pastes the installation command string onto the screen.

f. Press Enter to start the installation.

g. On the status line at the bottom of the display, you see progress messages as the installation proceeds. When you see the message Continue installation using the Windows server console, go to the Windows Server 2003 console to continue the installation.

h. Proceed to 3.5, “Completing installation from the Windows console” on page 70.

6. Type INSWNTSVR on the OS/400 command line and press F4.

7. Type in the information required to complete the first Install Windows Server

(INSWNTSVR) input display as shown in Figure 3-6 on page 66. Notice that this example is for an IXA, so you must specify *NONE for the TCP/IP port configuration parameter. Use the information from your completed worksheet as shown in Table 2-4 on page 41.

Figure 3-6 INSWNTSVR display (Part 1 of 7)

8. Enter information from the worksheet into the next four input displays of the Install Windows Server command (INSWNTSVR). Examples are shown in Figure 3-7, Figure 3-8 on page 67, Figure 3-9 on page 67, and Figure 3-10 on page 68.

Figure 3-7 INSWNTSVR display (Part 2 of 7)

Install Windows Server (INSWNTSVR)

In Figure 3-7 on page 66, the Library parameter for the Server message queue must exist for this command to be successful.

Figure 3-8 INSWNTSVR display (Part 3 of 7)

Figure 3-9 INSWNTSVR display (Part 4 of 7)

Install Windows Server (INSWNTSVR)

Figure 3-10 INSWNTSVR display (Part 5 of 7)

9. Press F10 to see additional parameters as shown in Figure 3-11 on page 69 and Figure 3-12 on page 69. This is only necessary if you wish to:

– Use a keyboard layout identifier other than the default on the Windows server.

– Use your own TCP/IP addresses for the virtual Ethernet LAN of the IXS. Notice that this parameter is only supported in V5R2 when installing Windows 2000 on the 333 MHz IXS, or Windows NT on any model of the IXS.

– Set up the LAN ports on the IXS to use the external host LAN capability. Notice that this function is only supported on AS/400 machines prior to the iSeries 2xx and 8xx models, and then only on the 200 MHz and 333 MHz IXSs.

– Use a network server description configuration (customization) file.

Install Windows Server (INSWNTSVR) Type choices, press Enter.

Cluster configuration:

Cluster domain name . . . *CLU Quorum resource ASP . . . 1-255 Connection port . . . *VRTETH0, *VRTETH1...

Cluster internet address . . . Cluster subnet mask . . . Account name . . . Account password . . . Character value Virtual PTP ethernet port:

OS/400 internet address . . . *GEN Windows internet address . . . *GEN Internal LAN port:

OS/400 internet address . . . *GEN Windows internet address . . . *GEN More...

F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Figure 3-11 INSWNTSVR display (Part 6 of 7)

Figure 3-12 INSWNTSVR display (Part 7 of 7)

10.Press Enter after you have filled out the last display. The installation process starts, unless you made an error or omitted a mandatory parameter. In this case a message appears at the bottom of the screen. Use the down arrow to move your cursor to the message and press F1 (Help). Notice that you may have to press F10 to view the joblog, which gives to more detailed information about the error. Correct the error and press Enter.

Install Windows Server (INSWNTSVR)

11.As installation proceeds, progress messages show on the status line at the bottom of the display. When you see the message Continue installation using the Windows server console, go to the Windows Server 2003 console to continue the installation.