Foreword -- This paper, contributed by Microsoft's Windows Embedded group, discusses how to migrate your existing development environment from Windows XP Embedded to Windows Embedded Standard. It covers the requirements to install Windows Embedded Standard 2009 Studio over Windows Embedded Studio for Windows XP Embedded, and the supported migration paths.

Enjoy. . . !

---

Migrating Windows XP Embedded to Windows Embedded Standard 2009
by Luca Amapane, Microsoft Corporation (January, 2009)

Contents

• Abstract
  
• Introduction
  
• Supported migration paths
  
• System requirements
  
• SQL Server requirements
  
• Back up your component database and repositories
  
• Migration to Windows Embedded Standard 2009
  
• Adding features to your installation
  
• Working with old configurations
  
• Working with multiple component databases
  
• Author and links

Abstract

This white paper discusses how to migrate your existing development environment from Windows XP Embedded to Windows Embedded Standard, the next generation of Windows XP Embedded. It covers the requirements to install Windows Embedded Standard 2009 Studio over Windows Embedded Studio for Windows XP Embedded and the supported migration paths.

Introduction

If you are a Windows XP Embedded user and you plan to move to Windows Embedded Standard 2009, you may be wondering if you have to uninstall Windows XP Embedded Studio before you install the new product. You may also want to know whether you can install Windows Embedded Standard 2009 over the earlier version and how to maintain all the custom components that you imported into your Component Database.

Windows Embedded Standard 2009 does support installation over an existing installation of Windows XP Embedded Studio. By installing Windows Embedded Standard 2009 over Windows XP Embedded, you will migrate to the latest version of the Tools and Component Database, and your custom components will be maintained in the Component Database.

The Windows Embedded Standard 2009 installer handles the migration automatically. It can determine whether you have an earlier version of the product installed. If you do, it continues with the migration option. If no version of Windows XP Embedded is detected, the installer performs a clean installation. Be aware that separate instances of Windows XP Embedded Studio and Windows Embedded Standard 2009 cannot be installed on the same workstation.

The migration is straightforward, as the installer handles all the steps without requiring user intervention. However, before you begin there are several things that you must review to determine the correct migration path. These considerations are discussed in the following sections.

You must purchase a Windows Embedded Standard 2009 toolkit to perform the migration. The toolkit includes a product key that is required to complete the installation. This is a different product key than the runtime product key required to activate the runtime image. You can obtain runtime product keys from your distributor.

This white paper does not address upgrading an image in the field to Windows Embedded Standard 2009. For this scenario, we recommend that you perform an image refresh.

Supported migration paths

All major versions of Windows XP Embedded can be migrated to Windows Embedded Standard 2009, as shown in Figure 1.


Fiqure 1: Migration paths from Windows XP Embedded
(Click to enlarge)
The Windows Embedded Standard 2009 installer detects any of the earlier versions that are listed here. If no earlier version is detected, it performs a clean installation. If an earlier version is detected, the installer automatically starts the migration process.

The installer determines if both the Windows XP Embedded Tools and the Component Database are installed on your workstation. If both are present, both are migrated to the Windows Embedded Standard 2009 Tools and Component Database. If only the Tools are installed, the migration is performed only for the Tools, and the Component Database is not installed. Similarly, if only the Component Database is installed, the migration is performed only for the Component Database and the Tools are not installed.

If you want to change your development setup, for example, you previously installed only the Windows XP Embedded Tools and you want to have the full Windows Embedded Standard 2009 Studio (Tools and Component Database), then you must uninstall Windows XP Embedded and perform a clean installation of Windows Embedded Standard 2009. Also, the Component Database cannot be migrated if it resides on a remote server.

Language Packs are not installed automatically during the migration. You can install Language Packs after the migration following the procedure that is described in section 8.

Microsoft Internet Explorer 7 and Windows Media Player 11 are automatically installed during the migration only if they are installed by Update Rollup 1.0 on your Windows XP Embedded Component Database. If not, by default, Internet Explorer 6 and Windows Media Player 10 are installed. After the migration you can install Internet Explorer 7 and Windows Media Player 11 by following the procedure that is described in section 8. Be aware that the two features are bundled. You cannot update them separately.

If you have an Evaluation version of Windows XP Embedded, you can migrate to the Evaluation version of Windows Embedded Standard 2009, downloadable from the Windows Embedded Web site. The Evaluation version cannot be migrated to the Retail version. In this case, you must uninstall the Evaluation version and perform a clean installation of the Retail version.

System requirements

Windows Embedded Standard 2009 has the same hardware requirements as Windows XP Embedded except for the hard disk drive space. Before you start the migration process, make sure that you have a minimum of 4.5 GB of available hard disk drive space. If you plan to perform a full installation, which includes all language packs and components, you need up to GB of free disk space.

The minimum operating system requirements to install Windows Embedded Standard 2009 is Windows XP Professional SP2 or Windows Server 2003.

Windows Installer 3.1 or a later version must exist for the installation to succeed. Windows Vista and Windows Server 2008 already contain an updated version of the Windows Installer. Windows Installer 3.1 can be installed from the Windows Embedded Standard 2009 product DVD by starting Setup.exe and selecting the Prepare option.

SQL Server requirements

SQL Server 2005 SP1, SQL Server 2005 Express SP1 or a later version is required to install the Windows Embedded 2009 Component Database. Earlier versions of SQL Server are not supported.

If your workstation has a local Windows XP Embedded Component Database running on an earlier version of SQL, such as Microsoft SQL Desktop Engine (MSDE), you must perform an upgrade to SQL Server 2005 SP1, SQL Server 2005 Express SP1, or a later version before you start the installation of Windows Embedded Standard 2009.

If you installed MSDE from the Windows XP Embedded installation disks or by using the MSDE MSI setup, generally you can perform an in-place upgrade of your database to SQL Server 2005 Express by following the procedure that is described below. Additional guidelines to upgrade MSDE to SQL Server 2005 Express are covered by the paper "Upgrading MSDE 2000 to SQL Server 2005 Express," which is available on MSDN, here.

To perform an in-place upgrade of your database to SQL Server 2005 Express:

• Install Windows Installer 3.1. This is required by SQL Server 2005 Express. Windows Installer 3.1 can be installed from the Windows Embedded Standard 2009 product DVD by starting Setup.exe and selecting the Prepare option. This option is available only if your workstation does not have Windows Installer 3.1 already installed.
  
  
• Install the .NET Framework 2.0. This is a prerequisite to SQL Server 2005 Express. You can download it from the Microsoft Download Center, here.
  
  
• Start the SQL Server 2005 Setup program. The Windows Embedded Standard 2009 product DVD includes SQL Server Express 2005. To install it from the DVD, insert the media and start Setup.exe. Select the Prepare option and then click Install SQL Server 2005 Express-DVD, as shown in Figure 2.
  
  
  Fiqure 2: nstall SQL Server 2005 Express from the Windows Embedded Standard 2009 product DVD
  (Click to enlarge)
  
• The Setup program runs the system configuration checks. If your system fails the configuration tests, click the failed link for more information and then take the corrective action required.
  
  
• On the Registration Information page, shown in Figure 3, clear the Hide Advance Configuration check box. You must do this because by default, Setup uses the instance name of SQLEXPRESS instead of the MSDE default instance name. By accessing the advance configurations options, you can select the instance installed by MSDE.
  
  
  Fiqure 3: Advanced configuration options
  (Click to enlarge)
  
• On the Feature Selection page, specify the features to install. Generally, accept all defaults
  
  
• On the Instance Name page, select Named Instance and type the MSDE instance name MSSQLSERVER as shown in Figure 4.
  
  
  Fiqure 4: Advanced configuration options
  (Click to enlarge)
  
• On the Existing Components page, select the SQL Server Database Services 8.00.761 check box and then click Next.
  
  
  Fiqure 5: Upgrading existing components
  (Click to enlarge)
  
• Specify the remaining configuration options. Generally, accept all defaults.
  
  
• In the Ready to Install dialog box, click Install. This upgrades the specified instance of MSDE to SQL Server 2005 Express.

Back up your component database and repositories

Before you continue with the migration, you should back up your Component Database and Repositories. This is a safety measure to follow any time that you upgrade your database.

To back up your Component Database, refer to the MSDN Web site, here.

To back up your Repositories, follow the guidelines provided by the MSDN Web site, here.

Migration to Windows Embedded Standard 2009

If you have reviewed the above sections and are sure that you comply with the requirements, you are now ready to start the actual migration. This section describes the steps to migrate from Windows XP Embedded to Windows Embedded Standard 2009.

To perform the migration, do the following:

• Start Setup.exe from the Windows Embedded Standard 2009 product DVD.
  
  
• On the splash screen select Install, and then click Run the Windows Embedded Standard Installation Wizard.
  
  
  Fiqure 6: Start the Windows Embedded Standard installation wizard
  (Click to enlarge)
  
• On the License Agreement page, read the license agreement and if you accept the terms, select the acceptance check box. Also, type the product key that is printed inside the product DVD box. These two steps are required to continue with the installation.
  
  
• If a local Component Database is found, you are presented with the SQL Server instance name that Setup detected, as shown in Figure 7 below. If your database cannot be found, make sure that you have a supported version of SQL Server, as described in the previous section.
  
  
  Fiqure 7: SQL Server instance name
  (Click to enlarge)
  
• On the Preinstallation page the components that will be migrated are listed: Tools, Component Database or both Tools and Component Database (Figure 8). Verify that the list is what you want to migrate and then click Install to continue with the installation.
  
  
  Fiqure 8: Preinstallation page for the migration of Tools and Component Database
  (Click to enlarge)
  
• The migration is executed and Windows Embedded Standard 2009 is installed. The log files that are related to your installation can be found at: %TEMP%\WindowsEmbeddedStandardSetup.log and, %TEMP%\WindowsEmbeddedStandard_WEUpdate.log.

Adding features to your installation

After the migration you may want to add features to your Windows Embedded Standard 2009 installation. For example, a customer asks for a localized image in a language that is currently not installed on your Component Database, or you want to install Internet Explorer 7 and Windows Media Player 11.

With Windows Embedded Standard 2009 you can easily add features to your installation as described in the following procedure:

• Start Setup.exe from the product DVD or click Start, Control Panel, Add or Remove Programs (in Windows XP) or Programs and Features (in Windows Vista), select Windows Embedded Standard and click Change.
  
  
• On the page shown in Figure 9, select Change to install additional features to your Windows Embedded Standard 2009.
  
  
  Fiqure 9: Add features, repair or remove Windows Embedded Standard 2009
  (Click to enlarge)
  
• On the Feature Selection pages shown in Figure 10, select the components that you want to add.
  
  
  Fiqure 10: Feature Selection page to add components
  (Click to enlarge)

Working with old configurations

If you have been working with Windows XP Embedded, you may want to open, edit, and build your old configurations with Windows Embedded Standard 2009.

Old configurations created by using Windows XP Embedded can still be opened, edited, and built by using Windows Embedded Standard 2009.

You must upgrade your configuration before you build your image.

After you upgrade your old configuration make sure that you remove the Windows XP Embedded runtime product key from the Run-time Image Licensing field of your configuration settings and replace it with a Windows Embedded Standard 2009 runtime product key, or leave it blank if you want to build an evaluation image. This is necessary because the activation of a Windows Embedded Standard 2009 image requires a Windows Embedded Standard 2009 runtime product key and cannot be activated with a Windows XP Embedded runtime product key. Runtime product keys can be obtained from your distributor.

Working with multiple component databases

If you have multiple customers, most likely you are working with multiple Component Databases on the same workstation. You attach and detach the appropriate database when you have to work with it.

With Windows Embedded Standard 2009, you are still able to work with multiple Component Databases, including Windows XP Embedded databases. As for Windows XP Embedded, if you are working with retail versions of the Component Databases, you cannot attach and detach evaluation versions of the Component Databases, and vice versa.

Useful tips on how to manage multiple databases appear in a blog entry by Brad Combs, here.

Author and links

Luca Amapane, Windows Embedded, Microsoft Corporation
www.windowsembedded.com
http://blogs.msdn.com/embedded/default.aspx

---

Related Stories:

• New Drivers in Windows Embedded Standard 2009
  
• Using Sysprep in Windows Embedded Standard 2009
  
• Microsoft launches new OS for retailers
  
• Tools for WES 2009 image deployment
  
• Microsoft nixes embedded Vista
  
• WES downloadable now
  
• Microsoft unleashes new embedded OS
  
• Microsoft renames embedded operating systems

Discuss Migrating Windows XP Embedded to Windows Embedded Standard 2009   >>> Be the FIRST to comment on this article!

>>> More Windows For Devices Articles Articles          >>> More By Staff