<?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>Search results for 'app:weblogs' matching tag 'scripting'</title><link>http://powershell.com/cs/search/SearchResults.aspx?q=app:weblogs&amp;tag=scripting&amp;orTags=0&amp;o=DateDescending</link><description>Search results for 'app:weblogs' matching tag 'scripting'</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 (Build: 30929.2835)</generator><item><title>Adding System Path to CIMInstance Objects</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/06/13/adding-system-path-to-ciminstance-objects.aspx</link><pubDate>Thu, 13 Jun 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:24250</guid><dc:creator>Anonymous</dc:creator><description>The other night when I presented for the Mississippi PowerShell Users&amp;#8217; Group, one of the members showed some PowerShell 3.0 code using the CIM cmdlets. At issue is how the CIM cmdlets handle the WMI system properties like __SERVER and __RELPATH. By default, those properties aren&amp;#8217;t displayed, but they are captured in the CimSystemProperties property. [...]</description></item><item><title>Turning CLI Tools into PowerShell Tools</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/06/12/turning-cli-tools-into-powershell-tools.aspx</link><pubDate>Wed, 12 Jun 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:24158</guid><dc:creator>Anonymous</dc:creator><description>Last night I gave a presentation for the Mississippi PowerShell User Group. My talk was based on the chapter I contributed to the forthcoming PowerShell Deep Dives book. In the chapter I explore different techniques for turning command line tools into PowerShell tools. My presentation demonstrated those techniques in action. As promised, I&amp;#8217;ve bundled my [...]</description></item><item><title>Friday Fun: It’s PowerShell, Baby!</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/06/07/friday-fun-it-s-powershell-baby.aspx</link><pubDate>Fri, 07 Jun 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:24026</guid><dc:creator>Anonymous</dc:creator><description>The other day I received an email looking for guidance on using Invoke-Webrequest to pull data from a table on a web page. Specifically, he wanted to get the list of popular baby names from http://www.ssa.gov/OACT/babynames/index.html. I gave him some quick tips but figured this would also be another teaching opportunity. Using Invoke-Webrequest with PowerShell [...]</description></item><item><title>Test 64-Bit Operating System</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/16/test-64-bit-operating-system.aspx</link><pubDate>Thu, 16 May 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23526</guid><dc:creator>Anonymous</dc:creator><description>One of the great features of PowerShell is how much you can get from a relatively simple one line command. For example. you might want to test if a computer is running a 64-bit operating system. You can find out with a command as simple as this. [crayon-5194daf6859b0/] If you are running PowerShell 3 you [...]</description></item><item><title>Scrub Up PowerShell Content</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/14/scrub-up-powershell-content.aspx</link><pubDate>Tue, 14 May 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23460</guid><dc:creator>Anonymous</dc:creator><description>It is probably a safe bet to say that IT Pros store a lot of information in simple text files. There&amp;#8217;s nothing with this. Notepad is ubiquitous and text files obviously easy to use. I bet you have text files of computer names, user names, service names, directories and probably a few that are unique [...]</description></item><item><title>PowerShell Scripting Games 2013 Impressions</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/13/powershell-scripting-games-2013-impressions.aspx</link><pubDate>Mon, 13 May 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23440</guid><dc:creator>Anonymous</dc:creator><description>Now that the PowerShell Scripting Games for 2013 are well underway, I thought I&amp;#8217;d share my thoughts and impressions on what I&amp;#8217;ve seen. I&amp;#8217;m very impressed with the number of entries and generally the quality is pretty good. But as a judge I see repeated items that bear comment. These comments are in no particular [...]</description></item><item><title>Getting Top Level Folder Report in PowerShell</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/09/getting-top-level-folder-report-in-powershell.aspx</link><pubDate>Thu, 09 May 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23372</guid><dc:creator>Anonymous</dc:creator><description>One of the sessions I presented recently at TechDays San Francisco was on file share management with PowerShell. One of the scripts I demonstrated was for a function to get information for top level folders. This is the type of thing that could be handy to run say against the root of your shared users [...]</description></item><item><title>PowerShell Messagebox</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/08/powershell-messagebox.aspx</link><pubDate>Wed, 08 May 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23341</guid><dc:creator>Anonymous</dc:creator><description>Recently I posted an article explaining how to create a popup box in PowerShell using the Wscript.Shell COM object from our VBScript days. That was something I presented at the PowerShell Summit. Another option is a MessageBox, again like we used to use in VBScript. This works very much like the popup except the user [...]</description></item><item><title>Why Doesn’t My Pipeline Work?</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/05/07/why-doesn-t-my-pipeline-work.aspx</link><pubDate>Tue, 07 May 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23309</guid><dc:creator>Anonymous</dc:creator><description>I saw a little discussion thread on Twitter this morning which I felt needed a little more room to explain. Plus since we&amp;#8217;re in ScriptingGames season beginners might like a few pointers. I always talk about PowerShell, objects and the pipeline. But sometimes what looks like a pipelined expression in the PowerShell ISE doesn&amp;#8217;t behave [...]</description></item><item><title>PowerShell PopUp</title><link>http://powershell.com/cs/blogs/lonelyadministrator/archive/2013/04/29/powershell-popup.aspx</link><pubDate>Mon, 29 Apr 2013 05:00:00 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23103</guid><dc:creator>Anonymous</dc:creator><description>At the recent PowerShell Summit I presented a session on adding graphical elements to your script without the need for WinForms or WPF. One of the items I demonstrated is a graphical popup that can either require the user to click a button or automatically dismiss after a set time period. If this sounds familiar, [...]</description></item></channel></rss>