http://blogs.technet.com/benp/archive/2007/04/10/creating-an-ad-shell.aspxHello Again This is my third post in the Active Directory and PowerShell series. In this post I want to talk about how to create your own pseudo-cmdlets to manage the AD. I`m going to talk about how to present scripts to PowerShell that behave in a similaren-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/benp/archive/2007/04/10/creating-an-ad-shell.aspx#750415Wed, 11 Apr 2007 20:51:54 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:750415Carpe Diem: Flaphead.com @ Home<p>Ben you are the dogs whatits. This is just an awesome post on how to 1) Make ad admin simpler and 2)</p> http://blogs.technet.com/benp/archive/2007/04/10/creating-an-ad-shell.aspx#1176581Fri, 08 Jun 2007 00:22:50 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:1176581Benp's Guide to Stuff<p>Ladies + Gents This week I have had the privilege of working at TechEd 2007. I’ve been on the PowerShell</p> http://blogs.technet.com/benp/archive/2007/04/10/creating-an-ad-shell.aspx#1541812Tue, 17 Jul 2007 18:27:51 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:1541812Per Østergaard<p>Wouldn't it just be much easier to place the functions in a directory and the simply add that to the path? In this way, you do not have to double the function/files.</p> <p>I have a subdir called library being part of my path, so I simply stick files in to that when I want them to be easy accessible.</p> <p>Per</p>