HP Rx2620-2 Recovering Windows Server 2003 on HP Integrity Servers - Page 4
Last Known Good Configuration LKG feature.
UPC - 829160435749
View all HP Rx2620-2 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 4 highlights
Last Known Good Configuration A successful Windows startup includes an initial phase, a boot loader phase, a kernel phase, and a logon phase. If a problem occurs during any of these phases, Windows may not start correctly. It may fail to respond (hang) or display an error message. If the startup problem occurs immediately after you make a change to the server (for example, after you install a new driver), try to start the server using the Last Known Good Configuration (LKG) feature. Using Last Known Good Configuration, you can recover from problems such as a newly added driver that may be incorrect for your hardware. This feature does not solve problems caused by corrupted or missing drivers or files. To start the server with the Last Known Good Configuration: 1. Click Start > Shutdown > Restart, and then click OK. 2. When prompted to choose the instance of Windows to boot, press F8 (GUI console) or Esc 8 (head- less server console). To enter Esc 8, press and release the Esc key and then press and release the 8 key within 2 seconds. 3. Use the arrow keys to select Last Known Good Configuration, and then press Enter. 4. If you are running other operating systems on the server, select Microsoft Windows Server 2003 from the list, and then press Enter. If you were able to start your server using LKG, the last change that you made to the server (for example, the installation of a driver) may be the cause of the startup problem. To recover from the problem, either remove or update the driver or program, and then test Windows for correct startup. Examine the system logs for information on why previous boot failed. Right-click My Computer, select Manage, and click on Event Viewer to see Application, Security, and System logs. Note When you select LKG, only the HKLM\System\CurrentControlSet registry settings are restored. All other registry keys are untouched, so if failure is related to application files or registry entries, this feature will not help. 4