MCTSi Exam 70-577 Windows Embedded Standard 2009 Preparation Kit Certification Exam Preparation Automation Not for resale. ii Table of Contents Contents at a Glance 1 Creating and Customizing the Configuration 2 Managing the Development Environment 3 Integrating Embedded Enabling Features 4Creating Components 5 Generating and Deploying an Image 6 Adding Windows Functionality Chapter 5 Generating and Deploying an Image After you have completed the tasks of designing your run-time image, configuring it with the necessary components and testing the configuration, you can continue with production deployment to your target devices. Production deployment entails reviewing the deployment scenario, preparing the image, and deploying it to devices for a final, retail-ready product. This chapter discusses key deployment scenarios for Internet- connected and unconnected devices including devices that start remotely or start from an onboard booting media. This chapter also covers the configuration dependencies you must complete to prepare your image for distribution. Exam objectives in this chapter: ■ Generate the Pre-First Boot Agent (pre-FBA) image ■ Seal and clone the post-FBA image ■ Prepare target media for deployment ■ Deploy the Post-First Boot Agent (post-FBA) image to the target device ■ Implement a remote boot solution Before You Begin To complete the lessons in this chapter you need the following: ■ Microsoft® Windows® Embedded Studio for Windows Embedded Standard 2009 installed. ■ Completed Chapters 1, 2, 3 and 4. 145 146 Chapter 5 Generating and Deploying an Image Lesson 1: Generate the Pre-FBA Image FBA runs the first time your operating system starts after you configure and build an image. FBA completes the run-time image build process by running a sequence of tasks on the target system, such as Plug and Play (PnP) device detection, security installation, and DLL registration. You can add commands to the FBA process and specify when they will run. You can also add tasks to the FBA process by defining custom resources, referred to as FBA commands, such as RunOnce requests, application shortcuts, and populating the registry with service data. After this lesson, you will be able to: ■ Include a product identification key (PID). ■ Understand the FBA process. ■ Create custom resources to customize the build process. Estimated lesson time: 20 minutes. Run-Time Image Licensing You must enter a PID for your retail image. Otherwise, the image that you create is an evaluation image and will stop working after the evaluation period expires 120 days after deployment. Windows Embedded Standard 2009 product activation does not require online access and is activated in Target Designer when you enter a run-time product key in the Run-time Image Licensing section of the image configuration settings. FBA Phases and Processing Order The Target Designer build process creates the raw system image, creates the necessary directory structure, and copies the files for each component to the specified directories. The build process also creates the registry hives and saves these in the \Windows\System32\Config folder. This raw system image is not ready to run as it is. On the first start of the raw run-time image, FBA runs to complete the build process. FBA performs any run-time tasks that could not be performed offline with Target Designer, including security installation, catalog registration, PnP device detection, network configuration, DLL registration, and profile initialization. The FBA process flows in a predefined, sequential order that is determined by phases and ordinal values to control the timing of various commands. FBA Generic Lesson 1: Generate the Pre-FBA Image 147 Command, FBA DLL/COM Registration, and FBA OC Manager Requests all have ordinal values associated with them. FBA starts at 0 and continues through 65,535. Phases 0 through 8,500 are reserved for use by the system and you should not set a directive to run below 8,500. The phase values are double words, where the high word indicates the FBA phase and the low word indicates the ordinal value within an FBA phase. You can view a log (Fbalog.txt) of the FBA process in the Windows\FBA directory on the target device after FBA has run. If you have a kernel debugger attached while FBA executes, the logging information is forwarded to the debugger as well as written to the log file. Custom Resources You add custom resources to enhance the functionality of a component when you create a component in Component Designer. However, custom resources are also FBA commands, because FBA controls their execution. During first boot, FBA uses these commands to populate the registry, set up application shortcuts, specify replacements for end-of-life components, and perform actions that cannot be done during the building of a configuration, such as Component Object Model (COM) registration. You use Target Designer to add custom resources to a configuration. FBA DLL or COM Registration This resource is required for any component that needs to register a COM InProc server. FBA uses functions from the Win32® application programming interface (API), including LoadLibrary, DllRegisterServer, DllUnregisterServer, and DllInstall, to register and load the DLLs containing the COM objects. Component Branch This resource is used to specify a replacement component for a component that is set to an end-of-life (EOL) state. When an EOL component is replaced by multiple components, one branch resource is added to the EOL component for each replacement component. Branch resources are only used in EOL components. However not all EOL components require replacements—in such a case there is no branch. In other cases there is only one branch which means that the EOL component is replaced by one new component. 148 Chapter 5 Generating and Deploying an Image PnP Device ID This resource is used to insert PnP information into a device component, and is required for PnP device drivers. As already mentioned in Chapter 4, you should not add PnP resources manually to a component, because these are created automatically when you import an INF file into Component Designer. RunOnce Request This resource is used to execute an application during the first start of the run-time image, after first boot, or after every logon. This functionality is added to the run-time image as one of three registry keys: ■ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \Run. The Run key is processed after every logon. The Explorer shell runs it if present, otherwise either Custom Shell, Command Shell, or Task Manager Shell run it. If FBA processes this key, it does so after every logon, not during first start as it nor- mally would. Typically, this key is used to load system tray applications, launch services in executables, hide auto start applications, or hide background pro- cesses. ■ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \RunOnce. FBA processes the RunOnce key only once after PnP device enumeration and DLL registration processing have completed. The values of this registry key are deleted from the registry after it is processed, so that it will not run again. Typi- cally, this flag is used when a restart is required, such as for a DLL or OCX reg- istration. ■ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \RunOnceEx. The RunOnceEx key is processed only once, by the Explorer shell, after the first logon. The values of this registry key are deleted from the registry after it is pro- cessed, so that it will not run again. If the Explorer shell is not present, this key is ignored. Typically, this flag is used for a process that runs only once, and that either cannot be run correctly by FBA or requires the system to be fully opera- tional. Lesson 1: Generate the Pre-FBA Image 149 Service Data This resource is required for components that define a Windows service. Start Menu Shortcuts This resource is used to create shortcuts on the Start menu or on the desktop if these are part of your image. FBA Generic Commands This is a custom resource which is required for a component that needs programs executed during FBA on the run-time image. FBA calls CreateProcess from the Win32 API to run a program and optionally pass it command-line arguments. Prepare for Cloning Before you prepare to clone your image, make sure that the configuration accurately reflects the hardware of your target device and that you have verified its functionality on your target device. Then, add the System Cloning Tool component to your configuration, which is located under Software>System>System Services>Base folder in component browser. After you add it to the configuration, you can configure its settings or leave the default settings. The next lesson covers the settings for the cloning tool. Lesson Summary This lesson introduces the tasks you have to perform before you build and deploy your production image. You need to stamp your image with a PID key for the image to become a production image that does not expire after 120 days. You create all the custom resources you need for FBA to prepare your raw image to function as intended. Finally, you must plan for mass deployment by adding the System Cloning Tool to your configuration. You complete a final dependency check, build your image and save your configuration file. 150 Chapter 5 Generating and Deploying an Image Quick Check 1. What must be done in order to prevent a Windows Embedded Standard 2009 operating system from expiring? 2. Is it safe to run FBA on a development machine, and then transfer the operat- ing system to a different machine for testing? 3. What do you add to your configuration to facilitate cloning of the operating system? Quick Check Answers 1. A retail run-time PID must be entered in Target Designer to prevent the run- time from expiring.