Hands-On Microsoft Windows Server Chapter 12 Managing System Reliability and Availability

Size: px

Start display at page:

Download "Hands-On Microsoft Windows Server 2008. Chapter 12 Managing System Reliability and Availability"

Donald Fitzgerald
10 years ago
Views:

1 Hands-On Microsoft Windows Server 2008 Chapter 12 Managing System Reliability and Availability

2 Objectives Understand general problem-solving strategies Resolve boot problems Use and configure Event Viewer Troubleshoot network connectivity Hands-On Microsoft Windows Server

3 General Problem-Solving Strategies Four general Problem-Solving strategies are: Understanding how a server and the network interact Training your users to help you solve problems Solving problems step by step Tracking problems and solutions Hands-On Microsoft Windows Server

Training your users to help you solve problems Solving problems step

4 Understanding How Servers and the Network Interact Many server and network administrators create a diagram of the entire network or diagrams of different portions of a network Hands-On Microsoft Windows Server

diagram of the entire network or diagrams of

5 Network Diagrams A network diagram should include the following elements: Servers and any mainframes Workstations and network printers Wireless network devices Cabled network devices Telecommunications links Wireless links Remote links Building locations Hands-On Microsoft Windows Server

network devices Cabled network devices Telecommunications links Wireless

6 Training Users to Help Train network users to be your partners in reporting problems For example, they should: Save their work at the first sign of a problem Record information about a problem as the problem is occurring Report any protocol information, such as error messages about a protocol or an address Quickly report a problem by telephone, or by voice mail if you cannot be reached immediately Avoid sending about urgent problems Hands-On Microsoft Windows Server

protocol information, such as error messages about a protocol or an address Quickly report a problem by telephone, or by

7 Solving Problems Step-by-Step Steps include: Get as much information as possible about the problem Record the error message at the time it appears or when a user reports it to you Determine if anyone else is experiencing the problem Check the Windows Server 2008 event logs for signs of a problem Use Performance Monitor, Reliability Monitor, Data Collector Sets, Task Manager, Server Manager, and the Computer Management tool to help you troubleshoot problems Hands-On Microsoft Windows Server

Windows Server 2008 event logs for signs of a problem Use Performance Monitor, Reliability Monitor, Data Collector Sets, Task

8 Solving Problems Step-by-Step (continued) Steps also include: Check for power interruptions Take the information you have gathered and define the problem Determine possible solutions for the problem Consider the best or most likely solutions Determine how the solution will affect users After your solution is implemented, continue monitoring the server to ensure there are no further problems Hands-On Microsoft Windows Server

the best or most likely solutions Determine how the solution will affect users After your solution is

9 Tracking Problems and Solutions Keep a log of all network problems and their solutions Help-desk system Application software designed to maintain information on computer systems, user questions, problem solutions, and other information that members of the organization can reference. eg. SpiceWorks (free download) The advantage of tracking problems is that you soon accumulate a wealth of information on solutions It is also good practice to keep a change log A record of changes made to a server s hardware and software Hands-On Microsoft Windows Server

10 Resolving Boot Problems Some of the common causes of boot failures include: Disk failure on the drive or drives containing the system and boot files A corrupted partition table A corrupted boot file A corrupted master boot record A disk read error In most cases, the first step is to power off the computer and try rebooting it Hands-On Microsoft Windows Server

corrupted boot file A corrupted master boot record A disk read error In most cases, the

11 Troubleshooting by Using Safe Mode Safe Mode Boots the server using the most generic default settings and only those services needed to boot a basic configuration After you boot into Safe Mode, you have the opportunity to further troubleshoot the problem Hands-On Microsoft Windows Server

basic configuration After you boot into Safe Mode, you have the

12 Troubleshooting by Using Safe Mode (continued) To access the Advanced Boot Options menu: Reboot the computer Press F8 as soon as the computer boots Select the option you want to use, such as Safe Mode, and press Enter If you use Safe Mode, but are unable to troubleshoot the problem, or a failed driver message is displayed during the boot process Use the Enable Boot Logging option so that you can create a log that you can later check for problems Hands-On Microsoft Windows Server

are unable to troubleshoot the problem, or a failed driver message is displayed during the boot process Use the Enable

13 Hands-On Microsoft Windows Server

14 Troubleshooting by Using the Installation DVD Windows Complete PC Restore Create a Volume Shadow-Copy Service (VSS) full backup using the Windows Server Backup tool This creates a backup of the data and program files and the system state data System state data Includes the operating system plus extra components and information that reflect the currently configured state of the server When you back up the system state data, you also are backing up the system protected files Hands-On Microsoft Windows Server

data Includes the operating system plus extra components and information that reflect the currently configured state of the

15 Troubleshooting by Using the Installation DVD (continued) Windows Server 2008 offers the capability to perform a Windows Complete PC Restore From the Windows Server 2008 installation DVD Windows Memory Diagnostic Tool Another tool available from the Repair your computer option on the Windows Server 2008 installation DVD Used to test the RAM in your computer Hands-On Microsoft Windows Server

Memory Diagnostic Tool Another tool available from the Repair your computer option on the Windows

16 Hands-On Microsoft Windows Server

17 Troubleshooting by Using the Installation DVD (continued) Hands-On Microsoft Windows Server

18 Using and Configuring Event Viewer Event Viewer (eventvwr.msc) Houses the event logs that record information about all types of server events, in the form of errors, warnings, and informational events Server 2008 event logs are divided into three general categories: Windows logs, applications and services logs, and Microsoft logs Hands-On Microsoft Windows Server

form of errors, warnings, and informational events Server 2008 event logs are divided into

19 Hands-On Microsoft Windows Server

20 Using and Configuring Event Viewer (continued) Windows generates four logs for reporting general operating system and software application events: System log Security log Application log Setup log Admin logs Designed to help give the system administrator information about a specific problem and its causes and may suggest how to solve the problem Hands-On Microsoft Windows Server

log Admin logs Designed to help give the system administrator information about a specific

21 Command-Line Tools Some TCP/IP utilities, such as Telnet, can troubleshoot TCP/IP connectivity Type ipconfig to view a dialog box showing the adapter address (MAC or Ethernet), IP address, subnet mask, and other information for that computer Type ping to poll the presence of another TCP/IP computer netstat is a quick way to verify that a workstation or server has established a successful TCP/IP connection Hands-On Microsoft Windows Server

22 Command-Line Tools: ipconfig Hands-On Microsoft Windows Server

23 Command-Line Tools: ping Hands-On Microsoft Windows Server

24 Graphical Tools You can use a GUI (graphical user interface) tool for diagnosing and repairing network problems The Network and Sharing Center Can provide a simple GUI representation of the network to show if network connectivity problems exist between your server and the network or the Internet Another way to use the Network and Sharing Center is to have it diagnose a specific connection, Such as the Local Area Connection from the Network Connections Window Hands-On Microsoft Windows Server

25 Hands-On Microsoft Windows Server

26 Hands-On Microsoft Windows Server

27 Hands-On Microsoft Windows Server

28 Summary Before problems occur, develop a problem-solving strategy A server that won t boot can mean big trouble The Windows Server 2008 installation DVD offers options to recover a system, or work with a system that won t boot Regularly perform a full backup, which includes system state data, so that you can fully recover a system that has failed Event Viewer is a storehouse of logs from which you can monitor a system and diagnose problems Hands-On Microsoft Windows Server

29 Summary (continued) Regularly use Event Viewer to monitor the contents of logs Server 2008 contains command-line and graphical tools for troubleshooting network connectivity problems You can use the Remote Desktop client capability, such as from Vista, to remotely manage a Server 2008 server Server 2008 comes with the Remote Server Administration Tools for managing multiple Server 2008 Hands-On Microsoft Windows Server

Implementing, Managing, and Maintaining a Microsoft Windows Server 2003 Network Infrastructure

Implementing, Managing, and Maintaining a Microsoft Windows Server 2003 Network Infrastructure Question Number (ID) : 1 (wmpmsp_mngnwi-121) You are an administrator for an organization that provides Internet connectivity to users from the corporate network. Several users complain that they cannot