Supporting Operating System Installation | 3
Total Page:16
File Type:pdf, Size:1020Kb
cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 1 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s Supporting Operating LESSON 1 System Installation 70-688 EXAM OBJECTIVE Objective 1.1 – Support operating system installation. This objective may include but is not limited to: Support Windows To Go; manage boot settings, including native virtual hard disk (VHD) and multi-boot; manage desktop images; customize a Windows installation by using Windows Preinstallation Environment (PE). LESSON HEADING EXAM OBJECTIVE Using a Troubleshooting Methodology Viewing System Information Using the Event Viewer Supporting Windows To Go Support Windows To Go Creating and Deploying a Windows To Go Workspace Drive Booting into a Windows To Go Workspace Managing Boot Settings Manage boot settings, including native virtual hard disk (VHD) and multi-boot Using BCDEdit and BCDBoot Configuring a Multi-Boot System Manage boot settings, including native virtual hard disk (VHD) and multi-boot Configuring a Native VHD Boot File Manage boot settings, including native virtual hard disk (VHD) and multi-boot Understanding VHD Formats Installing Windows 8.1 on a VHD with an Operating System Present Installing Windows 8.1 on a VHD Without an Operating SystemCOPYRIGHTED Present MATERIAL Managing Desktop Images Manage desktop images Capturing Images Modifying Images using DISM Customizing a Windows Installation by Using Windows PE Customize a Windows installation by using Windows Preinstallation Environment (PE) 1 cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 2 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s 2 | Lesson 1 KEY TERMS answer file file-based disk image virtual hard disk (VHD) Autounattend.xml Fixed Size hard disk VHD format Boot Configuration Data (BCD) Group Policy Object (GPO) VHDX format store Group Policy Management Windows 8.1 Pre-installation BCD b oot (bcd boot .exe) Console (gpmc.msc) Environment (PE) disk BCD Editor (bcdedit.exe) or bcdedit multi-boot (dual-boot) Windows Deployment Services Deployment Image Servicing and native VHD boot (WDS) Management (DISM) sector-based disk image Windows Image Format (WIM) disk image System Preparation Utility Windows PE Disk Management Console (sysprep.exe) Windows To Go workspace (diskmgmt.msc) System Information (msinfo32. Workspace to Go Creator Diskpart exe) (pwcreator.exe) Dynamically Expanding hard disk System Image Manager (SIM) ■ Using a Troubleshooting Methodology Since this course is focuses on supporting Windows 8.1 and resolving issues, you need to understand how to use a troubleshooting methodology. When you encounter computer problems, some problems will have obvious solutions and easy to fix. Many problems will THE BOTTOM LINE need to be resolved by following a troubleshooting methodology to efficiently troubleshoot a problem. However, before you perform any fix, you need to look at the big picture to determine what the fix will affect. By fixing one problem, you can cause another problem. The purpose of an effective troubleshooting methodology is to reduce the amount of guess- work and random solutions so that you can troubleshoot and fix the problem in a timely manner. Microsoft Product Support Service engineers use the “detect method,” which consists of the following six steps: 1. Discover the problem. Identify and document problem symptoms and search technical information resources, including searching Microsoft Knowledge Base (KB) articles to determine whether the problem is a known condition. In addition, search the organiza- tion’s knowledge base to determine if your organization has seen the problem before. 2. Gather information. Ask the client or customer and check the system’s documentation to determine if any hardware, software, or network changes have been made, including any new additions. Also check any available logs including looking in the Event Viewer. You also need to check the scope of the problem. Does it only affect one computer, does it affect the computers within a specific site or subnet, does it affect the computers within an Active Directory organizational unit, or does it affect the entire organization? 3. Develop an action plan. List or track possible solutions and try to isolate the problem by removing or disabling hardware or software components. You may also consider turning on additional logging or running diagnostic programs to gather more information and test certain components. 4. Execute the action plan. Test potential solutions and have a contingency plan if these solutions do not work or if they have a negative impact on the computer. Of course, cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 3 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s Supporting Operating System Installation | 3 you don’t want to make the problem worse, so if possible, back up any critical system or application files. 5. Check results. If the problem is not fixed, go back to develop an action plan. 6. Take a proactive approach. Document any changes that you made along the way while troubleshooting the problem. Also notify the customer or client and document internal systems in case the problem happens again or if those changes that fixed the problem affect other areas. When troubleshooting problems, several tools can help isolate and fix the problems, including: • System Information • Device Manager • Event Viewer • Task Manager • Resource Monitor • Performance Monitor • System Configuration • Memory Diagnostics tool • Troubleshooting Wizard • Boot Menu including Safe mode • Windows Repair When troubleshooting issues within Windows and related programs, you will eventually deal with problems confound you. In those situations, you will have to ask co-workers and research on the Internet. You will also need to check vendor websites, including Microsoft’s website. Most of the information available from Microsoft to design, plan, implement, manage, and monitor Microsoft products will be found at Microsoft’s website, particularly at TechNet. It will include Microsoft Knowledge Base, service packs, security updates, resource kits, techni- cal training, operations and deployment guides, white papers and case studies. Information used mostly for troubleshooting will be found in Microsoft’s Knowledge Base and several online Microsoft forums. These forums provide help for a wide range of problems; you can even leave messages for others to answer. The Microsoft Knowledge Base is a reposi- tory of thousands of articles—made available to the public by Microsoft—that contains infor- mation on many problems encountered by Microsoft users. Each article bears an ID number and articles are often referred to by their Knowledge Base (KB) ID. The Knowledge Base can be accessed by entering keywords or the ID at Microsoft’s support site. Viewing System Information When you first begin troubleshooting a computer, you need to know what is in the com- puter and what is running on the computer. System properties shows you the processor and amount of RAM. Device Manager shows you what hardware is recognized and what drivers are loaded. The System Information program is a useful troubleshooting tool to see what is in a system. System Information (also known as msinfo32.exe ) shows details about your computer’s hard- ware configuration, computer components, and software—including drivers. It was originally included with Windows to assist Microsoft support technicians in determining what is in a machine, especially when they were troubleshooting end-users’ issues, but System Information can be used by anyone at any time. cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 4 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s 4 | Lesson 1 System Information lists categories in the left pane and details about each category in the right pane. The categories include: • System Summary – Displays general information about your computer and the operat- ing system, such as the computer name and manufacturer, the type of basic input/output system (BIOS) your computer uses, and the amount of installed memory. • Hardware Resources – Displays advanced details about your computer’s hardware and is intended for IT professionals. • Components – Displays information about disk drives, sound devices, modems, and other components installed on your computer. • Software Environment – Displays information about drivers, network connections, and other program-related details. To find a specific detail in System Information, type the information you’re looking for in the Find what box at the bottom of the window and then click Find. For example, to find your computer’s Internet protocol (IP) address, type ip address in the Find what box and then click Find. Using the Event Viewer One of the most useful troubleshooting tools is the Event Viewer snap-in, which essen- tially is a log viewer. Any time you have problems, you should look in the Event Viewer to see any errors or warnings that might reveal the problem. The Event Viewer is a Microsoft Management Console (MMC) snap-in that enables you to browse and manage event logs. It is included