HPE System Healthcheck
Microsoft Windows Release Notes
Document Release Date: February
2019
Software Release Date: February
2019
Warranty
The only warranties for HPE 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. HPE 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 HPE 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 2019 Hewlett Packard Enterprise Development Company, L.P.
Trademark Notices
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
1 HPE System
Healthcheck for Microsoft Windows
1.2 Where can I obtain the kit
and user documentation?
2.1 SHC v10.1.9 (February 2019)
2.4 SHC v10.1.6 (January 2016)
2.8 SHC v10.1.2 (December 2011)
2.10 SHC v10.1.0 (December 2010)
2.13 SHC v10.0.1 (January 2009)
This document describes
the release notes for System Healthcheck (SHC) for Microsoft Windows. SHC is a
tool produced by HPE Services to analyze a system's configuration, performance, and
security status.
This is the release of version 10.1.9. The SHC v10.1.9 release includes support for minor updates and documentation updates. For more information, go to: 2.1 SHC v10.1.9 (February 2019).
All SHC Client kits and SHC documentation are available from the HPE Software Depot. Go to:
http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=SHCBASE01
If you have technical support issues or problems with the System Healthcheck tool, please contact your local support team.
This section describes the released versions of SHC.
· Updated PAC version to 1.2.9
· General release to support minor updates
· Updated SHC User Guide
· Added support for Windows 2019 on x86-64 architecture
· Updated PAC version to 1.2.8
· General release to support minor updates
· Updated SHC User Guide
· Added support for Windows 2016 on x86-64 architecture
· Added support for Synergy Generation 9 (Gen9) family
· Updated PAC version to 1.2.7
· General release to support minor updates
○ Added support for ProLiant Generation9 (Gen9) DL family
○ Added support for ProLiant Generation9 (Gen9) ML family
○ Added support for ProLiant Generation9 (Gen9) BL family
· Updated SHC User Guide
· Updated PAC version to 1.2.6
· General release to support minor updates
· Updated SHC User Guide
· Added support for Windows VMs running on VMWare ESXi 5.5 and 6.0
· Added support for Apollo 4200 Generation9 (Gen9) Server
· Added support for Apollo 4510/4530
· Added support for ProLiant ML10 v2 Server
· Defects fixed
○ 6681: Update SHC User Guide to more accurately reflect functionality of SADB Mail receiver.
○ 1410: Fixed analysis end time reflects correctly for Client (PAC) under “Analyzer Details” and analysis start and end time reflects correctly under “Package Summary”.
○ 6932: Updated documentation for clarity for the rule CRSH4010
· Updated PAC version to 1.2.5
· General release to support minor updates
· Updated SHC User Guide
· Updated PAC version to 1.2.4
· Added support for System Management Homepage (SMH) 7.4
· Defects fixed:
○ 1892: Inform users of shortcomings in SHC report generation
○ 3949: PAF SHCA: timestamp information missing from evidence
○ 4316: PAF SHCA: Detailed report: evidence tables are truncated
· Added support for VMware VMs to get SHC assessments report
· Updated SHC User Guide
· Added support for VMware guests hosted on ESXi 5.1
· Added support for System Management Homepage (SMH) 7.3.0
· Added support for Windows 2012 and R2 on x86-64 architecture. The SHC kit has been tested and verified on the following versions:
○ Windows Server 2012 Standard Edition
○ Windows Server 2012 Datacenter Edition
○ Windows Server 2012 R2 Standard Edition
○ Windows Server 2012 R2 Datacenter Edition
· Added support for IIS 8 and 8.5
· Added support for IE9, IE10, and IE11
· Defects fixed:
○ 10812: Issue with rule MEM1410
○ 12749: Rule BOOT4304 should not fire on 64 bit systems
○ 7296: IIS3307 - disabled rule - test description not appearing on report
○ 8229: Windows 2003 vm ware machine and background process
○ 8402: Update Windows: Rule AD5515 Updated user guide
· Updated SHC User Guide
· Added support for Gen8:
○ ProLiant DL360 Gen8
○ ProLiant DL380 Gen8
○ ProLiant ML350 Gen8
○ ProLiant SL390s Gen8
○ ProLiant BL460c Gen8
· Added support for VMware guests hosted on the following versions:
○ ESX 4.1
○ ESXi 4.1
○ ESXi 5.0
· Added support for System Management Homepage (SMH) 7.0.0
· Defects fixed:
○ 4979: There could be intermittent problems with handling DNS data
○ 5120: SHC for Windows: shc /t 168 gives strange error
○ 5632: WEBUI - View reports page error
· Updated SHC User Guide
· Added support for Windows Server 2008 R2 SP1
· Added support for System Management Homepage (SMH) 6.3
· Defect fixed:
○ 4919: MEM1413: Proposed minor changes for clarity
○ 5069: SHC maximum duration inconsistencies
○ 5220: Unable to launch System Health Check after installation
· Supports Windows Server 2008 R2. The SHC kit has been tested and verified on the following versions:
○ Windows Server 2008 R2 Standard Edition (x64)
○ Windows Server 2008 R2 Enterprise Edition (x64)
○ Windows Server 2008 R2 Datacenter Edition (x64)
○ Windows Server 2008 R2 for Itanium-based Systems
· Added support for Buccaneer, Sentosa, Kauai and Hydrazine hardware
· Added support for IE8
· Added support for IIS 7 and 7.5
· Rule content updated for Windows Server 2008 R2
· Removed ISEE v3 transport option
· Increased the time out value for the dynamic analysis and made it configurable using libdynamic.xml
· Active Directory rules are now set to use the current domain rather than the forest for queries. In most cases this should be sufficient as they query a Global Catalog server. If there is not a GC in the current domain, some rules will not fire. This is configurable using the libad.xml profile file.
<ruleProfile name="RULE_CONSTANTS">
...
...
<parameter name="forestSearch">false</parameter>
</ruleProfile>
Note: Changing this value to true may
cause the Active Directory package to run quite slowly.
· Defects fixed:
○ 1266: (BZ: 16172) Win 2008 review: nlb2261 - registry value changed
○ 1267: (BZ: 16173) Win 2008 review: nlb2262 - registry value changed
○ 1268: (BZ: 16209) Win 2008 review: libiis
○ 1269: (BZ: 16285) Win 2008 review: RAS rules
○ 1270; (BZ: 17115) audi1223 - CIS Level 2 query
○ 4664: AD package access violation on malaga
○ 4372: IIS3307 - MaxUserPort and TCPWindowSize changes
○ 4373: IIS metabase changes
○ 4378: nlb2261/2262 - need to update registry values for W2008
○ 4703: static packages don't die after timeout time
○ 4723: Svcs2006
○ 4229: pac-cli says it’s running when it’s not
○ 4340: event package showing errors on malaga
○ 4710: network package log errors
○ 4714: MSCS5031 - change text to reflect R2
○ 4718: SHAR rules need text needs updating to include R2
○ 4719: OPSY2321 - include Windows 2008 R2
○ 4720: AUTH5908 - update for R2
○ 4721: USER2118 - add additional infor on Windows 2008 R2
○ 4722: SVCS2002 - make relevant for 2003, 2008 and R2
○ 4725: PERF1517 - need to exclue blocking queues
○ 4726: PERF1518 - is this correct on malaga?
· Updated SHC User Guide
· Updated dynamic interval max to ten minutes
· Updated dynamic duration max to seven days
· Defects fixed:
○ 1292: (BZ: 16578) SHC Web UI; includes link "System Healthcheck Assessment Report" which is no longer valid.
○ 2861: Rule OPSY2318; evidence section has introduced HTML formatting errors in report.
○ 2965: SHC Web UI; an error is produced when SHC start analysis and "Request Professional Report" is selected and "No automatic submission" is also selected.
○ 2970: Rule MEM1410; out of date with respect to Windows 2003 R2 Enterprise Edition and Windows 2008.
○ 3332: Silent Installation of kit does not work as expected.
○ 3388: Rule TCP3926; misfiring
○ 3389: Rule PERF1532; misfiring
○ 3499: Rule MSCS5010; misfiring
○ 3388: Rule TCP3926; misfiring
· Updated SHC User Guide
· Defects fixed:
○ 1279: (BZ: 17860) Creation of motive.mf does not check for XML-compatible chars
○ 1293: (BZ: 17341) SHC Security Impact Statement document needs minor update
○ 1278: (BZ: 17568) output PAC version in the XML report
· Updated SHC User Guide
· Supports Windows Server 2008. Tested and verified the SHC Kit on the following versions:
○ Windows Server 2008 Enterprise Edition (x86 and x64)
○ Windows Server 2008 Datacenter Edition (x86 and x64)
○ Windows Server 2008 for Itanium-based Systems
· New rule content added specifically for Windows Server 2008
· Various rule updates
· Minor bug fixes
· Updated SHC User Guide
· Supports:
○ Microsoft Windows 2000 and Windows 2003 for 32-bit (Intel & AMD)
○ Microsoft Windows for x64 editions (Intel & AMD) (native support)
○ Microsoft Windows 2003 for Itanium-based systems (native support)
· New reports/reporting format
○ System Health Check Assessment - Management Summary Report (HTML, RTF)
○ System Health Check Assessment - Detailed Report (HTML)
· New reporting indicators
○ Introduced health impact concept
· Improved reporting graphics, navigation
· Reporting delivered via Backend Analysis Framework (BAF)
· Refactored SHC into two sub components:
○ Analysis harness: configuration, encryption, transport
○ Analysis engine: Proactive Analysis Client (PAC)
· Various rule updates
· Updated user guide
· Removed on site report generation (shclre) capability
· SHC lite report generation removed
Issue: Saving non-English UTF-8 customer data using the WebUI is not supported.
It is recommended to use shcconfig when entering customer data that contains non-English UTF-8 characters. Attempting to save such data using the WebUI will result in the data getting corrupted. Examples of languages not supported by the WebUI include Japanese, Korean, Chinese and Russian.
Issue: Some Active Directory rules may take over an hour to run in very large domains.
If performance and analysis time is an issue, you can disable the individual rules. For more information on how to disable a rule, refer to the SHC user guide.
Issue: Active Directory rule package limits data retrieval for some rule tests.
· A default retrieval limit of 500 active directory objects has been set for rule AD5501 which can take over an hour to run on domains with a large number of domain controllers.
· A default retrieval limit of 20 Domain Controller objects has been set for rules (AD5519, AD5535, AD5575, AD5581, AD5582) as these rules can take a very long time to run as the number of domain controllers increase significantly.
· A default retrieval limit of 15 Domain Controller objects has been set for rules (AD5563, AD5574) as these enterprise-wide rules can take a very long time to run as the number of domain controllers increase significantly.
You can change these limits if resources and analysis time is not an issue. To change these limits, change the specific rule setting in the libad.xml file under the <pacinstalldir>\packages folder.
Issue: Installing a new SHC kit over older version of SHC/PAC may result in broken/no PAC install. This is due to a known issue with the silent uninstall routine for a previous version of PAC failing to delete some keys from the registry.
If you encounter this issue, then do the following:
· Uninstall SHC and PAC (if present)
· Open the registry editor ('Start Menu'->'Run' 'regedit.exe') and delete the key: 'HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\hpesmc\PAC'
· Delete the directory 'C:\Program Files\hpesmc\pac' if still present
· Reinstall the new SHC kit
Issue: Running for long durations with short intervals is not successful. The following message appears:
pac-lib-cli error PacCli.cxx 580 An error has occurred while creating the xml report.
It is recommended to use the default interval of 120 seconds or greater. For a long run of 96 hours (4 days) or more, use the default interval of 120 seconds or greater. For short intervals of less than 5 seconds, only run the tool for 4 hours or less with an interval of no less than 3 seconds.