Windows Embedded Standard 2009 Step-by-Step Deployment

Blog
Contact

Windows Embedded Standard 2009 Step-by-Step Deployment – Part I

Check also:

Windows Embedded Standard 2009 Step-by-Step Deployment – Part II

Windows Embedded Standard 2009 Step-by-Step Deployment – Part III

I’ve been reviewing, for a while now, the opportunities that Embedded operating systems has to offer. If you take a look to previous posts of mine that I’ve prepared about XP Embedded you’ll find a quick introduction to the platform + the steps for building, preparing and deploying XP Embedded images in your environment, including deploying it on diskless devices (remote boot):

Preparing and Installing Windows XP Embedded Images – Part I: Setting up the Environment

Preparing and Installing Windows XP Embedded Images – Part II: Building Images

Preparing and Installing Windows XP Embedded Images – Part III: Using Remote Boot

Windows Embedded 2009 Standard Overview

Windows Embedded 2009 Standard is the newest version of the Embedded operating systems released by Microsoft, succeeding Windows XP Embedded. These operating systems are oriented to special devices or computers, where you need a secure, small, reliable and manageable OS. WES 2009 contains the same kernel as Windows XP with a few improvements:

Windows XP kernel with SP3 included
Internet Explorer 7
Windows Media Player 11
Silverlight 1.0
.Net Framework 3.5 (including also 1.0, 1.1 and 2.0).
IPv6 support

For more information about Windows Embedded Standard 2009 check the following links:

- Windows Embedded Standard 2009 Home
- [PDF] Windows Embedded Standard 2009 Overview
- [PDF] Windows Embedded Standard 2009 Datasheet
- [PDF] Windows Embedded Kiosk Solutions
- Download Windows Embedded Standard 2009 Trial

So, after a quick review, let’s start with the step-by-step guide for building and deploying Windows Embedded 2009 Standard images, including the remote boot process.

Requirements

We will consider installing all the WES roles within the same machine, including the DHCP server (necessary for the remote boot environment).

Valid Operating Systems

- Windows XP Pro SP2 or higher
- Windows Server 2003 SP1 or higher
- Windows Vista
- Windows Server 2008

Roles

- DHCP Server available on the network
On our case we’ll have this role on the same machine.

Valid Database Engines

- SQL Server 2005 SP1 or higher
- SQL Server 2005 Express Edition SP1 or higher *
- SQL Server 2008
- SQL Server 2008 Express Edition

* : Windows Embedded Standard 2009 installation media already includes the SQL Server 2005 Express Edition SP2.

DHCP Configuration

Remember that this role and configuration it’s used only to achieve remote boot on diskless devices. It’s to necessary if that’s not your environment.

The same procedure used for XP Embedded is needed. Check this link for more information.

C:\WINDOWS\system32>netsh
netsh>dhcp
netsh dhcp>server \\<server_machine_name>
netsh dhcp>add optiondef 60 PXEClient String 0 comment=PXE support
netsh dhcp>set optionvalue 60 STRING PXEClient

To verify the correct configuration, an option should be added and set on your DHCP server. You can check it on the DHCP Snap-In > Server Options.

Windows Embedded 2009 Standard Installation Step-by-Step

Well the process is quite simple, so you should not have any problem following it. But you’ll probably find a small issue within the procedure, let’s take a look:

1. Using the WES 2009 media, start the wizard from the autorun menu.

2. Insert the Product Key that you were given when you registered for the download.

3. Select “Custom” installation.

4. On the components to be installed, check also the entire feature for “Remote Boot Service”.

5. For the TFTP server, select “On this machine”.

6. Accept the default directory and click on “Next”.

7. Now select the SQL Server where the DB should be stored. I’m selecting it the local SQL Server Express instance already installed. Click on “Next”.

8. On the summary click on “Install”.

Here’s where you should find a problem. In the middle of the installation process this message will appear:

Windows Embedded Standard Error: WeUpdate.
D:\Setup\WMP11.exe failed. Return value = 0×40

(Also the message could appear using other components besides WMP11, Windows Media Player).

The log file should have this message:

Windows XP Embedded Service Pack 3 Installer
Cannot connect to the database – please check the database.
Setup cannot continue.
No objects or files were imported to the database (local)\SQLEXPRESS.
WEUpdate Exiting with return code: 64
*** End of Run ***

Solution

Wait 5-10 minutes and click on “Retry”.

You don’t believe it? Check this MSDN article about it. It’s related about how the installer access and closes the database during the installation process.

After that the installation should complete normally and you can access Windows Embedded 2009 Standard from the Start Menu.

We’ll review the rest of the process on the following posts.

Check also:

Windows Embedded Standard 2009 Step-by-Step Deployment – Part II

Windows Embedded Standard 2009 Step-by-Step Deployment – Part III

Cheers!

11 Comments »

RSS feed for comments on this post. TrackBack URI

[...] Windows Embedded Standard 2009 Step-by-Step Deployment – Part I [...]

Pingback by Windows Embedded Standard 2009 Step-by-Step Deployment – Part III « Augusto Alvarez— April 26, 2009 #

Reply
[...] Windows Embedded Standard 2009 Step-by-Step Deployment – Part I [...]

Pingback by Windows Embedded Standard 2009 Step-by-Step Deployment – Part II « Augusto Alvarez— April 26, 2009 #

Reply
[...] PART-3 After reviewing the necessary steps for preparing our environment (Post I) and building a custom image for a thin client (Post II); we’ll prepare the remote boot process [...]

Pingback by Windows Embedded Standard 2009 Step-by-Step Deployment— May 14, 2010 #

Reply
well you’ll probably think i’m a retard.
but still im going to give it a try.
I’m trying to deploy a network bootable xp embedded

this i my setup: (probably wrong)

I have NAT Router DSL line. With DHCP activated.
This one is connected trough a switch with my 2003 server R2 (my second NIC is disconnected)
I have the machine that needs to be remote booted also connected to this switch.
I did al the steps set up the DHCP server added the lines in CMD a written above.
The image worked when i hooked it up in to the target pc with the second disk.
The remote boot manager is configured. the ramdisk.sdi is in place.

but the target machine doesn’t receive the boot image.
what am i doing wrong. My best gues is that the network cabling is OK.

Thanks in advance and sorry for the crappy english

Comment by Rutten Glenn— July 20, 2011 #

Reply
- Hello Rutten,
  What is exactly the error you are receiving when you try to boot from PXE?
  Best regards,
  Augusto
  
  Comment by Augusto Alvarez— July 20, 2011 #
  
  Reply
Hello. Is it possible to make a repair in W embedded like in XP Pro. Like repairing the installation and repairing the boot and all the tricks one uses to revive a corrupted windows? My particular problem: BSOD telling me “config_list_failed” at the very start, after the Windows splash screen. So before I delve into my classic arsenal of tricks I will like to know if I can use Recovery Console (with a regular WXP disk), bootfix and other methods of performing CPR for a regular installation.
Thank you.
PS. none of the F8 options helped.

Comment by Adolfo Villanueva— August 25, 2011 #

Reply
- Hello there,
  The possibilities depend on the components you installed in that Windows Embedded, remember that this is a reduced version of the OS and not all components are included.
  Regarding that error, did you check this link? http://www.realgeek.com/forums/windows-xp-embedded-stop-error-during-boot-320454.html
  Hope it helps,
  Augusto
  
  Comment by Augusto Alvarez— August 25, 2011 #
  
  Reply
  - Yup. I saw it, didn’t help. Thank you for your reply though. I’m trying to make a repair with the Recovery console but it keeps resetting on me. If I can fix it I’ll let you know how so other victims of this failure can benefit from it. Adolfo.
    
    Comment by Adolfo— August 25, 2011 #
I don’t see my last post saying that I did see that link already and didn’t help at all. But I already fixed the problem and I’m going to tell you what was generating the error and what, ultimately corrected the issue. Since I had already exhausted all the regular procedures to try to get into DOS, (Recovery console was resetting on me every time I got to the option of what disc I wanted to select), I opted for an old utilities disc I had in my bag: Hiren’s boot CD. This disc comes with an option called “mini Windows XP”, which allows you to run a (limited) version of windows and allows you to see the c: disc on the computer. Well it seemed there was a large number of corrupted files in there. Luckily checkdisk worked and told me there were a bunch of broken chains. So with the option chkdsk /F it turned all those open links into files and PRESTO, I can get to the Windows installation again. I hope this helps somebody along the way when the dreadful BSOD gives you the CONFIG_LIST_FAILED stop sign. Cheers.
Adolfo

Comment by Adolfo Villanueva— August 25, 2011 #

Reply
hi augustu

i am mr abbas from iran.i want to install win xpe2009 standard. but i dont kno which component is need for my computer. i added some component but i couldnt boot it right.can yu help me.
i need ewf protocole,add hardware in my embedded and our fonts too.

Comment by abbas alaghaw— December 22, 2011 #

Reply
hi augusto
i am making a image base on yur instruction. but the system will be restart everytime.
i dont know that are there a conflict between some component or not.
pls lead me.

Comment by abbas alagha— January 9, 2012 #

Reply

	Augusto Alvarez on StarWind Contest and the iPad…
	Kenneth Sanchez on StarWind Contest and the iPad…
	Augusto Alvarez on StarWind Contest and the iPad…
	Kenneth Sanchez on StarWind Contest and the iPad…
	abbas alagha on Preparing and Installing Windo…

Augusto Alvarez