Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
ABOUT THE BLOGGER
Pavel BanskyProgram Manager
Pavel Bansky is a Program Manager on the Windows Embedded team in Microsoft. Pavel joined Microsoft in 2006, working in consulting services and field engineering, with a focus on mobile and embedded solutions. Inside the Windows Embedded team he worked on extensibility features of Windows Embedded Device Manager 2011 and its SDK. Currently he is working on Windows Embedded Compact.
Pavel likes to spend his time in the mountains around Seattle, where he hikes, snowboards or rides his motorcycle. When not outside, he likes to play with micro controllers and explore how things work.
Posted By Pavel BanskyProgram Manager
Good morning [place your current location here] and welcome to Approaching Embedded Intelligently. My name is Pavel Bansky and I work as a Program Manager in Windows Embedded team. I will be writing posts not only about Windows Embedded Device Manager but also other cool stuff we are doing here in Windows Embedded. Let me start with this Q&A article and stay tuned for more.
Windows Embedded Device Manager 2011 has been available on the market for about a year now. As the number of potential or actual users is increasing, there is a set of frequently asked questions that I hear. Let me go through the top ten of these questions in this article.
Comments Windows Embedded Standard
In today’s blog post I will look at a database for Windows Embedded Compact. Specifically I will look at SQLite which is becoming more and more popular, and compare it to good old SQL CE.
Comments Windows Embedded Compact
I want to describe you a situation and I’m sure you are familiar with it: You come across a digital signage device or point of sale terminal and there is an error code showing on the Windows desktop. The device is inactive, waiting for someone to reboot it. This is not just pretty lame; it might hurt your service or your company if you allow it to happen.
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
Thanks for checking back to Windows Embedded blog, I hope you won’t be disappointed. Today I want to write about an interesting usage of a Windows Embedded powered Thin Client. A friend of mine who works in Microsoft Support for Windows Phone was solving an interesting problem. One of the customers had issues accessing a particular webserver using Windows Phone. The webserver was using some certificate-based authentication and failed to authenticate the Windows Phone device. The question was: is it a problem with the phone or the server, or is the problem somewhere else? The first step was to capture and analyze the network traffic between the phone and server. Now, how to do it? There is nothing like WireShark for Windows Phone, so we can’t capture traffic there. Same on the server side, because the server is who knows where. So, I suggested capturing the traffic on the wireless router, but in order to do that we needed to build a router that allows network traffic to be captured.