<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>Practical PowerShell</title>
	<link>http://www.jansveld.net/powershell</link>
	<description>Observations and examples of PowerShell in the real world</description>
	<lastBuildDate>Mon, 22 Dec 2008 20:29:48 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Split-Job 0.93</title>
		<description><![CDATA[Wow, it has been a long time since I had time to post anything on this blog. However, I have been making some improvements to the Split-Job script over the last few months and the results are below. I use this script myself a lot and I hope this is useful for some of you as well.  Please [...]]]></description>
		<link>http://www.jansveld.net/powershell/2008/12/split-job-093/</link>
			</item>
	<item>
		<title>Split-Job 0.92</title>
		<description><![CDATA[Here is an update to the Split-Job function. Based in part on some of the comments on the previous version, I made the following changes:

The format for the scriptblock has changed; this was done to make it more straightforward to specify parameters for those commands/scripts that accept pipeline input. If you need a foreach (%) you will have [...]]]></description>
		<link>http://www.jansveld.net/powershell/2008/06/split-job-092/</link>
			</item>
	<item>
		<title>Get-ChildItem is not dir!</title>
		<description><![CDATA[Here is a simple but practical tip from the trenches. If you made the switch and are using PowerShell as your main console, you may have noticed that the dir command can be rather sluggish in large directories. While an attempt was made to make the transition to native PS CmdLets easier by making &#034;dir&#034; [...]]]></description>
		<link>http://www.jansveld.net/powershell/2008/06/get-childitem-is-not-dir/</link>
			</item>
	<item>
		<title>Split-Job: make your PC work harder</title>
		<description><![CDATA[When you need to run a simple process or gather (WMI) data from many machines, you need a lot of patience. Or, you can divide and conquer using multiple PowerShell runspaces. There are many ingenious scripts available on the web that allow us to launch and manage background processes (even for PS v1). For my [...]]]></description>
		<link>http://www.jansveld.net/powershell/2008/06/split-job-version-0-9/</link>
			</item>
	<item>
		<title>Select-Properties: a helper for exporting DirectoryEntry objects</title>
		<description><![CDATA[When you work with DirectoryEntry objects (AD or local accounts), you quickly run into the fact that their properties are actually PropertyValueCollections. This trips you up with certain operations, like exporting entries. For instance, the following will not work:
# Get some user accounts
$Users = ([ADSI]&#039;WinNT://.&#039;).PSBase.Children &#124; where {$_.PSBase.SchemaClassName -eq &#039;User&#039;}
# Export them to a CSV [...]]]></description>
		<link>http://www.jansveld.net/powershell/2008/06/select-properties-a-helper-for-exporting-directoryentry-objects/</link>
			</item>
	<item>
		<title>Show-Progress: a quick progress bar</title>
		<description><![CDATA[Often times I need to run some command on a large set of objects, say a WMI query on a few hundred PCs. Here is a simple script to have an easy way to show a progress bar using the built-in Write-Progress cmdlet. In my PS profile it is aliased as &#034;bar&#034; so I can do the following:
Get-Content [...]]]></description>
		<link>http://www.jansveld.net/powershell/2008/05/show-progress-a-quick-progress-bar/</link>
			</item>
</channel>
</rss>
