Security Updates - Microsoft Windows Embedded Standard 2009 Developer Resource Kit Componentizing Windows xp professional...

Security Updates
For device image servicing purposes you can obtain future Security Updates for your SP3-based designs at the OEM Secure web site. You obtain access to this site by contacting your Microsoft Authorized Embedded Distributors.
Deploying Microsoft security updates
Product comparison Comparison with Windows XP Professional
The following link relates to Windows XP Embedded which are for the most part still relevant when comparing Windows XP Professional with Standard 2009.
Differences between Windows XP Embedded and Windows XP Professional
At the tutorial site here, download and launch the Windows XP Embedded Product Overview video which compares Windows XP Embedded with Windows XP Pro and Windows CE.
Comparison with Windows Embedded POSReady
Windows Embedded POSReady (or its predecessor, Windows Embedded for Point of Service or WEPOS) is a version of Windows XP optimized for retail point of service (POS) devices. The POSReady platform is easy to use, includes technologies that enable present and future retail scenarios, and provides low lifecycle costs.
Windows Embedded POSReady Overview
Which Windows Embedded Product is Right for Me?
Features supported by POSReady but not supported by Standard 2009:
Windows Update
WEPOS-specific device drivers with Plug and Play functionality for retail device peripherals.
POS-specific API support
Comparison with Windows NT Embedded
The following white paper compares Windows XP Embedded SP1 features against Windows NT Embedded. Note that it does not include Windows XP Embedded SP2 or Standard 2009 (SP3) features.
Comparison of Windows XP Embedded and Windows NT Embedded
The following resource also is useful for comparing NT Embedded with XP Embedded.
Microsoft Windows XP Embedded Frequently Asked Questions
Chapter 3. Development Guide Introduction
This chapter walks you through the entire development process, with the goal of producing a complete and highly reliable Standard 2009 image, in the least time.
Installing Standard 2009 How to obtain
To obtain Standard 2009, visit the following Microsoft Web sites:
For general information:
How to Buy Windows Embedded Operating Systems
To order or download the evaluation versions (Developed runtime images have a 120 day expiration date but the development tools themselves never expire)
Windows XP Embedded Downloads and Updates
The installation procedure is available on-line:
Installation Guide
It can be useful to install the tools on Windows XP Professional (SP3) instead of Vista or later operating systems, because XP Embedded is based on Windows XP Professional binaries and hence you can use the XP Pro platform to compare features, functionality and binaries with your built Standard 2009 image.
For a list of all available free downloads related to Standard 2009, proceed to the Microsoft download site (www.microsoft.com/downloads ) and search on Windows Embedded Standard (or Windows XP Embedded for prior versions).
Installing
The following article offers valuable information regarding the upgrade process.
Migrating Windows XP Embedded to Windows Embedded Standard 2009
As described in the article, Standard 2009 supports installation over an existing installation.
Problems installing Standard 2009
If you have problems upgrading, for example if your component database is corrupted, you can perform a clean installation. Note that if you do so, you will need to later reimport any custom components that you may have developed and/or used.
Use the following clean installation checklist if you are having problems installing the tools. This procedure is also useful if upgrading from Evaluation (120 day) tools to Licensed tools (when upgrading from Eval to Licensed, you must perform a clean installation).
1. Back up any of your custom design files that may be present in the C:\Windows Embedded Data folder and C:\Windows Embedded Images folder.
2. Remove any existing third party antivirus software, and third party software that performs system monitoring activity. These applications can interfere with Target Designer's ability to process script files.
3. Uninstall existing Microsoft Windows XP Embedded Tools using Control Panel -> Add or Remove Programs.
4. Uninstall all Microsoft SQL Server component(s) using Control Panel ->Add or Remove Programs.
5. Reboot.
6. Delete the following folders:
C:\Windows Embedded Data
C:\Program Files\Windows Embedded
C:\Program Files\Microsoft SQL Server
7. Use Registry Editor (regedit) to delete the following sections of the registry:
[HKLM\Software\Microsoft\Microsoft SQL Server]
[HKLM\Software\Microsoft\Microsoft SQL Native Client]
8. Reboot.
9. Verify that all traces of XPE and SQL have been removed.
10. Reinstall Standard 2009
Installation Guide
11. Run the tools to verify that they are basically working.
12. Create and test your XPE design(s). Please note that for every licensed design, you need to take one final step to include one of your runtime PIDs in your design, in order to eliminate the Eval time limit:
How do I obtain and configure Licensing Runtime PIDs?
12. Consider reinstalling your third party system protection tools such as antivirus software. Retest the Tools afterwards to ensure the protection tools do not interfere with Target Designer functionality.
Once you are using the Licensed version of the Tools, you should obtain all future updates from the OEM Secure website. You obtain access to this site through your Authorized License Distributor.
Additional considerations:
If you plan to install the tools in Vista or later, the following blog contains special considerations owing to the User Account Control (UAC) feature:
Running Embedded Studio Tools on Vista
If you have a secondary development computer that contains XP Professional it might make sense to also do a parallel installation of XPE Tools on it, to help identify whether the OS in your original development computer is in an unusual state or is corrupted.
How to upgrade your database to the licensed version
The evaluation copy of the Standard 2009 tools produces an evaluation image. This is a fully running image that expires approximately 90 to 180 days after your image is first created using First Boot Agent. If you build using the release version, this expiration limitation is removed.
If you have decided to use Standard 2009 and want to create the images for your final target devices, you need a release version of the tools, and you must purchase a run-time license. To find local distributors, visit the following Microsoft Web site:
How to Buy Windows Embedded Operating Systems
Here is the recommended upgrade procedure.
You must completely uninstall the Evaluation version of Standard 2009. If you created custom components, make sure you back those up before uninstalling.
Completely install the retail (licensed) version of Standard 2009; both tools and database, and security updates. The evaluation versions of XP Embedded or Standard 2009 does not offer a field for you to enter the product ID for the deployed runtime images.
Deploying Microsoft security updates
Run Target Designer, and then open your configuration. Open the Settings node in the root (top-most) component of your configuration.
Select the following setting: Run-time Image Licensing - Product Identification Key (PID).
Enter your run-time image license PID, for example: JAS8A-9A8AS-8ASDA-124A9-8A9AA (this is a non working PID). This is the number obtained from one of the license stickers you receive. It is not the PID that was used to install Windows Embedded Studio. You only need to use the number from one of your stickers. This way, you can use a single image for mass device deployment.
If a built image fails to register as a licensed copy, try a different PID and/or contact the license distributor to obtain a working PID.
Note that you cannot change the PID associated with a deployed image after it has been built and deployed. You can only change the PID by modifying it using the Target Designer application, and then rebuild the image.
|