1 / 14

Understanding the Windows PE 2.0 Phase in XP Installation

Learn about the essential MS-DOS phase, Windows PE advantages, limitations, and scenarios for utilization in Windows XP installation. Explore the role of the operating system kernel and key functionalities.

clarkej
Download Presentation

Understanding the Windows PE 2.0 Phase in XP Installation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CIS 221 Lesson 2

  2. What is the first phase of the of the Installation of Windows XP? • MS-DOS phase • Why is the MS-DOS phase needed? • the computer required an operating system to run the installation program • to gain access to the disk drives • Once Windows XP is installed it takes over the installation process.

  3. Windows PE 2.0 • What does PE stand for? • Windows Preinstallation Environment • Windows PE uses a stripped down version of the Vista kernel.

  4. What is an Operating Systems kernel? • The central module of an operating system. It is the part of the operating system that loads first, and remains in main memory • What essential services is the kernel responsible for? • Memory management • Processor management • Task management • Disk management • Other services are called from the hard drive and loaded as needed into memory.

  5. Advantages of PE 2.0 • What is native 32-bit or 64-bit support ? • Enables the computer to address memory just as the full Windows Vista operating system does • What is native 32-bit or 64-bit driver support? • PE 2.0 can use the same drivers as a full Windows Vista installation

  6. Advantages of PE 2.0 • What is Internal networking support ? • Windows PE includes its own internal TCP/IP networking stack and is capable of functioning as a Windows file sharing client • This means that after booting Windows PE, an administrator only has to supply a driver for the network adapter, and the networking stack is complete

  7. Advantages of PE 2.0 • What is Internal NTFS support ? • Windows PE includes internal support for the NTFS 5.x file system used by Windows Vista, as well as the FAT file systems that MS-DOS

  8. Advantages of PE 2.0 • What is scripting language support ? • Windows PE includes internal support for a subset of the Win32 application programming interface (API), meaning that it is possible to run some Windows programs in the preinstallation environment.

  9. Advantages of PE 2.0 • What is flexible boot options ? • Windows PE can boot from a variety of media, including CD-ROM, DVD-ROM, a USB drive, or a Windows Deployment Services (DS) server

  10. Limitations of Windows PE 2.0 • Windows PE does not support the entire collection of Win32 APIs, as a full installation of Windows Vista does. • Windows PE automatically stops and reboots after 72 hours of continuous operation.

  11. Limitations of Windows PE 2.0 • Windows PE networking support is limited to the TCP/IP and NetBIOS Over TCP/IP (NetBT) protocols • While it is possible to modify the Windows PE registry when the operating system is running, all registry keys are reset to their default values each time the operating system restarts.

  12. Scenarios for Using Windows PE • Custom deployments - allows administrators to build their own unattended installation routines using Windows PE as a platform to run scripts and deploy customized disk images on fleets of workstations

  13. Scenarios for Using Windows PE • System troubleshooting - If a Windows Vista computer fails to start, or if it crashes repeatedly, a technician can launch the Windows Recovery Environment (RE), which is simply another name given to Windows PE. • Technician can use Vista’s built-in troubleshooting utilities or run third-party or custom diagnostic tools

  14. Scenarios for Using Windows PE • System recovery - OEMs can use Windows PE to build recovery solutions that automate the process of setting up Windows Vista, installing specific drivers, installing applications, and configuring the entire system to create a standardized environment.

More Related