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

Use > Software management > Remediate and installing software > Install software using a software policy > Remediate servers with software policies

Remediate servers with software policies

Remediation brings servers into compliance with their attached software policies. The remediation process has three stages: Analysis, Download, and Installation.

In the Analysis stage, SA compares the software that is actually installed on a managed server to the software that should be installed per the software policy. SA then determines what operations are required to make the server compliant with the software policy.
In the Download stage, SA downloads the necessary software resources (example: patches, packages) from the attached software policy to prepare for installation.
In the Installation stage, SA installs the downloaded software resources in the order specified in the policy and performs any of the other activities specified in the installation settings, such as running additional scripts and rebooting servers.

You can monitor the remediation job progress from the Job Status window. From this window you can view a summary of the actions performed in the job and the details of each action.

You can also cancel/terminate the job if you notice an error. See Terminate an active installation/uninstallation or remediation job.

About software resource reboot requirement settings

There are 2 ways to achieve a reboot during a remediation, depending on the software resource type:

For resources that support a reboot option (package, patch), set the reboot requirement option to yes.

To view the reboot requirement of a software resource: Find the package in the SA Library: Library > Packages > drill down to the individual software resource > Actions > Open. In the Properties view, expand the Install Parameters section to view the Reboot Required setting (yes or no).
For server scripts, (as you cannot set a reboot option on the script itself), this is determined based on the script output. If one of the lines in the output is OPSW_REBOOT or OPSW_FORCE_ REBOOT, the script is considered to require a reboot. The difference between the two choices is the strength of the reboot request.
- OPSW_REBOOT is treated as a softer request and may be suppressed, depending on the Reboot Option used when starting the remediation job.
- OPSW_FORCE_REBOOT will always result in a server reboot immediately after the script is run, even if the job Reboot Option is set to suppress reboots.

Send Help Center feedback