Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
ABOUT THE BLOGGER
Jeff Wettlaufer Sr. Technical Product Marketing Manager
Jeff Wettlaufer serves as a Sr. Technical Product Marketing Manager for Windows Embedded’s Marketing Team. In his 10 years at Microsoft, Jeff has specialized in technical consulting, sales and product marketing, event coordination and community management.
Jeff is recognized as a notable speaker for event scores and session attendance, and has delivered Technical Keynote Demonstrations to global audiences and been featured in the Microsoft TechEd and Microsoft Management Summit series of ITPro events. Jeff is also a regular participant in the Microsoft Partner Community, collaborating with SI and ISV partners to highlight their capabilities.
Outside of work, Jeff enjoys playing hockey (he grew up in Canada) cycling, skiing and golfing. He played basketball at Lock Haven University and University of Western Ontario, and rowed on Western Ontario’s crew team. Jeff continued his rowing for Vesta RC in the United Kingdom where he lived for seven years and originally joined Microsoft.
Jeff shares his love of sports, fitness, travel and cooking with his wife Daphne, a fellow Microsoftie, and their two children, Gavin and Imogen.
Posted By Jeff WettlauferSr. Technical Product Marketing Manager
With the release of Windows 8.1 and Windows Embedded 8.1, a new capability called Assigned Access has been introduced. This post will compare Assigned Access with the existing (and improved for 8.1) embedded lockdown features.
Assigned Access is a new feature offered in Windows 8.1 RT, Pro and Enterprise, and provides a way to enable a single Windows Store application experience on the device. Administrators can easily lock down a device through the PC settings by choosing a user profile and assigning a modern app to that profile.
When this is selected, the selected user account and app will be launched from boot (once authenticated). Assigned Access uses a pre-defined set of filters to block keyboard gestures, hardware buttons and system toast notifications to prohibit access to other apps or system settings. These cannot be changed, and the capability is restricted to one user and one modern (Windows 8 style) app.
Comments Product Updates
With the release of Windows Embedded 8.1 and our alignment to the Windows code base, a significant amount of new capability and tools are now available. In a recent blog, we talked about management for Windows Embedded; in this post, we’ll focus on deployment.
In the past, deployment for Windows Embedded products was, well, different. There were different tools, processes and procedures for standing up a master image of Windows Embedded. With 8.1, organizations can now use tools like the Assessment and Deployment Kit (ADK) for Windows 8.1, Microsoft Deployment Toolkit 2013 and System Center 2012 R2 Configuration Manager.
Comments Windows Embedded Standard
In this post, I would like to talk about the advancements we have made with our relationship with Microsoft System Center to manage Windows Embedded devices. As organizations today are looking to integrate intelligent connected devices into their existing distributed infrastructure (AD, Server, System Center), it has become more important than ever to ensure those devices are secure and well managed.
There are some classic challenges with managing embedded devices. I’ll highlight some of those general issues for you first, and then discuss how System Center has addressed these through Service Pack and R2.
Hi everyone. Last week, we achieved a major milestone within the Windows teams: the RTM of Windows 8.1 for both Windows and Windows Embedded platforms. In this post, I would like to share with you some technical highlights with the new release of Windows Embedded 8.1 Industry, and talk about some of the key elements that are new from a technical perspective.
It is important to first note a big change for Windows Embedded: In the past, the Embedded versions of Windows, right up to the 8 wave, were released a short period of time after the RTM of Windows Client. With the release of 8.1, Windows Embedded is aligned at an engineering level that not only effects timing of release, but the code base. Windows Embedded 8.1 is now built fully on Windows Client with Embedded features added (think of Embedded as a superset of capabilities over Client), and also on the same dates.
This alignment spans several levels of the stack. The hardware and OS stack are much more closely aligned than ever before, bringing better consistency for drivers and chipsets. Above the OS stack, we have integration with other infrastructure, such as identity (think AD) and development, deployment and management tools (Visual Studio x, System Center, Windows ADK and more) and at an app layer (with some API support for modern apps and industry specific peripherals). Finally, this alignment is more cloud-enabled than ever before, supporting smart, connected scenarios and services for edge devices.
With Microsoft Build Developer’s Conference (//Build/) running at full speed, we wanted to share some information about a compelling demo solution shown on the show floor featuring Kinect for Windows and Windows Embedded 8 Industry in an engaging in-store experience developed for the Amana brand.
The demo uses Kinect for Windows to track when a user physically interacts with the appliance, and to provide them with valuable information on the specific appliance they are touching. The concept is to enable a new, simple way for customers to interact and engage with home appliances on the sales floor, bringing features and benefits of each appliance to virtual life and driving purchasing decisions via simple gestures.
The Amana solution showcases the opportunity for developers to build rich app experiences on industry-specific hardware using the latest Microsoft tools and technologies. Specifically, it illustrates how developers can design not only beautiful Kinect for Windows-enabled experiences, but also targeted experiences unique to the retail setting with the Windows Embedded platform.
About the solution
From a hardware standpoint, the Amana demo is a complete 8' vignette that encompasses an Amana refrigerator, dishwasher, oven and microwave mounted in a cabinet with Kinect for Windows sensors positioned to capture customer and product interaction. One sensor is directed to where the customer interacts with appliances via a digital catalog projected on a large display; the other is pointed at the point of product interaction.
When a customer walks up to the experience, the application knows they are there and greets them with a friendly, eye-catching introductory screen. From there, the customer can navigate through the Amana catalog simply by gesturing and learn about a variety of features, such as appliance energy efficiency, easy-to-use options and more ways to save water, energy and money. All of this functionality is powered by Windows Embedded.
Comments Intelligent Systems