Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Server Automation10.51

Administer > SA Provisioning > OS sequence-based provisioning requirements, setup, and usage

OS sequence-based provisioning requirements, setup, and usage

Deprecation Notice: For certain managed server platforms, OS Sequences are deprecated in SA 10.10 and later and have been replaced by the new and more powerful provisioning Build Plans. See the SA 10.51 Support and Compatibility Matrix for the platforms that support Build Plans. It is strongly recommended that you migrate any existing OS Sequences to Build Plans on these platforms. Any new SA provisioning templates you need to create on these platforms should use Build Plans.

The OS Sequence Provisioning Process

Using SA OS Sequences requires of certain preparatory tasks including:

Installing and configuring the required OS Provisioning components including the following:
- Media server repository preparation including creating Media Resource Locators (MRLs) for use with OS Sequences.
- Uploading licensed OS media to the Media Server
- DHCP server management using the /opt/opsware/dhcpd/sbin/dhcpdtool.
Creating OS Installation Profiles for the operating systems to be provisioned. The Installation Profiles specify which operating system is to be installed and how it is to be configured and where the operating system media is located on the Media Server (using an MRL).
Associated with the Installation Profile are:
- Operating system-specific installation configuration files such as Kickstart (Linux), Jumpstart (Solaris/SPARC 10), Automated Installer (Solaris/SPARC 11) and unattend.xml (Windows).
- Build Customization Scripts that allow you to manage each operating system installation from the network connection to SA Agent installation.
- Custom Attributes that allow you to define server-specific custom attributes that set specified parameters and named data values. You can write scripts that use these parameters and data values to control network and server configuration, notifications, and CRON script configuration.
- Creating OS Sequences that specify the OS Installation Profile to use, device groups, and remediation policies. You must use OS Sequences in conjunction with OS Installation Profiles.

Create the OS sequence

After you have created your OS Provisioning configuration files, the process for provisioning new servers typically includes tasks similar to the following:

Preparation
1. Physically prepare the server for operation and connect it to a network that can communicate with SA.
2. In some cases, you must prepare the server hardware for OS Provisioning.
3. OS Installation Profile(s) defined and available.
Booting the server to be provisioned
Power on and boot the server to be provisioned using one of the following boot methods:
1. Use a bootable image provided by SA.
A bootable CD or DVD is not required for Intel-based servers that support PXE/WinPE or UNIX servers as these servers can be remotely booted over a network.
1. For servers that can be booted over the network, powering on the server causes the server to initiate its network boot process.
For more information about booting servers remotely, see Network booting and Managed boot clients.
A bootable CD or DVD is not required for Intel-based servers that support PXE/WinPE or UNIX servers as these servers can be remotely booted over a network.
After the server boots successfully and the SA Build Agent has been installed, the server appears in the SA Client in the Unprovisioned Server list and is ready for operating system installation.
Install the Operating System (Provision)
Select a server that has been booted with an OS Build Agent and select an appropriate OS Sequence for the operating system and configuration you want to install.
Start the OS Provisioning job.

Send Help Center feedback