<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Use PowerShell to Troubleshoot Windows</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2011/07/09/use-powershell-to-troubleshoot-windows.aspx</link><description>Summary : Learn how to use Windows PowerShell to troubleshoot Windows by working with ETW logs.</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Use PowerShell to Troubleshoot Windows</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2011/07/09/use-powershell-to-troubleshoot-windows.aspx#3441279</link><pubDate>Wed, 13 Jul 2011 07:49:26 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3441279</guid><dc:creator>Bigteddy</dc:creator><description>&lt;p&gt;Very interesting article, Ed. Thanks. &amp;nbsp;Just one thing: Enabling a trace doesn&amp;#39;t work like you describe on my Win7 machine. I have to go to the Properties of the Trace, and check the checkbox that says &amp;quot;Enable logging&amp;quot;.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3441279" width="1" height="1"&gt;</description></item><item><title>re: Use PowerShell to Troubleshoot Windows</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2011/07/09/use-powershell-to-troubleshoot-windows.aspx#3440510</link><pubDate>Sat, 09 Jul 2011 14:07:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3440510</guid><dc:creator>jrv</dc:creator><description>&lt;p&gt;Very useful. &amp;nbsp;Just saved me a lot of time with trial and error and doc searching.&lt;/p&gt;
&lt;p&gt;Thank You Ed.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3440510" width="1" height="1"&gt;</description></item><item><title>re: Use PowerShell to Troubleshoot Windows</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2011/07/09/use-powershell-to-troubleshoot-windows.aspx#3440506</link><pubDate>Sat, 09 Jul 2011 12:37:51 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3440506</guid><dc:creator>Klaus Schulte</dc:creator><description>&lt;p&gt;Hello Ed,&lt;/p&gt;
&lt;p&gt;good to know about the new logging capabilities and how to enable them!&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a bit of a teaser today and I&amp;#39;m very excited to read the following&lt;/p&gt;
&lt;p&gt;articles! I really need some tracing on applications that stop working &lt;/p&gt;
&lt;p&gt;unexpectedly in my daily work. Mabye these logs can help to detect what&lt;/p&gt;
&lt;p&gt;caused this behaviour ....&lt;/p&gt;
&lt;p&gt;Klaus&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3440506" width="1" height="1"&gt;</description></item></channel></rss>