Windows OS Component Variables

The variables described in the following list provide all the installation and configuration parameters for the Windows OS. In the list you see several variables that use the value of the targetable component. For purposes of the Windows Profile variables, the targetable component is the target host.

installPath

Description: Name of the Windows RIS image server.

Example: risserver-windows

osp_target_host

Description: Target host name.

Default value: :[targetableComponent:installPath]

osp_profile_control_service

Description: Whether to call the OSP Control Service, which automates power off, reboot, and power on functions (True, False).

---

Note –

To provision the Windows OS on target hosts, the value of this variable must be True.

---

description

Description: Description of the component.

Example: Windows 2003 Profile

version

Description: Windows version to be installed with this profile (2000, 2003).

Default: 2003

architecture

Description: Processor architecture of system to be installed with this profile (x86, x64).

Default: x86

min_disk_size

Description: Minimum disk size for this profile to be deployed.

Default: 10GB

boot_server_name

Description: Name of the Windows boot server.

Example: biwindows1

boot_server_subnet_address

Description: Subnet served by boot server.

Example: 192.168.5.0

boot_server_subnet_ip_address

Description: IP address of boot server on this subnet.

Example: 192.168.5.0

boot_srv_active_directory_domain

Description: Windows active directory domain for this subnet.

Example: winprov.n1lab.sun.com

windows_product_directory

Description: Windows product directory name on boot server.

Example: D:\RemoteInstall\Setup\English\Images\Win2003

sif_file

Description: Location of software information file (SIF).

Example:D:\RemoteInstall\Setup\English\Images\Win2003\i386\templates\ristndrd.sif

active_directory_userid

Description: Active directory user ID.

Example: n1ospadmin

boot_server_access_protocol

Description: Protocol to access the boot server, either RSH or SSH.

---

Note –

The RSH protocol is not supported with custom Windows profiles. You must use SSH as the communication protocol with custom Windows profiles.

---

Example: ssh

boot_server_access_userid

Description: User ID to access the boot server.

Example: n1opspssh

boot_server_access_password

Description: Password to access the boot server. Type the encrypted password as the value for this variable. For more information about how to encrypt passwords, see Password Encryption.

Example: Clkjgfw==

temporary_sif_directory

Description: Location of the temporary software information files (sif) in the RemInst share..

Example: D:\RemoteInstall\N1ospsif

ciw_directory

Description:Location of the CIW and OS Chooser files.

Example: D:\RemoteInstall\OSChooser\English

isp_scripts_directory

Description: Location of the OS Provisioning Plug-In scripts.

Example: C:\N1ospRisUtil\N1ospScripts

computer_name

Description: Host name of the target host.

Example: mysystem

user_full_name

Description: Full name of the user for the target host.

Example: Default user

organization_name

Description: Name of the organization to which the target host belongs.

Example: Default organization

product_key

Description: Product key for the Windows OS that you want to install. The product key is available with the software distribution of the OS, and follows the format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx.

repartition

Description: Specifies whether to reformat all partitions on the first drive of the target host with an NTFS file system.

Default: Yes

administrator_password

Description: Clear text password for the administrator user on the target host.

Default: default123

timezone

Description: Time zone for the target host.

Default value: %TIMEZONE%

profile_language

Description: Language to install on the target host.For more information, see “Supported Unattended RIS Variables” at theMicrosoft web site.

Example: 0409

profile_language_group

Description: Language group to install on the system.

Example: 1

ClientAccessLicense_automode_setting

Description: Specifies whether the Windows OS license applies on a per-seat basis or a per-server basis.

Example: PerSeat

ClientAccessLicense_autousers_setting

Description: Specifies the number of client licenses purchased for the server. You must set a value for this variable if ClientAccessLicense_automode_setting is set to PerServer.

Example: 100

dns_server_ip_address

Description: IP address of the DNS server on this subnet.

Example: 192.168.5.167

domain_name

Description: Name of the domain for the target host

---

Note –

If you specify this value, do not specify a value for the workgroup_name variable.

---

Example: n1lab.west.example.com

domain_administrator_name

Description: Name of the domain administrator user account.

Example: domadmin

domain_administrator_password

Description: Password for the domain administrator user account.

Example: domadmin567

workgroup_name

Description: Name of the workgroup in which the target host participates.

---

Note –

If you specify this value, do not specify a value for the domain_name, domain_administrator_name, or domain_administrator_password variables.

---

Example: n1labs

install_terminal_server

Description: Specifies whether to install a terminal server on the target host. Set this value to On to install the terminal server, or Off to not install the terminal server.

Example: On

terminal_server_allow_connections

Description: Specifies whether to allow remote connections to this target host through the terminal server.

Example: 1

terminal_server_licensing_mode

Description: Specifies how the Terminal Services manage the Client Access Licenses. Valid values are PerDevice and PerUser.

Example: PerDevice

terminal_server_permissions_setting

Description: Specifies the permissions for terminal server users. If this variable is set to 0, terminal server users have the same permissions as users of Windows 2000, Windows XP, and Windows 2003. If this variable is set to 1, terminal server users have the same permissions as users of terminal server 4.0.

Example: 0

pnp_drivers_path

Description: Location of Plug and Play drivers under the distribution share. To include multiple paths, separate each path with a semicolon (;).

Example: Drivers\Nic;Drivers\Lsi

mass_storage_drivers_entry1

Description: Specifies OEM SCSI drivers to use with the Setup Loader.

Example: LSI Logic PCI SCSI/FC MPI Driver (Server 2003 32-bit) = OEM

mass_storage_drivers_entryn

Description: Specifies additional OEM or retail SCSI drivers to use with the Setup Loader. n specifies a number between 2 and 5. For each additional driver, increase the value of n for each additional driver, up to 5. For example, mass_storage_drivers_entry2.

mass_storage_drivers_entry6

Description: Specifies retail SCSI drivers to use with the Setup Loader.

---

Note –

The retail driver must be listed at the end of the mass_storage_drivers_entry_ settings.

---

Example: IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller = RETAIL

oem_boot_filen

Description: Specifies mass storage SCSI driver files, as listed under $OEM$\Textmode folder. For each driver file, increase the value of n for each additional driver file, starting with the number 1, up to 10. For example, oem_boot_file1.

Example: lsi_sas.sys

gui_run_once_cmdn

Description: Specifies individual commands to run after GUI mode of Setup completes. For each command, increase the value of n for each additional command file, starting with the number 1, up to 10. For example, gui_run_once_cmd1

Example: dcpromo /answer:%SYSTEMDRIVE%\N1OSP\dc_answerfile

up to cmd5

help_page_url

Description: Specifies the URL for HTML-based help.

Example: http://n1labs.west.example.com/help.html

home_page_url

Description: Specifies the URL for the browser home page.

Example: http://www.example.com