Sun N1 Service Provisioning System User's Guide for OS Provisioning Plug-In 3.0

ProcedureHow to Set Up the Windows RIS Server

Steps
  1. Install Windows 2003 Server Standard or Enterprise Edition operating system with Service Pack 1 for 32–bit systems on the Windows boot and install server.

    Create a separate NTFS partition that is big enough to store at least one image of roughly 700 Mbytes to hold RIS images. You will need to identify this partition when you make the server into a RIS server.


    Note –

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


  2. Install and configure Active Directory Server on this machine.

    Identify this system as a domain controller. For information about Active Directory Server, see Microsoft Knowledge Base Article 324753.

  3. Install and configure RIS server on this machine.

    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 or the Windows 2003 x64 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 Windows 2003 Resource Kit software and Support Tools on the Windows boot and install server.

    This package includes tools like setupmgr and xcacls that are used by the OS provisioning scripts. You can install these tools in one of the following ways:

    • Install the Windows 2003 Support Tools.

      The Support Tools are not automatically installed when you install Windows 2003. The installation program is located on the OS CD-ROM in the \support\tools folder. You must manually open the setup file (suptools.msi) to launch the installation wizard.

    • Install the Windows 2003 Resource Kit tools.

      You can obtain the Resource Kit tools from a Windows 2003 Resource Kit CD or from http://www.microsoft.com/downloads.

  5. Install and configure the Windows RSH Server or the Windows SSH Server on the RIS server.


    Note –

    The N1 SPS OS Provisioning Plug-In 3.0 release supports only SSH for deploying Windows custom-based profiles and supports both RSH and SSH for Windows non-custom based profiles. SSH provides more secure and reliable communication between the RIS Server and the N1 OS Provisioning Server than the RSH service.


    • To install the Windows SSH Server on the Windows RIS Server, install and configure the Cygwin© Open Secure Shell Service (OpenSSH service) for Windows 2003 on the RIS Server as any user.

      For more information, see the following web sites.

    • To install the Windows RSH Server on the Windows RIS Server, follow these steps.

      1. Install the Windows 2003 Resource Kit and Windows Services for Unix 3.5 (SFU3.5) software on the Windows RIS server.

        For instructions about how to install the Windows 2003 Resource Kit and Windows Services for Unix 3.5 (SFU3.5) software, see Microsoft Knowledge Base Article #321712 .

        The Windows 2003 Resource Kit and Windows Services for Unix 3.5 (SFU3.5) software are available on the Windows Resource Kit CD and from the Windows web site. This software includes the Windows RSH service, and other tools that are used by the OS provisioning plug-in scripts, such as setupmgr, deploy.cab, xcacls.

      2. Install and configure the Windows Remote Shell Service (WinRsh service) on the RIS Server as user root.

        For instructions, seeRemote Shell Services in SFU.


        Note –

        If the permissions for the .rhosts file are not set correctly, the WinRsh service fails and the client receives an “Access denied” message. To prevent this failure, assign full permissions to the user group Administrators/SYSTEM in the .rhosts ACL list. For example add the following entry to the .rhosts file in c://windows/system32/drivers/etc/


        ------------------
        10.5.133.22 root
        ------------------

        After editing the .rhosts file, ensure that you save the file as .rhosts, not .rhosts.txt.


  6. Install the N1 SPS Remote Agent on the Windows RIS server.

  7. On the Master Server, prepare a new Remote Agent host for the Windows RIS server.