hit counter script
HP BL860c Management Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. Integrity BL860c
  6. Management manual
HP BL860c Management Manual

HP BL860c Management Manual

Managing the system registry hive on windows server 2003 and windows server 2008 integrity systems
Hide thumbs Also See for BL860c:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administrator's Manual, User and Service Manual
Managing the System Registry Hive on
Windows Server 2003 and Windows Server
2008 Integrity Systems
Published: November 2009
Edition: 1.0, Part Number: 5992-5670

Advertisement

Table of Contents
loading

Related Manuals for HP BL860c

Summary of Contents for HP BL860c

  • Page 1 Managing the System Registry Hive on Windows Server 2003 and Windows Server 2008 Integrity Systems Published: November 2009 Edition: 1.0, Part Number: 5992-5670...

  • Page 3: Table Of Contents

    Table of Contents About This Document......................5 Intended Audience..........................5 Typographic Conventions........................5 Technical Review............................7 Introduction............................7 Understanding System Hive Fundamentals and Limits..............7 Estimating System Hive Size......................8 Causes of Increasing System Hive Size...................10 Breaching the System Hive Limit....................10 Differences in Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2..10 System Recovery...........................11 General Outlines for Recovery......................11 Booting WinPE/WinRE and Loading the System Hive Registry.............11...
  • Page 4 List of Figures System Hive ControlSet structure....................7 Select Key values..........................8 RegEdit Export screen........................9 Directory listing showing difference in file size................9 Command Prompt option in WinPE (HP Reinstall media)............12 Command Prompt option in WinRE.....................12 Loading the System Hive in WinPE (HP Reinstall media)............13 General tab............................17 Triggers tab............................18 Actions tab.............................19...

  • Page 5: About This Document

    About This Document This white paper provides an explanation of the system registry hive and its limitations, and gives some methods for managing those limitations. The opinions in this document may suit some environments more than others. Intended Audience This document is intended for system architects and administrators responsible for managing HP Integrity servers.

  • Page 7: Technical Review

    Technical Review Introduction The Windows Server 2003 and Windows Server 2008 operating systems have a system registry hive size limitation of 32 MB (for all Service Packs). For most customer configurations, it is unlikely this limit will ever be reached. But in certain circumstances, particularly for customers with large configurations or numbers of SAN disks using multipath MPIO technology, the 32 MB limit is reachable, and can cause the system to fail to boot when restarted.

  • Page 8: Estimating System Hive Size

    known failed ControlSet. For the purposes of this document, the CurrentControlSet key is considered an exact replica or alias of one of the other ControlSets, and does not consume any System hive space. The other important key to note is the Select key, as shown in Figure Figure 2 Select Key values In the Select key, the Current and LastKnownGood subkey values are critically important.

  • Page 9: Regedit Export Screen

    its true size. Figure 3 shows the correct options for saving the System hive. Note the highlighted fields. Figure 3 RegEdit Export screen In the example above, a new file is created called CompactedRegFile. Now, by examining the file system, the size difference between the SYSTEM and CompactedRegFile files can be determined.

  • Page 10: Causes Of Increasing System Hive Size

    Causes of Increasing System Hive Size When Windows Server 2003 for Itanium-based Systems was first released, the System hive limit was set to 32 MB by design. This was not changed with the release of Windows Server 2008 for Itanium-based Systems (although it was increased in Windows Server 2008 R2 for Itanium-based Systems).

  • Page 11: System Recovery

    in the Recovery section of this document. While no such hotfix exists for Windows Server 2003, the same result can also be achieved for that operating system. Of these two operating systems, the hive limit is more likely reached in those running Windows Server 2008, mainly because these are newer installations and tend to run the latest software products.

  • Page 12: Command Prompt Option In Winpe (Hp Reinstall Media)

    Once the appropriate shell loads, a Command Prompt option becomes available. Figure 5 shows this option in the Windows Preinstallation Environment (the HP Reinstall Media DVD), while Figure 6 shows it in the Windows Recovery Environment. Figure 5 Command Prompt option in WinPE (HP Reinstall media) Figure 6 Command Prompt option in WinRE At this point, to load the system registry, complete the following steps:...

  • Page 13: Loading The System Hive In Winpe (Hp Reinstall Media)

    At the command prompt, type regedit and press Enter to run RegEdit. NOTE: This does not load the desired system registry hive, but the registry of the WinPE environment instead. To load the system registry hive, select the HKEY_LOCAL_MACHINE key in the left pane of the RegEdit window by clicking on it.

  • Page 14: Recovery Specifics: Windows Server 2003

    Once the target System hive registry is loaded, the method for recovery is different, depending on the operating system: • For Windows Server 2003, see the section: “Recovery Specifics: Windows Server 2003” (page 14). • For Windows Server 2008, see the section: “...

  • Page 15: Recovery Specifics: Windows Server 2008

    and selecting File Unload Hive. When the Hive unloads, all changes are automatically saved. Reboot the system. Further deletion of any redundant ControlSet(s) may be necessary at this time. If removal of unnecessary ControlSet(s) is difficult due to complex permissions, then contact Microsoft Support Services, since they can assist in deleting them fully.

  • Page 16: Creating A Pseudo Lastknowngood System Registry Hive For Windows Server 2003 And Windows Server 2008

    Hotfix KB973817 provides a replacement for Reg.exe that enables compression of the hive and allows the hive's true size to be ascertained from the command line (the graphical utility RegEdit already has this functionality). NOTE: Neither of these hotfixes can be installed on systems running Windows Server 2003 or Windows Server 2008 R2.

  • Page 17: General Tab

    Figure 8 General tab In the Triggers tab, change the following settings: • Begin the task: change to “At startup” Also select the following check boxes: • Delay Task for: 1 Minute The Triggers tab is not available on the Windows Server 2003 Task Scheduler, in which case the script must be run at startup.

  • Page 18: Triggers Tab

    Figure 9 Triggers tab...

  • Page 19: Using The Created Pseudo Lastknowngood (Lkg)

    In the Actions tab, change the following settings: • Action: change to “Start a program” • Program/script: change to “lkg.cmd” When finished, the Actions tab should look like this: Figure 10 Actions tab Administrator credentials must be supplied when the Task is added. No reboot is necessary for this task and it will take effect at the next reboot.

  • Page 20: Proactive Avoidance

    Proactive Avoidance This section provides information on how to avoid the System hive 32 MB limit as well as how to install the HP Registry Monitor Service, which provides alerts when the limit is near. Checking Disk Infrastructure Typically the biggest contributor to hive usage is the amount of disks and number of paths to those disks.

  • Page 21: Special Consideration For Symantec Veritas Volume Manager (Sfw)

    Administrator, but its true size could be closer to 12 or 13 MB. Since the true size of the consumed space cannot be gleaned with normal Windows tools, Hewlett-Packard has created a Management Service that monitors the true size of the System hive, sends an SNMP or WBEM...

  • Page 22: Installing The Hp Registry Monitor Service

    event, and logs an Error message in the Windows System Event Log if the System hive approaches its maximum limit. The next few sections explain the Service’s capabilities and how to configure it for more advanced scenarios. Installing the HP Registry Monitor Service The Registry Monitor Service is shipped as part of a larger Management Agent Package (either SNMP Agents 6.2.1, or WBEM Providers 6.5).

  • Page 23: Error Message

    Figure 12 Error message Default configuration of the thresholds, the time the System hive is checked, and the frequency of checking should be suitable for most configurations. However, if the System hive is checked and the file size is already over 24 MB, the service has to do some extra work to check the internal Hive size.

  • Page 24: Deciding Whether To Implement A Single Controlset Strategy

    Deciding Whether to Implement a Single ControlSet strategy Deploying a single ControlSet strategy (described in section, “System Recovery” (page 11)), can immediately reclaim approximately half the System hive space. You should deploy a single ControlSet strategy if the HP Registry Monitor Service has posted an Error message to the Windows System Event Log (similar to Figure 12), as the Hive is nearing its limit.

Table of Contents