Okay… I hope I’m not the last person in the world to have figured this out or I’ll feel dumber than I already do.

I’ve been messing with PowerShell a lot and couldn’t figure out what the difference was between write-output and write-host, two cmdlets that both APPEAR to do the same thing. But now I get it.

My first …

The Get-Culture cmdlet in Windows PowerShell does not actually give you an appreciation for art, fine wine, classical music, or opera.

While in Barcelona, I got a sneak peek at how PowerShell will – in a future version – handle remoting. It’s pretty cool. Say you start with this:

Get-Service

Simple enough, right? This uses gets a list of all services on the local computer. In fact, this runs in-process, meaning it executes within the current instance of PowerShell. Now try …

I’ve had a bunch of folks ask, recently, why PowerShell has an [ADSI] type accelerator, but doesn’t have an Active Directory PSDrive. I’ve also wondered a bit, myself about why PowerShell’s [ADSI] type doesn’t work as well with WinNT queries as it does with LDAP queries.

To elaborate: You can, in PowerShell, do something like this:

[ADSI]$user = “LDAP://cn=DonJ,ou=Tech,dc=domain,dc=com”

And …

Windows PowerShell will be a great asset to all administrators, regardless of your scripting ability. Here are my top 5 reasons I am going to love working with PowerShell.

The System Center 2007 Team has started a blog about how it will use PowerShell as its management shell. In case you were wondering, System Center 2007 will eventually replace Microsoft Operations Manager (MOM).

This is going to get interesting as more and more products move to PowerShell.