Release Notes

HP Server Automation, Enterprise Edition

Software version: 10.0

Original Publication Date: June 13, 2013

Enterprise and Standard Editions

There are two editions of Server Automation:

For information about using SAVA and differences between the Standard Edition and the Enterprise Edition, see the SAVA at a Glance guide.

Up-To-Date Documentation

Get the most up-to-date version of the documentation on the HP Software Product Manuals portal. Additionally, all guides are cataloged for easy access in the SA 10 Documentation Library.

This site requires that you sign in with your HP Passport. If you do not have one, click the New users - please register link on the HP Passport login page to register.

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details. Note the Document Release Date on the title page of your guide and see the Documentation Change Notes on page 3 of most documents for a list of any revisions. The release-notes change table is at the bottom of this document.


SA release notes contain information for users who are familiar with the installation and maintenance of SA, Storage Visibility and Automation, SE Connector, Application Deployment Manager, and DMA integration. The notes contain information that is not included in books or online Help.


Table of Contents

This document contains the following information:

What's New in This Release


Known Issues

Fixed Issues

Documentation Information

HP Software Support

Legal Notices


What's New In this Release

This section describes new functionality and other relevant release-specific information.

For information about what was new in previous releases, please see the corresponding release notes at:

What's New for Installation

New, Simplified SA Core Installation/Upgrade

SA 10.0 introduces major improvements to the SA Installer that simplify the installation and upgrade procedures, including:

Reserved Ports

SA 10.0 requires that the following ports be open:

Note: In addition, other ports are required to be open for previous releases of SA. See the corresponding release notes at:


If your SA Core matches one of the SA Core configurations supported for customer upgrade and described in Chapter 2: SA Core Configurations in the SA Standard/Advanced Installation Guide, you can upgrade from a previous SA version to SA 10.0 yourself. However, if your core does not match any of these SA Core configurations, your first upgrade of an SA Core to SA 10.0 from a previous version must be performed by HP Professional Services or an HP certified consultant.

After the core has been upgraded to SA 10.0, HP supports customer-performed upgrades to SA 10.x or later as long as your core configuration is one of the supported configurations. All other core configurations will continue to require the services of HP Professional Services. If you are uncertain whether
you can upgrade an existing SA Core yourself, contact HP Technical Support.

What's New for Qualified Managed Platform Support/OS Systems Support

SA Client Support for Windows Operating Systems

This section lists the operating-systems supported on the SA Client.

Support and Compatibility Information

For complete SA support and compatibility information, see the HP Server Automation Support and Compatibility Matrix for this release at:

For a list of supported operating systems and platforms for Storage Visibility and Automation Managed Servers, SE Connector, SAN Arrays, Fibre Channel Adapters, SAN Switches, File System Software, Database Support, and Storage Essentials Compatibility, see the Storage Visibility and Automation Support and Compatibility Matrix at the same link.

All SA and Storage guides are available at:

For more information about supported configurations, see SA 10.0 Standard/Advanced Installation Guide, chapter 2: “SA Core Configurations Supported For Customer Installation”.

What's New for Deprecated Managed Platforms/Agents/Features

This section lists deprecated platforms for this release.

When a platform/agent/feature is identified as deprecated for a release, it means that you (the SA customer) are considered notified of its future removal. Deprecated features are still fully supported in the release they are deprecated in, unless specified otherwise. The intent is that deprecated features or platforms will have support removed in the next major or minor SA release; however, eventual removal is at the discretion of HP.

Managed Platforms in SA 10.0

The following platforms are deprecated as of SA 10.0:

Agent Upgrade Tool

The Agent Upgrade Tool that is run from the OPSH shell and allows upgrading the agents on managed servers was deprecated. As of SA 10.0, a replacement APX was introduced that has several improvements and can be run from the SA Client.

SA Agents

SA no longer supports SA Agents associated with SA 7.8x and earlier versions.

Pre-SA 10.0 agents are supported only in upgraded cores.

If you upgrade to SA 10.0, it is recommended that you migrate to the newest versions of the SA Agent on your managed platforms.

API Methods

Since SA 9.0, moving application configurations and configuration templates into folders changed the behavior of the associated classes and services.

Attributes folder and lifecycle of the VO-s are required for the following API calls:


The following methods have been deprecated, but they still perform as expected.

com.opsware.folder.FolderVO#getCustomers should be used instead.

The following methods have been deprecated and they have a void implementation.

com.opsware.folder.FolderVO#setCustomers must be used instead.


What's New for Unsupported Platforms/Agents/Features

Unsupported Managed Platforms for SA 10.0

The following platforms are no longer supported as of SA 10.0:

Unsupported Features

Code Deployment and Rollback (CDR) and Configuration Tracking

Code Deployment and Rollback (CDR) was deprecated in the SA 7.80 release, and is no longer supported. The Application Deployment Manager replaces the CDR. See the SA User Guide: Application Deployment Manager for more information.

For more information about the deprecation of CDR, contact HP Technical Support.

Virtualization Features

Legacy Job Types No Longer Supported New Replacement Job Types
Clone Virtual Machine (VMware) Clone Virtual Machine
Create Virtual Machine (Hyper-V)
Create Virtual Machine (VMware)
Create Virtual Machine
Delete Virtual Machine (Hyper-V)
Remove Virtual Machine
Delete Virtual Machine
Modify Virtual Machine
Modify Virtual Machine (Hyper-V)
Modify Virtual Machine

Note:  Any scheduled or blocked jobs of the legacy job types will be marked as Deleted during migration.

Unsupported Scripts

As of SA 7.80, the following scripts are no longer supported:

Starting In SA 9.0, you must use the unified start script:


If you have any applications or scripts that depend on this script, you must rewrite them to use the unified start script.

What's New for Agents

Upgrading SA Agents

Since 9.11, SA Agents have used Python 2.4.4.

After you upgrade to SA 10.0, you should also upgrade to the 10.0 SA Agents on each Managed Server in the facility.

You can continue to use non-upgraded agents, but you will not benefit from new features in this release (such as qualified managed platforms, and the other features listed in the What's New section of these release notes).

Faster SA Agent Installation

For more information on the Agent Upgrade tool, on installing the agent, and on bringing servers under SA management, see the SA User Guide: Server Automation.

What's New for Audits

Audit Policies

The Windows Hyper-V Manager rule type has been removed from all audit policies.

Audit Results Viewer

In previous releases, when you viewed an audit result, all targets were shown in the left-tree panel. In this release, the servers are grouped by compliance status in the left-tree panel.

When you have a large number of target servers, you no longer have to navigate through a long list, you can now focus on the non-compliant or failed servers. Being able to focus increases the user-interface usability and improves load time.

Compliance-Based Audit Policy

A new Compliance view has been added to the Audit Policy panel. The view shows:

  • Target servers on which the Audit Policy has been executed.
  • Compliance status for the last execution of the Audit Policy for each target server.
  • Ordering of Custom Script Rules

    If you have multiple custom scripts, you can specify the order of their execution on the managed server using the Move Up or Move Down buttons. Remediation of the rules will happen in the same order.

    Soft Cancel

    Users can cancel recurring schedules and currently running ad-hoc supported audit and remediation jobs. The job on the current server in-flight will be finished. If a job has not already begun on a server, it will not start. This ability is enabled on a single core or a mesh.

    What's New for SA Command-line Interface (OCLI)

    Installation and Usage

    Starting with SA 10.0, installing and using OCLI on Linux and Unix machines is simpler:

    To install the SA Command-line Interface (OCLI), issue the following command:

    <package_name> -d <installation_directory>

    No other steps are necessary to setup the environment .

    When using the OCLI, use the new oupload and odownload scripts available in the new bin directory:


    OS Independent Packages

    Uploading of OS Independent packages (except of type UNKNOWN) might not be supported in a future release. Two new platform families (UNIX and WINDOWS) were added instead, and can be used with the --os option.

    What's New for Database and Middleware Automation

    Database and Middleware Automation (HP DMA) is no longer installed as part of Server Automation. Starting with HP DMA version 10.00, HP DMA is available as a separate product with its own installation media. HP DMA 10.0x is still integrated with Server Automation, however. For more information, see the HP DMA Installation Guide.

    What's New for OO-SA Integration

    Updates pertaining specifically to the OO-SA integration (Server Automation operations performed within Operations Orchestration) are delivered via the HP Live Network at

    What's New for Oracle Database and Model Repository

    As of SA 10.0, the schema and index statistics collection for SA database users AAA, TRUTH, and so on. have been moved from dba_jobs to Oracle's Automatic Optimizer Statistics Collection. Starting with SA 10 you will no longer see these jobs in dba_jobs.

    Starting with Oracle 10g, the DBA_JOB package was superseded by the improved Oracle Scheduler (dba_scheduler) package. Although Oracle still supports the DBA_JOB package for backward compatibility, Oracle will make no further enhancements to the package. Since the DBA_SCHEDULER provides better functionality, all the SA jobs that used the DBA_JOB package have been redesigned in this SA release to use the DBA_SCHEDULER package. The affected jobs can be found in the dba_scheduler_jobs table. These changes are only relevant to new SA 10.0 Cores and cores upgraded to SA 10.0.

    To view the jobs and changes made, you can run the following from SQL*Plus:

    # Su - oracle
    # Sqlplus "/ as sysdba"
    SQL>set line 200
    SQL>col owner format a14
    SQL>col job_action format a50
    SQL>col job_name format a50
    SQL>select job_name, owner, job_action from dba_scheduler_jobs where owner in

    Oracle RAC

    This release supports Oracle 11.2.03. For more information on Oracle RAC, see the SA installation guides.

    What's New for OS Provisioning

    New Features

    The following new features have been added to OS Provisioning:

    What's New for Build-Plan OGFS Script Execution

    In previous SA versions, if you created OGFS scripts and added them to your build plans, the scripts were executed in the file system in the following directory:


    Now, the scripts are executed in this new location:


    As a result of this change, you must add the following line to your build-plan scripts to avoid compatibility issues with user scripts:

    cd files/root (Linux)

    cd files/Administrator ( Windows)


    OS Build-Plan Support for VMware ESXi5 and ESXi5.1

    SA briefly stops the VMware ESXi firewall in order to communicate the VM's IP Address, so that it can be managed by the SA core. SA restarts the firewall immediately afterwards.

    If you do not want SA to stop and start the firewall, use static OS Provisioning instead.

    Enhanced HP ProLiant Support

    ProLiant support includes:

    For more information, see the SA README.html, SA UG: OS Provisioning guide, and the SA online help.

    Support for OS Build Plans

    HP ProLiant Gen8 models have two embedded service operating systems available: Linux and Windows Preinstallation Environment (Windows PE). SA can use either the Integrated Lights-Out (iLO) functionality of these embedded systems, or Preboot Execution Environment (PXE) booting.

    To use the embedded systems' iLO functionality, you must add your server as an iLO device to the list of unprovisioned servers.

    There are two ways to do this:

    In both these cases, you will need to manually provide iLO credentials and the corresponding SA realm (which is related to the SA Satellite or core available in the target network). This information defines the SA infrastructure to be contacted after the embedded service operating system is booted. When you use PXE booting, this information is provided by the PXE server automatically.

    For more information on how to add your server, see" Installing (Provisioning) an Operating System" in the UG: OS Provisioning.

    Operating System Build-Plan Updates

    New Features

    The following new features have been added to build plans:

    Enhanced Steps

    The following 3 steps have been enhanced, or added, to build plans for HP ProLiant Gen8 support.

    Virtual Installation Device (VID) handling

    HP ProLiant Gen8 devices support special Virtual Installation Devices (VIDs).

    SA handles VIDs as follows:

    For more information on this topic and for specific use case, see "Prepare Disks on HP ProLiant Gen8" in the SA OS Provisioning README.

    Running OS Build Plans on Servers

    Build plans can now be run on servers that are in the pre-unprovisioned lifecycle.

    SLES 11 SP1 kISO Handling

    If you are using SuSE Linux Enterprise Server (SLES) 11 SP1 and above, you must do the following to support the SuSE kernel & driver update method using kISO:

    1. Download the kISO & mount the ISO file for access.
    2. Create (or reuse) a SLES distribution repository in a directory (for example: /repositories/SLES-11-SP1-x86_64).
    3. Create a new directory called addon (the directory name does not have to be case sensitive, you can also use AddOn or ADDON) under your new repository directory (for example: /repositories/SLES-11-SP1-x86_64/addon).
    4. Copy the kISO contents to the addon directory.
    5. Replace the original installation kernel and initrd files with the kISO files found in the addon directory.
    6. Copy the contents of the addon/boot/x86_64/loader/initrd directory to the following directory: boot/x86_64/loader/initrd.
    7. Copy the contents of the addon/boot/x86_64/loader/linux directory to the following directory: boot/x86_64/loader/linux.

    Note: If you experience driver problems with SLES 11 SP1 and kISO on HP ProLiant Gen8 target machines, see the following technical support documents:

    For more information on kISO handling, see the kISO media documentation and the OS Provisioning README.

    OS Build-Plan Custom Attributes

    Custom attributes set on the build plan will now be resolved and used in parameters and scripts during the execution of the build plan. If a custom attribute with the same name exist anywhere else on or in the servers’ hierarchy, its value will take precedence over the value set on the build plan. This is the priority order from highest to lowest:

    1. server
    2. device group
    3. customer
    4. realm
    5. facility
    6. OS
    7. software policy
    8. (new) OS build plan

    Driver Update for HP ProLiant G6/G7 Servers

    SA service operating-system drivers have been updated with the latest HP ProLiant SP drivers: SPP 2012.02 b51.

    Multipath SAN Support for OS Provisioning

    As of this release, SA provides multipath SAN support for the topics listed in this section.

    OS Sequences

    Red Hat 6 automatically identifies multipathing and enables kernel modules, but Red Hat 5 does not.

    For Red Hat 5, before you run the Red Hat Enterprise Linux (REL) 5 OS Sequence, use the following steps to pass mpath' as a kernel argument for the server:

    1. Define a custom attribute kernel_arguments for the server, and set its value to mpath.
    2. Create the OS Installation Profile.
    3. Add a custom attribute to the Installation profile, and set its value to mpath.
    4. Set the value of the installation profile to mpath.

    If you are performing multipath installation, it is also recommended that you add mpath as the kernel argument in the kickstart Red Hat 5 file. You can do this by creating a copy of Configure Default Red Hat 5 ks.cfg and modifying the file for use in your OS build plan.

    SUSE Linux Enterprise Server 11

    SUSE Linux Enterprise Server 11 does not identify multipathing by default. Use the procedures in this section to install SUSE Linux Enterprise Server on multipath LUNs.

    Windows 2008/ Windows 2008 R2

    Windows supports installations in multipath environments. Install multipath Device Specific Modules (DSMs) to further improve the capabilities of the target server. Import these DSMs into the SA Software Repository and install them using software policies attached to OS sequences.

    You can modify the SAN Policy for the Windows Service OS (Winpe32, winpe64, winpe32-ogfs, winpe64-ogfs) shipped with SA. For more information about available options, see:

    The default SAN Policy registry value in the SA-provided Windows pre-installation environment (WinPE) boot image is 1.

    VMWare ESX/ESXi

    VMWare ESX and ESXi support multipathing - no additional steps are required.

    Use the Inject Multipath AutoYaST step

    You must add the Inject Multipath AutoYaST Settings step to the OS build plan.

    Perform the following tasks:

    1. Create a new OS build plan by copying the default SUSE Linux Enterprise Server 11 Install Build Plan from the SA Client library.
    2. Add the Inject Multipath AutoYaST Settings step after the Install And Configure SUSE Build Image step.
    3. Add the Embed Files Initrd step after the Inject Multipath AutoYaST Settings step with the following parameters:

      -s /tmp/user.autoinst.xml:/

    The drive injections in the AutoYaST will be performed based on the criterion defined in the OS sequences (see Partitioning Section in AutoYaST).

    Server Location Display

    The Server Location node shows the server’s physical location. The General category in the node displays the following information:

    Note: The server location section only displays information about the HP ProLiant BL servers.

    Accessing Partitions in Linux Service OS ( maintenance mode )

    You can already access your local-system partitions at: /mnt/<<device name>>. As an enhancement of SA 10.0, you will also be able to access your partitions in /mnt/by-uuid and /mnt/by-label to ease the identification of the partitions.

    What's New for Patching

    Windows Patch Management

    Improved Patch Importer

    Patch Library Changes

    Improved Remediation

    Support for newer platforms

    Improved HPLN Microsoft Patch Supplement scanner

    HPUX Patch Management

    What's New for Solaris 11

    New APIs

    To support Solaris 11, the following classes were added to the UAPI:

    Solaris 11 Memory Requirements

    Solaris 11 servers must have more than 1 Gigabyte memory in order to enter the SA Managed Server Pool.

    Solaris 11 Patching Support

    Oracle Solaris 11 uses IPS packages to deliver software and software updates. IPS (Image Packaging System) is a network-based package management system that is used for the entire software lifecycle, including package installation, upgrade and removal.

    Server Automation's Solaris 11 platform support for server patching allows you to update your managed servers to the latest versions of existing software without installing new software. This is a powerful way to keep your system up to date in an environment that no longer supports explicit patch units.

    Solaris 11 patching support leverages the existing Solaris patching functionality, with a few differences to adapt to the new Solaris IPS package delivery structure. Additionally, there are setup requirements for setting up the initial IPS Package database.

    Note: The SA 9.13 Solaris 11 Patching Whitepaper applies to all SA versions, starting with SA 9.13, and provides detailed instructions on setting up and maintaining the IPS Package database. This document also describes the Solaris 11 patch policy and remediation differences. This whitepaper is available via HP's Software Support Online at

    Using Server Modules (SMOs) with Solaris 11

    Solaris 11 introduces Role-based Access Control (RBAC), which affects the functionality of SA Server Modules (SMOs). SMOs rely on the root user to get information from the managed servers. In previous versions of Solaris, the root account is created as a user by default, with the option to have it as a role. In Solaris 11, the root account is created as a role by default; not as a user.

    In order to enable the SMO functionality, the system administrator must modify the root account (root) to make it a user with regular login capability. The best method for doing this is to run an ad hoc script on the managed server.

    To enable root for regular login capability:

    1. Navigate to Devices > Servers > All Managed Servers.
    2. Right-click on the target server and select Run Script > Select Script… and choose Define Ad hoc Script.
    3. In the Script Contents, enter the line ‘rolemod -K type=normal root’ and click Next.
    4. Choose Runtime User: root and click Start Job.

      After the job completes the user will be able to run the SMOs on the selected servers.

    Note: To change the root account to a role again, complete the same procedure but enter ‘usermod -K type=role root’ in the Script Contents.

    Oracle Solaris 11 OS Provisioning

    Oracle Solaris 11 provides a service called the Automated Installer to handle OS Provisioning of bare-metal servers. The Oracle Solaris Automated Installer requires a new package type called IPS.

    Solaris 11 OS Provisioning is somewhat different than the procedure used to provision Oracle Solaris 10.

    The Oracle Solaris 11 Automated Installer no longer uses the Solaris JumpStart mechanism. Instead, SA components have been adapted to use the new Solaris 11 provisioning mechanism.

    New Platform-Specific Changes

    1. Go to and download the images under "Oracle Solaris 11 11/11 Repository Image".  There are two ISO images: Part A SPARC, x86 (3.3 GB), and Part B SPARC, x86 (3.1 GB).
    2. Follow the instructions on the download page to concatenate the two images into a single full image.
    3. Mount the image and copy it to the SA Media server under the directory: /media/opsware/sunos
    Oracle Solaris Automated Installer

    The Oracle Solaris Automated Installer uses two response files:



    The new Oracle Solaris 11 OS provisioning mechanism allows the use of custom attributes to simplify system configuration.

    These are:

    Custom Attribute Name Use Example Values
    mrl The MRL created by the import_media script. This is useful when you want to use an external repository.
    Specify when you use HTTP repositories. http://PROXY_IP:PROXY_PORT
    root_password Specifies the root password in hash format. Use a password from the /etc/shadow directory on the Solaris 11 machine.
    enable_root_user Solaris 11 allows root to be defined as a role in the sc.xml file.

    Presence of this custom attribute will trigger the user creation, even if 'no' value is set.

    hostname Specifies the hostname of the machine. mysolaris11

    What's New for Software Management

    Application Configuration

    Application-Configuration Settings Preview

    In the software policy installation and remediation summary steps, you can now preview your application-configuration settings by pressing a new Preview button to display a preview dialog box. You can also set values. Previously, you had to wait until the installation was finished, and customize/push the application configuration data again.

    Application Configuration History

    When reviewing an existing application configuration, with multiple prior versions, it is now possible to review any archived versions of the application configurations before committing to a rollback.

    New ISM Tool Feature

    The ISM Tool can now create Solaris 11 Image Packaging System (IPS) packages.

    Support RPM Rollback Job Blocking

    RPM rollback jobs are now subject to Job Blocking through the Administration tab. You can configure those jobs in the same way as other types of jobs, including blocking approval of the job.

    Remediate RPM Packages Using the Native YUM

    The new Yellowdog Updater Modified (YUM) plugin is an alternative to the old YUM Adapter for the analyze phase of the remediation process. It uses the native YUM available on the managed server and has the following main advantages:

    The YUM version available on the managed server can be identified by running the following command in the command line:

    yum --version

    When available, the managed server’s native YUM is used to analyze RPM package dependencies. When the managed server does not have a native YUM available, the SA YUM Adapter is used instead. This behavior is based on the default and recommended setting governed by the SA configuration parameter, way.analyze.yum, which has the following available values:

    0 - use the YUM adapter (YUM v2.6.1)
    1 - use the native YUM when available, otherwise use the YUM adapter (Default)
    2 - use the native YUM

    Warning: Changes to SA Core configuration parameter values, as listed in this Release Notes document, are verified by HP and you can safely apply them as directed. However, exercise caution when modifying any default SA Core configuration parameter values as modifications can have a negative effect on core functionality and performance. SA configuration parameters are accessible through SA Client >Administration > System Configuration. Only system administrators with the ‘Manage system configurations in SA’ user group permission can change these settings.

    IMPORTANT—Known issue with legacy YUM: YUM versions prior to 3.2.22 may encounter an installation error if a package is stored in multiple locations. For example, if you import a package to Folder A, run a remediation job, and then import the same package to Folder B and try to install it, the analysis might fail, reporting the package from folder B as missing. This issue does not reproduce on servers using YUM version 3.2.22 or later, where the YUM repository is updated to contain both packages.

    Enhanced Import/Export Software windows

    The import/export windows were enhanced as follows:

    What's New for Storage Essentials


    Storage Essentials dropped support of SA 6.x in this release.

    Migration Instructions

    Migrating from SA 7.8 to SA 10.0
    1. Upgrade to 9.10 first.
    2. Upgrade to 10.0.

    Migrating from SA 9.0x to SA 10.0

    1. From SA 9.0x, first rollback to 9.0  .
    2. Upgrade to 10.0.

    Migrating from SA 9.1x to SA 10.0

    1. Roll back to 9.10.
    2. Upgrade to 10.0.

    Note: If the upgrade fails with an Oracle missing permissions error, perform the following procedure:

    1. Connect to the Oracle database.
    2. Issue the following commands:
      1. Su – oracle
      2. Sqlplus / as sysdba
      3. Grant create job to opsware_admin with admin option;

    SA Script Running Order - Upgrade

    Upgrade From SA


    Script Running Order Steps

    9.11, 9.12, 9.13, 9.14


    1. Run the following scripts to roll back to SA 9.10:
    2. Upgrade to SA 10.0.
    9.0x 10.0
    1. Roll back to 9.0.
    2. Upgrade to SA 10.0.



    Run the following script to upgrade to SA 10.0:


    Changes to Documentation

    The SE Connector guides have been folded into the Storage guides: Storage Visibility and Automation User Guide, and Storage Visibility and Automation Installation & Administration Guide.

    What's New for Usability

    Porting SA Web Client Functionality

    The following functionality was ported to the SA Client to provide a unified user interface:

  • Agent Recertification
  • Agent Upgrade
  • Change Password
  • Customer Group Management
  • Manage Gateway
  • Multi-Master Conflict Resolution
  • Server Attributes
  • Software Repository Mirroring
  • System Configuration
  • System Diagnosis
  • Other Improvements

    Other usability improvements include:

    What’s New for Virtualization Management


    See the SA installation guides for installation information.

    Adobe Flash Player and HP SA Client Launcher Issues

    Certain SA Client features (such as Run OS Build Plan or HP UX Provisioning) require the Adobe Flash Player. If you try to run these features, and you have not yet installed Adobe Flash Player, you will get an error.

    To make sure Adobe Flash Player functions correctly and to avoid the error message, you should:

    1. Make sure that the latest version of Adobe Flash Player is installed in Internet Explorer.
    2. Using Internet Explorer, access the following site:
    3. Follow the instructions there to download the latest Adobe Flash Player.
    4. Restart the SA client

    The HP SA Client Launcher has been updated in this release. Users who have a previous version of the launcher installed will receive a warning message, and will be required to reinstall the latest version.

    Follow these steps to install the new launcher:

    1. Exit all instances of the SA Client (check your TaskManager to ensure that all instances are stopped).
    2. Uninstall the HP SA Client Launcher.
    3. Download the HP SA Client Launcher (1.6.4 or later):
      1. Access the OCC login page and download the new launcher, or
      2. Login to the OCC and download the installer from the right panel in the home page.
    4. Reinstall the HP SA Client Launcher.
    5. Restart the SA Client and run the features normally. 

    Post-Installation Tasks

    This section lists the tasks that should be performed after you install SA 10.0. Some tasks might not be appropriate for your situation.

    Windows Server OCLI Installation

    If you plan to install the SA Command-line Interface (OCLI) on a Windows Server after upgrading to SA 10.0, you must update the SA Agent on that server to the latest version. Errors occur during OCLI installation on Windows servers with earlier SA Agent versions.



    Customized Settings

    If you have customized such settings as Java heap settings, you must reapply your customizations after you install SA 10.0, as the settings are set to the SA default during installation or upgrade.

    Back to the Table of Contents

    Known Issues

    This section describes known issues for SA 10.0. The table lists issues first alphabetically by Subsystem, then numerically within each subsystem.

    Known Issues

    QCCR1D Symptom/Description Platform Subsystem Workaround

    Administration User Interface

    QCCR1D147462 Web Services Data Access Engine (Twist) stops functioning when the WebLogic Server Administration Console is accessed. As a consequence, the WebLogic Server Administration Console is disabled in SA 10.0, by default.


    Independent Administration UI To enable WebLogic Server Administration Console:

    1. Edit /opt/opsware/twist/
      1. Remove -XX:+UseCompressedOops.
      2. Replace:OPTION_COMPRESSEDOOPS="-XX:+UseCompressedOops" with OPTION_COMPRESSEDOOPS="".
    2. Edit /var/opt/opsware/twist/config/config.xml and remove "<console-enabled>false</console-enabled>".
    3. Save these 2 files.
    4. Restart the Web Services Data Access Engine (Twist) and access the console.

    If, after you have completed the procedure described above, you want to use the Web Services Data Access Engine instead of the WebLogic Server Administration Console:

    1. Roll back the changes in #1 and #2 above.
    2. Restart the Web Services Data Access Engine .
    QCCR1D166272 You cannot launch the SA Client after upgrading your core from an earlier version of SA to SA 10.0, and you receive a Launch File Error. Independent Administration UI

    Follow these steps:

    1. Uninstall the old launcher.
    2. Download the new launcher by doing one of the following:
      1. Accessing the login page and downloading the new launcher.
      2. Logging-in to the core and, from the right panel in the home page, download the installer.
    3. Install the new launcher.

    All the previous settings are retained and it should be able to launch without any issues.


    QCCR1D91352 Agent deployment times are increased considerably (sometimes up to 30 minutes) if you try to deploy to a host that does not have the uudecode program installed.

    In the staging phase of the Agent deployment process, the transmission of the binaries to UNIX/Linux hosts is done over a character stream. The binary files are encoded prior to the transmission and decoded once uploaded to the remote host (using the uudecode program). If uudecode program is not present on the remote host, ADT uses an inline implementation that is very slow.

    Unix, Linux Agent Deployment Make sure that the uudecode program is installed on the host to be managed.
    QCCR1D107917 Failed SA agent installation returns error message in the agent log file (%SystemDrive%\Windows\System32\opsware-agent-installer- .log). Windows Agent Installer Remove all the files from the following three directories,
    if they exist, and reinstall the agent.

    %SystemDrive%\Program Files\opsware\agent\lcpython15
    \Lib\site-packages\win32c om\gen_py\



    QCCR1D110347 Windows servers running a pre-9.0 agent can perform a scan on an upgraded 9.0 core but not on a freshly installed 9.0 core because scanning Windows utilities are retained on the upgraded core but are absent from the freshly installed core. Windows Agent Upgrade the agent on the managed servers that you registered
    with SA 9.0.
    QCCR1D111593 Agent fails to install when there is a gateway problem, but the agent log reports that the installation was successful.

    Windows Agent Installer Make sure the gateway can be reached from the managed server.
    QCCR1D118437 Agent deployment fails several times due to timeout issues when the uudecode utility is not installed on the machine to which the Agent is deployed.
    Red Hat or SUSE Linux s390x Agent Deployment/Upgrade Install the uudcode utility on the machine(s) to which Agents are to be deployed to facilitate Agent deployment.

    Your Solaris satellites and managed servers cannot be accessed with OGFS, because your PAM library for Secure Shell (SSH) is incompatible with the SSH daemon that SA uses for OGFS.

    Solaris Agent

    To resolve the issue, add ptymonitor.nopam:1 to the agent.args file on Solaris. This will bypass the PAM-based authentication.

    Caution: Contact HP Support for more information before you make this change.


    SA Agent scan for installed software fails.

    RHEL 5 x86 - 64 Agent Either rename the createrepo folder or add an RpmQueryCli: rpm line to the agent.args file that will instruct the SA Agent use the rpm command when searching for installed packages.


    QCCR1D116476 APX session timeout is not correctly implemented. Independent APX To increase timeout for Web APX Proxy (Note: this must be
    done at all the Slices on all the Cores):
    1. Edit /etc/opt/opsware/apxproxy/apxproxy.conf
      to specify both the session timeout and socket
      timeout. Make sure socket timeout is at least
      equal to session timeout. For example,


    2. Edit both /opt/opsware/apxhttpd/conf/httpd.conf.tmpl
      and /var/opt/opsware/ogfs/mnt/root/opt/opsware/
      to add a timeout directive.
      Add this property after the "Server" property. For example,

      imeOut 1200

      Remember, unlike apxproxy.conf, the timeout value in
      httpd.conf.tmpl is in seconds, not millisecond.

    3. Restart the Core.
    QCCR1D160543 HPLN APX content developed for 'platform_linux' stream fails on content reload if managed platform content is already imported

    Independent APX Tool None

    Audit and Remediation

    QCCR1D81308 An erroneous status is displayed when remediation of registry and COM+ objects fails.
    Windows Audit and Remediation - Backend None
    QCCR1D151552 If you cancel a running audit job, and a target server shows a "SKIPPED" job status in the audit results, until an audit has successfully run, the server's compliance view shows the following incorrect status for the policy:

    Policy has changed since the last scan”.

    Independent Audit and Remediation Rerun the audit job.
    QCCR1D161054 If you set an audit schedule in previous releases (pre-SA 10.0), and you used System time zones (such as SystemV/PST8 or System V/PST8PDT), you will receive a com.opsware.job.IllegalScheduleException error.

    Independent Audit and Remediation Reset the audit schedule to use supported time zones.
    QCCR1D162962 When you export audit results to XML, the results will not be correctly displayed if they include text that has an accented character. The following error appears in the results:

    XML page cannot be displayed. Invalid character was found in text content.

    Independent Audit and Remediation None
    QCCR1D165732 Running a snapshot-based audit with multiple Perform Inventory rules will result in the following RuntimeException error:

    Multiple Inventory checks are not supported for snapshot-based audit. Optionally, run the corresponding rule types with (*) option.

    Independent Audit and Remediation Run the snapshot-based audit for corresponding rule types with the (*) option instead of the Perform Inventory option enabled.

    BSA Essentials Dataminer

    QCCR1D112784 In multimaster environments, Application Deployment data mismatches between SA and BSA Essention can occur if the data is replicated across the Model Repository Multimaster Component (vault) to where the BSA Essentials Dataminer is installed within the first few milliseconds of a minute. Independent BSA Essentials Dataminer None

    Data Access Engine

    QCCR1D111804 Reloading the cache on 10 clients simultaneously makes the Data Access Engine (Twist) malfunction, and blocks access to the core server. Other users are unable to log in to the core.

    The following error is displayed:

    Java Web Start 1.4.2_15 Console, started Thu May 06 15:48:55 PDT 2010 Java 2 Runtime Environment: Version 1.6.0_18 by Sun Microsystems Inc.
    Logging to file: C:\Documents and Settings\buslovic\Application Data\HP BSA\Cache\deployment\log\javaws\javaws1476906802910963403.log
    FINE accepting connections on port 1098
    FINE Protocol handlers:
    FINE Connecting to Twist: https,, 443
    May 6, 2010 3:49:04 PM <init>
    WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_SSL_WLS; hostname:; port: 443"
    org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
    at Source)
    at Source)
    ... 32 more

    Independent Data Access Engine None

    Database Scanner for Oracle

    QCCR1D91143 The status of an ASM Diskgroup shown in the Properties view (for one database instance only) is different than the status shown in the Database Configuration Assistant (DBCA) view (a CONNECTED status is displayed instead of a
    MOUNTED status).
    Independent Database Scanner for Oracle None
    QCCR1D133226 In order to monitor an Oracle 11G database with the SA Oracle Database Scanner, the XML DB and DBMS_NETWORK_ACL_ADMIN package must exist in the database. 

    The SA Oracle DB Scanner needs access to these objects in order to grant privileges and access for itself. If the objects do not exist, then the "pamuserprivilege.sql" will fail and the DB Scanner cannot be run.   An application may or may not install these objects in its Oracle 11G database.

    The following error might be displayed under these circumstances:
    "PLS-00905: object SYS.DBMS_NETWORK_ACL_ADMIN is invalid". 

    Independent Database Scanner for Oracle Before executing the SA DB Scanner "pamuserprivilege.sql" in the Oracle database, first perform the following steps to install the XML DB and DBMS_NETWORK_ACL_ADMIN package in the Oracle 11G database.

    1) cd $ORACLE_HOME/rdbms/admin
    2) sqlplus /nolog
    3) SQL> connect <sys_user>/<password> as sysdba
    4) SQL> spool install_xml.log
    5) SQL> @catqm xdb sysaux temp NO
    6) SQL> @dbmsnacl.sql
    7) SQL> spool off;

    Database and Middleware Automation (DMA)

    QCCR1D133378 Workflow cancellation indicates success in the DMA Console, but workflow runs to completion on SA managed server. Independent DMA Use the appropriate process manager for the managed server's Operating System (for example, kill for UNIX and Task Manager for Windows) to manually terminate the process. 
    QCCR1D146469 If you run the -erase command manually in order to delete all of your Database and Middleware Automation data and reload the default data, the Discovery solution pack is not reloaded. Independent DMA Follow these steps to import the Discovery solution pack:

    1. Copy the following file from the SA Core server to the system where you will access the Database and Middleware Automation user interface (UI): /opt/opsware/da/webapps/dma/discovery/
    2. On that system, open the Database and Middleware Automation UI in a browser:
    3. Log in using your SA user name and password.
      At least one of your roles must include the Manage Database & Middleware Automation SA action permission.
    4. On the Solutions ® Installed page, browse to the file that you copied in step 1.
    5. Click Import.

    Gateways (Bandwidth Configuration Tool)

    QCCR1D147794 Provide warning for bandwidth throttle behavior in 9.06 -> 9.0 -> SA 10.0 upgrade path.

    Independent Gateways (Bandwidth Configuration Tool) During the 9.06 to 9.0 rollback, changes made in 9.06 to the Bandwidth Configuration Management Tool (including properties files changes and to the default BWT.conf file) are deleted (undone).
    When you upgrade the core to SA 10.0, perform the following task to restore your configuration:

    From a Slice Component bundle host (or from a Satellite host), run the following command to push the configuration file:

    /opt/opsware/opswgw/bin/gwctl -f <path_of_your_config_file>

      After you upgrade your core to SA 10.0, the SA 9.0 satellite is unreachable. Independent Gateway For 9.0 Satellites to work with SA 10.0, an Egress filter must be modified in the Gateway.

    For example, for a 9.0 Satellite that connects to TOMATOSAT1 Core:

    1. Change the Gateway configuration as follows:

      Original Gateway Filter:
      Change to :

    2. Restart the satellite gateway.
    3. **Important ** After upgrading the satellite to SA 10.0 the Gateway filter must be restored to the original filter. In this case, restore it back to:



    If you only upgrade your SA Core from 9.1x to 10.0, then upgrade to 10.01, but do not upgrade your SA satellites in the same maintenance window, the satellite facility and its managed subsystem become unreachable.

    Linux Gateway Upgrade your satellites at the same time as you upgrade your SA core.

    Global Shell

    QCCR1D142123 Test button action for RDP and Telnet fails although it successfully works on the server. Windows Global Shell Identify the Windows PID and terminate it using Windows Task Manager or the taskkill command.


    QCCR1D111215 Restoring OS Provisioning Stage 2 images fails on SUSE Enterprise Linux 9, which is a deprecated platform. SUSE Enterprise Linux 9 Installer You can restore the OS Provisioning Stage 2 images by manually running the restore_stage2.pyc script. This script is located in:
    QCCR1D114639 If you install additional Slice Component bundle instances after patching the SA Core, wayscript versions are set to the version you already have, rather than to the patch version. Independent SA Installer In the SA Web Client:
    1. Log in as administrator (opsware admin user) and
      navigate to Environment -> Customer -> Opsware ->
      Custom Attributes -> CORD_OPSWwayscripts
    2. Identify the SA core server by checking the value field
      of the custom attribute CORD_OPSWwayscripts.
    3. Log in to the SA Core server you identified in step 1
      and execute the following two commands:
      Command #1:
      cd /var/opt/opsware/OPSWpatch/OPSWwayscripts/scripts

      Command #2:
    4. Apply any required hotfixes to the wayscripts.
    QCCR1D132004 Health check fails with mismatched core component version errors (check_occ_up, lnxisoupload, new_platforms, opswbia_upload) Independent Installer None
    QCCR1D161352 Upgrade failed on a slice during OS Provisioning. Independent Installer Restart the upgrade process.

    HP has been unable to reproduce this issue. If the same behavior still exists and you can reproduce it, please contact HP Support, referencing QCCR1D161352. Please provide the exact steps to reproduce and/or demonstrate the steps and environment details to HP Support. The current Change Request will remain in HP's database for future reference.

    ISM Tool

    QCCR1D163521 After the ISM Tool is installed, if commands (such as ismtool.cmd, ismusertool.cmd) are issued, they fail with the following error:

    The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.

    Windows ISM Tool Install Microsoft Visual C++ 2005 Redistributable Package (x86).


    QCCR1D161658 If you chose a Traditional Chinese Windows desktop setting, or you chose a Traditional Chinese profile locale setting in the user interface, your default display language will be Simplified Chinese. This release does not support the Traditional Chinese locale.

    Independent Localization None

    OS Provisioning

    QCCR1D100928 RAID deployment fails when the RAID configuration is captured using ACU version (linux5 boot image) for valid RAID configurations on machines with SCSI
    drives because the "pretty printing" of SCSI drive bus values uses 0-based index instead of 1-based index.
    Red Hat Enterprise Server 5 OS Provisioning
    1. Perform captures with ACU Version
      (using boot images other than linux5) and deploy
    2. Modify the raid.hpacu.script custom attribute value for
      RAID Array Configuration on ACU Version: RAID policies to use the correct drive
      For example, modify this captured configuration:
      ; Array Specifications
      Array= A
      ; Array Drive Type is Parallel SCSI
      ; 1:0 (36.4 GB), 1:1 (36.4 GB), 1:2 (36.4 GB),
      1:3 (36.4 GB),
      1:4 (36.4 GB), 1:5 (36.4 GB)
      Drive= 1:0, 1:1, 1:2, 1:3, 1:4, 1:5
      to the following:
      ; Array Specifications
      Array= A
      ; Array Drive Type is Parallel SCSI
      ; 2:0 (36.4 GB), 2:1 (36.4 GB), 2:2 (36.4 GB),
      2:3 (36.4 GB),
      2:4 (36.4 GB), 2:5 (36.4 GB)
      Drive= 2:0, 2:1, 2:2, 2:3, 2:4, 2:5
    QCCR1D104194 When RAID deployment fails after the RAID controller configuration has been cleared, subsequent RAID captures or deployments will fail unless RAID is first configured manually.

    The following error displays:
    Exit status: 1280

    Error message from ACU: ERROR: (2821)
    No controllers detected.

    Independent OS Provisioning - Backend Manually set the RAID controller configuration:
    1. Restart the server and press F8 when prompted.
    2. Create logical drive(s).
    3. Assign physical disks and RAID level.

    After the RAID controller has been manually configured,
    SA can be used to capture and deploy RAID configurations on
    the machine.

    QCCR1D104739 During a network boot of the server, the following
    error displays:
    "No driver found" screen appears:
    "Unable to find any devices of the type
    needed for this installation type.
    Would you like to manually select your
    driver or use a driver disk? [Select driver]
    [Use a driver disk] [Back]
    Red Hat Enterprise Server IA64 OS Provisioning The missing driver is not required. Press F12 to bypass the driver.
    QCCR1D109077 Assign Customer OS Build Plan content script fails if customer names contain quote characters. Windows OS Provisioning Backend Specify the customer ID instead of the actual customer name.
    QCCR1D114523 When performing OS provisioning using Application Deployment Automation, if the SA OS Sequence in use includes a device group and multiple servers are provisioned simultaneously, some of those server provisioning jobs will fail with the following error:
    Unexpected general exception: com.opsware.device.DeviceGroupVO.modifiedDate
    Linux, Solaris, Windows OS Provisioning Do not include any device groups in your OS Sequence.
    QCCR1D117539 Unable to stop an OS Build Plan job.

    Independent OS Provisioning Wait for the rosh session to time out (the default timeout is 4 hours) or end the rosh session and start a new one. This workaround will only work with a single core, not a mesh.

    QCCR1D131265 Manage Boot Client utility: WAPX sometimes fails at the second step with: 503 Service Unavailable Error Independent OS Provisioning Backend In the Global File System (GFS), use the /opsw/apx/bin/osprov/manage_boot_clients_script.
    QCCR1D132628 SUSE Linux Enterprise Server provisioning fails on an HP ProLiant server with a CCISS disk. SLES OS Provisioning For post-SUSE Linux Enterprise Server 10 SP2 provisioning on HP ProLiant servers with CCISS disks, ensure that the <code1>autoyast.xml</code1> file has the partitioning configuration specified as shown below:

    <partitioning config:type="list">
    <partitions config:type="list">

    QCCR1D132825/130199 During provisioning in a  non-DHCP environment, Red Hat Enterprise Linux 6 provisioning can become interactive if the HPSAlinux_boot_cd.iso remains connected. Red Hat Enterprise Linux 6 OS Provisioning Backend Eject the boot CD when the server reaches the restart phase or after provisioning becomes interactive.
    QCCR1D133153 VMware ESX 4.1 OS Sequence with OS firewall enabled fails with a broken pipe exception during the Agent download phase. VMware ESX 4.1 OS Provisioning The firewall should be disabled during OS Provisioning and re-enabled after.
    QCCR1D135080 Spaces at the beginning or the end of rootpw are ignored for ESXi5.
    Independent OS Provisioning To use passwords that contain spaces, use quotes (" ") when setting the root_password custom attribute.
    QCCR1D136144 Running a single OS Sequence job against two servers with the same MAC address in different networks causes an exception. Independent OS Provisioning - Backend If you have servers with the same MAC address in different networks, you must provision them sequentially. For example,  complete the Run OS Sequence job on the first server before you power on the second server.
    QCCR1D136423 Provisioning dupe-mac Linux servers sequentially into a managed server, then reprovisioning the servers simultaneously, should result in a Run OS Sequence job error.
    Linux OS Provisioning None
    QCCR1D136445 If you attempt to register another server with the same MAC address as a mini agent after a server is in the OS Provisioning lifecycle, the Run OS Sequence job on the first server fails. Independent OS Provisioning Follow these instructions:
    1. Shut down the second server.
    2. Reboot the first server.
    3. Re-register the first server as a mini-agent.
    4. Re-run the OS Sequence steps.
    After a server is registered with SA as miniagent, if you then attempt to register a second server with the same MAC address (but with a different service operating system than the first server) as a miniagent, the registration fails. Then, if you shut down the second server as instructed, the Run OS Sequence job against the first server fails with an error. Linux OS Provisioning When this problem occurs, you must

    1. Ensure the second server remains shut down
    2. Reboot the first server and  re-register it with SA as miniagent
    3. Run the Run OS Sequence job against the first server again.


    Linux 6-OGFS boot failed on HP ProLiant DL380 G4 and DL385 G1. Linux OS Provisioning None
    QCCR1D147226 An iLO's realm information is not updated after the iLO is moved from one satellite to another. Independent   Remove the iLO server, then add it again, this time into the correct realm.
    QCCR1D155788 OS Build Plan does not reboot into the installer for Red Hat Enterprise Linux 5.0 and 5.1.

    Red Hat Enterprise Linux 5.0 and 5.1 HTTP OS Provisioning

    There are two possible workarounds:

    • Do not specify "text" and/or "skipx" (graphical install) in the Kickstart file.
    • Use NFS instead.
    QCCR1D160191 SLES11 Guest Customization fails on SCVMM and VMware source template if the source is using Integrated Drive Electronics (IDE) disks.

    Microsoft SCVMM and VMware OS Provisioning Add a section into the OS Build Plan (in the step that configures the AutoYaST file) to name the disks as needed (for example: /dev/sda*) or, after the system is installed with SA's default OS build plan, change /etc/fstab to a supported format (for example, change the /dev/disk/by-id to /dev/sda*)

    OS Provisioning fails when trying to provision Solaris Version 10u8 or older releases using the Z File System.


    Solaris X86 OS Provisioning, Backend Use a file system other than the Z File System if you are using Solaris Version 10u8 and older.

    OS Sequence Provisioning fails on RHEL 6 PPC with the following error:

    Cannot resolve a valid OS media server from OS media resource locator ('nfs://').

    Linux OS Provisioning Run the import_media script using the IP address of the media server, instead of its hostname.
    QCCR1D162834 The following error is displayed when you run an OS build plan, and that build plan is started on a different facility to the one that its target uses:
    "Failed to inject required settings.[Errno 2] No such file or directory: '/tmp/osbp_info/'"

    Independent OS Provisioning, Backend Start the OS build plan from the same facility that contains its target. This ensures that the plan and its target are using the same database.
    QCCR1D164212 The 'Add to Virtualization Manager' step fails during Windows HyperV provisioning with "Agent installation failed on <server> because of a WS-Management configuration error." Windows 2008 R2, Windows 2008 R2 SP1, Windows 2012 OS Provisioning Add a 'Sleep' step for several minutes before the 'Add to Virtualization Manager' step. This will leave sufficient time for the Windows Remote Mangement service to start.
    QCCR1D165305 Provisioning fails with the following ESXi installer timed out error:
    "The IP address was not reported. The ESXi installer probably failed."

    ESXi 4.1 Update 1 OS Provisioning The ESXi 4.1 Update 1 installer sometimes fails to configure the DNS properly through DHCP. Perform static provisioning or set the media server by IP Address instead of Host Name.

    OS Build Plans jobs fail with "Unsupported target OS Osprov Service OS in PROVISIONING/OK". This is happening if the recurring "Agent Communication Test" job coincides with the server being unreachable during the build plan execution, like after the "Reboot" step.

    All platforms supported by OS Build Plans OS Provisioning, Backend Bring the failed machine back to the state when the build plan was started, either in the service or productions OS. To recover the lifecycle/state combination for the production OS trigger an agent hardware registration. For the ogfs-agent the lifecycle can be recovered back to UNPROVISIONED only programatically. Once the lifecycle/state combination is recovered, run the build plan.

    Patch Management - HP-UX

    QCCR1D165089 Compliance for HP-UX depots not working when multiple depots are attached to the same server. HP-UX HP-UX Patching None

    Patch Management - Solaris

    QCCR1D100566 Although the reboot is performed correctly, when you preview remediating a patch policy on a server, or view
    the job status for a patch policy that is already remediated, the reboot setting might incorrectly display “Install and Reboot Later” when it should display “Install and Reboot”.

    Solaris Patch Management - Solaris A workaround is not required because the reboot is performed correctly,
    even though the display may be incorrect.
    QCCR1D111342 Importing clusters with old names using the solpatch_import command will fail because Sun has renamed their Solaris patch clusters - the clusters in your SA Library may not match the cluster names from Sun on Sunsolve. SunOS 5.6 - 5.10 and SunOS 5.10 x86 Patch Management - Solaris Download the latest supplement file from HP LNc. For complete
    instructions, see “Obtaining the Solaris Patch Supplementary
    Data File” in the SA User Guide: Application Automation.
    QCCR1D114156 The solpatch_import –filter option does not display recommended and/or security patches if they had previously been marked obsolete. This became an issue on June 4, 2010 when Oracle changed the criteria for
    recommended and security patches (described here:
    Solaris Patch Management - Solaris Users with an existing metadata database (solpatchdb) must
    delete the, and
    files and run create_db
    to have support for recommended obsolete patches.

    You must recreate the Solaris patch metadata database
    (solpatchdb) if the following are true:
    1. You use the solpatch_import –filter option.
    2. You have run solpatch_import –update_db on
      June 4, 2010 or later.

    After you have installed SA 9.13, perform these tasks to recreate
    the metadata database (solpatchdb):

    1. Log in to the SA Client.
    2. Select Library in the Navigation pane.
    3. Select By Folder.
    4. Navigate to /Opsware/Tools/Solaris Patching.
    5. Delete the following files:

    Follow the steps to create a new metadata database (solpatchdb)
    as described in the SA User Guide: Application Automation,
    Patch Management for Solaris.
    QCCR1D130601 solpatch_import: Import "Fujitsu Solaris 10 OS Recommended Patch Cluster" fails with 'KeyError: 'patch_order.SS' on a Solaris core. The following error displays when importing a large cluster on an older Solaris core:

    bash-3.00# echo Fujitsu Solaris 10 OS Recommended Patch Cluster | ./solpatch_import -a import
    Importing patch cluster Fujitsu Solaris 10 OS Recommended Patch Cluster note: didn't find end-of-central-dir signature at end of central dir.
    (please check that you have transferred or created the zipfile in the appropriate BINARY mode and that you have compiled UnZip properly)

    Solaris Patch Management - Solaris - Backend Import a specific patch on your core. See the article from Oracle at
    QCCR1D132332 After upgrading to SA 10.0, you must manually run update_supplements to see new clusters, such as Fujitsu clusters. Solaris Patch Management - Solaris SA 9.10 provides new clusters (Fujitsu clusters) in the Solaris collection file.
    This workaround applies to a mesh that contains different SA cores (such as SA 7.88 or SA 10.0), where the mesh has Solaris patching configured (solpatchdb). After the mesh has been upgraded to SA 10.0, the following command must be manually run on a core server (slice):

    /opt/opsware/solpatch_import/bin/solpatch_import -a update_supplements

    This command loads the new collection file into solpatchdb.

    To see all available clusters, including the new clusters, run the following command:

    /opt/opsware/solpatch_import/bin/solpatch_import -a show --available_clusters

    QCCR1D147304 Recommended patches KB979309 and KB2416400 are not shown as recommended in SA, but are present in scanpatchoutput. Solaris Patch Management - Solaris None
    QCCR1D153979 You might encounter the following error when attempting to import the Solaris patch supplement:

    2011-08-31 19:09:48,823 live-network-connector:DEBUG : }
    2011-08-31 19:09:48,823 live-network-connector:ERROR : Import of content Solaris Patch Supplement version 2.00.00-01 failed. Exception: [PostExecuteError] Non-zero exit (6) for post-execute command '/tmp/tmpgcTtsa/'.
    2011-08-31 19:09:48,823 live-network-connector:DEBUG : Associated metadata: /content/sas/solaris_patching/dd78741ee8ea41718ca70bf0debf3f51.metadata.xml
    2011-08-31 19:09:48,824 live-network-connector:DEBUG : {
    File "modules/", line 584, in _importStreams
    File "modules/content-handlers/", line 87, in import_content
    File "modules/lnc_common/", line 111, in do_post_execute

    Solaris Patch Management - Solaris This issue is caused by the fact that Fujitsu recently started requiring username/passwords to download README's from their website.

    1. If you have a Fujitsu account, enter the Fujitsu account credentials into /etc/opt/opsware/solpatch_import.conf.

    Here are the Fujitsu credential entries in the solpatch_import.conf file:

    fujitsu_download_user=<user name>

    2. You can also do a temporary workaround to disable the attempted download of Fujitsu account information by editing the /etc/opt/opsware/solpatch_import/collections.xml file to remove the <Fujitsu_clusters> tag information. This will prevent the solpatch_import script from attempting to import the Fujitsu README files. Here is an example of the XML data that will need to be removed:

    <fujitsu_cluster name="Fujitsu Solaris 10 OS Recommended Patch Cluster">
    <fujitsu_cluster name="Fujitsu Solaris 9 OS Recommended Patch Cluster">
    <fujitsu_cluster name="Fujitsu Solaris 8 OS Recommended Patch Cluster">


    QCCR1D157891 Solaris 11 Patch policies should prevent the user from changing the reboot option to something other than the default option: 'Hold all server reboots until all actions are complete.' Solaris Patch Management - Solaris Always ensure that the reboot option is 'Hold all server reboots until all actions are complete.' when remediating Solaris 11 Patch Policies.
    QCCR1D159052 When the agent takes a long time to connect to the network after a reboot, the status of the patches that are already installed changes to 'Skipped'. Solaris Patch Management - Solaris None

    Installation of Solaris 11 recommended patch policy containing Solaris 11.1 IPS units fails with unsatisfied dependencies.

    Solaris Patch Management - Solaris

    Solaris 11.1 IPS units should not be present in SA when creating Solaris 11 recommended patch policies. When importing Solaris 11 IPS packages using the sol_ips_import tool, apply the filter ‘-f 5.11-0.175.0’ to exclude Solaris 11.1 IPS packages.  Solaris 11.1 already uploaded into SA should be deleted.

    Patch Management - Windows

    QCCR1D102713 If a patch policy contains one or more superseded patches, the number of total rules counted after remediating or patch installation is incorrect. Note that the compliance state of the server is accurate before and after remediating. Windows Patch Management - Windows - Backend None
    QCCR1D130284 Install patch Q979309 failed on a Windows 2008 R2 server with exit code 4. Windows Patch Management - Windows - Backend Install KB978601 and KB979309.
    QCCR1D131240 If you do not have the SA 9.10 Agent installed on a managed server, the Reboot Server option will not change the server's Reboot Required state from "Yes" to "No". Windows Patch Management - Windows - Backend Upgrade the Agent on your managed server to the SA 9.10 Agent and then reboot the server. The server's Reboot Required state will then accurately display the state as "No".
    QCCR1D148400 After MBSA import completes, it takes a long time to update patches in library and database information in the Administration page. Windows Patch Management - Windows None
    QCCR1D157363/139856/152927 Occasionally, the following uninstall patch job message is displayed when you manually uninstall a patch using SA: "The Agent reports that this software is not uninstallable."

    However, the patch is actually uninstalled.  When you uninstall the patch using the Control Panel > Add/Remove Programs method, the patch uninstalls correctly.

    Windows Patch Management - Windows - Backend  
    QCCR1D161961 Uninstalling an SP1 patch on Windows 2008 R2 fails with timeout. Windows Patch Management - Windows When the next scan occurs, the status will be updated.

    QCCR1D162337 Windows 2k12 software policy remediation fails with the following type of error:


    Windows Patch Management - Windows Import and run the latest (later than October 2012) Microsoft patch CAB file once. You should only have to do this one time.

    SA Client (Framework)

    QCCR1D105671 The SA Client cannot be installed under a localized (I18N) directory if the directory path contains non-ascii characters. Windows SA Client Framework Install the SA Client Launcher in a path containing only ascii characters.

    SA Client (Search)

    QCCR1D66448 Some discovery dates for SAN arrays, NAS filers, and switches will not display as expected, although they are
    technically correct, if the user profile is set to a non-UTC timezone for Storage System Discovery Date.
    Independent SA Client (Search) None

    SA Web Client

    QCCR1D118067 Chinese Date format: Commonly used date formats, like yyyy ’year’ mm ‘month’ dd ‘date’ and ‘yyyy-mm-dd’ are not listed in the user profile setting, so users cannot select a favorite date format. Win2008 Win2008 R2 SA Web Client None


    QCCR1D91097 In some cases, in the SA Web Client Manage Gateway page, changes to bandwidth throttling values between two gateways do not persist. Independent Satellites You must apply any bandwidth changes between gateways on the Core Gateways only. Changes made on other gateways will not take effect.
    QCCR1D97659 Network scans to a satellite realm fail for hosts with the error:
    XML document structures must start and end within the same entity.
    Windows Satellites In the SA Client Options select Tools -> Options-> Unmanaged Servers -> Advanced and remove the argument -S %GATEWAY_IP% from the NMAP parameters. The network scan should complete successfully.


    QCCR1D79545 Exporting a Run Server Script Job output containing multi-byte characters (Japanese/Korean) to .csv results in question marks in place of the multi-byte characters. Windows Script Execution Export the job results in .txt format to eliminate the garbled text.
    QCCR1D163487 Python script types are not supported on Unix servers.
    Unix Scripts Backend Do not run or choose Python- type scripts on Unix servers.


    QCCR1D92244 Searching on extended ascii (that is, European) characters returns no matching results. Independent Search None

    Software Management

    QCCR1D115665 Migrating a Windows Server 2008 R2 x64 server, attached to a dynamic device group with the rule Operating System=Windows Server 2008 x64 specified, prevents all Application Configurations, remediated using a Software Policy, from being detached from the server. Windows Server 2008 R2 x64 Software Management None
    QCCR1D152877 If the Xen server '/' folder has ‘execute’ permissions for only the root user, then any remediation performed by a non-root user will fail. The folder permission should not be restricted to root users.

    Citrix Xen Server 6.0.2 Software Management Run chmod 755 /
    QCCR1D159841 When performing a core upgrade, you might experience conflicts originating from the UNITS and REALM_UNITS tables. In order to continue the upgrade process, you must solve the conflicts using the force resolver script.

    Independent Software Management Backend Solve the conflicts with the force resolver script and continue with the upgrade process.
    QCCR1D161867 After applying the 9.05 patch, all Solaris 10 x86 remediation jobs failed with the following error:

    The operation to download software failed.Execution error: Traceback (innermost last):

    File "./base/", line 136, in evaluator File " ", line 1342, in ?
    File " ", line 1336, in main
    File " ", line 1224, in stage File " ", line 610, in download_packages
    File " ", line 303, in finishDownload
    File " ", line 229, in setProgress
    OverflowError: long int too long to convert

    Solaris Software Management None
    QCCR1D163868 When remediating two different versions of the same rpm package with the install flag set, the older version of the package will be overridden by the newest one, instead of having two different versions of the same package installed on the managed server.

    AIX, Linux, Solaris Software Management None

    Software Repository

    QCCR1D131751 HP Server Automation 9.10 configurations that use a Solaris machine as the Network File System (NFS) server may encounter unexpected behavior and unreliable performance. Due to known instability issues with Solaris NFS, this configuration should be avoided. The recommended configuration is a Linux NFS server, which works reliably with either Solaris or Linux clients. Solaris Software Repository The recommended configuration is a Linux server as the NFS, which works with either Solaris or Linux machines as clients.
    QCCR1D152739 During Secondary Core Model Repository installation, the following warnings are seen in the installer log:

    ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."FIBREFABRICELEMENTS" created with compilation warnings
    ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."AGENTPACKAGE" created with compilation warnings
    ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."STORAGEDEVICE" created with compilation warnings
    ORA-39082: Object type ALTER_PROCEDURE:"TRUTH"."RESOLVEDUPLICATEWWN" created with compilation warnings

    Red Hat Linux Server 5 Software Repository The warnings occur due to the Oracle RDBMS's improper object import order or due to dependencies on others objects. Although the SA Installer corrects these issues by compiling all objects after import, these warnings may still be seen in the installer log. You can ignore the Oracle RDBMS warning messages in the installer log.

    Storage Host Agent Extension

    QCCR1D93630 LUNs that are multipathed by EMC PowerPath are shown as both "ROOT" and "LUN" in the Inventory -> Storage -> Volumes Panel alongside LUNs that are correctly displayed. The SCSI Bus number provided by PowerPath (using the powermt command) does not match the bus number of the disks (LUNs). Windows Storage Host Agent Extension None
    QCCR1D93690 The Server -> Relationships -> SAN Switches
    panel on a virtual server is empty/only displays SAN switches to which the given server is directly connected.
    In some cases, a server may depend on SAN switches that are not displayed in this panel.
    For example, a virtual server may be using storage allocated from a hypervisor that was allocated storage from a SAN.
    Independent Database Scanner for Oracle None
    QCCR1D105382 When you run the storage snapshot specification, the disk capacity information is changed in the
    Inventory -> Storage -> Disk panel. This occurs if there is a mismatch in the disk names, as reported by the hardware registration script and the storage snapshot specification.
    Windows 2008 Storage Host Agent Extension Reboot the server after changing disk information (such as installing or uninstalling multipathing software, presenting new LUNs, deleting LUNs, and so on),
    and run the hardware registration before running the storage snapshot specification.
    QCCR1D105953 An EMC Symmetrix array that is discovered through SE Connector can report more than one storage volume with the same LUN number presented to a managed server. Running the storage snapshot specification on the managed server will succeed; however, the Inventory -> Storage -> File Systems and Inventory -> Storage -> Managed Software panels will be empty. In addition, some host volumes with a LUN service type will not be displayed in the Storage -> Inventory -> Volumes panel. Independent Storage Host Agent Extension None
    QCCR1D106699 For managed servers with mirrored volumes, if one of the disks that is part of a mirrored volume fails or is removed, the state of the volume is shown as "Failed Redundancy" in the Disks Management panel. However, in the Inventory -> Storage -> Volumes panel for the managed server, the status of this volume is shown as "OK", even after running storage snapshot specifications. Windows 2008 Storage Host Agent Extension None
    QCCR1D111727 Storex does not support VMWare hosts that have Virtual Machine Disk (VMDK) volumes created on Network File System (NFS) storage. Independent Storage Host Agent Extension Contact your Server Automation administrator.
    QCCR1D142746 Storage Visibility Automation does not support ESX Servers on the Storage Host Agent. Independent Storage Host Agent Extension None
    Bug ID: 159580 / QCCR1D70934 The SAV displays incorrect information after adding a zone to a fabric. The zone is not associated to the
    correct server/port/WWN.
    independent Storage Host Agent Extension None



    The SA-installed Oracle RDBMS modifies the /etc/sysconfig/selinux file and inserts the following entry for SELINUX regardless of whether a previous entry exists.

    #SAS Oracle parameters begin
    #SAS Oracle parameters end

    Linux Usability

    If multiple entries exist in the /etc/sysconfig/selinux file, only keep the entry that is shown in the description, but make sure that the value for SELINUX is 'disabled' or 'permissive', not 'enforcing'.


    QCCR1D150577 Cloning a powered-on VM running Windows on some earlier versions of VMware ESX/ESXi fails during the Guest Customization step.

    If you are:

    • Running a version of VMware before ESXi 4.1 Update 2 or ESXi 5.0 Update 1, and
    • the VM is running Windows, and
    • the VM has VMware guest tools installed, and
    • the VM is powered on, and
    • you try to clone the VM, then:
    The clone operation can fail in the Guest Customization step.

    This occurs because of a VMware problem that has been resolved in ESXi 4.1 Update 2 and ESXi 5.0 Update 1. For details, see the Resolved Issues listed in the VMware ESXi 4.1 Update 2 Release Notes or the VMware ESXi 5.0 Update 1 Release Notes.
    VMware vCenter, Windows Virtualization - VMware To resolve this issue, you can do either of the following:
    • Upgrade to a later version of VMware ESXi where this problem is fixed. For details, see the Resolved Issues listed in the VMware ESXi 4.1 Update 2 Release Notes or the VMware ESXi 5.0 Update 1 Release Notes.
    • Power off the VM before cloning it.
    QCCR1D141907 If you configured the number of cores per socket using the native vSphere client, and modify the number of virtual processors with a Modify VM job in SA, the CPUs might end up in an invalid configuration.  When you edit the CPU settings in the native vSphere client, this error, “Number of cores per socket cannot be greater than number of virtual CPUs” occurs when the configuration is invalid.

    The native vSphere client multiplies the number of virtual sockets by the number of cores per socket to determine the Total CPUs.  SA only discovers and sets the Total CPUs (from the Virtual Processors field). 
    Examples when the VM has 2 cores per socket: 

    • Set SA’s Virtual Processors to 8, there will be 4 virtual sockets and 8 total CPUs. 
    • Set SA’s Virtual Processors to 1, the number of virtual sockets will be 1 and that results in an invalid configuration.
    VMware vCenter Virtualization If the number of cores per socket for a VM is greater than 1, and you want to modify the CPUs:

    1. From SA, set the number of Virtual Processors as a strong multiple of the number of cores per socket.
    2. Or, use the native vSphere client to modify the CPUs.
    QCCR1D142816 HP-UX virtualization APX displays incorrect message when user tries to start a vpar. HP-UX HP-UX virtualization None
    QCCR1D153021 If you clone a Windows 2008 VM or deploy a VM from a Windows 2008 VM Template using static-to-static configuration, the source’s IP Address is not removed from the new VM and the gateway is not set.

    The problem occurs when:

    • Clone VM or Deploy VM from Template
    • The source is Windows 2008 32-bit or 64-bit
    • The source has a static IP address

    Although the source’s IP address is not removed, the new VM still works because it marks the correct IP address as preferred.

    Although the gateway is not set, the agent can still communicate with the core.  However, DNS will not work.

    VMware vCenter, Windows Server 2008 32-bit/64-bit Virtualization None.

    QCCR1D155406 When SA discovers SCVMM VMs or Templates that were already agent-managed, SA ends up with one agent-managed device record and one virtualization-managed device record, both for the same device. This occurs because device correlation does not work for SCVMM VMs or Templates.

    SCVMM does not discover the SMBIOS UUID of their VMs and Templates.  SA uses the SMBIOS UUID to correlate the newly discovered device or template with the agent-discovered SMBIOS UUID property. 

    Microsoft SCVMM Virtualization Backend Device correlation works when you install agents after discovery.

    Device correlation works when you do the following from SA:

    • Create VM with OS Build Plan
    • Convert VM to VM Template
    • Deploy VM from VM Template with Guest Customization
    It is possible to merge two device records using the com.opsware.server.serverService.merge function in twister.

    Your job fails with the following error:

    The host server or the Virtualization Service is not reachable. Check the network communication and retry the operation. Ensure server hosting Virtualization Service has SA agent installed.

    This may occur in several scenarios, here are a few examples:

    • The SCVMM server is down.
    • You have a large SCVMM inventory and you are running concurrent reload data jobs.
    • You perform Delete VM, Delete VM Template, or any power control operation on a large number of objects in one job.
    • You have many concurrent jobs running against the same SCVMM.
    The reason is that SA is unable to connect to the SCVMM server. Or, the maximum number of connections to the SCVMM server through the SA Agent has been reached.
    Microsoft SCVMM Virtualization Backend Check the following:

    • That the host server is running and has a valid network computer name.
    • The Virtualization Service is running, is DNS resolvable, and has proper network communication.

    Contact HP Support.

    QCCR1D157368/160408 Search with IP Address or Hostnames on Add Virtual Server screen does not list HP-UX machines. HP-UX HP-UX Virtualization None
    QCCR1D157587 When you migrate both host and storage for a VM in SCVMM, and you select a host in a Cluster (in SCVMM the Transfer Type is Cluster), then the settings for the Storage and Network steps are ignored. SA does not discover the Transfer Type property for the hosts.

    When you do a cluster migration in SCVMM, SCVMM does not offer the option to set additional migration parameters.

    Microsoft SCVMM Virtualization Backend None

    Web Services Data Access Engine

    QCCR1D112222 The Web Services Data Access Engine does not start and records the error:

    Could not reserve enough space for object heap in:

    The default maximum JVM heap size has been increased to 2560 MB, and as a result, the Web Services Data Access Engine (twist) does not start properly on Linux AS3 32-bit systems due to a two-gigabyte memory limit
    for a single process running on JVM on 32-bit systems.

    Platform: Red Hat Enterprise
    Linux AS3
    Web Services Data Access Engine (twist) Before upgrading, edit the file:

    and add the following entry:
    twist.mxMem=<memory size in Megabytes>

    The value must be 2000 megabytes or less.
    Example: twist.mxMem=1960m

    Work Load Manager (WLM)

    QCCRID163928 For recurring non-blocked WLM jobs, once the child job is run, SA determines if the parent job should expire by comparing the end date with the next fire date. The status of the parent job is updated to EXPIRED if the next fire date is beyond the end date. For recurring blocked WLM jobs, however, when the child job completes its run, SA does not determine the expiration of the parent job. If the approval notification for a BLOCKED job is not setup at all or setup incorrectly, the child job will remain in the BLOCKED state and no computation will be made to determine the status of the parent job.

    Independent Work Load Manager None

    Jobs remain with a status of Active, even though their associated tasks show a status of Success.

    This known issue is applicable only to Workload Manager framework-based jobs, such as V12n or iLO.

    Independent Work Load Manager This issue occurs only in multi-core mesh installations where the SA Jobs are being approved using Operations Orchestration on all the cores of the mesh. To work around this issue, setup OO workflow only on the primary core of the mesh.

    Back to the Table of Contents

    Fixed Issues

    The Fixed Issues table includes issues that:

    The table lists issues first by subsystem, then numerically within each subsystem.

    This section describes Fixed issues for SA 10.0. The table lists issues first alphabetically by Subsystem, then numerically within each subsystem.


    QCCR1D Symptom/Description Platform

    Agent Deployment

    QCCR1D100660 Windows ADT login fails for administrators that are not user Administrator due to security controls for Windows UAC. Windows Server 2008 using UAC
    QCCR1D151512 The hosts scan results should provide information on unreachable hosts.

    Result: Unreachable (not responding) hosts now show up in the scan results list with an appropriate icon.

    QCCR1D155534 Hosts scan fails with no error message when opsw.GWAddress is not set correctly

    Result: An error dialog describing the error is now displayed.

    Application Deployment

    QCCR1D133132 The Application Deployment Manager now installs correctly on an Oracle RAC instance, regardless of the Oracle TNS entry line format.

    QCCR1D138678 Target groups are now consistently displayed properly in the Application Deployment Manager. Independent
    QCCR1D142009 The following special variables are now available: Server IP Address, Deploy Server IP Addresses, and Server IP Addresses for Tier <name of the tier>.

    QCCR1D142223 You can now specify a Base Directory for Configuration File type components and Code type components. Independent
    QCCR1D142852 The Manage Applications dialog will now allow you to select only one application at a time. Independent
    QCCR1D158723 The Application Deployment Manager no longer reports an error when a user who has the required permissions changes the status of an environment within a lifecycle.



    QCCR1D160936/161406 The script goes into an infinite loop on external socket close (causing the CPU usage to boost to 100%).
    QCCR1D142069/161565 Recurring Scheduled Extensible Discovery Job does not update servers when executed against device groups. Independent

    DCML Exchange Tool

    QCCR1D137633/152515 DET full import failed. An error is thrown because there is a request to create a folder in the parent directory (FolderRef:-1), which is an invalid reference.

    The following error message is displayed:
    SEVERE: Importing Folder: ..... Message: A Persistence layer error occurred while trying to read an object.
    Details: The object (FolderRef:-1) was not found.
    com.opsware.common.ReadException: A Persistence layer error occurred while trying to read an object.
    Details: The object (FolderRef:-1) was not found.

    QCCR1D142804/154916 DET/CBT fails to overwrite the configuration file when it has the option and the /tmp is located in a different file system.



    QCCR1D147740 If you have a dollar sign ($) in a parameter, you cannot upgrade because dollar signs in parameters are not supported.



    QCCR1D121448 When you run the dba_jobs script in the database, the following type of error is displayed:
    8412:ORA-06512: at "SYS.DBMS_STATS", line 21271
    8413:ORA-06512: at line 1
    8433:ORA-12012: error on auto execute of job 68
    8434:ORA-20003: Unable to gather system statistics

    OS Provisioning

    QCCR1D103362 After a server is provisioned using a Red Hat DHCP-LESS image in the VLAN, attempting to reprovision the server causes the server to reboot, after which the reprovision process fails at the Anaconda Configure TCP/IP window, prompting for network information. Independent
    QCCR1D103602 After you choose Windows as the OS Family, you cannot use the Manage Boot Client (MBC) to create winpexx-ogfs server records in the MBC Single Form because winpe32-ogfs and winpe64-ogfs image types are not displayed in the PXE image drop-down box. Windows
    QCCR1D116039 I18N: Run OSBP with I18N ZIP Install PATH failed. Independent
    QCCR1D123031 Reprovisioning for Red Hat Enterprise Linux 6 with the ext4 file system is not yet supported. Linux
    QCCR1D129619 ESXi DHCP-LESS: DNS Search Domain was not set via the DHCP-LESS value VMware ESXi 4.1

    OS sequence provisioning for SuSE Linux 11 x64 on HP ProLiant DL385G5 fails randomly.

    SuSE Linux
    QCCR1D146201 Run OS Build Plan (OSBP) does not check the folder execute permission for the library folder where the selected OSBP resides. Independent

    In the ESXi 4.1 kickstart settings file, the specified network device is ignored, causing installation failure.

    VMware ESXi 4.1

    Patch Management - Windows

    QCCR1D105098 Automatically installing recommended Microsoft patches Q934041 (2000) and Q924883 (MS07-014) fails. Manually installing the patches results in a Non-Compliant server status and a dialog that is displayed:

    Update has already been applied or is included in an update that has already been applied.
    QCCR1D108451 Windows Patch 944036 (installer for IE 8) reports install failure (and returns a non-zero exit code) on Windows Server 2008 x64 managed servers, even though the patch is installed correctly. Subsequent patch and compliance scans will indicate the patch is installed and compliant. Windows Server 2008 x64
    QCCR1D110257 If you try to install the March 2010 (or later) MBSA patch database, and then attempt to install MS10-015 (KB977165) and MS10-021 (KB979683) on to a Windows Server 2008 x86 using a Windows Patch policy, the Patch install job results will incorrectly indicate success. After a patch compliance scan, SA will still report the patches as recommended for the server, and the server will be listed as non-compliant. Windows Server 2008 x86
    QCCR1D111397 After remediating the vendor recommended policy on a Windows managed server, the server's recommended patch list shows additional patches that need to be installed, requiring the vendor recommended policy to be remediated again. This sometimes occurs when older patches introduce problems that newer patches already fixed. Windows
    QCCR1D136373 Windows systems that use .cab files for remediation time out during the installation process for a vendor recommended policy. When installing multiple .cab files without reboot, calls to the Windows API UpdateSearcher.Search do not return in a timely manner, causing the timeout. Windows
    QCCR1D140751 Attempts to install the Windows KB929300 multi-binary patch without including all the binaries in the SA patch policy remediation job will fail with the following error and stack trace:

    The operation to install or uninstall software failed.Execution error: Traceback (most recent call last):
    File ".\base\", line 136, in evaluator
    File "", line 7177, in ?
    File "", line 7171, in main
    File "", line 6872, in action
    File "", line 6346, in actionImpl
    File "", line 0, in ?
    File "", line 5044, in install
    File "", line 4987, in getResult
    TypeError: int() argument must be a string or a number

    Note: In this example for KB929300, at least 4 binaries were missing from the job.

    Python API Access

    QCCR1D164436 OPSWpytwist dialog causes timeout during remediations on some W2K8 Windows servers, and the following error is displayed:

    Error 1935 An error occurred during the installation of assembly <server information>. Please refer to Help and Support for more information.


    Software Repository Accelerator

    QCCR1D150913 Software Repository Accelerator is able to connect through a satellite gateway. Independent

    SA Client (Framework)

    QCCR1D112476 JRex is not fully W3C compatible, causing client executable codes failures. Independent
    QCCR1D115211 Launching the SA Client under Windows Vista or Windows 7 causes flickering/redrawing of the screen. Windows Vista, Windows 7
    QCCR1D115403 The SA Client freezes when any of the following items is launched for the first time: Application Deployment, Web Automation Platform Extension (APX) processes (including OS Build Plans and HP Virtualization), and reports. Windows

    SA/SAR Reports

    QCCR1D107293 Scheduled reports exported to .xls do not display charts or graphs (“Unsupported Image error” is displayed
    instead). However, tables are sent correctly. Graphs are not visible in the .xls file, but the report should not display empty image blocks.

    SE Connector

    QCCR1D105778 When a server on which SE Connector is running is directly deactivated and deleted, selecting Administration -> Storage Scanners -> <The names of the SE Scanner on "Host"> shows stale entries of Storage scanners in the Scanner panel. The stale entries count will increase, depending on how many times the server is deactivated and deleted from the core. Independent

    Software Management

    QCCR1D132314 Allow review archived version(s) of AppConfig prior to rollback. Independent
    QCCR1D136284 Allow user name and password as open plain text. Independent
    QCCR1D42659 Cannot select packages of type "OS Independent" when trying to (un)install software. Independent
    QCCR1D149937 Allow support for RPM rollback job blocking. Independent
    QCCR1D150135 There is a multi-core (GIL) scalability bottleneck in the yum aggregate XML repo generator. Independent
    QCCR1D150981 Allow application configuration preview during software-policy installation. Independent
    QCCR1D152889 OPSWyum does not recognize that an update is available for a package if the new version has a different architecture than the installed one.

    Starting with 9.14, the yum plugin is the preferred tool for the analysis phase of remediation jobs. Please refer to the section Remediate RPM Packages Using the Native YUM in these release notes for more information.

    QCCR1D152900 Unable to attach a server to a software policy without immediate remediation. Solaris
    QCCR1D158750 Unable to attach software policies to a device group using the device group browser. Independent
    QCCR1D159620 The following error is occasionally seen when processing jobs:

    "KeyError: 'special_reboot_dict'"

    QCCR1D160774 Unable to add items to a policy with read-only permissions on a library folder. Users with read access to the folder should be able to add the items when browsing by folders. Independent
    QCCR1D160823 RHN import failing with unexpected error: KeyError: 'channel_name'. Independent
    QCCR1D161094 You cannot add items to a software policy without write permissions on the corresponding feature, if you are attempting to add the item by navigating the directory tree.

    QCCR1D161095 Unnecessary parameter (<all_host_progress_dic>) passed from a parent session to a child session during remediation, causing scalability bottleneck..

    QCCR1D161265 When attempting to remediate an RPM package whose metadata XML contains international characters, the following error is displayed:
    "The metadata needed to install this package is missing...".

    Red Hat Linux Server
    QCCR1D161917 On 64-bit systems, the ISM Tool pre/post install script path does not use %ProgramFiles(x86)% when using --registerAppScripts.


    Software Repository

    QCCR1D131751 HP Server Automation 9.10 configurations that use a Solaris machine as the Network File System (NFS) server may encounter unexpected behavior and unreliable performance. Due to known instability issues with Solaris NFS, this configuration should be avoided. The recommended configuration is a Linux NFS server, which works reliably with either Solaris or Linux clients. Solaris
    QCCR1D152739 During Secondary Core Model Repository installation, the following warnings are seen in the installer log:

    ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."FIBREFABRICELEMENTS" created with compilation warnings
    ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."AGENTPACKAGE" created with compilation warnings
    ORA-39082: Object type ALTER_PACKAGE_SPEC:"TRUTH"."STORAGEDEVICE" created with compilation warnings
    ORA-39082: Object type ALTER_PROCEDURE:"TRUTH"."RESOLVEDUPLICATEWWN" created with compilation warnings

    Red Hat Linux Server 5

    Storage Host Agent Extension

    Bug ID: 159580 / QCCR1D 70934 The SAV displays incorrect information after adding a zone to a fabric. The zone is not associated to the correct server/port/WWN. independent
    Bug ID: 164951 / QCCR1D 76305 The multipath information is not reported correctly for a server that has HP-UX 11iv2 OS installed and Veritas DMP managing the multipathing in the SA Client. The SNIA library does not support HBA_GetFcpTargetMappingsV2r. HP-UX 11iv2


    QCCR1D142939 Unclear when to use script: windows_2008_R2_fix_script.pyc.



    QCCR1D137328 Only 1, 2, or 4 CPUs available to guest VM while modifying. VMware vCenter
    QCCR1D159589 ESXi reports the number of CPU cores instead of physical CPUs VMware vCenter
    QCCR1D159596 /159598  Cloning VM fails for Windows due to 10-minute timeout. Windows

    Web Services Data Access Engine

    QCCR1D111039 An out-of-memory error is encountered in the Web Services Data Access Engine Red Hat Linux/Solaris

    Back to the table of contents

    Documentation Information

    This section discusses documentation information for this release.

    Note: The most up-to-date information for this release can be found in the latest version of the release notes, guides, and white papers, located at:

    Documents Relevant to This Release

    In addition to the 10.0 guides on the Self Solve website, the following white papers and guides are relevant to this release:

    Note: Some of these guides and white papers were released in earlier patches, but are still relevant to SA 10.0.

    Back to the Table of Contents

    HP Software Support

    This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

    HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

    To access the Self-Solve knowledge base, visit the Self-Solve knowledge search home page.

    Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

    To register for an HP Passport ID, go to: HP Passport Registration.

    Legal Notices



    The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

    The information contained herein is subject to change without notice.

    Restricted Rights Legend

    Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

    Copyright Notices

    © Copyright 2000-2013 Hewlett-Packard Development Company, L.P.

    Trademark Notices

    Adobe® is a trademark of Adobe Systems Incorporated.
    Intel® and Itanium® are trademarks of Intel Corporation in the U.S. and other countries.
    Microsoft®, Windows®‚ Windows® XP are U.S. registered trademarks of Microsoft Corporation.
    Oracle and Java are registered trademarks of Oracle and/or its affiliates.
    UNIX® is a registered trademark of The Open Group.

    Release-Notes Updates

    New Publication Date Change
    May 20, 2013 Original release notes bundled with SA software.
    June 3, 2013 Added numerous changes to issues tables, and what's new sections.
    June 8, 2013 Added information about upgrading from 9.x/9.0x to 10.x in the installation section.

    To check for recent updates or to verify that you are using the most recent edition of a document, go to:

    This site requires that you register for an HP Passport and sign in.
    Or click the New users - please register link on the HP Passport login page. You will also receive updated or new editions if you subscribe to the appropriate product support service.

    Contact your HP sales representative for details.

    Back to the Table of Contents