<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Updating Windows Embedded Standard systems using WSUS</title><link>http://blogs.msdn.com/embedded/archive/2008/12/23/updating-windows-embedded-standard-systems-using-wsus.aspx</link><description>**Updated 3/26/09 with preface [The following article is authored by one of the Windows Embedded MVPs (Most Valuable Professionals). Our MVPs have a heavy background in Embedded systems and are a great repository of information on Windows Embedded products.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Updating Windows Embedded Standard systems using WSUS</title><link>http://blogs.msdn.com/embedded/archive/2008/12/23/updating-windows-embedded-standard-systems-using-wsus.aspx#9541367</link><pubDate>Thu, 09 Apr 2009 23:30:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9541367</guid><dc:creator>Amante Mangaser</dc:creator><description>&lt;p&gt;We have WUAgent3.0 on a client and setup an intranet server with WSUS. But during WSUS installation, there is no OS option for Windows Embedded Standard. Which do we use, just Win XP?&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
</description></item><item><title>re: Updating Windows Embedded Standard systems using WSUS</title><link>http://blogs.msdn.com/embedded/archive/2008/12/23/updating-windows-embedded-standard-systems-using-wsus.aspx#9547984</link><pubDate>Tue, 14 Apr 2009 08:55:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9547984</guid><dc:creator>Alexander Wechsler</dc:creator><description>&lt;p&gt;Yes, there is no option for WES. Choosing the Windows XP optionis fine. Having the WES systems grouped in one or more dedicated collections is the way you could target them for updating.&lt;/p&gt;
</description></item><item><title>re: Updating Windows Embedded Standard systems using WSUS</title><link>http://blogs.msdn.com/embedded/archive/2008/12/23/updating-windows-embedded-standard-systems-using-wsus.aspx#9893325</link><pubDate>Thu, 10 Sep 2009 00:18:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9893325</guid><dc:creator>Domenic Ciancarelli</dc:creator><description>&lt;p&gt;How does the WSUS get around EWF on the WES devices?&lt;/p&gt;
</description></item><item><title>re: Updating Windows Embedded Standard systems using WSUS</title><link>http://blogs.msdn.com/embedded/archive/2008/12/23/updating-windows-embedded-standard-systems-using-wsus.aspx#9893451</link><pubDate>Thu, 10 Sep 2009 06:49:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9893451</guid><dc:creator>Alexander Wechsler</dc:creator><description>&lt;p&gt;There is currently no tool or mechanism for WSUS that allows to &amp;quot;get around&amp;quot; EWF. A workaround could be to turn off EWF on the target group of EWF devices e.g. via script and then roll out the update. EWF, of course should be turned on afterwards. &lt;/p&gt;
</description></item></channel></rss>