Since Windows Embedded Standard is Windows XP Professional, SP3 (a supported envrionment), it follows that WES would also be supported. The fact that certain "components" (e.g. unnecessary drivers, applications such as notepad, etc.) are excluded from a particular WES design should not render the minimized implementation of XP Pro to "unsupported" status.
So the questions is... why does SAP take this "non-support" position with regard to SAPgui for Windows running on WES? As long as the required components are included in the WES instance, the product will work. Perhaps SAP could publish a list of the XP Professional components that would qualify the WES implementation to SAP supported status.
Please help us better understand the situation?
The scenario where an enterprise wants to reduce costs and save money by deploying an SAPgui device, which would be defined as a workstation limited to running the SAPgui. The embedded version of Windows XP (aka Embedded Standard) is an ideal platform for creating an SAPgui for Windows workstation device.
Continuing to deploy PC hardware is expensive. When deploying full PCs, you have added costs associated with (1) maintaining the physical hardware, (2) maintaining the device operating system, (3) annual operating system licensing, (4) increased personnel resources, (5) software specific to protecting the environment, etc.. Embedded devices do not have near the associated costs and are dramatically less expensive ($2,000 to $4,000 per year per device) to operate.
There's also the fact that workstation devices running embedded operating systems are GREEN when compared to deploying full PCs. Since "Going green!" is a major initiative for most enterprises today, it makes even more sense that organizations want to deploy an embedded OS with all of its benefits.
What people want to know is "Will SAP support SAPgui for Windows running on the embedded version of Windows XP Professional, Service Pack 3, which Microsoft brands Windows Embedded Standard?"