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

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

3. Hands-On Microsoft Windows Server 20083 Objectives (continued) Troubleshoot network connectivity Remotely administer a server using Remote Desktop Remotely administer multiple servers using Remote Server Administration Tools

4. Hands-On Microsoft Windows Server 20084 General Problem-Solving Strategies The best approach to solving server and network problems is to develop effective troubleshooting strategies Four general 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

5. Hands-On Microsoft Windows Server 20085 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 –And then update the diagrams each time an aspect of the network changes

6. Hands-On Microsoft Windows Server 20086

7. 7 Understanding How Servers and the Network Interact (continued) 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

8. Hands-On Microsoft Windows Server 20088 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 e-mail about urgent problems

9. Hands-On Microsoft Windows Server 20089 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

10. Hands-On Microsoft Windows Server 200810 Solving Problems Step-by-Step (continued) Steps include: (continued) –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

11. Hands-On Microsoft Windows Server 200811 Tracking Problems and Solutions Keep a log of all network problems and their solution 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 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

12. Hands-On Microsoft Windows Server 200812 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

13. Hands-On Microsoft Windows Server 200813 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

14. Hands-On Microsoft Windows Server 200814

15. Hands-On Microsoft Windows Server 200815 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

16. Hands-On Microsoft Windows Server 200816

17. Hands-On Microsoft Windows Server 200817 Troubleshooting by Using Safe Mode (continued) Activity 12-1: Booting into Safe Mode –Time Required: Approximately 15 minutes –Objective: Learn how to boot into Safe Mode

18. Hands-On Microsoft Windows Server 200818 Troubleshooting by Using the Installation DVD Windows Complete PC Restore –When you create a 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

19. Hands-On Microsoft Windows Server 200819 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

20. Hands-On Microsoft Windows Server 200820

21. Hands-On Microsoft Windows Server 200821 Troubleshooting by Using the Installation DVD (continued)

22. Hands-On Microsoft Windows Server 200822 Troubleshooting by Using the Installation DVD (continued) Activity 12-2: Performing Memory Diagnostics –Time Required: Approximately 15 minutes –Objective: Learn how to test RAM

23. Hands-On Microsoft Windows Server 200823 Troubleshooting by Using the Installation DVD (continued) Using the Command Prompt –When you insert the installation DVD, you can use it to access the command prompt So that you can repair a disk problem or copy a critical file back to the server –You can execute many commands from the command prompt

24. Hands-On Microsoft Windows Server 200824

25. Hands-On Microsoft Windows Server 200825 Troubleshooting by Using the Installation DVD (continued) Activity 12-3: Using the Command Prompt –Time Required: Approximately 15 minutes –Objective: Learn how to access the command prompt from the Windows Server 2008 installation DVD

26. Hands-On Microsoft Windows Server 200826 General Tips for Fixing Boot Problems Stop message –An error message displayed when the server experiences a serious problem and then stops functioning

27. Hands-On Microsoft Windows Server 200827

28. Hands-On Microsoft Windows Server 200828

29. Hands-On Microsoft Windows Server 200829

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

31. Hands-On Microsoft Windows Server 200831

32. Hands-On Microsoft Windows Server 200832 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

33. Hands-On Microsoft Windows Server 200833 Using and Configuring Event Viewer (continued) Operational log –Tracks occurrences of specific operations, such as when a disk drive is added Applications and services logs available in Event Viewer include: –DFS Replication log –Directory Service log –DNS Server log –File Replication Service log –Hardware Events –Internet Explorer

34. Hands-On Microsoft Windows Server 200834 Using and Configuring Event Viewer (continued) Analytic logs –Relate to how programs are operating and are typically used by application or system programmers Debug logs –Used by application developers to help trace problems in programs so they can fix program code or program structures

35. Hands-On Microsoft Windows Server 200835 Viewing Log Events Log events are displayed in Event Viewer with an icon that indicates the seriousness of the event Each log displays descriptive information about individual events, including the following: –Description of the event –Name of the log in which the event is recorded –Source of the event –Event ID –Level of the event—information, warning, error –User associated with the event, if any –OpCode of the event

36. Hands-On Microsoft Windows Server 200836 Viewing Log Events (continued) Event Viewer can be opened from the Administrative Tools menu, as an MMC snap-in, from the Computer Management tool, and from Server Manager To view the contents of a log, click that log in the tree under Event Viewer –To view the detailed information about an event, double-click the event The event logs are a good source of information to help you troubleshoot a software or hardware problem

37. Hands-On Microsoft Windows Server 200837 Viewing Log Events (continued)

38. Hands-On Microsoft Windows Server 200838 Using the Event Viewer Filter Option All of the event logs in Event Viewer have a filter option to help you quickly locate a problem The events can be filtered on the basis of the following criteria: –When the event was logged, such as in the last seven days –Event level, such as information, warning, error, critical, and verbose –By log, such as the system or security log –By source of the event, such as a particular service or software component

39. Hands-On Microsoft Windows Server 200839 Using the Event Viewer Filter Option (continued) The events can be filtered on the basis of the following criteria: (continued) –Task category of the event, such as a security change –Keywords, such as Audit Failure and Audit Success –User associated with the event –Computer associated with the event –Date range –Time of day range

40. Hands-On Microsoft Windows Server 200840 Maintaining Event Logs The event logs quickly fill with information Logs can be maintained using several methods, as follows: –Size each log to prevent it from filling too quickly –Overwrite the oldest events when the log is full –Archive the log when it is full –Clear the log manually (does not overwrite events) It is recommended that you develop a maintenance schedule –To save the log contents for a designated time period

41. Hands-On Microsoft Windows Server 200841 Maintaining Event Logs (continued) To tune the event logs, open Event Viewer and right- click each log you want to tune, one at a time –And click Properties On the General tab, set the log size in the Maximum log size (KB): box You can save the log as one of the following kinds of files: –.evtx –.xml –.txt –.csv

42. Hands-On Microsoft Windows Server 200842 Maintaining Event Logs (continued) Activity 12-4: Using Event Viewer –Time Required: Approximately 10 minutes –Objective: Use Event Viewer to view system log events

43. Hands-On Microsoft Windows Server 200843 Troubleshooting Connectivity One area that server and network administrators often troubleshoot is TCP/IP connectivity Both command-line tools and graphical tools are available for troubleshooting Windows Server 2008 connectivity

44. Hands-On Microsoft Windows Server 200844 Command-Line Tools Some TCP/IP utilities, such as Telnet, have IP troubleshooting tools built in 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

45. Hands-On Microsoft Windows Server 200845 Command-Line Tools (continued)

46. Hands-On Microsoft Windows Server 200846 Command-Line Tools (continued)

47. Hands-On Microsoft Windows Server 200847 Command-Line Tools (continued)

48. Hands-On Microsoft Windows Server 200848

49. Hands-On Microsoft Windows Server 200849 Command-Line Tools (continued) Activity 12-5: Using TCP/IP Connectivity Troubleshooting Tools –Time Required: Approximately 10 minutes –Objective: Learn how to use nbtstat and netstat

50. Hands-On Microsoft Windows Server 200850 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

51. Hands-On Microsoft Windows Server 200851

52. Hands-On Microsoft Windows Server 200852

53. Hands-On Microsoft Windows Server 200853

54. Hands-On Microsoft Windows Server 200854 Remotely Administering a Server In some organizations, it is important for server administrators to be able to remotely access a server in order to solve a problem Use the Remote Desktop client to remotely access and manage the server Configure Remote Desktop using Server Manager –Or the System applet in Control Panel to access the System Properties dialog box Configure a strong password for the account from which you perform administration

55. Hands-On Microsoft Windows Server 200855