., which is included with Windows Embedded POSReady 2009, was updated to Windows Preinstallation Environment (Windows PE) 2005 (the version that was included with Windows Server 2003 Service Pack (SP) 1 and Windows Fundamentals for Legacy PCs (WinFLP). Setup continues to run in the Microsoft.NET Framework 1.1; however, Setup may install the.NET Framework 2.0 and/or the.NET Framework 3.5 if selected. In Windows Embedded Point of Service (WEPOS), optional components were installed by a file from components that were derived from the Windows Embedded components. Now, they are installed by a, by using files on the installation media in the i386 directory.

• Windows Embedded 2009

Download Update for Windows Embedded POSReady 2009 (KB3055973) from Official Microsoft Download Center.

This matches the Windows XP method of installing or uninstalling components. Microsoft.NET Framework and Microsoft POS for.NET are installed through their own installers. The base OS is still installed by a.wim file. In POSReady, optional components include not only programs, but also fonts (Asian and Complex Script) and Multilanguage User Interface (MUI), whereas WEPOS included only programs. Additionally, in POSReady, the user can install and uninstall these components. The Unattend.xml file that Setup uses changed significantly after WEPOS.

The biggest change relates to selecting components. WEPOS used a hard-coded list, whereas POSReady is more data-driven. There is no separate Unattended Generator utility for POSReady. Therefore, to make an Unattend.xml file, you must run a /GUIOnly setup. Pre/Post Setup scripts are the same. USB boot is also natively supported in Setup for POSReady. For more information, see.

What is the difference between POSReady 2009 and Windows XP Professional?. Windows Embedded POSReady 2009 contains the following Embedded Enabling Features:. File-Based Write Filter (FBWF), which redirects writes to disk to RAM and helps protect the underlying OS image. USB Boot, which allows installation from a USB key. Office productivity applications are not licensed to be run on POSReady.

POS for.NET is included with POSReady. POSReady does not contain Help files, which reduces its footprint. Both products use the same management software.

For more information, see. What is the difference between POSReady 2009 and Windows Embedded Standard 2009?. Windows Embedded POSReady 2009 is optimized with only the features and components necessary for full-function POS devices in retail and hospitality organizations. This product is an installable operating system much like Windows XP, whereas Windows Embedded Standard 2009 is a toolkit for creating a custom operating system on a development computer prior to deploying to the production systems.

POSReady can use Windows XP Professional drivers. You do not have to componentize drivers as for Standard 2009. POSReady does not offer the Embedded Enabling Feature: Enhanced Write Filter (EWF). POSReady supports POS for.NET to interface with Unified Point of Service UnifiedPOS-standard peripherals.

POSReady contains Microsoft Silverlight 2.0. Windows Embedded Standard 2009 includes Silverlight 1.0. POSReady provides Language Collections. For more information, see.

What is WinPE and how does it relate to POSReady 2009? Windows Embedded POSReady 2009 is built on the Windows XP Professional base. Applications that are compatible with Windows XP Professional should run on POSReady. As always, you must thoroughly validate your applications to guarantee that they behave as expected before you deploy them to production. You must also review applicable licensing agreements to make sure you can use the application on POSReady.

For example, applications such as Microsoft Office are restricted, thereby preventing the user from using the application on POSReady. Can custom security templates be used on POSReady 2009? Windows Embedded POSReady 2009 uses the same language collections as Windows XP. In Windows XP, the 17 Language Groups that have been central to international support in Windows 2000 have been consolidated into three major Language Collections to simplify installation and improve user experience. The Language Collections are as follows:.

Basic collection (installed on all languages of the OS). Complex script collection (always installed on Arabic and Hebrew localized operating systems). East Asian collection (always installed on operating systems localized for East Asian) Language Collections offer expanded functionality over language groups. They allow the use of more locales and languages without the inconvenience of constantly adding or removing desired languages, thus improving multilingual computing and reducing IT support costs. For more information about Language Collections, see the following Microsoft Web sites:.

You can only run Windows Embedded POSReady 2009 Setup on the version of Windows PE included on the installation media, which is incompatible with. To do a deployment, you must first install POSReady on a reference device and then capture the image to a.wim file by using a capture utility. To run an unattended installation from a share, if your WDS role is currently installed in 'mixed' mode, you can set up a POSReady image for WDS Legacy installation.

For more information, see Installing POSReady by Using Remote Desktop in POSReady Help. POSReady Setup requires a custom version of Windows Preinstallation Environment 2005 (1.x) that has.NET 1.1 support. POSReady Setup will not work with Windows Preinstallation Environment 2.0. POSReady Setup relies on Plug and Play information from Windows Preinstallation Environment 1.x (XP kernel) to install device drivers.

Windows PE 2.0 is based on the Vista Kernel and has different Plug and Play data associated with it. You can do an image installation from Server 2008 WDS. However, you cannot run Setup in this environment because you cannot replace the Windows PE 2.0 boot image with the custom Windows PE 2005 image. You must use Server 2003 RIS if you want to deploy your image by using the POSReady Setup wizard. Why is my custom script specified in the GUIRunOnce section of sysprep.inf not executed after Sysprep runs? You can add the commands from your script directly into the HKEYCURRENTUSER Software Microsoft Windows CurrentVersion Runonce registry key so they are present for first login. If you want to use Sysprep and you are using the Registry Filter service, you must disable the Registry Filter service.

Windows Embedded 2009

The Registry Filter service complements the File Based Write Filter service; you should disable both in a session prior to the session when you run Sysprep. RunOnce commands in sysprep.inf will execute successfully after you disable the Registry Filter service with a REG file containing the following. There is a VB Script file on POSReady images that you can use to determine which OS is deployed, as follows:. If the file windows system32 osver.vbs exists, this indicates that the OS is POSReady. The logic in osver.vbs shows you how to check the OS version. Running osver.vbs displays an informational dialog box indicating which OS the customer is running.

You would need to deploy osver.vbs on Windows Embedded Point of Service or Windows XP, but it will support either OS. You can also click Start, click Run, type winver.exe, and then click OK. How can I manage and update my connected POSReady device? Yes, you can use System Center Configuration Manager (ConfigMgr) or System Center Operations Manager (SCOM) to manage POSReady machines. To distinguish POSReady or Windows Embedded Point of Service from other machines on the network you can extend the hardware inventory to collect information in the registry, such as querying the product version from the HKLM Software Microsoft Windows Embedded Point of Service Version or HKLM Software Microsoft POSReady Version registry keys. For more logic to identify the OS, see the OSVER.VBS file included with POSReady in the Windows System32 directory. Can I use FBWF as antivirus protection on POSReady 2009?

The following tools can be used perform security checks and to monitor the health of the device. Microsoft Baseline Security Analyzer (MBSA), which you use to determine the security state of the device for compliance with Microsoft security recommendations.

It also offers specific remediation guidance. You can download MBSA from the.

Windows Firewall (included in POSReady), which monitors the health of your device. Group Policy tools (included in POSReady), which you use to review local/domain security policies for your device.