test

Sun N1 System Manager 1.3 Site Preparation Guide

Setting Up a Windows Remote Installation Services Server

The N1 System Manager OS provisioning process uses the Microsoft Remote Installation Services (RIS) technology to provision Windows operating systems to manageable servers from a RIS server. To provision Windows operating systems to manageable servers, you must set up a RIS server that is accessible to the N1 System Manager as described in the following sections. For more information about RIS, see the Microsoft RIS documentation at http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/c62e5951-5eb9-42f1-95ae-490e5d7a5551.mspx.

Setting up the Windows RIS server consists of the following tasks:

ProcedureTo Set Up the Windows RIS Server

Steps

  1. Install Windows 2003 Enterprise Edition operating system for 32–bit systems with Service Pack 1 on the Windows RIS server.

    Create a separate NTFS partition that contains 800 Mbytes for each Windows operating system image that you want to provision. The Windows OS image partition should be on a drive or logical partition other than the C: drive. You will prompted for the partition information when you configure the N1 System Manager.

    Note –

    If you already have a machine that is running Windows 2003 Server 32-bit Enterprise edition without Service Pack 1, you can install just the Windows 2003 Service Pack 1 on the server See Microsoft Knowledge Base Article #891128.

  2. Install and configure Active Directory Server on the RIS server.

    During installation of Active Directory Server software on your RIS server, identify your RIS server as a domain controller. For information about Active Directory Server, see Microsoft Knowledge Base Article 324753

  3. Install and configure the RIS server software on the RIS server.

    For more information, see Microsoft Knowledge Base Article 325862.

    Note –

    While installing RIS server, add a Windows 2003 x64 Risetup.exe image or the Windows 2003-Service Pack 1 x86 Risetup.exe image on the RIS server.

    If the Windows Server 2003 SP1 RISETUP image is the first image to be uploaded to the RIS server, the new OS chooser screen (x8664.osc ) is copied to the RIS server by default.

    If there are existing Windows OS images on the RIS server at the time the first Windows Server 2003 SP1 image is added, you must choose whether to overwrite (or backup and overwrite) the OS chooser screens during the installation to get the new screen. See Microsoft Knowledge Base Article #891128.

  4. Install Cygwin© on the RIS Server and configure Open Secure Shell Service (OpenSsh service) for Windows 2003 on the RIS server as n1smssh user.

    For more information, see the Cygwin Home Page and the Open Ssh Windows Install Instructions. For information about removing existing Cygwin packages, see http://cygwin.com/faq/faq_2.html#SEC20.

    The Cygwin install source is located in the install media Windows directory.

ProcedureTo Set Up a Windows Image on the Windows RIS Server

Steps

  1. Log onto the Windows RIS server using the administrator account or an account with administrator privileges.

  2. Copy the Windows distribution from a CD or Network Share to the RIS server CIFS.

    On the RIS server, copy the windows distribution either from a CD or Network Share using the RiSetup.exe utility with the -add option onto the RIS Server Common Internet File System (CIFS) share.

    Note –

    Make sure you select the option “Keep the old existing OSC files” in the risetup wizard while creating RIS images.

    When you copy a Windows distribution to the RIS server, the appropriate Windows drivers are copied automatically. To add other drivers into the distribution, copy the drivers into the scripts directory on the RIS server.

    Do not use the Microsoft Developers Network (MSDN) Combination CDs to create a RIS Image. RIS image creation will fail, and you will get an error message that is described in the Microsoft Knowledge Base Article #300556. To resolve this issue, use a retail version of the OS image being created.

    To create a RIS image of a Windows distribution integrated with service packs, follow the procedures described in the following articles:

  3. (Optional) To provision non-English versions of the Windows OS, you need to do some additional configuration when you set up the image on the RIS server.

    Basically, the RIS server assumes that you have files in an English path. To resolve this issue, copy the other language's files to the English path.

    1. Go to the directory in which the OS Chooser files live.

      For example:


      % cd RemoteInstall\OSChooser

    2. Copy the files from the language directory to an English directory.

      For example:


      % copy -r Japanese English

      This creates a directory RemoteInstall\OSChooser\English that contains the install screens in the native language. When the RIS software looks into the default English path, it will display the non-English OS Chooser screens during install.

ProcedureTo Set the BIOS Boot Order on a Manageable Server

Before You Begin

Ensure that the Windows operating system is supported on each target manageable server. For a list of manageable servers that support the Windows operating system, see Table 2–6.

Steps

  1. Set the BIOS Settings on the target host in the following order:

    1. Boot from Hard Disk

    2. Boot from Network (PXE-enabled)

    3. Boot from CD

    4. Boot from Floppy

  2. Identify the target host's primary NIC MAC address for a PXE network boot and the Globally Unique Identifier (GUID) value.

    You can obtain the GUID from the target host's BIOS settings or from any of the following other sources:

    • A label on the side of the computer case.

    • A label within the computer case.

    • The basic input/output system (BIOS) of the client computer.

    • Network traffic from the client computer. You can use a network utility to sniff the network traffic and locate the DHCPDiscover packet. That field will contain the 128-bit, 16-byte GUID or a 128 bit Universally Unique IDentifier (UUID).

    Note –

    The GUID must be in the form {dddddddd-dddd-dddd-dddd-dddddddddddd}, where d is a hexadecimal text digit. For example, {921FB974-ED42-11BE-BACD-00AA0057B223}. Valid entries for the client GUID are restricted to the numbers 0 through 9, lowercase alphabetical characters, uppercase alphabetical characters, and a dash.

    Caution – Caution –

    Spaces, underscores, and other special symbols are not permitted in a GUID nor in a UUID.