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.60

Use > Server patching > Patch management for Windows > Patch management process > Step 1 - Configure patch settings > Prerequisites for importing the offline MS patch database

Prerequisites for importing the MS offline catalog

If you are working in the Offline Catalog patching mode, check the following prerequisites before importing the wsusscn2.cab file from Microsoft:

Configure your browser for importing the MS offline catalog
Import Windows patch utilities for the offline patch catalog
Make sure that Windows Installer 3.1, Windows Update Agent and MSXML 3+ are installed on your Windows managed servers. MSXML is a general requirement for all Windows managed servers.
The Windows Update service on your managed servers is not be disabled but is set to never check for updates.

Configure your browser for importing the MS offline catalog

If you are working in Offline Catalog patching mode and you want to import the wsusscn2.cab file from your local network, configure your browser to not use the web proxy when communicating with your SA core.

If you are importing the offline catalog using the Import from Vendor option, make sure to use a proxy to be able to connect to Microsoft for accessing the Windows patch database.

To configure your browser for importing the Windows offline catalog file stored locally:

In the Log in to HPE Server Automation Client window, click More to expand the window.
Click Advanced Settings to open the Advanced Settings window.
In the Proxies section, if the Use Browser is selected, configure your browser to not use the web proxy when communicating with your SA core.

Or
In the Proxies section, if Manual is selected (which means that the proxy is set manually), enter the core's IP or hostname in the No Proxy Hosts text box. This will ensure that the SA Client communicates directly with the SA core.

Import Windows patch utilities for the offline patch catalog

Windows Patch utilities deploys the latest version of the Microsoft Update agent onto the managed servers. SA uses Windows Update Agent (WUA) to scan computers for security updates without connecting to Windows Server Update Services (WSUS) server.

Import the Windows Patch utilities only if you are working in Offline Catalog patching mode. Windows Update Agent (WUA) automatically updates itself when it is connected to the WSUS server.

If you do not plan to use SA to manage your Windows servers, you can optionally choose not to install these files and still successfully complete the installation process. However, if these files are not installed, no operations against Windows servers should be performed. These files are required for many Windows-based operations other than Windows patching.
During an SA core installation, if you set the windows_util_loc parameter to none, the Windows utilities will not be imported during a core installation and operations on Windows servers will not be supported. See the SA Install section for more information.
Before you can import the Windows utilities, you must configure your browser to not use the web proxy when communicating with your SA core. See Prerequisites for importing the MS offline catalog for instructions.

After you install an SA core, you can import (download) the following Windows utilities from the vendor:

WindowsUpdateAgent-ia64.exe
WindowsUpdateAgent-x64.exe
WindowsUpdateAgent-x86.exe

To update and import Windows patch utilities:

In the navigation pane, select Administration > Patch Settings.
The Patch Settings window appears and SA checks for Windows patch utility updates. The Latest column in the Windows Patch Utilities section of the window indicates that SA is checking for updates.
- The Latest column displays the latest version that is available from the vendor.
- The Version column displays the version of the utility that is already in the SA database.

If you are connected to the internet, the Latest column is updated to the latest version that is available from the vendor.
1. Compare the values in the Latest column to the Version column.
2. If the Version in the SA database is lower than the Latest version that is available from the vendor your utilities need to be updated.
3. Click Import from Vendor to get the latest utilities.
4. In the Import from Vendor window, select one or more utilities and then click Import.
  
  The Importing Utility Update window displays the status of the process.
  - If the job complete, the Status column will display the success icon .
  - If the job fails, the Status column will display the error icon . Double-click the error icon to display the error message.
5. After the process completes, click Close.

If you are not connected to the internet, the Unable to Access wuredist.cabwindow appears providing an option to import the Windows Update Agent (wuredist.cab) from a local file.
1. Click Import.
2. In the Import Patch Utility dialog, find and select the wuredist.cab file locally.
3. Click Import to import the utility update.
4. After the import is complete, the Latest column shows which utilities have updates available.

Manually import the Windows patching utilities

If you are working in Microsoft Offline Catalog patching mode and you did not install the Windows patch management files during core installation, get the following Microsoft files from a machine with internet access and add them to the core.

If you need to work in a tightly secured environment, consider switching to WSUS patching mode as this enables you to get Windows patches from a WSUS server on your network.

Note The links to the following Microsoft files are provided as a convenience. However, Microsoft Corporation may change the links after the release of this document. Therefore, we cannot guarantee that these links will be valid when you use them and you may need to search the Microsoft Support website to find the correct files.

wsusscn2.cab

The wsusscn2.cab file contains the Microsoft patch database.

Download wsusscn2.cab from http://go.microsoft.com/fwlink/?LinkId=76054.
WindowsUpdateAgent30-x86.exe

The WindowsUpdateAgent30-x86.exe file is required when SA scans x86-based managed servers to determine which Windows patches/hotfixes are installed.
1. Download the package containing WindowsUpdateAgent30-x86.exe from http://go.microsoft.com/fwlink/?LinkID=100334.
2. After downloading, rename the file "WindowsUpdateAgent-x86.exe".

WindowsUpdateAgent30-x64.exe

The WindowsUpdateAgent30-x64.exe file is required when SA scans x64-based managed servers to determine which Windows patches/hotfixes are installed.
1. Download the package containing WindowsUpdateAgent30-x64.exe from http://go.microsoft.com/fwlink/?LinkID=100335.
2. After downloading, rename the file "WindowsUpdateAgent-x64.exe".
WindowsUpdateAgent30-ia64.exe

The WindowsUpdateAgent30-ia64.exe file is required when SA scans Itanium x64-based managed servers to determine which Windows patches/hotfixes are installed.
1. Download the package containing WindowsUpdateAgent30-ia64.exe from http://go.microsoft.com/fwlink/?LinkID=100336.
2. After downloading, rename the file "WindowsUpdateAgent-ia64.exe".

Send Help Center feedback