Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
Posted By J.T. Kimbell Program Manager
Hey everyone. You may have noticed posts were a bit sparser during the month of September as I was out on paternity leave spending time with my new little boy. However, I’m back and we’re ready to get the content flowing again.
We’ve had the privilege this summer of having quite a few interns in Windows Embedded and you’ve heard from five of them including Jordan Goldberg, the author of this post. In Jordan’s first post, he told us about his summer and his work on a Windows Debugger extension for Unified Write Filter (UWF). This time, he gets technical and explains the work needed to ensure your application functions correctly on a system with UWF enabled. To see any of the previous posts from our interns, click one of the links below.
Greetings from Redmond! Today I want to take some time to talk about a new feature in Windows Embedded Standard 8, Unified Write Filters (UWF), and the best way for adding support for applications. UWF takes the best of Enhanced Write Filter (EWF) and File-Based Write Filter (FBWF) and bundles in a few more features to create a complete Write Filter solution. As a quick overview, a Write Filter is a virtual overlay that can be applied to a volume and transparently capture all disk I/O. The overlay is then wiped each time a machine is rebooted. This can be useful in a scenario such as a public kiosk where all user data needs to be wiped after use. For more information on Unified Write Filters, check out this post.
The issue with supporting applications with Write Filters is that by default, all I/O is redirected to an overlay and wiped after reboot. This can be problematic for applications storing information in the registry and file system since the data will be lost regularly. In UWF, the way to prevent this is to set exclusions on the registry and file locations of where this information is being stored. This will cause the data to bypasses the overlay and get written directly to disk. However, applying these exclusions is not always user friendly since it can only be done through WMI, the Embedded Lockdown Manager (ELM) or the command line utility uwfmgr.exe.
Comments Windows Embedded Standard
Posted By David CampbellProgram Manager
At the recent Visual Studio launch event, it was confirmed that Visual Studio 2012 will once again include support for Windows Embedded Compact. Included in that support we’re targeting much of the newest compiler and tools functionality, most notable of which includes new compiler features such as C++11 language standards, faster more efficient code generated, an updated CRT, auto-parallelization and auto-vectorization (Wow, that’s a mouthful.), range based loops, RValue references, and more. Also included will be an updated version of .net CF which has greatly improved performance, particularly around memory allocation and garbage collection - using the “generational” garbage collector. This not only provides more performance, but more predictability in the execution of applications.
More information about the new Visual Studio, including support for Compact, can be found at the Visual Studio Launch site. (Yes, I’m in the video and no, I’m not going to be able to make a living in front of the camera. But it’s the message that’s important here.)
Be sure to check back in the future as we release more information on the upcoming Windows Embedded Compact release.
Comments Windows Embedded Compact
Posted By Barb EdsonGeneral Manager, Marketing and Business Development
Recently, I joined our partners at Ford for the European launch of Ford SYNC with MyFord Touch at the IFA consumer electronics show in Berlin.
At IFA Ford announced that this version of Ford SYNC—which includes a touchscreen interface—will be coming to Europe in 2013 in the Ford Focus Electric.
While I was at the conference I participated in a roundtable discussion with Ford and a few other industry experts to discuss the future of the connected car. The connected car focuses on how the vehicle experience can be enhanced when you integrate internet connectivity, data, and new user interface technologies like speech and touch.
The subject of the connected car is especially near and dear to us in Windows Embedded – and not only because Ford SYNC is built on the Windows Embedded Automotive software platform. When we talk about intelligent systems as the evolution of the embedded device market, it’s exciting to see how this is affecting the automotive industry.
Comments Windows Embedded Automotive
Posted By The Embedded Ninja
As we’ve seen in previous posts, Intelligent Systems touch every industry whether it be banking, retail, manufacturing, or healthcare. Today’s post showcases continuity of care and how Intelligent Systems can have a positive impact. Authored and presented by a member of The Embedded Ninja clan, Ben Smith shares his thoughts and some wonderful resources. Enjoy!
We really would love to hear feedback on usage of the video blog – as well as feedback on the content. Let us know how the ninjas are doing!
Posted By Pavel Bansky Program Manager
One of the most common questions asked by customers and users of Windows Embedded Device Manager 2011 is the applicability of group policies on write filter protected box. Although, most of the embedded devices usually operate outside of the domain, with Thin Clients in enterprises this is no longer true.
Windows Embedded Device Manager 2011 in combination with System Center Configuration Manager 2007 persist updates and configurations on write filter protected devices based on “on demand” principle. This maintenance task needs to be planned and scheduled from Configuration Manager Console. Group policies are usually updated outside of this maintenance task therefore they will never persists on the device, unless the timing for maintenance task crosses with timing for group policy update; which is very unlikely.
In this article I would like to give you step-by-step guide how to issue maintenance task for policy update from Configuration Manager Console to persist the updated policy. All we are going to do is create task sequence that will be disable write filters, run the gpupdate.exe and restore write filters again. This task sequence will have a mandatory assignment scheduled for 1am every night.
1) In System Center Configuration Manager console right click on Task Sequence node under the Computer Management. In the context menu select New Task Sequence