NetIQ Secure Configuration Manager

Version 5.9 Service Pack 1

Release Notes

Date Published: June 2013

 
 

 

This service pack improves usability and resolves several previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure our products meet all your needs. You can post feedback in the Secure Configuration Manager forum on Qmunity, our community Web site that also includes product notifications, blogs, and product user groups.

For more information about this release and for the latest Release Notes, see the Secure Configuration Manager Documentation web site. To download this product, see the Secure Configuration Manager Service Packs Web site.

What's New?

The following outline the key features and functions provided by this version, as well as issues resolved in this release:

Operating System Support

You can install the Secure Configuration Manager console and Core Services components on a computer running Windows Server 2012. You can also install the console on a computer running Windows 8 (32-bit and 64-bit).

Additional Agent Support

This service pack adds support for NetIQ Secure Configuration Manager Windows Agent 5.9 Service Pack 1 (Windows agent). It also includes Hotfix 73317, which adds and updates objects and attributes in the UNIX namespace to support NetIQ Secure Configuration Manager UNIX Agent 7.2 (UNIX agent), at a minimum.

For detailed information on these agents, see the respective release notes on the Secure Configuration Manager Documentation Web site. For more information about the hotfix, see Previous Releases.

Additional Windows Endpoints

Secure Configuration Manager adds support for the following Windows endpoint types:

  • Windows Server 2012
  • Windows 8
  • SQL Server 2012

Secure Configuration Manager places SQL Server 2012 endpoints in the MS SQL Server category in the console.

Enhancements and Software Fixes

Secure Configuration Manager 5.9 Service Pack 1 includes software fixes that resolve several previous issues. For the list of software fixes and enhancements in previous releases, see Previous Releases.

Improved Information about an Agent's Last Activity

This service pack modifies the way that Secure Configuration Manager reports the last activity of a security agent. The Last Activity field in IT Assets > Agents now represents only the last successful communication:

  • Successful agent registration
  • Successful heartbeat response
  • Successful response to a query, such as for a security check, policy template, or scheduled job

Previously, Secure Configuration Manager reported every attempted communication with the agent, regardless of success or failure. With this improvement, you can use Last Activity to verify the status of an agent.

Adds an Attribute to the UNIX Agent Properties

The service pack adds an attribute to the UNIX Agent Properties window: Number of CPUs. Secure Configuration Manager populates this field when you run the Discovery - System Details for the UNIX Endpoint security check. To ensure that you have the latest version of the check, use the AutoSync update service. (ENG323011)

Provides Additional Options for Scheduled Jobs

This release provides the following improvements for scheduled jobs:

  • You can now schedule reports to run at specific hourly intervals on specific days of the week and month. For example, you can schedule a policy template to run every three hours, Monday through Friday. (ENG313584)
  • The Scheduled Jobs Wizard now allows you to modify the report options, such as the page layout and whether to include only the violations listed in the policy template results. The Run Policy Template Wizard and the Full Report Options in the Report Viewer already allowed you to set the report options for the policy template. When you modify the report options in any of these wizards, Secure Configuration Manager applies the changes to all runs of the specified policy template. (ENG325667, ENG325666)

Hide Exceptions in a Distributed Report

If a policy template or security check report contains exceptions, Secure Configuration Manager now allows you to hide the excepted rows when you distribute or export the report. This improvement applies to reports in both .pdf and .xml format. Reports exported or distributed in other formats already hide excepted rows when required. (ENG321607)

Administrators Can Create Delta Reports that Include Reports Run by Other Users

The delta reporting feature allows you to observe changes in an endpoint's results for a policy template or security check report over time. This version of Secure Configuration Manager allows members of the Administrators console role to create a delta report that compares the reports run by other users. Previously, console accounts with the Administrators role could view reports by other users but not include those reports in a delta comparison.

Delta reporting also allows you to compare results of a known, good endpoint against those of another endpoint for the same template or check run. For more information about delta reports, see the Help and the User Guide for NetIQ Secure Configuration Manager. (ENG297189)

Adds Security Check Name to the Policy Template Preview File

The Policy Template - Print Preview file now lists the security check name associated with each description of the check. To see the preview, right-click a policy template in Security Knowledge and then click Print. (ENG325613)

Temporarily Enables WUS when Running Security Checks for Patch Assessment

When you run security checks that assess the patch-level status of your Windows endpoints, the Windows agent needs Windows Update or Automatic Update services enabled on the endpoint to complete the query. If the Windows Update Service (WUS) is disabled, the agent temporarily enables WUS while running the check, and then disables the service upon completing the query. For more information, see the Release Notes for NetIQ Secure Configuration Manager Windows Agent 5.9 Service Pack 1. ENG329077

Normalizes Names of Windows Service Accounts in Reports

Issue:

When you run security checks that get the account name for a Windows service, the reported names vary, depending on which attribute in the Windows namespace that the check uses in the query. For example, some security checks might report the account name as NT AUTHORITY\LocalSystem or .\LocalSystem. With this type of variance in the names, the reports do not enable users to easily correlate permissions granted to users or groups with the service account. (ENG251149)

Fix:

Secure Configuration Manager now normalizes the names of service accounts to reduce variations in the security check or policy template report. For example, if the Windows agent reports NT AUTHORITY\LocalSystem, Secure Configuration Manager changes the account name to LocalSystem. Secure Configuration Manager also changes account@domain to domain\account. This fix affects reports that include the following security checks.

  • Local - High risk services running
  • Service status and permissions
  • Service status and permissions setting minimum
  • SQL Server account group membership
  • SQLServerAgent account

The checks have not changed. However, the reported results might be different. If you use the All Services baseline for your Windows systems, NetIQ recommends that you reestablish the baseline to incorporate the modified account names. You should also review all scheduled delta reports that include the affected security checks, such as delta reports for policy templates. Run the check or template, and then use the most recent run as the base report. For more information and a list of affected policy templates, see NetIQ Knowledge Base article 7011763.

Filter Window in the Security Check Wizard Does Not Allow Incomplete Custom Check Filter Values

The Security Check wizard now provides controls that improve your ability to create, edit, and delete parameter filters. For example, one option enables you to delete an unfinished filter row. Another option lets you accept the edits and move to the next filter row or click Next to continue to the next window in the wizard. The Filter window displays the new options above Attribute Description. (ENG292940)

Cannot Report Some Tasks Scheduled on Windows Vista or Windows Server 2008

Secure Configuration Manager now collects scheduled task information when the tasks are created by the Task Scheduler on Windows Vista or Windows Server 2008. (ENG255154)

Cannot Use SSL Algorithms for Communication between Core Services and the Database When You Enable FIPS Mode

Issue:

Core Services cannot connect to the Secure Configuration Manager database after you enable FIPS mode and you use Secure Socket Layer (SSL) algorithms for communication. (ENG316972)

Fix:

You can use SSL algorithms for communication between Core Services and the database after you enable FIPS mode if the database runs on the following software:

  • Microsoft SQL Server 2008 Service Pack 3 with the associated cumulative update package
  • Microsoft SQL Server 2008 R2 Service Pack 2

Window Lists Agent Properties in an Inconsistent Order

Issue:

The Agent Component Properties window does not list the properties of a Windows agent in a consistent order, even when the agent computers are similar. The listed order depends on whether Core Services registers the agent automatically or you register the agent manually. (ENG325967)

Fix:

The Agent Component Properties window now lists the properties in a consistent order, regardless of the registration method.

Cannot Import an Edited or Custom Policy Template

Issue:

When you export a policy template that contains built-in NetIQ security checks, Secure Configuration Manager fails to re-import the template or any templates created from the exported template. This issue occurs because the imported template contains security checks that already exist in the Secure Configuration Manager database. The database does not allow duplicate security checks. (ENG321231)

Fix:

When you import an edited policy template or a template that you previously exported, Secure Configuration Manager parses the content for <CHECKDEFINITIONS> elements that include existing NetIQ security checks. The check definition element identifies security checks that can be used for multiple, unique check instances in a policy template. If a check definition already exists in the database, Secure Configuration Manager does not import that check with the policy template file. When you run the imported template, Secure Configuration Manager uses the existing security check.

Scheduled Jobs Stop Running when You Delete a Targeted Endpoint

Issue:

When you create a scheduled job to run against specific endpoints and then delete one of the endpoints from your asset map, the scheduled job stops running. This issue occurs only when you target individual endpoints rather than targeting a managed group of endpoints. (ENG283755)

Fix:

Secure Configuration Manager continues to run scheduled jobs after you remove one or more of the targeted endpoints from the asset map. However, NetIQ recommends that your scheduled jobs target managed groups rather than individual endpoints. By using groups, you can more easily organize, identify, and manage the endpoints that you want to assess.

Cannot Export Data View Results when the First Endpoint Has No Data

Issue:

If the first of several endpoints successfully completes the security check or policy template but no data matches the query criteria, Secure Configuration Manager fails to export the Data View results. Instead, you receive the following error message: The exporting will not continue since the Data View is empty. (ENG325485, ENG326205)

Fix:

Secure Configuration Manager can export the Data View report for a security check or policy template, regardless whether the first endpoint's results contain any data.

Maximum Log Size Reverts to Default Value after Upgrading Core Services

Issue:

When you upgrade Core Services, the setting for the maximum size of the core.log file reverts to the default value of 2 MB. (ENG325187)

Fix:

Before upgrading Secure Configuration Manager, the setup program copies the existing log.properties file to a temporary folder to retain your settings. Upon completing the upgrade process, the setup program restores the file to the Core Services/etc folder.

Using Special Characters Affects Windows Agent Deployment

Issue:

Secure Configuration Manager does not deploy the Windows agent to a remote computer after you specify an installation path that includes a special character such as !*#)_%;. (ENG323196)

Fix:

Secure Configuration Manager no longer allows you to specify an installation path that includes a special character such as !*#)_%;.

Return to Top

System Requirements

This service pack includes a full version of Secure Configuration Manager 5.9. For detailed information on hardware requirements and supported operating systems for version 5.9, see the Installation Guide for NetIQ Secure Configuration Manager.

Also, when determining the system requirements for applying this service pack to a previous version, NetIQ Corporation recommends that you review the following considerations:

  • You can use this service pack to upgrade previous versions of Secure Configuration Manager. For more information, see Installing This Version.
  • This service pack installs NetIQ Secure Configuration Manager Windows Agent 5.9 Service Pack 1 on the Core Services computer. To monitor SQL Server 2012, Windows Server 2012, or Windows 8 endpoints, your agent computers must have Windows Agent 5.9 Service Pack 1. For more information about the service pack, see the Secure Configuration Manager Service Packs Web site.
  • You must install this service pack to use Secure Configuration Manager Security Windows Agent 5.9 Service Pack 1 as a deployment agent.
  • To use the updated objects and attributes in the UNIX namespace, your agent computers must have NetIQ Secure Configuration Manager UNIX Agent 7.2, at a minimum. For more information about updating your UNIX agents, see the Secure Configuration Manager Upgrades Web site.

For the most recently updated list of supported application versions, see the Secure Configuration Manager Technical Information page.

Return to Top

Installing This Version

NetIQ Corporation recommends that you review the following considerations before installing or upgrading to this version:

  • This service pack includes a full version of Secure Configuration Manager 5.9. You can install this version in a clean environment. The Installation Guide for NetIQ Secure Configuration Manager provides information about planning for, installing, and upgrading Secure Configuration Manager. For more information about version 5.9, see the Release Notes.
  • You can apply this service pack to the following previous versions of Secure Configuration Manager:

    • 5.9
    • 5.8 Service Pack 2
  • You must install this service pack on the Core Services and console computers. The installation program automatically connects to and updates the database through Core Services. For more information about installation or to apply this service pack to older versions of Secure Configuration Manager, contact Technical Support.
  • Before upgrading to this version, make a note of the configuration settings in the console. The installation process resets these settings to their default values. To review the settings, complete the following steps:

    1. In the console, click Tools > Options.
    2. Use the screenshot feature in the operating system or make a note of the values on the Settings and Other tabs.
    3. After upgrading to this version, update the settings to their previous values.
  • After you install this version, you should ensure that the normalization of service account names does not affect your data results:
    • Reestablish the All Services baseline to incorporate the modified account names for Windows services.
    • Review all scheduled delta reports that include the following security checks, including delta reports for policy templates:
      • Local - High risk services running
      • Service status and permissions
      • Service status and permissions setting minimum
      • SQL Server account group membership
      • SQL Server Agent account
    • Run the checks or templates, and then use the most recent runs as the base report. For more information and a list of affected policy templates, see NetIQ Knowledge Base article 7011763.
  • To upgrade your version 5.9 Windows agents, NetIQ recommends that you use the deployment feature in the Secure Configuration Manager console.
  • For more information about installing and upgrading Windows agents to this version, see the Release Notes for NetIQ Secure Configuration Manager Windows Agent 5.9 Service Pack 1.
  • You must install the Secure Configuration Manager database and its associated files on an uncompressed drive. Microsoft does not support SQL Server databases on compressed volumes.

Return to Top

Verifying the Installation

Complete the following steps to verify that the installation was successful.

To check the installed version:

  1. Log on to the Secure Configuration Manager console.
  2. On the Help menu, click About NetIQ Secure Configuration Manager.
  3. Verify that the version is 5.9.[build number].1000.

Return to Top

Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.

Upgrade Process Resets Console Settings to Default Values

When you upgrade to this version, the installation process resets the configuration settings for the console. For more information about saving your settings before upgrading, see Installing this Version. (ENG328791)

Filtered Lists in the Security Checkup Results Viewer Do Not Save Custom Policy Templates with Commas in Their Names

The Security Checkup Results Viewer allows you to create a filtered list of custom policy templates, including templates that have a comma (,) in their name. However, after you save and reopen the filtered list, the list does not include the policy templates with commas. (ENG322291)

Using Special Characters Affects Returned Data

Using special characters, such as !*#)_%, to name user-defined items can adversely affect returned data. The following issues can occur:

  • When you create a policy template, the Asset Compliance View does not include data for the policy template. (ENG268091)
  • When you create a policy template, the Security Checkup Results Viewer shows incorrect compliance status for the policy template. (ENG262663)
  • When you create a policy template, delta reports run against the policy template include unhandled exception errors. (ENG262649)
  • When you create a user-defined folder in Job Queues > My Reports, Secure Configuration Manager does not support the use of special characters for the folder name. (ENG262100)
  • When you create custom security checks, Secure Configuration Manager does not support the use of special characters in the fields for those checks. (ENG137515)
  • When an organizational unit (OU) name contains special characters, the following Active Directory security checks do not return data for that OU: AD Number of user accounts by OU and AD Number of groups by group. (ENG260966)

Wildcards Not Supported for Custom Check Filters

When you create a filter for a custom security check, Secure Configuration Manager does not support the use of wildcards as filter values. (DOC182820)

Only Console Administrators Can Edit and Delete Custom Tasks and Task Suites

Secure Configuration Manager allows only console users with administrator permissions to edit or delete a custom task or task suite. Users without administrator permissions can still create tasks and task suites. (ENG321120)

Exceptions Wizard Might List More Security Checks Than You Can Except

The Select Check window in the Exceptions wizard might display more security checks than you can apply exceptions against. This issue occurs when you run a policy template containing checks for multiple platforms, such as Windows and UNIX, and you attempt to apply an exception against a group of endpoints. (ENG318704)

Process Namespace Object Reports Only One Instance of a Process

When you use the Process object in the Windows namespace to search for processes and the computer has multiple instances of a process with the same name, Secure Configuration Manager reports only one instance of that process. This issue occurs on computers running Windows XP Service Pack 2 and Windows Server 2003 Service Pack 2 operating systems. (ENG241828)

Some Ports Not Reported by Port Object

The Port object in the Windows namespace does not return data for all existing ports when the managed system has more than one IP address and Secure Configuration Manager communicates with each IP address through the same port. The Port object returns data for only one of the ports because the Port object places the port number in the name field and then reports only one instance of that name. (ENG257340)

Password Object is Not Supported on Microsoft Windows 64-bit Operating Systems

The Password object in the Windows namespace uses methods that are not supported on 64-bit computers to obtain password hashes. Security checks using this object do not return valid results on 64-bit computers. (DOC243481)

Custom Check Namespace Changes Might Cause Issues

If you wrote custom security checks in Secure Configuration Manager 5.6, you might need to modify those checks to work properly in this version of the product due to namespace changes.

Changing an IP Address Affects SQL Server and Core Services

If you change the IP address on a system, you might need to restart SQL Server. If you restart SQL Server, you must then restart Core Services.

Database Connection Difficulty

If you are having difficulty connecting to the Secure Configuration Manager database from the console, create a server alias in the SQL Server Client Network Utility for the database and set up the alias to use the TCP/IP network library. (ENG123939)

Aliased Security Check Exceptions Inconsistent

Policy templates can use an aliased instance of a security check to check different parameters of an endpoint. When exceptions are created and approved for policy templates that use aliases, application of the exceptions can be inconsistent. (ENG236185)

Data Caching Turned Off for Active Directory Objects by Default

When you add a custom attribute from an extended Active Directory (AD) schema, that attribute might not be added to the data cache, and will return void for a field that actually contains valid data. Therefore, to ensure the data validity of your security checkup reports, Secure Configuration Manager is delivered with caching turned off for AD objects. In extremely large AD environments, the lack of caching might cause an increase in the processing time of AD-specific reports, but this precaution ensures the validity of those reports. For more information about caching options, contact NetIQ Technical Support. (DOC236909)

Deleting Non-Mandatory Attribute String Might Cause Inaccurate Data

Active Directory user and group reports might return inaccurate data if a user deletes a non-mandatory string attribute in Active Directory. If a non-mandatory string attribute is deleted, the agent cache does not reflect the change in Active Directory. (DOC184047)

Latest Version of Scheduled Task Suites Does Not Run

If you schedule a task suite, and then edit the task suite after you schedule it, Secure Configuration Manager runs the originally scheduled task suite instead of the latest version. (ENG136763)

Canceling Jobs for Windows Agents Might Cause Issues

When you cancel a currently running job for a Windows agent, any process for the Windows agent that is actively running might not stop.

Console Might Not Exit Gracefully when Database Connection is Lost

When the Secure Configuration Manager console loses its database connection, the console might not exit gracefully.

Policy Template Requires NetIQ Group Policy Administrator or Group Policy Objects

The AD Computer Analysis policy template can return data only in an environment with NetIQ Group Policy Administrator or Group Policy Objects in place. (DOC228702)

Console Might Take A Long Time to Import and Display Policy Templates with a Large Volume of Checks

When you import and attempt to view a policy template that contains a large volume of security checks, the console might require extra time to respond. For example, a policy template with more than 1,000 security checks might require more than five minutes to import. (ENG317381)

Scheduled Jobs Do Not Run At Expected Times in a Distributed Environment

When you use Secure Configuration Manager in an environment distributed across multiple time zones, scheduled jobs might not run or might run at a time other than the scheduled hour. This issue occurs because of the discrepancy between the time zones for the Core Services computer, the database computer, and the console computers. For example, a console user in London schedules a job to run at 4 a.m., with the assumption that the job runs according to Greenwich Mean Time. However, the Core Services computer in New York City runs the job at 4 a.m. Eastern Daylight Time, which is five hours later than the user planned. (ENG321656)

Might Need to Register iSeries Agents Multiple Times

When you register an existing or new agent for NetIQ Security Solutions for iSeries with Core Services, you might need to register the agent more than once before Core Services updates the registration status. This issue occurs because the registration process initiates a security check that verifies information about the agent and its host computer. The security check starts the PSEAGENT job, but does not stop the job. When you re-register the agent, the job PSEAGENT stops and Core Services verifies agent registration. (ENG323220)

Some Components Cannot be Installed in a FIPS-Enabled Environment or Function on a FIPS-Enabled Computer

Issue:

The following software cannot be installed or function on a computer that has FIPS mode enabled:

  • Components for the NetIQ® Security and Compliance Dashboard 1.1 (the Dashboard)
  • NetIQ Aegis Adapter for NetIQ Secure Configuration Manager 2.0 (the Aegis adapter)

Also, the Dashboard installation program cannot connect to Core Services if you enable the FIPS option in the Core Services Configuration Utility or on the Core Services computer. (ENG323071)

Workaround:

Disable FIPS mode on the Dashboard component and Aegis adapter computers, on the Core Services computer, and in the Core Services Configuration Utility. After installing the Dashboard and Aegis adapter, you can enable FIPS mode on the Core Services computer. However, you cannot enable FIPS mode on the computers that support Dashboard components. Also, if you have a Windows agent installed on the same computer as a Dashboard component, the agent cannot be configured for FIPS-compliant communication.

Managing IIS Endpoints with Windows Server 2003 Agent Computers Might Cause Issues

Issue:

When you run security checks for Internet Information Services (IIS) endpoints installed on Windows Server 2003 agent computers, a memory leak might occur if the BITS server extensions are installed on the agent computer. This is a known Microsoft issue. (DOC182866)

Workaround:

Use a Windows XP agent computer to manage IIS endpoints.

Password Policy Changes Do Not Update When Connecting Multiple Core Services to the Same Database

Issue:

When you have two or more Core Services computers connecting to the same database and you change the password policy on one Core Services computer, Secure Configuration Manager does not automatically update the password policy on the other Core Services computer. (ENG292025)

Workaround:

When you update the password policy on a Core Services computer connected to the same database as other computers, restart all other Core Services computers connected to the database.

Some Internet Browsers Display Logon Fields for the Results Viewer in an Odd Location

Issue:

When you use Chrome, Mozilla, or Internet Explorer version 9 or 10 Internet browsers to log on to the Security Checkup Results Viewer, the logon fields appear toward the top of the window and obscure product information. This display issue does not affect functionality. (ENG322282)

Workaround:

You can continue to log on with the appropriate credentials. NetIQ Corporation recommends using Microsoft Internet Explorer for the Results Viewer. You must enable Compatibility View for Internet Explorer versions 9 and 10.

Additional Folder Installed in the Root Directory on the Core Services Computer

Issue:

In addition to the files installed in the Program Files folder, the installation program installs an SCMNSS folder in the root directory on the Core Services computer. When you use Secure Configuration Manager in a FIPS-enabled environment, the folder and its files can be deleted. (DOC322228)

Workaround:

Set permissions to prevent users from removing the SCMNSS folder and its files. Secure Configuration Manager requires these files for functionality with Java software.

Cannot Use WordPad to View a List Exported in .rtf Format

Issue:

When you export a list containing information that the console displays as a table to an .rtf file, WordPad cannot display the table in a format that is easily readable. For example, the console displays the Audit History and security check information in table format. (ENG322147)

Workaround:

Open the .rtf file in Microsoft Word. Alternatively, export the list in a different format, such as .xls or .txt.

Cannot Uninstall Secure Configuration Manager from a Drive Other than C:

Issue:

When you install Secure Configuration Manager components in a location other than the C: drive, you cannot uninstall or remove the components or their related files. This problem occurs because the un-installation process cannot find the appropriate log files on your C: drive. (ENG326232)

Workaround:

If you cannot remove or uninstall Secure Configuration Manager components, NetIQ recommends that you complete the following steps:

  1. In the C:\Program Files (x86) folder, create the following folders:
    • NetIQ\Secure Configuration Manager\Uninstall\Core Services
    • NetIQ\Secure Configuration Manager\Uninstall\VSM
  2. Copy the VSSINSTALL.log file from the Core Services folder on drive where you installed Secure Configuration Manager to the folder you created on the C: drive.
  3. Copy the VSMINSTALL.log file from the VSM folder on drive where you installed Secure Configuration Manager to the folder you created on the C: drive.
  4. On the drive where you installed Secure Configuration Manager, run the UNWISE.exe file in each of the respective component's folder. You might need to specify the path to the new folders on the C: drive.

Some Asset Compliance View Reports Fail to Display All Data Columns on the Same Page

Issue:

When you print, export, or email information in .pdf or .rtf format from the Asset Compliance View, the default page width cannot display all columns of data. Also, the report Preview does not display the results in an easily readable format, regardless of the exported format. (ENG328797)

Workaround:

In the report's Preview window, change the page setup to Landscape orientation.

Return to Top

Additions to Documentation

This service pack does not provide updated guides for Secure Configuration Manager or the Windows agent. The following topics describe additions and modifications to the installation, user, and Windows agent guides.

For the most recent documentation, see the NetIQ Secure Configuration Manager Documentation Web site. For more information about supported versions, see the NetIQ Secure Configuration Manager Technical Specification Web site.

Installation Guide

The Installation Guide for NetIQ Secure Configuration Manager does not include the following updated information:

Section Added Information

Database Requirements

To use SSL algorithms for communication with Core Services when FIPS is enabled:

  • Microsoft SQL Server 2008 Service Pack 3 with the associated cumulative update package
  • Microsoft SQL Server 2008 R2 Service Pack 2

Core Services Computer Requirements

Windows Server 2012

Console Computer Requirements

Windows Server 2012

Windows 8 (32-bit and 64-bit)

Windows Agent Guide

The Installation and Configuration Guide for NetIQ Secure Configuration Manager Windows Agent does not include the following updated information:

Section Added Information

Windows Agent Computer Requirements

Windows Server 2012

Windows 8 (32-bit and 64-bit)

Considerations for Managing the Windows Agent Environment

To successfully run Windows patch assessment checks, the following programs must be running on the endpoint computers that you want to assess:

  • Windows Update or Automatic Updates service, depending on the operating system
  • Windows Update Agent 7.4 or later

Secure Configuration Manager does not require a specific setting for the Windows service.

Windows Endpoints

Windows Server 2012

Windows 8 (32-bit and 64-bit)

Managing Microsoft SQL Server Endpoints

SQL Server 2012

Return to Top

Previous Releases

This service pack includes a full version of Secure Configuration Manager 5.9. For more information about that release, see the Version 5.9 Release Notes.

This service pack also includes enhancements added in Hotfixes 73317, 7011456, and 7011592. For more information, review the following descriptions:

Adds Objects and Attributes to the Namespace for NetIQ Secure Configuration Manager UNIX Agent

Hotfix 73317 adds and updates objects and attributes in the UNIX namespace for NetIQ Secure Configuration Manager UNIX Agent 7.2 (UNIX agent), at a minimum. You can use the objects and attributes to create custom security checks and policy templates. (ENG316503)

Cannot View or Edit Exceptions After Upgrading to Secure Configuration Manager 5.9

Hotfix 7011456 resolves an issue where the console does not display nor allow you to edit exceptions after you upgrade to Secure Configuration Manager 5.9. (ENG325250)

Adds and Updates Stored Procedures in the Database

Hotfix 7011592 adds or updates stored procedures that resolve the following issues:

Reduces Conflicts that Occur when Concurrently Purging and Adding Records in the Database

This hotfix updates the SPADDRDATAREQUEST stored procedure to reduce potential conflicts that occur when Core Services attempts to delete old data while concurrently adding new data to the same tables in the database. This issue might occur when you run a policy template while simultaneously purging old reports. (ENG325017)

Improves the Process for Purging Database Records

This hotfix updates two stored procedures that resolve two issues in the automatic process for purging reports from the Secure Configuration Manager database:

  • Users do not need to restart the service for Secure Configuration Manager Core Services after the nightly purge process causes the service to become unresponsive. The purge process no longer adversely affects the service. (ENG323065)
  • The automated purge process now removes records from the R_Tasks, R_TaskAttributes, and R_TaskParameter tables in the database. (ENG324810)

Adds Ability to Delete Custom Agent and System Properties

This hotfix adds the following stored procedure that enables you to remove custom attributes from the properties that define the agents and systems in your asset map: SPDeleteServerAgentAttribute.

For example, you might have added a property that specifies the department to which a system belongs, and you no longer want to use that property. For more information about running the stored procedure, see NetIQ Knowledge Base article 7011394. (ENG324820)

Updates a Stored Procedure that Deletes Orphan Records from the Database

This hotfix updates the SPDeleteOrphans stored procedure, which deletes orphan records from the Secure Configuration Manager database. The updated stored procedure does not look for the discovered agent table. The table exists in previous versions of the database but is not in version 5.9. (ENG324551)

Return to Top

Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information Web site.

For general corporate and product information, see the NetIQ Corporate Web site.

For interactive conversations with your peers and NetIQ experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups.

Return to Top

Legal Notice

Return to Top