Sun N1 System Manager 1.3 Operating System Provisioning Guide

Creating Windows Distributions

Before you can install an OS profile on a managed server, you must copy the files that comprise a Windows OS release to the RIS server and link to it from the management server.

To Set Up a Windows Image on the Windows RIS Server

Steps

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

Use the risetup.exe utility to copy the Windows distribution from a CD or Network Share to the RIS server.

On the RIS server, use the RiSetup.exe utility with -add option.

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 MSDN Combo CDs to create a RIS Image. You will get an error message that was 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:
- How to obtain the latest Windows 2000 service pack is explained in Microsoft Knowledge Base Article #260910
  
  Choose “Network installation” option for Windows Service Pack Express/Network Installation for downloading a service pack to create a RIS image. Windows 2000 Service pack 3 download process is explained in http://www.microsoft.com/Windows2000/downloads/servicepacks/sp3/download.aspx. Similar download pages can be found in Microsoft documentation for other OS version service packs as well.
- How to create a RIS image with the service pack bundled is explained in Service Pack 3 Installation and Deployment Guide for Windows 2000 Server edition. Similar guides can be found in Microsoft documentation for other OS version service packs as well.

(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.

To Create a Windows OS Distribution

This procedure describes how to use the command line to link a Windows OS distribution from the management server to the Windows RIS server.

Note –

You cannot perform this task through the browser interface.

After a distribution is added, an OS profile of the same name is created by default. This profile will appear in the OS Profiles list in the Task Shortcuts pane.

Steps

Install and configure a Windows RIS server.

See Setting Up a Windows Remote Installation Services Server in Sun N1 System Manager 1.3 Site Preparation Guide.

Copy the Windows distribution from a CD or network share to the RIS server.

See To Set Up a Windows Image on the Windows RIS Server.

Link the distribution on the RIS server to the N1 System Manager.

Type the following command on the N1 System Manager command line:
N1-ok> create os os-name type windows languageedition language version version arch arch rissourcepath path-to-RIS-distribution
Where:
- os-name is the name that you defined for the distribution when you added it to the RIS server. The os-name must be unique and may include numbers, letters, and some special symbols. The following special symbols are prohibited: comma, asterisk, single quote, double quote, parenthesis, question mark, equal sign, and newline.
- type windows identifies the type of OS as Windows.
- language specifies the language to support viewing web pages and other content encoded in a different language and character set. For a list of valid values, use the tab completion feature in the CLI.
- version identifies the Windows version. For the most current list of valid values, use the tab completion help feature in the CLI. Valid values are:
  - 2000AS - Windows 2000 Advanced Server
  - 2000SS - Windows 2000 Standard Server
  - 2003EE - Windows 2003 Enterprise Edition
  - 2003SE - Windows 2003 Standard Edition
  - 2003WE - Windows 2003 Web Edition
  - 2003SESP1 – Windows 2003 Standard Edition Service Pack 1
  - 2003EESP1 – Windows 2003 Enterprise Edition Service Pack 1
- arch is the architecture of the system to be installed. Valid values are amd64 or i386.
- rissourcepath is optional. If specified, it provides a full path to the distribution on the RIS server.
An OS profile is created that uses the os-name as the profile name.

Example 3–1 Linking a Windows OS Distribution from the RIS Server to the Management Server

N1-ok> create os win2003EE type windows languageedition English version 2003EE 
arch i386 rissourcepath j:

To Create a Windows OS Profile

Tip –

When you create an OS distribution, a default OS profile is created automatically. Most likely, you will need to use the command line to customize the default profile for your specific hardware and configuration parameters. For information about modifying an existing OS profile, see To Modify an OS Profile.

This procedure describes how to create an OS profile from the command line interface. To create an OS profile from the browser interface, click the New button under the OS Profiles list on the Task Shortcuts pane of the System Dashboard.

Before You Begin

You must make the OS distribution known to the management server before you can create a new OS profile.

Steps

To see a list of the available OS profiles, type the show osprofile all command at the N1–ok prompt.

Tip –
To see a list of available profiles in the browser interface, click the Edit button under the OS Profiles list on the Task Shortcuts pane of the System Dashboard.

To create an OS profile, type the following command:
N1-ok> create osprofile osprofile-name os os-name rootpassword rootpassword fullname fullname organizationname organization-name productkey productkey [Optional-Windows-Attributes]
Where:
- fullname is your full name, surrounded by quotation marks.
- organizationame is the name of your organization, surrounded by quotation marks.
- os is the name of the OS distribution to install.
- osprofile is a name for the OS profile. The OS profile name must be unique and may include up to 100 numbers, letters, and some special symbols. The following special symbols are prohibited: comma, asterisk, single quote, double quote, parenthesis, question mark, equal sign, and newline.
- productkey is the product key for each unique installation of Windows. To find the product key, look at the packaging for the operating system CD-ROM. The product key will look similar to this example: 11111-11111-11111-1111-11111
  
  You can also set the product key through the load server or load group command when you install the OS onto a managed server.
- rootpassword specifies the root password for the server to use after installation. If you do not want the password to display in the command line, type a question mark (?). The software prompts you to enter the password after you issue the command.
- Optional-Windows-Attributes provide several additional features that enable you to specify a variety of Windows-specific details, such as language, time zone, license information, and scripts to run when you first login to the system. For more information about Windows attributes, see the “OPTIONAL WINDOWS ATTRIBUTES” section in create osprofile in Sun N1 System Manager 1.3 Command Line Reference Manual.

Example 3–2 Creating a Windows OS Profile

The following command creates an OS profile for a Windows 2003 Enterprise Edition distribution and prompts the user to enter the password.

N1-ok> create osprofile win2003EE os win2003EE rootpassword ? 
fullname "IamMe" organizationname "MyOrgPlace" productkey productkey
description "win2003EE" licensingmode "perseat" licenseperserver 1 repartition true
wtsallowconnection false wtsenable true wtslicensingmode perseat wtspermissionssetting all
rootpassword:

Once the create osprofile command completes, the following command shows details about the OS profile:

N1-ok> show osprofile win2003EE
ID:                3
Name:              win2003EE
Distribution:      win2003EE
Description:       win2003EE
In Use:            false
User's Full Name:  
Organization Name: 
Language:          
Timezone:          
Language Group:    
Firstloginscript:  
repartition:       true
targetpath:        Windows
oem driver path:   
Windows Licensing Mode: PerSeat
Licenses Per Server: 1
Terminal Server Enable: true
Terminal Server Allow connections: false
Terminal Server Licensing mode: PerSeat
Terminal Server Permissions Setting: All
N1-ok>

To Modify a Windows OS Profile

The following task describes some of the specific modifications that you are likely to make to a Windows OS profile. You can also modify some Windows information when you load the OS profile onto the managed server.

Steps

To change information in an existing Windows OS profile, type the following command:
N1-ok> set osprofile osprofile-name [Optional-Windows-Attributes]
Optional-Windows-Attributes are the same for modifying an OS profile as for creating an OS profile. See set osprofile in Sun N1 System Manager 1.3 Command Line Reference Manual for details.

Remove existing OS profile attributes.
N1-ok> remove osprofile osprofile-name [Optional-Windows-Attributes]
Optional-Windows-Attributes are the same for removing attributes from an OS profile as for creating an OS profile. See remove osprofile in Sun N1 System Manager 1.3 Command Line Reference Manual for details.

Example 3–3 Adding a Product Key to an OS Profile

The following example adds a product key to an existing OS profile. To find the product key, look at the packaging for the operating system CD-ROM. Adding a product key is a fairly common change that you need to make for installing the Windows OS.

N1-ok> set osprofile win2003EE productkey BVVVV-99PMV-HH9Z9-BDY9Z-896Z9

For security reasons, the actual product key value will not display in the command-line interface.