Creating Windows Images and Profiles

A provisioning profile identifies the OS files to use and includes additional information about how those files are to be deployed.

How to Create a Windows Provisioning Profile (Browser Interface)

Before You Begin

Make sure the Windows image server exists and that the Windows OS software is available to that server. For more information about creating the Windows image server, see Setting Up the Windows Server.

Steps

1. In the Common Tasks section of the provisioning software page, select OS Provisioning.

2. On the OS Provisioning Common Tasks page, click Create Profile in the Windows Images section.

3. On the Plans Details page, click Run.

4. Choose variables to use for this plan.

   • To use an existing variables set, select a name from the drop-down menu in the WindowsImage component row of the Plan Parameters table.

   • To create a new variables set, click Select from List in the WindowsImage component row of the Plan Parameters table.

     1. Click Create Set.

     2. Type a name for the variables set.

     3. Verify variables and change them, if needed.

        If you need more information than is provided in the prompts in the component variables table, see the detailed list of components, along with default values and examples, in Windows Provisioning Profile Variables.

     4. Save the variables set.

     5. Select the variables set that you just saved from the drop-down menu in the WindowsImage component row of the Plan Parameters table.

5. On the Plan Details Run page, select the Windows image server on which to attach the image.

   ---

   Tip –

   The host name of the Windows image server ends in -windows.

   ---

6. Click Run Plan (includes preflight).

7. To verify that the Windows image is attached to the Windows image server, click Components in the left pane of the N1 SPS browser interface.

   You should see a component of type com.sun.n1osp#Provision that has a description similar to Windows provisioning profile.

How to Create a Windows Provisioning Profile (Command-Line Interface)

Steps

1. To create a variable set for the WindowsProfile component, type a command similar to the following example:

   # cr_cli -cmd cdb.vs.add -comp NM:/com/sun/n1osp/untyped/LinuxImage \ -name "redhat3" -u admin -p admin -vars "osp_server=masterserver-osp;version=RedHat3.0; \ architecture=x86;installPath=Linux:[version]_:[architecture];description=testlinux; \ min_disk_size=10GB;monitor_install=FALSE;boot_server_name=bikickstart; \ boot_server_subnet_address=10.42.42.0; \ boot_server_subnet_ip_address=10.42.42.3;kickstart_file=/export/el30.cfg; \ pxe_boot_file=linux-install/pxelinux.0;pxe_configuration_file=el30-console"

   For more information about the variables, see Windows Provisioning Profile Variables.

2. To run the plan, type a command similar to the following example:

   # cr_cli -cmd pe.p.run -u admin -p admin -PID NM:/com/sun/n1osp/untyped/LinuxImage-attach \ -tar H:NM:bikickstart-linux -comp + -vs redhat3 -pto 30 -nto 10

Windows Provisioning Profile Variables

The following table lists all component variables for the Windows provisioning profile. For those variables that have default values, the default is listed. For those variables that do not have default values, an example value is shown for illustration.