<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://powershell.com/cs/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>Ravikanth's Blog : PowerShell Scripting</title><link>http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell+Scripting/default.aspx</link><description>Tags: PowerShell Scripting</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 (Build: 30929.2835)</generator><item><title>PowerShell 3.0: Save-Help woes and solution</title><link>http://powershell.com/cs/blogs/ravikanth/archive/2012/05/05/powershell-3-0-save-help-woes-and-solution.aspx</link><pubDate>Sat, 05 May 2012 11:22:05 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:16381</guid><dc:creator>From Ravikanth's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/ravikanth/rsscomments.aspx?PostID=16381</wfw:commentRss><comments>http://powershell.com/cs/blogs/ravikanth/archive/2012/05/05/powershell-3-0-save-help-woes-and-solution.aspx#comments</comments><description>PowerShell 3.0 introduced updateable help feature because of which there is no in-box help. We need to use Update-Help and Save-Help cmdlets to update the help content from Microsoft download sites. Now, this is a great feature to help people get up-to...(&lt;a href="http://powershell.com/cs/blogs/ravikanth/archive/2012/05/05/powershell-3-0-save-help-woes-and-solution.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=16381" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell+Scripting/default.aspx">PowerShell Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/vNext/default.aspx">vNext</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Windows+8/default.aspx">Windows 8</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Save-Help/default.aspx">Save-Help</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Updateable+Help/default.aspx">Updateable Help</category></item><item><title>Accessing Windows Imaging Application Platform Interface (WIMGAPI) in PowerShell</title><link>http://powershell.com/cs/blogs/ravikanth/archive/2012/04/24/accessing-windows-imaging-application-platform-interface-wimgapi-in-powershell.aspx</link><pubDate>Tue, 24 Apr 2012 09:56:20 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:16138</guid><dc:creator>From Ravikanth's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/ravikanth/rsscomments.aspx?PostID=16138</wfw:commentRss><comments>http://powershell.com/cs/blogs/ravikanth/archive/2012/04/24/accessing-windows-imaging-application-platform-interface-wimgapi-in-powershell.aspx#comments</comments><description>If you have used the Deployment Imaging Servicing Management (DISM) cmdlets in Windows 8 (Server or Client), you would have quickly realized that the functionality is limited only to certain basic tasks around image servicing and tasks such as capturing...(&lt;a href="http://powershell.com/cs/blogs/ravikanth/archive/2012/04/24/accessing-windows-imaging-application-platform-interface-wimgapi-in-powershell.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=16138" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell+Scripting/default.aspx">PowerShell Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Windows+8/default.aspx">Windows 8</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Windows+7/default.aspx">Windows 7</category></item><item><title>Attaching scripts or tasks to Windows event log entries using PowerShell and WMI</title><link>http://powershell.com/cs/blogs/ravikanth/archive/2011/06/24/attaching-scripts-or-tasks-to-windows-event-log-entries-using-powershell-and-wmi.aspx</link><pubDate>Fri, 24 Jun 2011 09:27:57 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:10999</guid><dc:creator>From Ravikanth's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/ravikanth/rsscomments.aspx?PostID=10999</wfw:commentRss><comments>http://powershell.com/cs/blogs/ravikanth/archive/2011/06/24/attaching-scripts-or-tasks-to-windows-event-log-entries-using-powershell-and-wmi.aspx#comments</comments><description>During a few load test iterations on a SharePoint farm, I started seeing some SQL exceptions in the application log of SharePoint servers. If you are familiar with SharePoint platform, you may have seen these events such as event ID 3355. This event complains...(&lt;a href="http://powershell.com/cs/blogs/ravikanth/archive/2011/06/24/attaching-scripts-or-tasks-to-windows-event-log-entries-using-powershell-and-wmi.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=10999" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell+Scripting/default.aspx">PowerShell Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/WQL/default.aspx">WQL</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/wmi/default.aspx">wmi</category></item><item><title>Passing variables or arguments to an event action in PowerShell</title><link>http://powershell.com/cs/blogs/ravikanth/archive/2011/06/22/passing-variables-or-arguments-to-an-event-action-in-powershell.aspx</link><pubDate>Wed, 22 Jun 2011 12:17:14 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:10960</guid><dc:creator>From Ravikanth's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/ravikanth/rsscomments.aspx?PostID=10960</wfw:commentRss><comments>http://powershell.com/cs/blogs/ravikanth/archive/2011/06/22/passing-variables-or-arguments-to-an-event-action-in-powershell.aspx#comments</comments><description>I was helping @LaerteSQLDBA to add PowerShell eventing support in his most recent script for performing SQL restores using SMO. He has a complex script where events are used inside a background job. And, in another event subscription outside the job,...(&lt;a href="http://powershell.com/cs/blogs/ravikanth/archive/2011/06/22/passing-variables-or-arguments-to-an-event-action-in-powershell.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=10960" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell+Scripting/default.aspx">PowerShell Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell/default.aspx">PowerShell</category></item><item><title>PowerShell to watch TechEd 2011 sessions</title><link>http://powershell.com/cs/blogs/ravikanth/archive/2011/05/23/powershell-to-watch-teched-2011-sessions.aspx</link><pubDate>Mon, 23 May 2011 14:48:21 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:10646</guid><dc:creator>From Ravikanth's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/ravikanth/rsscomments.aspx?PostID=10646</wfw:commentRss><comments>http://powershell.com/cs/blogs/ravikanth/archive/2011/05/23/powershell-to-watch-teched-2011-sessions.aspx#comments</comments><description>Now that TechED North America is done, all the sessions are now available for offline viewing at https://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/RSS/. There were some great PowerShell sessions by Windows PowerShell team and MVPs. So, I quickly...(&lt;a href="http://powershell.com/cs/blogs/ravikanth/archive/2011/05/23/powershell-to-watch-teched-2011-sessions.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=10646" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell+Scripting/default.aspx">PowerShell Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/Scripting/default.aspx">Scripting</category><category domain="http://powershell.com/cs/blogs/ravikanth/archive/tags/PowerShell/default.aspx">PowerShell</category></item></channel></rss>