IT tutorials
 
Technology
 

Using the Debugging Tools Available in Windows Server 2012 : System Startup and Recovery

11/24/2014 3:17:10 AM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

The System Startup and Recovery utility stores system startup, system failure, and debugging information. It also controls the behavior (what to do) when a system failure occurs.

To open System Startup and Recovery, launch Control Panel, select System and Security, select System, Advanced System Settings, click the Advanced tab in the Systems Settings dialog box, and then click Settings under Startup and Recovery to display a property page similar to the one shown in Figure 1.

Image

Figure 1. The Startup and Recovery page.

The Default Operating System field contains information that is displayed at startup. This information is typically the name of the operating system such as Windows Server 2012. You can edit this information using bcdedit from a command prompt. If the machine is dual-booted, there will be an entry for each operating system. The Time to Display List of Operating Systems option specifies the time the system takes to display the name of the operating system at startup. The default time is 30 seconds. This can be increased or reduced. The Time to Display Recovery Options When Needed is unchecked by default but can be selected and an interval in seconds entered.

You can set the action to be taken when system failure occurs in the System Failure section. There are two options. The first option is Write an Event to the System Log. This action is not editable in Windows Server 2012 because this action occurs by default every time a stop error occurs. The next option, Automatically Restart, reboots the system in the event of a system failure.

The Write Debugging Information section tells the system where to write debugging information when a system failure occurs. The options available include where the debugging information can be written to and the level of debugging information: Small Memory Dump (128KB), Kernel Memory Dump, Complete Memory Dump, or (None). The Write Debugging Information To option requires a paging file on the boot volume, which should be large enough to contain the select debugging option.

 
Others
 
- Using the Debugging Tools Available in Windows Server 2012 : Other Useful Troubleshooting Command-Line Tools
- Using the Debugging Tools Available in Windows Server 2012 : TCP/IP Tools (part 3) - Route, Nslookup, DCDiag
- Using the Debugging Tools Available in Windows Server 2012 : TCP/IP Tools (part 2) - Pathping, Ipconfig, ARP , Netstat
- Using the Debugging Tools Available in Windows Server 2012 : TCP/IP Tools (part 1) - Ping, Tracert
- Using the Debugging Tools Available in Windows Server 2012 : Best Practices Analyzer Tools
- Windows Server 2012 : Logging and Debugging - Setting Baseline Values
- Microsoft Exchange Server 2013 : Preserving information (part 10) - Executing searches with EMS , What Exchange can search
- Microsoft Exchange Server 2013 : Preserving information (part 9) - Using groups with searches, Removing a search
- Microsoft Exchange Server 2013 : Preserving information (part 8) - How in-place holds work
- Microsoft Exchange Server 2013 : Preserving information (part 7) - Resource throttling for searches
 
 
Top 10
 
 
Facebook
 
Technology FAQ
- Microsoft ebs security server configuration
- IIs7 on Windows server 2003
- How to Configure Failover Clusters With Win 2008 Server R2?
- Windows 2008 Network Load Balancing
- Windows Server 2008 - Group Policy Management - Remove Computer Management
- Remove shortcuts possibility in a web page or to put in favorite
- HTA Dynamic Drop Down List
- IIS host header and DNS
- VMware or MS Virtual Server?
- Adobe Acrobat 9 inserting tab pages
programming4us programming4us