msgoodies-powershell

Messing with output from Format-Table

Per Østergaard — Thu, 19 Nov 2009 13:26:00 -0800

Found at question at psobject.codeplex.com:

I was wondering if I could write the outout without any blank spaces between 2 fields. For example, I am using hash tables to display 2 columns from dir output. But it always comes up with a blank space between those 2 data elements. I need this to generate a fixed format output with data elements only and no spaces in between. Any help is greatly appreciated.

$column1 = @{expression="mode";width=5;label="mode";alignment="left"}
$column2 = @{expression="name";width=10;label="name";alignment="left"}

$dir |format-table $column1,$column2

$mode name
---- ----
d---- download
d---- extract
-a--- alias.txt
-a--- Compute...
-a--- execute...
-a--- get_dn.ps1
-a--- hh

Well, it can be done. I looked into the objects the Format-Table spit out and after some poking around, I came up with this -

$column1 = @{expression="mode";width=5;label="mode";alignment="left"}
$column2 = @{expression="name";width=20;label="name";alignment="left"}

# Save widths, all non-fixed length value should specify a width
$widths=@{}
dir | format-table $column1,@{l="|";e={"|"}},$column2 | foreach {
 if ($_.pstypenames[0] -eq "Microsoft.PowerShell.Commands.Internal.Format.FormatEntryData") {
 # Capture the values and convert them to one value
 $value=""
 $count=$_.formatentryinfo.formatPropertyFieldList.count
 foreach($i in 0..($count-1)) {
 $value+=$_.formatentryinfo.formatPropertyFieldList.item($i).propertyvalue.ToString().padright($widths.$i)
 }
 # Delete all but one field
 $_.formatentryinfo.formatPropertyFieldList.removerange(1,$count-1)
 # and update its value
 $_.formatentryinfo.formatPropertyFieldList.item(0).propertyValue=$value
 $_
 }
 elseif ($_.pstypenames[0] -eq "Microsoft.PowerShell.Commands.Internal.Format.FormatStartData") {
 # Capture the headers and convert them to one header
 $value=""
 $width=0
 
 $count=$_.shapeinfo.tablecolumninfolist.count
 foreach($i in 0..($count-1)) {
 $w=$_.shapeinfo.tablecolumninfolist.item($i).width
 $width+=$w
 $widths.$i=$w
 $value+=$_.shapeinfo.tablecolumninfolist.item($i).propertyname.ToString().padright($w)
 }
 # Delete all but one field
 $_.shapeinfo.tablecolumninfolist.removerange(1,$count-1)
 # and update its value
 $_.shapeinfo.tablecolumninfolist.item(0).propertyName=$value
 $_.shapeinfo.tablecolumninfolist.item(0).width=$width
 $_
 }
 else
 {
 $_
 }
}

If you like it, convert it to a function as en exercise ;)

Happy formatting!

PS Remoting to Home Server

Per Østergaard — Thu, 19 Nov 2009 08:25:00 -0800

I wanted to PowerShell remote to my home server, but as it is – for the good reason, that it is impossible – not in the domain of my PC, I have to add it to TrustedHosts.

This is my story.

First, I enabled PS remoting on the home server with a simple

Enable-PSRemoting

Next, I attempted to access the server

enter-pssession server -cre server\administrator

By doing so, I received a very long error message.

I tried with –authentication negotiate. This reduced the error message to 10 lines ;) It told me to configure TrustedHosts with Winrm.cmd.

I looked at Winrm.cmd, but that looked very complicated and this is at the end of the day. Luckily, the WSMAN drive popped up in my mind. I switched to my administrative account and did this

PS C:\Users\user> cd wsman:
PS WSMan:\> dir

 WSManConfig:

ComputerName Type
------------ ----
localhost Container

PS WSMan:\> cd .\localhost
PS WSMan:\localhost> dir


 WSManConfig: Microsoft.WSMan.Management\WSMan::localhost

Name Value Type
---- ----- ----
MaxEnvelopeSizekb 150 System.String
MaxTimeoutms 60000 System.String
MaxBatchItems 32000 System.String
MaxProviderRequests 4294967295 System.String
Client Container
Service Container
Shell Container
Listener Container
Plugin Container
ClientCertificate Container


PS WSMan:\localhost> cd .\Client
PS WSMan:\localhost\Client> dir


 WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Client

Name Value Type
---- ----- ----
NetworkDelayms 5000 System.String
URLPrefix wsman System.String
AllowUnencrypted false System.String
Auth Container
DefaultPorts Container
TrustedHosts System.String


PS WSMan:\localhost\Client> Set-Item .\TrustedHosts server

WinRM Security Configuration.
This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be authenticated. The
client might send credential information to these computers. Are you sure that you want to modify this list?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
PS WSMan:\localhost\Client>

Back to my standard user

194 WSMan:\localhost> enter-pssession server -cre server\administrator
[server]: PS C:\Documents and Settings\Administrator\My Documents>

and it worked.

Happy remoting

PowerShell 2.0 is supported for Exchange 2007 SP2

Per Østergaard — Mon, 16 Nov 2009 06:00:00 -0800

In case you wondered, the greatly improved PowerShell 2.0 can be installed on servers running Exchange 2007. But you must be running Service Pack 2.

BTW: You cannot find PowerShell v2 on www.microsoft.com/downloads. You have to go to http://support.microsoft.com/kb/968929.

Picking files with the mouse using Get-DroppedFile

Per Østergaard — Wed, 11 Nov 2009 02:22:00 -0800

Sometimes (often?) it is just easier picking your files with the mouse. As long as the files are in one folder that is not that hard, but if you have files scattered all around that is tougher. Also right-clicking and copy-as-path is annoying.

To make this easier, I have created a small drop box function. A small transparent window will be shows and when you drop files on it, those files will be send to the output pipeline where you can do the rest of your processing.

I made the forms part using Visual C#. Relativily trivial. And Add-Type enabled me to embed it into my script. The hard part was making it async so that files would appear ín the output pipeline as soon as they were dropped. I had to resort to good old VB5-style DoEvents (just revealed my age, I guess). If you can come up with a non-polling solution, please let me know.

What it can be used for -

Testing scripts with different files
Move photos to a folder, converting them as they are moved
Renaming files
Compressing files
continue the list yourself

All tasks where you – the human – can make the decision about what to do with a file are relevant.

With PowerShell v2 being available on all platform, do I have to say, that this is a V2-only script?

Please, read the comments in the script for further information.

Get-DroppedFile.ps1


<#
.Synopsis
 Create a drop box window and output the files dropped to the pipeline
.Description
 Create a drop box window. When files are dropped, they are send to the output pipeline right away.
 Stop Get-DroppedFile by closing the window.
.Inputs
 None
.Outputs
 File names (-asText), IO.DirectoryInfo or IO.FileInfo objects
.Example
 Get-DroppedFile | Copy -destination e:\ -passthru | foreach { $x.attributes=$x.Attributes.ToString()+",readonly" } 
 Copy dropped files to e:\ and set the readonly bit
#>
param(
   [string]
   # The caption of the drop box
   $Caption,
   [switch]
   # Return file names (full path) as text
   $AsText,
   [switch]
   # Recurse directories, I.E. the folder itself is not returned, only its children
   $Recurse,
   [switch]
   # (Internal switch used to detect -sta invocation)
   $_InternalReinvoked)

# Create the script code - direct execution or SingleThreadedApartment is determined later
$script={

$loaded=$false
try {
    $null=[system.type] "Get_DroppedFile.Form1"
    $loaded=$true
}
catch {}

# The form code. Created in Visual C# 2008 Express and slightly adopted
if (!$loaded) {
    add-type -TypeDefinition @'

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Drawing;
using System.Windows.Forms;

namespace Get_DroppedFile
{
 public partial class Form1 : Form
 {
 Color defaultColor;
 public Form1()
 {
 InitializeComponent();
 defaultColor = this.BackColor;
 
 }
 
 public void avoidWarning()
	{
	}
 
 private void Form1_DragDrop(object sender, DragEventArgs e)
 {
 // Back to default color
 this.BackColor = defaultColor;
 }

 private void Form1_DragOver(object sender, DragEventArgs e)
 {
 // Start dragdrop
 e.Effect = DragDropEffects.Copy;
 }

 private void Form1_DragEnter(object sender, DragEventArgs e)
 {
 // visual feedback in drag
 this.BackColor = Color.FromArgb(defaultColor.ToArgb() - 0x101010);
 }

 private void Form1_DragLeave(object sender, EventArgs e)
 {
 // restore color
 this.BackColor = defaultColor;
 }
 }
}

namespace Get_DroppedFile
{
 partial class Form1
 {
 /// <summary>
 /// Required designer variable.
 /// </summary>
 private System.ComponentModel.IContainer components = null;

 /// <summary>
 /// Clean up any resources being used.
 /// </summary>
 /// <param name="disposing">true if managed resources should be disposed; otherwise, false.</param>
 protected override void Dispose(bool disposing)
 {
 if (disposing && (components != null))
 {
 components.Dispose();
 }
 base.Dispose(disposing);
 }

 #region Windows Form Designer generated code

 /// <summary>
 /// Required method for Designer support - do not modify
 /// the contents of this method with the code editor.
 /// </summary>
 private void InitializeComponent()
 {
 this.SuspendLayout();
 // 
 // Form1
 // 
 this.AllowDrop = true;
 this.AutoScaleDimensions = new System.Drawing.SizeF(6F, 13F);
 this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;
 this.BackColor = System.Drawing.SystemColors.ActiveCaption;
 this.ClientSize = new System.Drawing.Size(116, 49);
 this.Cursor = System.Windows.Forms.Cursors.Default;
 this.MaximizeBox = false;
 this.MinimizeBox = false;
 this.Name = "Form1";
 this.Opacity = 0.75;
 this.ShowIcon = false;
 this.Text = "Drop Box";
 this.TopMost = true;
 //this.Load += new System.EventHandler(this.Form1_Load);
 this.DragLeave += new System.EventHandler(this.Form1_DragLeave);
 this.DragDrop += new System.Windows.Forms.DragEventHandler(this.Form1_DragDrop);
 this.DragEnter += new System.Windows.Forms.DragEventHandler(this.Form1_DragEnter);
 this.DragOver += new System.Windows.Forms.DragEventHandler(this.Form1_DragOver);
 this.ResumeLayout(false);

 }

 #endregion


 }
}

'@ -verbose -ReferencedAssemblies system.drawing,system.windows.forms
}

# Create our form object
$form=New-object get_droppedfile.form1

# Get rid of any events leftover
get-event get-droppedfile -erroraction silentlycontinue | remove-event

# Add handlers
# The handlers transfer the action/file to the main loop using event
$form.add_dragdrop( { $null=new-event -sourceidentifier get-droppedfile -messagedata $args[1].Data.GetData("FileDrop", $true)  })
$form.add_formclosed( { $null=new-event -sourceidentifier get-droppedfile -messagedata "[close]" })

#Register-ObjectEvent -InputObject $form -EventName dragdrop #-SourceIdentifier blah#
#Register-ObjectEvent -InputObject $form -EventName formclosed #-SourceIdentifier blah

# Custom caption
if ($caption) {$form.text=$caption}

# This is the tricky part. Dropping is quite simple, but feeding the output pipeline with
# the dropped files (so you do not have to wait until the drop box is closed) is not simple.
# I came up with this solution:
# - Do not use ShowDialog as is modal and will suspend PowerShell processing
# - use Show and doevents in a loop
# - this method consumes some CPU, but the Start-Sleep keeps it to a few per cent
# - The Event actions generates events and they are read here in the main loop
# and converted to file names which are sent to the pipeline

# Show the drop box
$form.show()

do {
  $e=get-event get-droppedfile -erroraction silentlycontinue # suppress no such events
	$exit=$e.messagedata -eq "[close]" # Test close message
	if ($e.messagedata -and !$exit) {$e.MessageData} # Send file to pipeline
	if ($e) {$e | remove-event} # Remove event from queue
	if ($exit) {break}
	start-sleep -m 100 # Wait a little
	[System.Windows.Forms.Application]::doevents() # React to form events so the windows can be moved etc.
} while($true)

# Shutdown
$form.close()
} # end of script assignment


# Generate command for -sta recursive call. Done here where $myinvocation has the right value
$command = "&'" + $myinvocation.mycommand.definition + "' -caption '$caption' -_InternalReinvoked"

# Execute the next in a scriptblock so output can be piped
&{

	# Forms must run in SingleThreadedApartment style
	# Re-invoke PowerShell if necessary
    if ($host.runspace.ApartmentState -ne "sta") {


     write-verbose "Invoking PowerShell with -sta"
        $bytes = [System.Text.Encoding]::Unicode.GetBytes($command)
        $encodedCommand = [Convert]::ToBase64String($bytes)
        powershell.exe -sta -noprofile -encodedCommand $encodedCommand
     #powershell -sta -noprofile $script
    }
    else {
     &$script
    }

} | where {$_} | foreach {
    # Handle the different return options
	if ($_InternalReinvoked.ispresent) {
        # -sta call, always return strings
 $_
	}
	elseif ($recurse.ispresent -and (test-path -pathtype container $_)) {
        # Recurse folder tree, return text or objects
 Get-ChildItem $_ -recurse -force | foreach {
 if ($astext.ispresent) {
 $_.fullname
 }
 else {
 $_
 }
 }
	}
	elseif ($astext.ispresent) {
 $_
	}
	else {
 Get-Item $_
	}
}

Have fun

PowerShell V2 now Available on Older Operating Systems

Per Østergaard — Mon, 02 Nov 2009 01:50:00 -0800

Now you can safely forget V1 and switch to the vastly superior V2. As of last week it is now available on -

Windows Server 2008 with Service Pack 2 Windows Server 2003 with Service Pack 2 Windows Vista with Service Pack 2 Windows Vista with Service Pack 1 Windows XP with Service Pack 3

In Windows 7 and WS08 R2 it is part of the package.

PS2 is part of Windows Management Framework which also includes WinRM and BITS4.

BTW: You need to install PowerShell 2 on server core. Read how in KB 976736.

DFS, IPv6 and – sort of – disabling it

Per Østergaard — Mon, 02 Nov 2009 00:22:00 -0800

Ask the Directory Services Team has a good article on troubleshooting DFS links (DFS Referrals and IPv6: Outta site!) as well as a discussion of how not to disable IPv6 (unbinding it from an adapter) and how to do it correctly (KB929852).

In case you really need to disable IPv6, consider using a Group Policy Preference or automate it with PowerShell -

Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters DisabledComponents 0xffffffff -type dword

Useful information.

Executing a PowerShell Pipeline from your own program

Per Østergaard — Fri, 30 Oct 2009 02:51:00 -0700

In Executing PowerShell code from within your own program I showed how to execute PowerShell code, but the interface was rather rude as the value had to be converted to string and added to the script code involved. If you have lots of objects to proces, this method is inefficient – a pipeline would be much better as the script source only has to be parsed once and the script would be able to access the objects as real objects.

I have now taken it a step further and created a piece of code that can execute a pipeline. If you have lots of objects – ‘lots’ depends on the amount of memory you have available – this may not be the most efficient method. All input and output objects will be represented as List<PSObject> giving some overhead. An alternative would be to use a steppable pipeline but for now, I’ll stick to the easy method.

Here’s the code

public class PSHost
{
 private PSDataStreams _InvokePipeline(string Script,
 List<PSObject> inputPipeline,
 out Collection<PSObject> outputPipeline)
 {

 PowerShell PS = PowerShell.Create();
 PS.AddScript(Script);

 outputPipeline=PS.Invoke<PSObject>(inputPipeline);
 return PS.Streams;
 }
 private string _ConvertStreamsToString(PSDataStreams streams)
 {
 string s = "";
 foreach (DebugRecord result in PS.Streams.Debug)
 {
 s += "DEBUG: " + result.ToString();
 }
 foreach (VerboseRecord result in PS.Streams.Verbose)
 {
 s += "VERBOSE: " + result.ToString();
 }
 foreach (WarningRecord result in PS.Streams.Warning)
 {
 s += "WARNING: " + result.ToString();
 }
 foreach (ErrorRecord result in PS.Streams.Error)
 {
 s += "ERROR: " + result.ToString();
 }
 return s;

 }

 public string PSExecutePipeline(string Script,
 List<PSObject> inputPipeline,
 out Collection<PSObject> outputPipeline)
 {

 PSDataStreams ds = _InvokePipeline(Script, inputPipeline, out outputPipeline);
 return _ConvertStreamsToString(ds);
 }
}

The script must include $input to pick up the values – if any. The streams collection is returned as a string, so you can check for warning/error/verbose/debug/progress output. Parsing errors will throw an exception; you would use a try-catch to handle that. Naturally, you can change the interface to your own requirements.

Note that output objects may be real objects with properties or just simple value types. A property value can be retrieved with p.property[“propertyname”].value and a simple with p.BaseObject.

Example 1 – summing numbers

// Input pipeline
List<PSObject> numbers = new List<PSObject>();

// Add values/objects
numbers.Add(new PSObject(1));
numbers.Add(new PSObject(2));
numbers.Add(new PSObject(3));
numbers.Add(new PSObject(4));
numbers.Add(new PSObject(5));

// Output pipeline
System.Collections.ObjectModel.Collection<PSObject> outputPipeline;

PSHost psh = new PSHost();
string s = psh.PSExecutePipeline("$input | measure-object -sum", numbers, out outputPipeline);
if (string.IsNullOrEmpty(s))
{
 foreach (PSObject p in outputPipeline)
 {
 System.Diagnostics.Debug.WriteLine("Sum is " + p.Properties["Sum"].Value.ToString());
 }
}
else
{
 System.Diagnostics.Debug.WriteLine("PowerShell failed: " + s);
}

Example 2 demonstrates how to return a value type

// Re-uses the variable from example 1
List<PSObject> empty = new List<PSObject>();
s = psh.PSExecutePipeline("100", empty, out outputPipeline);
if (string.IsNullOrEmpty(s))
{
 foreach (PSObject p in outputPipeline)
 {
 if (p.BaseObject.GetType().IsValueType)
 {
 System.Diagnostics.Debug.WriteLine("Number is " + p.BaseObject.ToString());
 }
 else
 {
 System.Diagnostics.Debug.WriteLine("Number is " + p.Properties["Value"].Value.ToString());
 }
 }
}
else
{
 System.Diagnostics.Debug.WriteLine("PowerShell failed: " + s);
}

Debug output can be seen with DbgView.

Have fun

Using ILM for DMZ Account Management

Per Østergaard — Thu, 29 Oct 2009 03:06:00 -0700

When you need to manage your users and group in a DMZ, it can be done in several ways. At least these methods can be used -

Autonomous. All users and groups are maintained locally in the DMZ.
Forest trust. A forest trust is constructed so the DMZ forest trust internal accounts. To restrict.
Read-only Domain Controller. A RODC is deployed in the DMZ.

Besides these, ILM can also be used and when you read the advantages/disadvantages below, you may or may not decide that ILM is the best for your environment.

Method	Advantages	Disadvantages
Autonomous	Can be totally isolated No firewall setup No information leak from internal AD	Expensive owing to added administration Distributed administration No SSO
Forest trust	Good integration with internal AD SSO with Kerberos Access to DMZ for internal AD objects can be restricted with Selective authentication	Complex firewall setup Cannot pick internal objects with GUI picker (unless you open for LDAP from non-DC) Have to change the registry to allow RDP logon on WS03. See KB 902336
Read-only domain controller	A single forest SSO Exposure can be controlled by managing what sensitive properties are on the RODC	Windows Server 2008 only Complex control of updates like DDNS Cannot limit users and groups visible
ILM	Simple firewall setup No inbound firewall rules No ILM license if you use IIFP (Enterprise Edition is required). See more below. Single place of management in the internal AD. Everything is pushed to DMZ including password changes. Helpdesk does not need access to DMZ and not even special procedures for changing properties. Full control of what object that are visible in DMZ No leak of other objects (trust cannot be queried) SSO or at least same password	Requires an extra infrastructure component SQL license (unless existing can be used) May not have full SSO to all services (re-enter password)

The seems fine, you say. I know how to do the other stuff, how complex is it to implement the ILM solution? Well, with ILM 2007 you have to create at least some code or get the code from someone who have made it (like Inceptio). But besides this, the rest is standard components. A very rough plan looks like this -

Install ILM
Install and configure PCNS on the internal AD domain controllers to capture password changes
Enable password management in ILM
Create an DMZ AD management agent, specifying it as password target
Create an internal AD management agent. Specify it as password source and the DMZ AD Management Agent as target
Create a management agent that can figure out what objects should be replicated to DMZ (use a group membership, naming convention or some other property). Let this populate an expectedDN property. If the logic is simple, it could be done in an MVExtension. In the solution I have made, I have done it using attribute-value-property files and PowerShell code.
Flow the properties you want to keep in sync from the internal AD and export them to the DMZ AD

With Forefront Identity Manager (FIM) 2010, you should be able to get rid of the coding part, making the solution more attractive. When it comes to IIFP, that is not supported anymore. Microsoft removed the download at some time but made it available again. From my sources at Microsoft, no IIFP version of FIM will be available, so you have to buy it.

Executing PowerShell code from within your own program

Per Østergaard — Mon, 26 Oct 2009 07:31:00 -0700

In V2 this got a lot easier. Here’s my PSExecute function. The idea is that you send in a text value and a script. The script references the value as $_. All output from the script is returned as the result of PSExecute. Exceptions (e.g. syntax errors), errors etc. are returned as well. Depending on the usage, this may not be what you need, but you can change it yourself.

I’m planning to use this in combination with ILM. Having the ability to use a piece of PowerShell script in an advanced flow rule or in the MVExtension seems very useful.

A script could be $_.toupper() etc.

private String PSExecute(String Script, String InputValue)
{
 // Create PS outside the function if called multiple times for performance reasons
 PowerShell PS = PowerShell.Create(); 

 // The script could probably be parsed once to speed things up if the same script is used repeatably
 PS.AddScript("'" + InputValue + "' | foreach {" + Script + "}");
 String s = "";
 try
 {
 foreach (PSObject result in PS.Invoke())
 {
 s += result.ToString();
 } // End foreach.
 }
 catch (Exception e)
 {
 s += "EXCEPTION: " + e.Message; // ToString();
 // just continue
 }
 foreach (DebugRecord result in PS.Streams.Debug)
 {
 s += "DEBUG: " + result.ToString();
 }
 foreach (VerboseRecord result in PS.Streams.Verbose)
 {
 s += "VERBOSE: " + result.ToString();
 }
 foreach (WarningRecord result in PS.Streams.Warning)
 {
 s += "WARNING: " + result.ToString();
 }
 foreach (ErrorRecord result in PS.Streams.Error)
 {
 s += "ERROR: " + result.ToString();
 }

 return s;
}

If you want to try it from PowerShell first, here’s the statements -

$script='$input | fforeach {$_.toupper()}'
$script='$_.toupper()'
$ps=[System.Management.Automation.powershell]::create()
$ps.AddScript('''' + $Inputvalue + ''' | foreach {' + $script + '}')
$ps.invoke()
$ps.Streams

Have fun!

Getting PowerShell V2 SDK

Per Østergaard — Mon, 26 Oct 2009 06:54:00 -0700

Messing around to find it, I’ll make it easier for you!

Unlike V1, the SDK is not a separate download, but part of Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1. After installing it (you can exclude the Win32 parts), add references to the relevant DLLs found in C:\Program Files\Reference Assemblies\Microsoft\WindowsPowerShell\v1.0.

Have fun

Using a PS Session without having Administrative Permissions

Per Østergaard — Sat, 19 Sep 2009 16:03:00 -0700

One of the great features of PowerShell V2 is the remote session support. But in the default configuration only local administrators can create a remote session. This is what a normal user sees -

This is how you delegate the feature to other users – the easy way.

First, create a local group and insert the user(s)

net localgroup "PowerShell Session Users" /add
net localgroup "PowerShell Session Users" the-user /add

Second, execute this command to bring up the permissions GUI

Set-PSSessionConfiguration microsoft.powershell -ShowSecurityDescriptorUI

add the group and grant execute (invoke) permissions -

Note that you have to restart the service -

And finally, try it out.

Let me draw your attention to two things in the picture above. First, the remote command is executed by a wsmprovhost process and second, extra properties are returned even though only the processname was selected. The extra properties are useful if you execute command on multiple sessions. In this way, you can recognize the returned objects.

msgoodies-powershell

Messing with output from Format-Table

PS Remoting to Home Server

PowerShell 2.0 *is* supported for Exchange 2007 SP2

Picking files with the mouse using Get-DroppedFile

PowerShell V2 now Available on Older Operating Systems

DFS, IPv6 and – sort of – disabling it

Executing a PowerShell Pipeline from your own program

Using ILM for DMZ Account Management

Executing PowerShell code from within your own program

Getting PowerShell V2 SDK

Using a PS Session without having Administrative Permissions

PowerShell 2.0 is supported for Exchange 2007 SP2