Exam Windows Embedded Standard 7. Preparation Kit. Certification Exam Preparation utomation. Not for resale.

Transcription

1 MCTS i Exam Windows Embedded Standard 7 Preparation Kit Certification Exam Preparation utomation Not for resale.

2 Contents at a Glance 1 Product Concepts 2 Building a Base Operating System Image Using Image Builder Wizard 3 Advanced Installation using Image Configuration Editor 4 Customizing an Image using Image Build Wizard 5 Advanced Image Creation 6 Preparing and Deploying an Image 7 Servicing an Image

3 Chapter 1 Product Concepts Windows Embedded Standard 7 is very different from its predecessors. It s now based on a Windows 7 client platform and implements an on-device build process for the development of all operating-system images. As with all first-of-a-kind products, it comes with a suite of new terms and technologies. In addition, it uses some previous product terms in a slightly different context, so having a good understanding of the product concepts and terminology is especially important. This overview introduces Windows Embedded Standard 7 concepts, terminology, and technologies. Later chapters go into additional detail, and you can get more information about particular terms and technologies by referring to the glossary at the end of the preparation kit. Exam objectives in this chapter: Although this chapter does not specifically address any particular Exam Objectives, it is relevant as an introduction to essential Embedded Standard 7 concepts. Before You Begin This chapter discusses product concepts and introduces terminology and technology. Unlike the following chapters, this overview is not divided into lessons and does not include a Practical Lab. It assumes the reader possesses a basic understanding of computer hardware. After this chapter, you will be able to: Understand the different ways to develop a Windows Embedded Standard 7 operating system. Identify the application of key technologies the Image Configuration Editor (ICE) and the Image Builder Wizard (IBW). Come away with a general understanding of the product concepts as well as the processes and technologies specific to Windows Embedded Standard 7. Be familiar with the product terminology. Estimated time: 15 minutes. 1

4 2 Chapter 1 Product Concepts Image Creation To create a Windows Embedded Standard 7 operating system, use your running reference device (the Target Device, so called because all deployed images will be duplicates) instead of a separate development computer, and one of three methods: Interactive Your selections made in the Image Builder Wizard (IBW) creates a configuration in the form of an unattended answer file. Using the configuration, the Image Builder installation process then installs the operating system to the target device. Automated You can use an existing configuration created in Image Configuration Editor (ICE) on a separate development system to install the same operating system on another target device. The Image Builder installation process installs the operating system to the reference device without any user interaction. Combined A combination of the two. Using a partially unattended answer file created in Image Configuration Editor as a basis, you can still install interactively in IBW. This provides the opportunity for specific installation options to be entered during the IBW process and still maintain a level of automation. As in the previous two methods, the Image Builder installation process then installs the operating system to the reference device. Whichever method you choose, the Image Builder installation process creates the operating system based on the contents of the configuration file and installs it on the target device. Configurations Configurations contain the selected functionality, settings, and information required by the Image Builder installation process to create a customized operating system. Unattended answer files contain the specific selections to build a configuration. The information contained in the configuration is used to install and configure software applications, device drivers, specifies language packs to install, registry modifications to make, how to configure the operating system, and how to partition and format hard disks. Configurations can also include Microsoft runtime licensing and identity information and can customize the Windows welcome screen (Welcome Center) and even provide for a completely unattended installation. Windows Embedded Standard 7 configurations are created and modified in either IBW or ICE and are stored as answer files.

5 Before You Begin 3 The Image Builder Wizard The fastest, easiest way to create, build, and install a Windows Embedded Standard 7 operating system is by using the Image Builder Wizard. To do so, you start the target device using the bootable Windows Embedded DVD appropriate for the device s architecture (x32 or x64). The interactive wizard commences and you make your selections and enter values through a series of screens. The IBW process creates a configuration that is then used by the Image Builder Engine to initialize, create and install the operating system on the reference device. Image Builder Engine The Image Builder Engine build process is the installation mechanism, as shown in Figure 1-1, which installs and configures the Windows Embedded Standard 7 operating system and Windows Welcome (as discussed later in this chapter) to a target device from a configuration. In this way, Image Builder Engine supports installations that are interactive using IBW and automated (unattended) using a configuration created in ICE. Whichever method you choose, unlike previous versions of Windows Embedded, this release lets you create the image on the actual device, rather than on a development system. Embedded Core File Based Write Filter Internet Explorer Language Packs/ Driver Packs 3rd Party Software Installer Operating System Updates selected functionality Image Builder creates the operating system on the device Final Windows Embedded Standard 7 operating system Figure 1-1 Graphical representation of the Image Builder Engine build process using IBW or ICE

6 4 Chapter 1 Product Concepts Packages The Image Configuration Editor Because the Image Configuration Editor enables you to add, remove, and configure any of the Windows Embedded Standard 7 functionality in a single view, it gives you the most flexibility when creating a Windows Embedded Standard 7 operating system. After you install the ICE toolset on a development system, it is used to create a configuration that is processed by Image Builder. An implementation of Windows Embedded Standard 7 consists of the Windows Embedded Core package combined with your choices from more than 200 system packages. Packages are the smallest individually selectable unit of functionality and form the basis of the operating system s modular design. The packages included in Windows Embedded Standard 7 provide features and functionality comparable to Windows 7 Ultimate in addition to embedded specific functionality known as Embedded Enabling Features. To ease development IBW and ICE organizes its display of packages into categories and subcategories. All packages are available for 32- and 64-bit architectures. Microsoft alone creates and signs packages. Each contains file information and registry values that determine a specific capability. A package can belong to a dependency group (we ll cover dependencies shortly). Package Categories Package Categories are assigned according to the types of features a package provides, such as diagnostics or graphics and multimedia. The ICE interface and certain IBW dialogs organize and display packages by category. Package Types The five package types of Windows Embedded Standard 7 are: Feature Pack Language Pack Driver Pack Embedded Enabling Feature (EEF) Windows Update

7 Before You Begin 5 An understanding of the different package types is required. You use different tools and methodologies when working with different package types. NOTE Third-party applications, out-of-box drivers, and Windows Embedded Standard 7 service packs are not packages. None of these have a package type, and you add them to and remove them from images differently than you do packages. Package Feature Sets Most packages belong to a feature set a group of packages in which all the members either comprise or support the same functionality. Feature sets simplify the inclusion of a specific functionality by adding one item to the Configuration, multiple packages are added. Feature sets also ensure that all the required packages for a specific technology are included into the Configuration. Feature Sets achieve this through dependencies to other packages, discussed later in this chapter. Internet Explorer 8 and Security Credentials offer two examples of feature sets that each contains multiple packages. Embedded Core The Embedded Core (ecore) is the smallest deployable Windows Embedded Standard 7 image it contains the essential capabilities every image requires, such as bootcritical drivers, along with basic support for security, servicing, and networking. You can t modify ecore with an altered version, you could create an image that wouldn t function. Windows Embedded Standard 7 has 32 and 64-bit versions of ecore. ICE adds ecore to every new answer file automatically. You can deploy an ecore image from the Windows Imaging (WIM) file, INSTALL.WIM, and you can create a minimal ecore-like operating system using the Minimal Configuration Template in both IBW and ICE. NOTE 32-bit and 64-bit differences Although the 32 and 64-bit versions of the embedded core are similar, they exhibit some differences in functionality. Refer to later chapters in this Preparation Kit for more details.

8 6 Chapter 1 Product Concepts Dependencies A dependency is a defined relationship between a package and one or more packages. A dependency ensures that the operation of the package is as intended, by the inclusion or exclusion of other packages in the configuration. By dividing a specific functionality across multiple packages grouped by dependencies, each of the packages can be as small as possible, whilst still ensuring that the package has all the required resources and function correctly. A dependency can be on a single package or a set of packages (a dependency group). Dependency Groups A dependency group is a set of packages to which any other package can specify an inclusive or exclusive relationship. This allows for flexible, indirect relationships among packages and the creation of complex dependencies. Package-to-package relationships are direct and are automatically resolved by the toolset. Package-to-group dependencies provide an opportunity for the developer to make decisions on a perconfiguration basis. Dependency groups exist as independent objects. They enable you to include or exclude packages en masse, they provide a level of automation during development, and they assist with consistency. The dependency type (the nature of the package s relationship to a group) determines how the ICE or IBW resolves the dependency (automatically or manually) and how many members of the dependency group will be included in the configuration. There are five dependency types: Requires exactly one package from the group One and only one package from the group must be in the configuration. Requires at least one package from the group At least one package from the group must be in the configuration and in some instances more than one package can be added. Requires all packages from the group All the packages from the group must be in the configuration. Conflicts with all packages from the group None of the packages from the group is allowed in the configuration. Can take advantage of zero or more packages from the group Zero or more packages from the group can be in the configuration

9 Before You Begin 7 Required and Optional Dependencies In addition to having a type, a dependency can be required or optional. You must resolve the former for the operating system to function reliably. You can resolve the latter at your discretion, but not resolving optional dependencies may result in the operating system not being fully functional. Figure 1-2 shows an example of dependency resolution. Figure 1-2 Dependency resolution in Image Configuration Editor Unattended Answer Files A configuration is saved as an unattended answer file, is XML-based, and contains settings and values the Image Builder will use when creating the image on the reference device. The answer file is created manually with ICE or using the IBW, and specifies setup options that include information such as how you want disks partitioned, the location of the Windows Embedded Standard 7 image to install, and the product key to apply. You can also stipulate values that apply to the Windows Embedded Standard 7 installation, such as the names of user accounts, display settings, and Internet Explorer favorites. When creating configurations in ICE, you can validate the settings in the Windows Embedded Standard 7 image.

10 8 Chapter 1 Product Concepts TIP The unattended answer file for Image Builder is called UNATTEND.XML or AUTOUNATTEND.XML. Templates Templates are used to form the basis of a new configuration or to provide a quick way to introduce functionality to an existing one. Templates are an answer file that is merged into a configuration and consist of application and device driver packages or sets of packages needed for various models of devices. As an example Microsoft offers a template that, when merged with your unattended answer file, gives the resulting embedded OS support for viewing Excel documents. For new configurations, a number of device templates have been included with the toolkit and templates from third parties are also available. Above all, templates save you time as their dependencies have been fully analyzed and tested. Distribution Shares and Configuration Sets To locate the physical files Image Builder needs for creating the Windows Embedded Standard 7 operating system, a distribution share is required. This is a set of folders containing the physical package files and any additional applications and device drivers. Distribution Shares, which may be several gigabytes in size, can reside on a local disk or network share. You create and manage distribution shares using ICE, and unattended answer files reference the shares specifically. Configuration Sets After you ve validated and saved a configuration/unattended answer file in ICE, you can create a configuration set a subset of a distribution share. The configuration set contains the complete collection of files, drivers, applications, and updates that a particular unattended answer file requires. Configuration sets are self-contained and separate from the distribution share, which you use during development. Configuration sets are a smaller and more portable than distribution shares and are useful for deployments in the field or when a network share isn t available.

11 Before You Begin 9 Configuration Passes Processing the configuration/unattended answer file requires from one to seven cycles called configuration passes. These passes synchronize the different phases of the process. Out Of Box Experience (OOBE) Windows Welcome, also called the Out Of Box Experience (OOBE), specifies the behavior of certain user-interface screens during the first system start-up. You control OOBE via an XML file called OOBE.XML. This file holds text and graphics for customizing Windows Welcome and the Welcome Center. You can include multiple OOBE.XML files in an operating system image to customize the OOBE experience based on the language, country, and region selections the end user makes. Configurations created in ICE can include properties set in Windows Welcome such as computer name, user and password, as shown in Figure 1-3. Figure 1-3 Windows Embedded Standard 7 Welcome screen

12 10 Chapter 1 Product Concepts Windows Embedded Standard Image Files A Windows Embedded Standard 7 image file (which has a WIM extension) contains one or more compressed Windows Embedded Standard 7 operating system volume images. A volume image is the captured volume or partition of a Windows Embedded Standard 7 operating system. You manage WIM files offline using a variety of utilities in the Windows Embedded Standard 7 Toolkit. Normally you create the files using Microsoft s ImageX tool. Image X ImageX is a command-line tool that works with the latest Windows Embedded Standard 7 image (WIM) files. The main purpose of the tool is to capture, modify, and deploy operating system images in a manufacturing or development environment. You generally use ImageX with the Windows Imaging File System Filter (WIM FS Filter) driver. The driver enables you to mount a WIM file to a directory. You can then use a file-management tool such as Windows Explorer to perform actions such as browsing, copying, pasting,and editing the file without first extracting or re-creating the Image. In addition to running ImageX from the bootable Windows Embedded Standard DVD, you can also use ImageX from a Windows Preinstallation Environment (WinPE) during image-based deployments. Windows Preinstallation Environment Windows Preinstallation Environment 3.0 (WinPE 3.0) is a bootable operating system that you can use to install, troubleshoot, and recover an operating system. WinPE is a minimal Windows API subsystem with limited services, not a general-purpose operating system. You can boot and run the environment from DVD-ROM, a USB flash drive, or hard disk. The Windows Embedded Standard 7 Toolkit has a number of tools for creating, editing, and manipulating bootable Windows PE images. In Windows Embedded Standard 7, WinPE plays a key image-creation role. Image Builder uses the compact operating system to boot the target device as well as to initialize and deploy the Windows Embedded Standard 7 operating system to the hard disk drive from a WIM file. You can start a WinPE command prompt from the main screen of IBW.

13 Before You Begin 11 NOTE 32-bit and 64-bit Versions The Windows Embedded Standard 7 Toolkit includes both 32 and 64-bit versions of Windows PE 3.0. Device Architecture Selection Before you build an operating system image, you must select the device architecture (x32 or x64) the same build can t support more than one device architecture. Most 64-bit CPUs today do support a legacy 32-bit mode for backward compatibility, though, which gives you some flexibility. Whether you re trying to decide which architecture to choose for your device or pondering the use of a 32-bit operating system on 64-bit architecture, you should consider the factors outlined in this table. Device Drivers Image Size Memory Requirements Application Support Depending on the hardware vendor, 64-bit device drivers may not be available. In addition, 64-bit drivers must be certified for Windows 7 by Windows Hardware Quality Labs. The Windows Embedded Standard 7 operating-system size is larger for 64-bit than for 32-bit installations. 64-bit installations require twice the physical RAM (1GB minimum recommended). Your application set may not support a 64-bit environment. The selection of the device architecture is critical to the development process with both the Image Builder Wizard and Image Configuration Editor. NOTE Processor architecture terminology can be confusing. Intel x32 architecture (IA-32) is also referred to as x86. The x32 architecture is compatible with the Intel Pentium III architecture and includes processor families such as the Intel Pentium III, Intel Pentium 4 (before Prescott), VIA C3, and VIA C7. The x64 architecture uses 64-bit processor technology that includes a legacy x32 compatible mode. The x64 is also referred to as AMD64, x86-64 and Intel64. Processor families built around x64-compatible technology include the AMD Athlon 64, Intel Pentium D, Intel Core 2, Intel Pentium Dual-Core, Intel Nehalem micro-architecture, and VIA Nano. The Intel IA-64 (Itanium) is not x64 compatible.

14 12 Chapter 1 Product Concepts Chapter Summary Windows Embedded Standard 7 introduces a lot of new concepts, technology, and terminology. This chapter provides the foundation you need to get the most from the Preparation Kit and your future studies.