Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Patch management tasks
- Viewing patch information
- Patch dependencies and supersedence
- Viewing Windows patches
- Editing Windows patch properties
- Importing custom documentation for a patch
- Deleting custom documentation for a patch
- Finding vendor-recommended Windows patches
- Finding servers that have Windows patch installed
- Finding servers that do not have Windows patch installed
- Importing a Windows patch from the SA Library
- Importing Windows patch contents from the managed servers view
- Downloading the Microsoft patch database from the Command Line
- Exporting a Windows patch
- Exporting Windows patch information
Downloading the Microsoft patch database from the Command Line
The populate-opsware-update-library
shell script downloads the Microsoft Patch Database and patches from the Microsoft site. This script also imports the database and patches into Server Automation.
Related topics:
- For information about importing via the SA Client, see Importing a Windows patch from the SA Client Library.
- For instructions on configuring and importing the patch metadata, see Configuring and importing the Microsoft patch database metadata. (Note: the metadata import method has the same capabilities as this shell script.)
Best Practice:A patch can be imported with this script or via the SA Client. The command line script is better when you want to download all the available patches to the system. If you updated your patches monthly, for example, you would most likely use the command line tool, and save the arguments.
Script Options:
- This shell script sets the initial status of newly imported patches to Available or Limited.
- The script can also filter the patches imported according to operating system, such as specific versions of Windows Servers. When you run this script, patches from all products that are selected in the Patch Settings product list will be imported, unless they are specifically omitted by one of the command-line options. See Options of populate-opsware-update-library.
Note
This script provides options for omitting patches from certain Windows operating systems; but it does not provide options for omitting non-OS products, such as Microsoft Office or Exchange.
Note
To run the command line script, your SA Core must have access to the internet or a web proxy.
To import a patch binary into SA, the patch metadata must be present in the currently loaded Microsoft Patch Database in the Software Repository.
Running the script
To run the populate-opsware-update-library
script, you must log on to the Software Repository server as root.
The script is located in the following directory:
/opt/opsware/mm_wordbot/util/
Typically, you schedule the script to run periodically as a cron job on the Software Repository server. From the SA Client, the patches imported with the script appear to have been automatically imported.
Note
Do not run concurrent instances of the script.
Options of populate-opsware-update-libraryThe following table describes the script’s options.
Option |
Description |
---|---|
|
Hostname or IP address of the Data Access Engine (spin) host. |
|
Hostname or IP address of the Software Repository (theword) host. |
|
File specification of the cert file to be used for the spin connection. |
|
File specification of CA file to be used for Spin connection. |
|
Display copious output. |
--no_nt4
|
Do not process NT4 patches. |
--no_w2k |
Do not process W2K patches. |
--no_xp
|
Do not process XP patches. |
--no_w2k3 |
Do not process W2K3 patches. |
--no_w2k3x64 |
Do not process W2K8 x64 patches. |
--no_w2k8
|
Do not process W2K8 patches. |
--no_w2k8x64
|
Do not process W2K8 x64 patches. |
--no_w2k8r2x64
|
Do not process W2K8 R2 x64 patches. |
--no_w2k8r2ia64
|
Do not process W2K8 R2 IA64 patches. |
--no_w2k12x64
|
Do not process W2K12 x64 patches. |
--no_w2k12r2x64
|
Do not process W2K12 R2 x64 patches. |
--no_w7x64
|
Do not process W7 x64 patches. |
--no_w7 |
Do not process W7 patches. |
--no_w81x64
|
Do not process W8.1 x64 patches. |
--no_w10x64
|
Do not process W10 x64 patches. |
--wget_path <file-path>
|
Use wget for the downloads vs built-in download support. File specification of the wget utility. |
--wget_http_proxy <server:port> |
wget HTTP proxy server in format proxyserver:httpport. This option is ignored if wget http proxy is configured in wget user startup file .wgetrc. |
--wget_ftp_proxy <server:port>
|
wget FTP proxy server in format proxyserver:ftpport. This option is ignored if wget ftp proxy is configured in wget user startup file .wgetrc. |
--use_proxy_url <url>
|
When downloading binaries, connect via this proxy URL. This option overrides the proxy settings specified via the http_proxy environment variable. |
--proxy_userid <userid> |
Basic-auth userid to provide to proxy server. Another way of providing the proxy userid is by setting the POP_OPSW_LIB_PROXY_USER environment variable. This option overrides the proxy userid specified via the POP_OPSW_LIB_PROXY_USER environment variable. |
--proxy_passwd <passwd>
|
Basic-auth passwd to provide to proxy server. Another way of providing the proxy password is by setting the POP_OPSW_LIB_PROXY_PASSWD environment variable. This option overrides the proxy password specified via the POP_OPSW_LIB_PROXY_PASSWD environment variable. Please note that specifying the proxy password via this option makes the password visible to any user on the process command line. To avoid this do not use this option and specify the password via the POP_OPSW_LIB_PROXY_PASSWD environment variable. |
|
Set availability status to Available when uploading patches. |
|
Set availability status to Limited when uploading patches. |
--no_hotfixes
|
Do not upload hotfixes. |
--no_servicepacks
|
Do not upload service packs. |
--no_updaterollups |
Do not upload updaterollups. |
--no_wsusscan_upload
|
Do not upload the MBSA 2.1x patch database. |
--wsusscan_url_override <url>
|
Download the MBSA 2.1x patch database from this URL. |
--force_msutil_upload |
Force new Microsoft utilities to be fetched and uploaded This option is ignored if --download_only is also specified. |
--no_msutil_upload | Skip Microsoft utilites check and upload |
--wua_x86_url_override <url
|
Download x86 Windows Update Agent from this URL. |
--wua_x64_url_override <url>
|
Download x64 Windows Update Agent from this URL. |
--wua_ia64_url_override <url> |
Download ia64 Windows Update Agent from this URL. |
--update_all
|
Refresh the patches already uploaded into Opsware SAS. |
--download_only <path>
|
Download files from the vendor's web site to the specified path, but do not upload them into Opsware SAS. |
--download_only_if_not_exists
|
If --download_only specified, only download patches that don't yet exist. |
--upload_from_update_root <path>
|
Upload files from specified directory instead of from vendor's website.
This option is ignored if --download_only is also specified.
|
--use_temp_download_path <path>
|
Download files to temporary download directory instead of a subdirectory under /var/tmp. |
--log_file <path> |
Log the output to the specific file. |
--parallel_uploads <number>
|
Number of patch uploads to run in parallel. System specific default value will be used. |
--download_retry <number>
|
Number of times to retry the download of patches |
|
Display this message. Note that
This script has been developed and test-run on a word server, but should run on any core server with word or spin crypto. No parsing of the cab is done in this script. |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to hpe_sa_docs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: