Creating Non-Custom Windows Provisioning Profiles (Sun N1 Service Provisioning System User's Guide for OS Provisioning Plug-In 3.0)

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

Creating Non-Custom Windows Provisioning Profiles

Through the N1 SPS browser or command line interface, you can manually create a Windows Provisioning profile. When you manually create a provisioning profile, you must supply the appropriate variable values to use in your provisioning plans.

If you want the OS Provisioning plug-in to generate a Windows provisioning profile for you, see How to Create a Custom Windows Provisioning Profile (Browser Interface).

To create a non-custom Windows Provisioning Profile, complete the following tasks.

How to Configure the Setup Information for the Windows Image

This procedure describes how to manually configure the setup information for a Windows image. You must complete this procedure if you are creating a non-custom Windows provisioning profile.

Setup information for Windows is stored in a RIS configuration profile. See the sample setup files from SampleSIFFiles folder for more details.

Steps

Edit the configuration profile file for each distribution to set the parameters mentioned in the following steps.

To edit this file, use the SetupMgr.exe utility. from the Windows Resource Kit CD (deploy.cab file). You can also manually edit the file using the notepad tool.

For a Windows 2003 image, the default SIF file is on the RIS Server at the following location:
//Reminst/Setup/English/Images/Windows2003/i386/templates/ristndrd.sif

Verify or add the following configuration parameters to the [data] section in your ristndrd.sif configuration file:
```
AutoPartition=1
UnattendedInstall="Yes"
```

Verify or add the following configuration parameters to the [Unattended] section in your ristndrd.sif configuration file:
```
UnattendMode=FullUnattended
NtUpgrade=No
OverwriteOemFilesOnUpgrade=No
OemPreinstall = Yes
```

Verify or add the following configuration parameters to the [UserData] section in your ristndrd.sif configuration file:
```
FullName = "N1osp SunUser"
OrgName = "Sun Microsystems"
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
         
```
Note –
Replace the FullName and OrgName values with something that is appropriate for your environment.

While deploying some operating systems, such as Windows 2000 Advanced Server, ProductKey does not work. Instead, use a ProductID variable.

Verify or add the following configuration parameters to the [GuiUnattended] section in your ristndrd.sif configuration file:
```
AdminPassword="sun123"
AutoLogon=Yes
AutoLogonCount=1
EncryptedAdminPassword=NO
```
Note –
AutoLogonCount=1 implies that the super-user administrator is automatically logged on to the target host after installation with the default password as sun123 for the very first time. This is required to execute the provision time commands specified in the [GuiRunOnce] section in the SIF file. When the Administrator user attempts to login again, he will be prompted to change the password.

Edit the software information file (sif) to automate download of critical security updates after the installation.

Add the following lines to the sif file.
[WindowsFirewall] Profiles=WindowsFirewall.TurnOffFirewall [WindowsFirewall.TurnOffFirewall] Mode=0

Verify or add the following sections to your ristndrd.sif configuration file:
```
[Branding]
        BrandIEUsingUnattended=Yes
[Proxy]
        Proxy_Enable=0
        Use_Same_Proxy=0
```
Tip –
The SetupMgr.exe utility generally adds these sections for you.

Add any specific plug and play drivers to the image.

See the instructions in Microsoft Knowledge Base article #: 315279.

How to Create a Non-Custom Windows Provisioning Profile (Browser Interface)

This procedure describes how to use the OS Provisioning browser interface to manually create your own Windows provisioning profile.

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 and How to Set Up the Windows RIS Server.

Steps

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

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

On the Plans Details page, click Run.

Click Select from List in the WindowsImage component row of the Plan Parameters table.

Click Create Set.

Type a name for the variables set.

Specify the variable values to use with this plan.

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.

Note –
You must specify a value for the sif_file variable.

Save the variables set.

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

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.

Type values for the Profile Name and Profile Description plan variables.

Deselect the Create Custom Profile check box.

Click Run Plan (includes preflight).

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.

Next Steps

To install the Windows OS on your target host, you must modify the BIOS boot settings, then run the provisioning plan. For more information, see Installing the Windows OS on the Target Host.

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

Steps

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/WindowsImage \
-name "windows2003" -u admin -p admin -vars "osp_server=masterserver-osp;version=2003; \
os_name="WIN2003_trial";description=test windows image 2003;min_disk_size=10GB; \
boot_server_name=biw1;boot_server_subnet_address=10.42.42.0; \
boot_server_subnet_ip_address=10.42.42.4;boot_srv_active_directory_domain=n1isp.sfbay.sun.com; \
windows_product_directory=D:\\\\RemoteInstall\\\\Setup\\\\English\\\\Images\\\\Win2003_trial; \
sif_file=D:\\\\RemoteInstall\\\\Setup\\\\English\\\\Images\\\\Win2003_trial\\\\i386\\\\templates\\\\
Ispristndrd.sif"

Note –

The windows_product_directory should be included all on one line. For display purposes, this entry appears on three separate lines.

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

Create a file named /tmp/windows-profile with the following entries.
noncustom Windows 2003 EE x86 Profile false
The entries in this file correspond to the following plan variables.
- noncustom specifies the Profile Name.
- Windows 2003 EE x86 Profile specifies the Profile Description.
- false specifies that this plan will not use a custom profile.

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/WindowsImage-create-profile \
-tar H:NM:risserver-windows -comp + -vs windows2003 -pto 30 -nto 1 -f /tmp/windows-profile0