ERserver. iseries. Windows server on iseries

Transcription

1 ERserer iseries Windows serer on iseries

2

3 ERserer iseries Windows serer on iseries

4 Copyright International Business Machines Corporation 1998, All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Windows serer on iseries Code disclaimer information What s new for V5R Print this topic Terminology How Windows serer on iseries differs from Windows on PC What is an Integrated xseries Serer for iseries? Adantages of Windows Serer on iseries Run multiple Windows serers on multiple Integrated xseries Serers Performance and capacity of Windows serer on iseries Install and configure iseries Integration for Windows Serer Hardware requirements for running Windows serer on iseries Integrated xseries Serer for iseries CCIN and feature code numbers Preinstallation checklist for iseries Integration for Windows Serer Machine pool size requirements for iseries Integration for Windows Serer Local area networks used by Windows serer on iseries Windows Cluster Serice on the iseries Integrated Windows Serer Installing Windows Cluster serice Installing Windows Cluster serice on a new Windows serer Installing Windows Cluster serice on an existing serer Preparing Windows before installing Windows Cluster serice Installing Windows Cluster serice on Windows Install Windows Cluster serice on Windows Install Windows Cluster serice on Windows.NET Time synchronization Verifying that OS/400 time zone is set Tip: Find resource names when you hae multiple Integrated xseries Serers Configuring OS/400 TCP/IP for Windows serer on iseries iseries Access for Windows on Windows serer on iseries Enabling iseries NetSerer Create a guest user profile for iseries NetSerer Comparison of FAT, FAT32, and NTFS file systems Network serer descriptions for Windows serer on iseries Supported language ersions Plan for iseries Integration for Windows Serer installation on Windows 2000 and Windows.NET 28 Installation work sheet for OS/400 parameters Windows serer installation adisor Install iseries Integration for Windows Serer Install Windows 2000 or Windows.NET Serer on the Integrated xseries Serer Software requirements for running Windows 2000 or Windows.NET Serer on iseries Start the Windows 2000 or Windows.NET Serer installation from the OS/400 console Continue the Windows 2000 and Windows.NET installation from the Windows serer console 43 Complete the installation of Windows 2000 and Windows.NET Serer on iseries Plan for iseries Integration for Windows Serer installation on Windows NT Install Windows NT 4.0 on the Integrated xseries Serer Software requirements for running Windows NT 4.0 on iseries Start the Windows NT 4.0 serer installation from the OS/400 console Continue the Windows NT 4.0 installation from the Windows serer console Complete the installation of Windows NT 4.0 on iseries Responding to error messages during installation Upgrade your serer from Windows NT 4.0 to Windows 2000 or Windows.NET Serer Upgrade and migration considerations for iseries Integration for Windows Serer and Integrated xseries Serer Copyright IBM Corp. 1998, 2002 iii

6 Set Windows serer to automatically ary on with TCP/IP Code fixes for iseries Integration for Windows Serer iseries Integration for Windows Serer Code and the Microsoft Windows Update Web site Types of iseries Integration for Windows Serer code fixes Check iseries Integration for Windows Serer serice leels on Windows 2000 and Windows.NET Serer Check iseries Integration for Windows Serer serice leels on Windows NT Install iseries Integration for Windows Serer serice packs on Windows 2000 or Windows.NET Serer View or install serice packs using Integration for Windows Serer Snap-in View or Install serice packs using iseries Naigator Install iseries Integration for Windows Serer serice packs for Windows NT Install and uninstall serice packs with the llsync command Remoe iseries Integration for Windows Serer serice pack and hot fixes on Windows 2000 and Windows.NET Serer Remoe serice packs and hot fixes using the Integration for Windows Serer Snap-in To iew or remoe serice packs and hot fixes using iseries Naigator Details: Remoe iseries Integration for Windows Serer serice packs Remoe iseries Integration for Windows Serer maintenance leels for Windows NT Upgrade iseries Integration for Windows Serer Upgrade OS/400 and iseries Integration for Windows Serer Upgrade Windows serers when you upgrade iseries Integration for Windows Serer Upgrade iseries Integration for Windows Serer using iseries Naigator Migrating to 2890 Integrated xseries Serer hardware Install the Saage 4 Video Drier for Windows NT 4.0 on the 2890 Integrated xseries Serer 70 Migrating to 50xx Migration Tower Add new network adapters to Windows serer on iseries Create line descriptions for network adapters shared between OS/400 and Windows serer on iseries Configure Virtual Ethernet connections to OS/400, another Windows serer, or LPAR on iseries 73 Add a TCP interface for a new shared network adapter Update network serer descriptions with Windows serer adapter information Install network adapter driers and adding adapter address information to Windows serer Install network adapter driers and add adapter address information to Windows serer for Windows 2000 or Windows.NET Serer Install network adapter driers and add adapter address information to Windows serer for Windows NT Installing OS/400 Multi-Port protocol drier Install Gigabit Ethernet adapters on Windows NT Remoing network adapters from Windows serer on iseries Administer Windows serer on iseries Starting and stopping Windows serer on an Integrated xseries Serer for iseries Starting Windows serer from OS/ Start Windows serer without starting the external host LAN Shut down Windows serer from OS/ Details: Vary off a Windows serer NWSD when OS/400 is sharing LAN adapters on the Integrated xseries Serer Shut down Windows serer on iseries from Windows serer Restart Windows serer on iseries from Windows serer Aoid data loss when entering restricted state or powering down iseries Manage your Windows serers from OS/ Manage properties for Windows serer on iseries Display Windows serer information on OS/ Monitor Windows serer eent logs on OS/ Print from Windows serer on iseries Run Windows serer batch commands from OS/ i iseries: Windows serer on iseries

7 Considerations for running Windows serer batch commands from OS/ Manage storage OS/400 storage management Disk dries for Windows serer on iseries Predefined disk dries for Windows serer on iseries Administer Windows disk dries from OS/ Access the OS/400 integrated file system from Windows serer on iseries Obtain information about disk dries for Windows serer on iseries Add disk dries for Windows serer on iseries Create disk dries for Windows serer on iseries Link disk dries for Windows serer on iseries Format disk dries for Windows serer on iseries Copy a disk drie Unlink disk dries from Windows serer on iseries Deleting disk dries for Windows serer on iseries Deleting disk dries when remoing a Windows serer Use Windows disk management programs with Windows serer on iseries Administer Windows serer users from OS/ User and group enrollment to Windows serer Enable OS/400 user enrollment on Windows serers Limit QAS400NT user profile changes Use PRPDMNUSR to control user enrollment Enroll a single user to Windows serer on iseries Details: Enrolling users to Windows serer on iseries with network serer attributes Create user templates for Windows serer on iseries User enrollment templates Preent accidental deletion of users from Windows serer Enroll OS/400 groups to Windows serer on iseries Enrolling only the members of OS/400 groups to Windows serer on iseries Check enrollment status End user enrollment to Windows serer on iseries Effects of ending user enrollment to Windows serer on iseries End group enrollment to Windows serer on iseries Effects of ending group enrollment to Windows serer on iseries Share deices Determine the deice description and hardware resource names for iseries deices Use iseries optical dries with Windows serer on iseries Use iseries tape dries from Windows serer Supported iseries tape dries Format a tape on OS/400 for Windows serer Allocate the iseries tape drie to Windows serer on iseries Identify iseries tape deices for applications Transfer control of the iseries tape and optical dries between Windows serers Return control of a tape drie from Windows serer to iseries Return control of an optical deice from Windows serer to iseries Print from Windows serer on iseries to iseries printers Back up and recoer Windows serer on iseries Back up the NWSD and disk dries associated with Windows serer on iseries Back up NWSDs for Windows serer on iseries Back up predefined disk dries for Windows serers created on V4R5 and later OS/400 systems 118 Back up predefined disk dries for Windows serers created on pre-v4r5 OS/400 systems 118 Back up user-defined disk dries for Windows serer What objects to sae and their location on OS/ Back up indiidual Windows serer files and directories File-leel backup restrictions Preliminary administrator setup tasks Contents

8 Create shares on Windows serer Add members to QAZLCSAVL file Ensure iseries NetSerer and Windows serer are in same domain Sae your files Examples: How to address parts of Windows serer Windows Backup utility Restore the NWSD and disk dries for Windows serer on iseries Restore predefined disk dries for Windows serers created on V4R5 and later systems Restore predefined disk dries for Windows serers created on pre-v4r5 systems Restore user-defined disk dries for Windows serers on iseries Restore NWSDs for Windows serer on iseries Recoer Windows serer files Sae and restore user enrollment information Uninstall Windows serer from Integrated xseries Serer Delete network serer descriptions for Windows serer on iseries Delete line descriptions for Windows serer on iseries Delete TCP/IP interfaces associated with Windows serer on iseries Delete controller descriptions associated with Windows serer on iseries Delete deice descriptions associated with Windows serer on iseries Delete iseries Integration for Windows Serer Troubleshoot Windows serer on iseries Check message and job logs Monitor job Troubleshoot problems with Windows serer on iseries Blue screen errors on Windows serer on iseries A full system drie on Windows serer on iseries Remapping a full C drie on Windows serer on iseries Drie letters Optical deice problems on Windows serer on iseries Locked optical deice for a failed serer Tape problems on Windows serer on iseries Verify that the iseries Tape Drie deice drier is loaded Display problems with Windows NT Problems starting Windows serer on iseries Vary-off failures of Windows serer on iseries NWSD configuration file errors Repair the NWSD configuration file Reset NWSD configuration file parameter Use a preious ersion of the Windows serer file DASD in externally attached xseries serers HSL communication problems with the Integrated xseries adapter Failures enrolling users and groups on Windows serer on iseries User and group enrollment from a Windows NT 4.0 serer to a Windows 2000 or Windows.NET Serer User-enrollment authorization problems Password problems Leel Check or Integration for Windows Serer snap-in program for Windows serer on iseries 147 Virtual Ethernet connection problems Troubleshooting Virtual Ethernet problems OS/400 external LAN when sharing network adapters External LANs for Windows 2000 and Windows.NET Serer Manually update LAN driers in Windows 2000 or Windows.NET Begin the LAN drier installation or update Select the adapter to install or update Complete the LAN drier installation or update Priate LAN IP address conflicts i iseries: Windows serer on iseries

9 Details: assign priate LAN IP addresses IP forwarding problems TCP/IP failure between OS/400 and Windows IFS access problems Problems with saing Windows serer files Unreadable messages in the serer message queue Problems getting a Windows serer system memory dump Reinstall Windows serer on iseries Collect serice data for Windows serer on iseries Create a Windows serer memory dump on OS/ Use the network serer description (NWSD) dump tool on OS/ Network serer description configuration files NWSD configuration file format Create an NWSD configuration file Example: NWSD configuration file Remoe lines from an existing Windows serer file with CLEARCONFIG entry type TARGETDIR keyword TARGETFILE keyword Change a Windows serer file with ADDCONFIG entry type VAR keyword ADDSTR keyword ADDWHEN keyword ADDWHEN and DELETEWHEN expression operators DELETEWHEN keyword LINECOMMENT keyword LOCATION keyword LINESEARCHPOS keyword LINESEARCHSTR keyword LINELOCATION keyword FILESEARCHPOS keyword (ADDCONFIG entry type) FILESEARCHSTR keyword FILESEARCHSTROCC keyword REPLACEOCC keyword TARGETFILE keyword UNIQUE keyword VAROCC keyword VARVALUE keyword Change a Windows serer file with UPDATECONFIG entry type FILESEARCHPOS keyword (UPDATECONFIG entry type) FILESEARCHSTR keyword (UPDATECONFIG entry type) FILESEARCHSTROCC keyword (UPDATECONFIG entry type) Setting configuration defaults with the SETDEFAULTS entry type ADDWHEN DELETEWHEN FILESEARCHPOS keyword (SETDEFAULTS entry type) FILESEARCHSTR keyword (SETDEFAULTS entry type) TARGETDIR TARGETFILE Use substitution ariables for keyword alues Related information Contents ii

10 iii iseries: Windows serer on iseries

11 Windows serer on iseries If you are already familiar with iseries Integration for Windows Serer, you might want to start with What s new for V5R2 on page 2 for this release. If you want, you can Print this topic on page 3 or display a Portable Document Format (PDF) ersion of the Windows serer on iseries information. Running Windows serer on an What is an Integrated xseries Serer for iseries? on page 5 is easy and only a little How Windows serer on iseries differs from Windows on PC on page 4 than running Windows NT (R) 4.0, Windows (R) 2000, or Windows (R).NET Serer on a PC. It proides some adantages such as allowing you to use iseries disk storage,iseries optical dries, and iseries tape dries. It also gies you the benefits of OS/400 administration. To use Windows serer on iseries, you need these items: The licensed program iseries Integration for Windows Serer (product number 5722-WSV), and either option 1 (for Windows NT 4.0) or option 2 (for Windows 2000 and Windows.NET Serer). This program comes on one of the Operating System/400 CD-ROMs, and there is no extra charge for it One of the following is needed: An Integrated xseries Serer for iseries An Integrated xseries Adapter for iseries along with a supported externally attached xseries serer An Integrated Netfinity Serer for AS/400 Licenses for the Windows serer that you purchase from your Microsoft reseller. Up and running Install and configure iseries Integration for Windows Serer on page 7 the integration software and a supported ersion of Windows 2000, Windows.NET, or Windows NT 4.0 on your iseries. Learn about code fixes, upgrading your software, and installing and remoing network adapters. Windows serer and users management Administer Windows serer on iseries on page 80 from OS/400. Start and stop the serer, run Windows serer batch commands remotely, monitor serer operation, and print to OS/400 printers. Go to Manage storage on page 89 for information about storing data and sharing network files. Administer Windows serer users from OS/400 on page 98 from OS/400. Change passwords and enrollment status. Use templates to create user and group profiles. Share deices on page 109 such as tape and optical dries and printers. Planning your backup strategy, handling problems, and uninstalling the program. Read information about Back up and recoer Windows serer on iseries on page 116 that is specific to iseries Integration for Windows Serer. If necessary, Uninstall Windows serer from Integrated xseries Serer on page 130 Windows serer from your OS/400 system. Use the Troubleshoot Windows serer on iseries on page 133 articles to help you sole problems. Read suggestions for collecting serice data and soling specific problems. Find Related information on page 179 sources. Code disclaimer information This document contains programming examples. Copyright IBM Corp. 1998,

12 IBM grants you a nonexclusie copyright license to use all programming code examples from which you can generate similar function tailored to your own specific needs. All sample code is proided by IBM for illustratie purposes only. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. All programs contained herein are proided to you AS IS without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed. What s new for V5R2 This release brought a number of changes and enhancements to Windows serer. It also proides enhancements to the Windows Administration section of iseries Naigator. The changes and enhancements for this release include: Support for Windows.NET Standard and Enterprise Serer was added. Official support will be proided within 30 days of their general aailability. For more information and the specifc requirements to run Windows.NET, see the IBM Windows Integration Web site. Support for Windows Cluster Serice on the iseries Integrated Windows Serer on page 19. Support for linking up to 16 shared disk dries for clustered Windows serers which increases the total number of disk dries on clustered serers to 48. Windows system drie size has increased to MB for supported Integrated xseries Serers and Integrated xseries Adapters when using Windows 2000 or Windows.NET serers. Support for read-only disk dries to be shared between Windows.NET Serers. A Delete Windows Serer (DLTWNTSVR) command was added. In iseries Naigator, a Run Windows command function was added to the Windows Administration section. In iseries Naigator, iseries Integration for Windows Serer serice functions were added to the Windows Administration section. Support for Tape Auto Cartrage Loader (ACL) was added. Support for Virtual optical media library was added. Support for managing user domain enrollment on multiple Windows serers was added. User enrollment support was added for organizational units in the Windows 2000 Actie Directory. Enhanced the usability of the iseries Integration MMC Snap-in for Serice and Deice Locking functions. Support for high speed Virtual Ethernet networks was added. A Virtual Ethernet network is much faster and more ersatile than a token ring Internal LAN. New hardware type 2892, model 001 Integrated xseries Serer card is aailable (see Integrated xseries Serer for iseries CCIN and feature code numbers on page 10 for Integrated xseries Serer cards that work with Windows serers). Details of the 2892 were not aailable when this topic was written. For more information about the 2892, including technical specifications, see the IBM Windows Integration Web site. 2 iseries: Windows serer on iseries

13 Print this topic To iew or download the PDF ersion, select Windows serer on iseries (about 192 pages or 985 KB). Saing PDF files To sae a PDF on your workstation for iewing or printing: 1. Right-click the PDF in your browser (right-click the link aboe). 2. Click Sae Target As Naigate to the directory in which you would like to sae the PDF. 4. Click Sae. Downloading Adobe Acrobat Reader If you need Adobe Acrobat Reader to iew or print these PDFs, you can download a copy from the Adobe Web site Terminology The following terms and concepts are new for V5R2. For more terms and concepts, see the Information Center glossary. Cluster serice The Windows cluster serice manages the cluster specific actiities and is installed on each node of the cluster. The components of the Cluster serice proide high aailability, easy management and enhanced scalability for Windows. Forming a cluster The first node of a cluster to install the Cluster serice attempts to gain control of the quorum resource and forms the cluster by creating cluster recoery databases. Windows 2000 Adanced serer allows for two-node clusters while Windows.NET Enterprise Serer allows for four-node clusters. Joining a cluster Additional nodes join an existing cluster when they can communicate with another actie clustered node and can alidate the node name and ersion compatibility. Node A node is a network serer that participates in a Windows cluster. A cluster is formed by joining together two or more network serers from the same iseries serer partition. All jointed network serers share a common quorum resource drie, which appears on a shared SCSI bus, and can communicate with each other through the Virtual Ethernet. Each node can detect the other nodes as they join or leae the cluster. Node-to-node communication Internal communication between clustered nodes uses the Virtual Ethernet as the priate network (or interconnect) that carries the heartbeat. The Cluster serice on each node uses a heartbeat to keep track of the current state of the nodes within the cluster. The Cluster serice uses the heartbeat to: Determine when a failoer to another node should occur Synchronize the cluster databases on each node Verify node failures during a cluster configuration change. The priate network uses the single network Virtual Ethernet model. Quorum resource Eery cluster contains a single drie designated as the quorum resource. It contains the Windows serer on iseries 3

14 configuration data used by the cluster to recoer the cluster database. The quorum resource is created as a network serer storage space with the cluster name specified on the Cluster name and uses the Cluster configuration information. Shared dries Network serer storage spaces can be linked as shared using the Add Serer Storage Link (ADDNWSSTGL ACCESS(*SHRUPD)) parameters once a quorum resource drie has been created and linked to a node. Dries which are shared appear to Windows as though they were on a common shared storage bus and can be controlled as separate resources by the Cluster serice. These dries can be failed oer to another node in the cluster. How Windows serer on iseries differs from Windows on PC Although running Windows serer on an What is an Integrated xseries Serer for iseries? on page 5 is much like running it from a PC, there are a few differences: Because of the hardware implementation of the Integrated xseries Serer, the most obious difference between it and a PC-based serer is the absence of a diskette drie. Unless you hae an externally attached xseries serer with a diskette drie, you cannot use a startup diskette or an emergency repair diskette with your Integrated xseries Serer. Howeer, you can use iseries disk space to back up your Windows serer files. Additionally, an externally attached xseries serer can hae a diskette drie. Although the Integrated xseries Serer has no tape or disk dries of its own, it can use iseries deices. Integrated xseries Serer does not require LAN adapters, cables, hubs, or switches for TCP/IP communication with other parts of the iseries system or other Integrated xseries Serers oer the Virtual Ethernet LAN. Installing Windows serer on an Integrated xseries Serer is different from a typical PC serer installation. You first install the integration software on OS/400, then install Windows serer. You enter much of the configuration information with the OS/400 INSWNTSVR command, so some of the usual Windows serer installation panels do not appear. This command also includes some additional parameters that are specific to integrating the serer with OS/400, such as Synchronize date and time. On the OS/400 side of serer management, a Windows serer is represented by a network serer description (NWSD), and network interfaces are represented by line descriptions (LINDs). You can stop and restart the serer from OS/400 by arying the NWSD off and on. When you install applications, you do not need to install tape driers. The driers that allow Windows serer to use iseries tape dries come with the Integrated xseries Serer. You can do a lot of your user administration tasks from OS/400, such as creating Windows users. Because OS/400 OS/400 storage management on page 89 differently than a PC, some techniques necessary to administer storage on a PC are unnecessary when you run Windows serer on the Integrated xseries Serer. You do not need to partition high-growth databases, defragment disks, or employ disk striping on your Integrated xseries Serer. You might also want to read about the Adantages of Windows Serer on iseries on page 5 and the Performance and capacity of Windows serer on iseries on page 7 of 4 iseries: Windows serer on iseries

15 What is an Integrated xseries Serer for iseries? Figure 1. An Integrated xseries Serer The Integrated xseries Serer for iseries is essentially a PC on a card. It contains an Intel processor and memory. You install it in iseries much like a memory upgrade. Similarly, the Integrated xseries Adapter for iseries is an HSL bus adapter plugged into a supported Netfinity or xseries Serer. The Netfinity or xseries Serer appears as an HSL attached expansion unit to the iseries system. Neither contains disk dries; OS/400 storage is allocated to each serer. You can configure the disk as one or more irtual dries of arying sizes. These irtual dries are allocated within the OS/400 integrated file system. The PC software perceies them as physical hard dries. Depending on the model, the Integrated xseries Serer card has either parallel and serial ports or a Uniersal Serial Bus (USB) and can support Token Ring and Ethernet (copper or fiber based) adapters. A keyboard, mouse, and monitor are directly attached to the Integrated xseries Serer card. In conjunction with the Integrated xseries Serer card, these peripherals act as the console for the Windows serer software. Integrated and HSL-attached serers can securely communicate with OS/400 using TCP/IP, without going through LAN hardware. The newer models can also securely communicate with each other and with logical partitions on the same system without going through LAN hardware. Because the hardware type 289x Integrated xseries Serers require a Peripheral Component Interconnect (PCI) nodes infrastructure, it is aailable on OS/400 systems at Version 4 Release 5 and later. For more specific information, refer to: Performance and capacity of Windows serer on iseries on page 7 Integrated xseries Serer for iseries CCIN and feature code numbers on page 10 Adantages of Windows Serer on iseries iseries Integration for Windows Serer proides most of the capabilities of running Windows serer on a personal computer and proides the following adantages: Space saings A smaller hardware footprint, with fewer pieces of hardware to manage, than an iseries system and a separate PC serer. Greater accessibility and protection for your data Access to iseries disk storage, which is generally more reliable than PC hard disks. Improed disk storage access performance because storage is spread across multiple disk storage arms. Access to the faster iseries tape dries to back up Windows serer. Windows serer on iseries 5

16 Better data protection if you use mirroring or RAID on OS/400. Windows serer implicitly takes adantage of it to protect your data. Add additional storage to a Windows 2000 or Windows.NET Serer without arying the serer off (2890, 2892, and 2689 models). Gain access to DB2 UDB for iseries data through an enhanced Open Database Connectiity (ODBC) drier using iseries Access. This drier enables serer-to-serer applications between Windows serer and OS/400. The ability to use iseries Integration for Windows Serer as a second tier in a three-tier client/serer application. Secure TCP/IP communications with OS/400 without using LAN hardware. Simplified administration Simplified administration of user parameters, such as passwords, from OS/400. You can create users and groups and enroll them from OS/400 to Windows serers on Integrated xseries Serers. This makes updating passwords and other user information from OS/400 easy. Easier maintenance of members in a group. Integration of user administration function, security, serer management, and backup and recoery plans between the OS/400 and Windows serer enironments. For V4R5 and later releases you can sae your Windows serer data on the same media as other OS/400 data and restore indiidual files as well as OS/400 objects. Multiple serers The ability to simultaneously run Run multiple Windows serers on multiple Integrated xseries Serers on multiple Integrated xseries Serers on a single iseries. Also, the ability to simply switch to another up-and-running serer if the hardware fails. Cluster serice, aailable only for Windows 2000 Adanced Serer or Windows.NET Enterprise Serer running on an Integrated xseries Serer or Integrated xseries Adapter, enables connecting multiple serers into serer clusters. Serer clusters proide high-aailability and easy manageability of data and programs running within the cluster. High-performance, secure TCP/IP communications with other serers and logical partitions on the same system without using LAN hardware. This is aailable only for Windows 2000 or Windows.NET serers running on an Integrated xseries serer or Integrated xseries adapter. Remote management and problem analysis Ability to sign on to OS/400 from a remote location and shut down or restart your Windows serer. Remote analysis of Windows serer errors because you can mirror Windows serer eent log information to OS/400. Direct-attached xseries Serer Greater scalability Better currency with Intel processor offerings Wider aailability of supported PCI feature cards Run multiple Windows serers on multiple Integrated xseries Serers If you hae multiple Integrated xseries Serers installed on your iseries, you can define their domain roles in a way that will simplify user enrollment and access. For example, you might want to set up one of these serers as a Windows serer domain controller and the others as Windows serers on the same domain. If you set up your serers this way, you enroll users to only the domain. Users can then log on to the domain from any Windows serer machine on that domain. Users can hae multiple Windows belonging to the same Windows domain. When the administrator enrolls users to a domain, there may be multiple Windows serers to which enrollment can be processed. A network serer description parameter can be used to specify whether domain enrollment is allowed. The Propagate Domain User (PRDMNUSR) 6 iseries: Windows serer on iseries

17 parameter of the Install Windows Serer (INSWNTSVR), Change Network Serer Description (CHGNWSD), and Create Network Serer Description (CRTNWSD) commands proide the capability to determine whether to allow user enrollment to domains. The ability to turn user enrollment off and on reduces redundant network processing. Multiple Windows serers on Integrated xseries Serers can share the iseries CD-ROM and tape dries. Howeer, only one serer at a time can use an iseries CD-ROM or tape drie because it must first be Allocate the iseries tape drie to Windows serer on iseries on page 112 to the serer. If your iseries serer has logical partitions, you may only allocate CD-ROM and tape dries that exist in the same partition as Performance and capacity of Windows serer on iseries The Integrated xseries Serer on which Windows serer runs has a 200 MHz Pentium Pro, 333 MHz Pentium II, 700 MHz Pentium III, 850 MHz Pentium III, or 1.0 GHz Pentium III processor. The Pentium Pro processor has a 512 KB L2 cache and from 64 MB to 512 MB of memory. The Pentium II processor has a 512 KB cache and up to 1 GB of memory. The 700 MHz or 850 MHz Pentium III processor has a 256 KB L2 cache and up to 4 GB of memory. For benchmarks that are processor intensie, you can refer to capacity charts for similarly configured personal computers. Most benchmarks are dependent on much more than the processor speed. Disk dries also play an important part in understanding the performance and capacity of a system. Windows serer on an Integrated xseries Serer does not use traditional disk dries. Instead, it uses space in OS/400 single leel store to simulate disk dries for Windows serer. Therefore, you need to add the disk requirements of Windows serer to that of OS/400 to determine if disk capacity is adequate. On the iseries, the disk actiity should be monitored to determine if you hae adequate disk capacity. You may also monitor system loads by using the Work with Disk Status (WRKDSKSTS), Work with Network Serer Storage Spaces (WRKNWSSTG), and Work with Network Serer Status (WRKNWSSTS) commands. For many other performance issues, Windows serer on an Integrated xseries Serer behaes like a PC-based Windows serer. You can use the Windows serer Performance Monitor as you would on a PC. See Windows serer documentation from Microsoft for information about using the Performance Monitor. Use the following links to see more performance-related information: For supported hardware and detailed performance numbers, see the IBM Windows Integration Web site For more information about performance tools and IXS performance, see the iseries Performance Management Web site For more information about IXS performance, see Chapter 17 of the iseries Performance Capabilities Reference on the Install and configure iseries Integration for Windows Serer Installing Windows serer on an Integrated xseries Serer inoles installing two separate pieces of software: IBM iseries Integration for Windows Serer and the Windows serer software from Microsoft. If you use logical partitions on your iseries: Verify that 5722-WSV is already installed and if not, install it. There is no requirement to install the licensed program on all the logical partitions. For example, one logical partition might hae Integration Windows serer on iseries 7

18 for Windows Serer and one or more Windows serers installed while another logical partition has neither Integration for Windows Serer nor any Windows serers installed. Note: You can hae both Option 1 and Option 2 installed on a partition. You need to install the Integration for Windows Serer and a Windows serer only on the logical partition that you will use to ary on the serer. If you want to run both Windows NT 4.0 and Windows 2000 or Windows.NET Serer, you can install both options of iseries Integration for Windows Serer on an iseries or partition. When you install a Windows serer on OS/400, you specify the ersion of Windows and the hardware resource by a network serer description (NWSD) object. Howeer, you can hae only one NWSD aried on (running) for a gien hardware resource at any gien time. Once you hae set up TCP/IP on OS/400, decide how many Windows serers and subnets you need for your particular business. One larger model of iseries can hold up to 32 indiidual Windows serers. Obtain TCP/IP addresses from your network administrator. These include: IP addresses for all external TCP/IP ports Subnet mask Your domain name or workgroup name IP address for your Domain Name System (DNS) serer, if you hae one IP address of the default gateway for your local area network (LAN), if you hae one If you are already running TCP/IP on your OS/400 system, you might be able to use the same alues that your OS/400 system uses for the last two items in the list. (To do this, specify *SYS for those parameters on the INSWNTSVR command.) Note: Microsoft documentation tells you to disable disk mirroring and disconnect any uninterruptible power supply before installing or upgrading to Windows 2000 or Windows.NET Serer. Be aware that this does not apply to disk mirroring or an uninterruptible power supply that you hae on your iseries. The installation requires basic iseries operational skills and a knowledge of Windows NT 4.0, Windows 2000, or Windows.NET and knowledge of network administration. Other setup tasks that you might want to do with your Integrated xseries Serer include: Code fixes for iseries Integration for Windows Serer on page 56 Upgrade iseries Integration for Windows Serer on page 64 to a new software ersion. Migrating to 2890 Integrated xseries Serer hardware on page 67 to new Integrated xseries Serer hardware. Install a Add new network adapters to Windows serer on iseries on page 71. Remoing network adapters from Windows serer on iseries on page 78 When you are ready to begin installation, select the Windows operating system that you will be installing: Plan for iseries Integration for Windows Serer installation on Windows 2000 and Windows.NET on page 28 Plan for iseries Integration for Windows Serer installation on Windows NT 4.0 on page 45 Hardware requirements for running Windows serer on iseries To run iseries Integration for Windows Serer, you need the following hardware: Any 64-bit RISC iseries or AS/ iseries: Windows serer on iseries

19 Integrated xseries Serer for iseries CCIN and feature code numbers on page 10 that is compatible with your model of iseries (an internal Integrated xseries Serer, internal Integrated Netfinity Serer, or an Integrated xseries Adapter along with a supported external xseries serer model): Attached SVGA compatible monitor Attached mouse or other pointing deice At least 128 MB of random access memory (RAM) At least 256 MB of RAM for Windows.NET Serer Attached keyboard You need free iseries disk space for each network serer description. Depending on the drie size you specify when you install your serer, that required disk space can range from 1224 MB up to MB. Up to 100 MB of free iseries disk space for the code of the iseries Integration for Windows Serer licensed program. One or more approed LAN ports or PCI adapters: The IBM iseries 2892 Integrated xseries Serer supports the following IBM iseries LAN ports or PCI adapters: - iseries /100 Ethernet port - Feature Code High-Speed 10/16/4 MB Token-ring PCI Adapter - Feature Code iseries Gigabit Ethernet Adapter (fiber optic) - Feature Code iseries 1000/100/10 Ethernet Adapter (copper UTP) The IBM iseries 2890 Integrated xseries Serer supports the following IBM iseries LAN PCI adapters: - Feature Code iseries Gigabit Ethernet Adapter (fiber optic) - Feature Code High-speed 100/16/4 MB Token-Ring PCI Adapter - Feature Code iseries Gigabit Ethernet Adapter (copper UTP) - Feature Code 4838 (hardware type 2838) - iseries 10/100 Ethernet Adapter The 6617 and 2850 Integrated Netfinity Serers support the following IBM iseries LAN PCI adapters: - Feature Code iseries Ethernet Adapter (10 Mbit/s) - Feature Code PCI Token-Ring Adapter (16/4 Mbit/s) - Feature Code IBM iseries 10/100 Ethernet Adapter Note: The Integrated xseries Serer cannot share its external LAN adapters with OS/400 (you cannot define OS/400 line descriptions for the external LAN adapters) if any of the following are true: It is a model 2890 or 2892 Integrated xseries Serer or a model 2689 Integrated xseries adapter. The IP forwarding function is enabled on Windows serer. The Integrated Netfinity hardware was migrated to a 50xx Migration tower. In these instances, OS/400 needs a separate LAN adapter on another input-output processor (IOP) in order to access the same LAN as the Windows serer. If you plan to run seeral Windows serers on multiple Integrated xseries Serers and need to see only one serer screen at a time, you can use an automated monitor, keyboard, and mouse switch. Connecting this box to the Integrated xseries Serers enables one set of deices to control multiple integrated Windows serers. Note: 2892 IXS hardware and 2689 IXA attached hardware do not support Windows NT 4.0. For additional hardware requirements, see: Windows serer on iseries 9

20 Machine pool size requirements for iseries Integration for Windows Serer on page 12 Local area networks used by Windows serer on iseries on page 13 You may want to read the following information: Planning for iseries Integration for Windows Serer installation Software requirements for running Windows 2000 or Windows.NET Serer on iseries on page 41 Software requirements for running Windows NT 4.0 on iseries on page 46 Upgrade and migration considerations for iseries Integration for Windows Serer and Integrated xseries Serer on page 54. Integrated xseries Serer for iseries CCIN and feature code numbers The Integrated xseries Serer for iseries hardware that you need to install Windows serer on your iseries is identified by a feature code and a custom card identification number (CCIN). This table shows the relationship between those numbers and which Integrated xseries Serer card you can use for your model of iseries. Feature Code System Model CCIN Numbers # A-003 # / S10/S A-003 # A-003 # / S10/S20 720/730/ A-003 # , A-003 # Description Pentium Pro Integrated xseries Serer Windows serer bridge Pentium Pro Integrated xseries Serer Windows serer bridge Pentium Pro Integrated xseries Serer Windows serer bridge Pentium II Integrated xseries Serer Windows serer bridge Pentium II Integrated xseries Serer Windows serer bridge Pentium II Integrated xseries Serer # , 830, 840, SB2, SB3, A003 Windows serer bridge **Pentium III Integrated xseries Serer # **Pentium III Integrated xseries Serer #6617 All RISC systems with Book Packages Pentium Pro Integrated xseries Serer #6618 All RISC systems with Book Packages # , 820, 830, 840 # , 830, 840 SB2, SB3, Pentium II Integrated xseries Serer ** Integrated xseries Adapter for iseries. Note: The Integrated xseries Adapter for iseries must be ordered ia AAS/WTAAS using Machine Type **Pentium III Integrated xseries Serer 10 iseries: Windows serer on iseries

21 Feature Code System Model CCIN Numbers Description # **Pentium III Integrated xseries Serer # , 830, 840, **Pentium III Integrated xseries Serer SB2, SB3, 890 # **Pentium III Integrated xseries Serer # , 830, 840, ** Integrated xseries Serer SB2, SB3, 890 # ** Integrated xseries Serer Notes: 1. **These Integrated xseries Serer for iseries models cannot sere as an external host LAN for your iseries. 2. Any Integrated Netfinity Serer migrated to a 50xx Migration Tower cannot sere as an External Host LAN for your iseries. 3. Throughout this information, unless specifically stated otherwise, the following conentions apply: The name 2890 Integrated xseries Serer applies equally to feature codes #2790, 2791, 2799, 2890, 2891, and 2899 The name 2892 Integrated xseries Serer applies equally to feature codes #2792 and Feature codes #2854, #2865, #6617, #6618 can be used in an 820, 830, 840, or SBx iseries system model when attached ia a 50xx Migration Tower. Preinstallation checklist for iseries Integration for Windows Serer Performing a few preliminary tasks before installing Windows serer on iseries should make the installation go smoothly. Before you begin installing the software, do the following: 1. Verify that you hae the necessary authority to perform the installation. To set up Windows serer on an Integrated xseries Serer, you must hae *IOSYSCFG, *ALLOBJ, and *JOBCTL special authority on OS/400. An administrator with *SECADM special authority must perform step 10 of this checklist. For information about special authorities, refer to the iseries Security Reference. 2. Verify that you hae the necessary Hardware requirements for running Windows serer on iseries on page 8 and software that is required for the ersion you will install. 3. Also erify that you hae enough memory allocated to the machine pool (see Machine pool size requirements for iseries Integration for Windows Serer on page 12). 4. If the Integrated xseries Serer has 2 LAN adapters on the same network, disconnect one of them from the network before installing the serer. By doing so, you aoid the problem of the Windows installation determining that there is a duplicate computer on the network. To disconnect the adapter, unplug the cable that connects the adapter to the network from either the hub/switch or the back of the adapter. After the installation is complete, you can reconnect the second adapter to the network (step 3 (See 44)). 5. To ensure that time synchronization will work, Verifying that OS/400 time zone is set on page 24 that the OS/400 QUTCOFFSET system alue is correctly set. For countries other than the United States, erify that hte OS/400 QLOCALE system alue is set correctly. 6. If you are installing on Windows 2000 or Windows.NET, complete the Windows serer installation adisor on page 39 and print out the summary page. If you are installing on Windows NT 4.0, complete and print the Installation work sheet for OS/400 parameters on page 29. Windows serer on iseries 11