Dear Niklas Goude,

Congratulations! We are pleased to present you with the 2010 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in PowerShell technical communities during the past year.

It feels amazing receiving this award and Im really happy to be a part of the PowerShell MVP’s.

Thank You!

Click here to download the scripts

Click here to download the PowerPoint presentation

The book focuses on getting started with Windows PowerShell and includes: Basic cmdlets, parameters, pipelines, functions, filters, security, writing scripts, learning .NET, WMI, COM and much more. The last chapter in the book focuses on how to administrate Windows environments through PowerShell which includes: managing folders and files, acl, services, eventlogs, processes, the registry, windows forms, Active Directory, Microsoft SQL Server, New functionality in Windows 7 and much more.

Note that the book is written in Swedish, so you might want to run it through google translator..

Happy Reading.

First, start the SharePoint 2010 Management Shell.

Now we can get fancy with SharePoint administration. Adding a new announcement is done basically in the same way as in MOSS, though it’s alot simpler since Microsoft added tons of new great SharePoint CmdLets. Below is an example on adding a new announcement to a SharePoint list.

PS > $siteScope = Start-SPAssignment
PS > $Announcement = ($siteScope | Get-SPWeb -identity http://sharepoint).Lists["Announcements"]
PS > $NewItem = $Announcement.Items.Add()
PS > $NewItem["Title"] = "My First Announcement"
PS > $NewItem["Body"] = "<h2>PowerShell Magic</h2>"
PS > $NewItem["Expires"] = "1/28/2010"
PS > $NewItem.Update()
PS > Stop-SPAssignment $siteScope

The Start-SPAssignment and Stop-SPAssignment should be used with certain objects such as SPSite, SPWeb and SPSiteAdministration, since they need to be disposed. You can read more about the CmdLets at the I Love SharePoint blog.

The rest of the code is pretty straightforward, Get the Web through Get-SPWeb, create an object holding the List, use the Add() method, add the information and finally update the new item using the Update() method.

Here’s what it looks like in the Shell.

And here’s our new Item in SharePoint.

When put in a script, we can simply add a new announcement on a single line.

PS > Add-SharePointAnnouncement.ps1 -identity http://sharepoint -List Announcements -Title "Added From Script" `
>> -Body "<h2>PowerShell Scripts Rock</h2>" -Expires 1/28/2010

Click here to download the script.

]]> http://www.powershell.nu/2010/01/27/adding-announcements-to-sharepoint-2010-through-powershell/feed/ 0 http://www.powershell.nu/2009/12/16/running-scripts-with-arguments-in-powershell/ http://www.powershell.nu/2009/12/16/running-scripts-with-arguments-in-powershell/#comments Wed, 16 Dec 2009 16:34:19 +0000 Niklas Goude http://www.powershell.nu/?p=924 Here’s a short guide on running scripts in powershell.

The guide is divided into three parts:

• Running Scripts from the Console
• Running Scripts from Start/Run
• Running Scripts as Backgournd Jobs in PowerShell

First, let’s look at the script examples that we want to run.

Here’s the first script:

##################
#
# Script 1
#
##################

"Arguments: $($args.count)"
$args

And here’s the second script:

##################
#
# Script 2
#
##################

param($Argument1,$Argument2)

"Argument1 is: $Argument1"
"Argument2 is: $Argument2"

Script 1 uses $args variable to handle arguments. This is a automatic Variable created by PowerShell. It will handle any arguments that are passed to the script.

Script 2 uses a param statement. the param statement let’s us define variables that hold our arguments. The variables are available throughout the script.

Running Scripts from the Console

Now, let’s look at a couple of different ways of running scripts from the PowerShell console.

PS > C:\temp\Scripts\script1.ps1 Hello World

Arguments: 2
Hello
World

In the example, we triggered the script with two arguments, Hello and World. If we instead want Hello World to pass as a single argument, we can use quotation marks:

PS > C:\temp\Scripts\script1.ps1 “Hello World”

Arguments: 1
Hello World

In this example, There's only one argument passed to the script since "Hello World" is within quotation marks.

Obviously, we can use variables as arguments.

PS > $HelloWorld = "Hello World"
PS > $Hello = "Hello"
PS > $World = "World"

PS > C:\temp\Scripts\script1.ps1 $HelloWorld

Arguments: 1
Hello World

When we enter $HelloWorld, the value of the $HelloWorld variable is passed on as one argument to the script.

If we instead use the Variables $Hello and $World, they will be handled as two different arguments.

PS > C:\temp\Scripts\script1.ps1 $Hello $World

Arguments: 2
Hello
World

If we put the variables within quotation marks, they will be passed on to the script as one single argument.

PS > C:\temp\Scripts\script1.ps1 "$Hello $World"

Arguments: 1
Hello World

Using Single Quotation takes passes the argument exactly as written, in other words, the Argument will be $Hello $World and not the values of the variables.

PS > C:\temp\Scripts\script1.ps1 '$Hello $World'

Arguments: 1
$Hello $World

It's possible to achieve this when using Double Quotation marks. Just add a backtrick character in front of the variables.

PS > C:\temp\Scripts\script1.ps1 "`$Hello `$World"

Arguments: 1
$Hello $World

Let's look at a few examples on running Script 2 from the console. Script 2 uses the param statement.

PS > C:\temp\Scripts\script2.ps1 Hello World

Argument1 is: Hello
Argument2 is: World

In this example, Hello is assigned to $Argument1 and World is Assigned to $Argument2

PS > C:\temp\Scripts\script2.ps1 "Hello World"

Argument1 is: Hello World
Argument2 is:

If we put Hello World in double quotation marks, both Hello and World are assigned to $Argument1. $Argument2 is empty.

It's also possible to use the param variables as parameters to the script as the examples below show.

PS > C:\temp\Scripts\script2.ps1 -Argument1 Hello -Argument2 World

Argument1 is: Hello
Argument2 is: World

If we only specify one parameter the second will automatically be assigned to the first variable in the param that doesn't have a value.

PS > C:\temp\Scripts\script2.ps1 -Argument1 Hello World

Argument1 is: Hello
Argument2 is: World

PS > C:\temp\Scripts\script2.ps1 -Argument2 World Hello

Argument1 is: Hello
Argument2 is: World

You can, of course, use quotation marks here as well.

PS > C:\temp\Scripts\script2.ps1 -Argument1 "Hello World"

Argument1 is: Hello World
Argument2 is:

What if the Path to the script contains spaces ?. Let's see what happens. in these examples I've changed the path to the scripts to C:\Temp\Example Scripts\

PS > C:\temp\Example Scripts\script1.ps1 "Hello World"

The term 'C:\temp\Example' is not recognized as the name..

so this didn't work. It's because PowerShell separates commands with a space, so it tries to run the command C:\Temp\Example. You can solve this by using quotation marks and a Call Operator. without the Call Operator, PowerShell will handle the script path as a string value.

PS > & "C:\temp\Example Scripts\script1.ps1" "Hello World"

Arguments: 1
Hello World

Script2 can be triggered in the same way, note that the arguments are after the scriptpath and not within quotation marks.

PS > & "C:\temp\Example Scripts\script2.ps1" -Argument1 Hello -Argument2 World

Argument1 is: Hello
Argument2 is: World

Another way of running scripts is if you're in the same directory as the scripts are located. Then you can simply use the .\ notation in front of the script.

PS > cd 'C:\temp\Example Scripts\'
PS > .\script1.ps1 "Hello World"

Arguments: 1
Hello World

The easist way to run scripts is if you include the scriptpath in the environment PATH.

$Env:PATH = $Env:PATH + ";C:\Temp\Example Scripts"

Now we can simply type the name of the script to run it.

PS > script2.ps1 -Argument1 Hello -Argument2 World

Argument1 is: Hello
Argument2 is: World

You don't even have to type the script extension when running the scripts.

PS > script2 -Argument1 Hello -Argument2 World

Argument1 is: Hello
Argument2 is: World

Running Scripts from Start/Run

You can also trigger scripts from Start / Run in Windows. Here are a couple of examples on how we can run our scripts from Start / Run. The NoExit switch is used in these examples so that we can check the result easily.

powershell.exe -noexit C:\temp\Scripts\script1.ps1 Hello World

When running Scripts that are in a path that doesn't include spaces you can simply type the scripts FullPath followed by the arguments as shown in the example above. But what if you want "Hello World" to be handled as just one argument?

powershell.exe -noexit C:\temp\Scripts\script1.ps1 "Hello World"

If we type "Hello World" inside double quotation marks it's still handled as two different arguments. We can solve this by using Single Quotation Marks.

powershell.exe -noexit C:\temp\Scripts\script1.ps1 'Hello World'

Let's see how this works with the script that uses a param.

powershell.exe -noexit C:\temp\Scripts\script2.ps1 Hello World

This works just fine, lets specify the parameters in the script as well.

powershell.exe -noexit C:\temp\Scripts\script2.ps1 -Argument1 Hello -Argument2 World

And, as you can see, this works fine as well. Now let's see what happens if we double quote on of the arguments.

powershell.exe -noexit C:\temp\Scripts\script2.ps1 -Argument1 "Hello World" -Argument2 Monkey

This returns Hello as Argument1 and Monkey as Argument2. World is not in the script ouput. Now let's do the same example with single quotation marks.

powershell.exe -noexit C:\temp\Scripts\script2.ps1 -Argument1 'Hello World' -Argument2 Monkey

Now we got the result that we wanted. So lesson learned from this is: use single quotation marks when passing arguments containing spaces.

Now let's test this with the scripts containing spaces in the script path.

powershell.exe -noexit C:\temp\Example Scripts\script1.ps1 "Hello World"

This didn't work since the path contains spaces, now let's try it with double quotes at first.

powershell.exe -noexit "C:\temp\Example Scripts\script1.ps1" "Hello World"

Still no luck, lets try adding the Call Operator.

powershell.exe -noexit & "C:\temp\Example Scripts\script1.ps1" "Hello World"

In order to get it right, we have to use single quotation marks.

powershell.exe -noexit & 'C:\temp\Example Scripts\script1.ps1' "Hello World"

Note that Hello World is handled as two different arguments. Whe can solve this by typing Hello World within single quotation marks.

powershell.exe -noexit & 'C:\temp\Example Scripts\script1.ps1' 'Hello World'

Script 2, that uses the param statement works in the same way.

powershell.exe -noexit & 'C:\temp\Example Scripts\script2.ps1' -Argument1 Hello -Argument2 World

powershell.exe -noexit & 'C:\temp\Example Scripts\script2.ps1' -Argument1 'Hello World'  -Argument2 Monkey

Finally, let's see what happens if we run scripts included in the $Env:PATH variable.

First, we should add the script path to our profile so that it's loaded when powershell starts. Just Add $Env:PATH = $Env:PATH + ";C:\Temp\Example Scripts" into your profile.ps1 file.

powershell.exe -noexit script1.ps1 'Hello World'

powershell.exe -noexit script2.ps1 -Argument1 Hello -Argument2 World

We can even run the scripts without the extension.

powershell.exe -noexit script1 'Hello World'

powershell.exe -noexit script2 -Argument1 Hello -Argument2 World

Adding a script path to the $Env:PATH variable makes it alot more simple to run scripts in PowerShell.

Running Scripts as Backgournd Jobs in PowerShell

Let's take a look on how to run scripts as background Jobs. PowerShell v2 includes a great cmdlet callet Start-Job. It let's us run Jobs in the background. We can use this to run our scripts as background jobs.

Let's take a look on How to Run Scripts witth Start-Job.

PS > $Job1 = Start-Job .\script1.ps1 -ArgumentList Hello,World

By placing the command in a variable, we can easily access the Job informationm, check for status and use it to retrieve the output of the command. Start-Job Doesn't return the Job Result when completed so we have to use Receive-Job to get the Result from the Script.

PS > Receive-Job $Job1.ID
Arguments: 2
Hello
World
PS > Receive-Job $Job1.ID
PS >

When we run the Receive-Job CmdLet and use the Jobs ID as argument, we get the Result from the Job Returned. Note that if we run the same command again, we don't get anything returned. This is becauese Receive-Job, by default, deletes the Returned information after it's accessed. We can bypass this with the -Keep switch.

PS > $Job1 = Start-Job .\script1.ps1 -ArgumentList Hello,World
PS > Receive-Job $Job1.ID -Keep
Arguments: 2
Hello
World
PS > Receive-Job $Job1.ID -Keep
Arguments: 2
Hello
World

To Close the Session, run the Receive-Job command without the -Keep switch or use the Remove-Job CmdLet as shown below.

PS > Remove-Job $Job1.ID

So how to solve this without PowerShell V2 installed ? well, we could always use Wscript.Shell. Here's an example on running backgroundjobs with wscript.shell.

PS > $Wscript = New-Object -Com Wscript.Shell
PS > $Command = "powershell.exe & 'C:\temp\Example Scripts\script2.ps1' -Argument1 'Hello' -Argument2 'World'"
PS > $Wscript.Run($command,0,$False)
0

So how do we varify that the script actually runs ? Well, we can solve this with a simple pipeline.

PS > $Wscript = New-Object -Com Wscript.Shell
PS > $OutFile = "C:\temp\output.txt"
PS > $Command = "powershell.exe & 'C:\temp\Example Scripts\script2.ps1' -Argument1 'Hello' -Argument2 'World' | Out-File $OutFile"
PS > $Wscript.Run($command,0,$False)

0

PS > Get-Content $OutFile

Argument1 is: Hello
Argument2 is: World

Hope you find this guide useful.

The international Speakers included Joel Oleson, Eric Shupps, Todd Klindt, Steve Smith and Penny Coventry.
On the Swedish team we got some great sessions from Wictor Wilén, Tobias Zimmergren and, of course, Göran Husman.

My session on SharePoint & PowerShell went well.. almost. The night before my presentation I decided to run through all my code examples one last time, which resultet in a USB-Disc crash. Unlucky for me was that my VMWare was stored on the USB-Disc.
So after half an hour of panic, 3 hours of installation and 1 hour of testing i finally got everything in place, just in time to get my morning coffee and head off to SEF. Anyway, you can download my presentation here or on www.seforum.se

Hope to see all y’all next year!

]]> http://www.powershell.nu/2009/11/19/sef09/feed/ 0 http://www.powershell.nu/2009/09/08/moss-2007-script-collection/ http://www.powershell.nu/2009/09/08/moss-2007-script-collection/#comments Tue, 08 Sep 2009 16:54:14 +0000 Niklas Goude http://www.powershell.nu/?p=857 I’ve been working with SharePoint and PowerShell for quite some time now and I would like to share a couple of Scripts that I use when scripting MOSS. Actually, it’s 44 Scripts, Loads of Coffee and alot of long nights so I hope you enjoy them. There are Links at the bottom of the Post where you can Download all the scripts, or you can Download all scripts from the link below.

moss-script-collection.zip

Down to business then. I’ll put up a scenario based on the Session that I used at the SharePoint UserGroup meeting in Stockholm Sweden, explaining all Steps and how to use the Scripts.

First I set up a Folder where I keep all my scripts, I use C:\Scripts. Then I add the folder to the Windows Path.

PS > $env:path = $env:path + ";c:\scripts"

Adding the Script folder to the Environment Path let’s Us Call the script simply by typing it’s name. so instead of typing:

PS > .\Get-SPSite.ps1 -url http://moss

We can Type:

PS > Get-SPSite -url http://moss

Note, Don’t forget to set the Execution-Policy, otherwise, the scripts won’t run. Read more about it here

PS > Set-ExecutionPolicy RemoteSigned

All Scripts include a help text that explains how to use the Script. To access the helptext simply type the Script Name followed by -help.

PS > Get-SPSite -help

Now We can start Scripting MOSS!

Loading SharePoint Assemblies

The first thing we have to do in order to Access the MOSS 2007 Assemblies is Loading them into PowerShell. Even though they Exist in our Windows Environment, PowerShell isn’t aware of them. By Loading them into our Global Assembly Cache, PowerShell can access and use the MOSS 2007 .NET Classes.

[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")

Get-SPSite.ps1

First, We’ll Check out the Site Collection. Here’s how we can add our Site Collection to a variable using the Get-SPSite.ps1 script and retrieve information from it. When working with SPSite or OpenWeb objects in the PowerShell console you have to dispose of the object on the same row as the command, otherwise they will leak memory. This only applies when you create SharePoint objects directly in the PowerShell console. When run in functions and scripts, the commands are run in a single thread. for more information click here

PS > $SPSite = Get-SPSite -url http://moss; $SPSite | Select Url, Port, Owner | Format-List; $SPSite.Dispose()

Url   : http://moss
Port  : 80
Owner : POWERSHELL\administrator

 
We can also get usage Information:

PS >  $SPSite = Get-SPSite -url http://moss; $SPSite.Usage; $SPSite.Dispose()


Storage           : 550113
Bandwidth         : 0
Visits            : 0
Hits              : 0
DiscussionStorage : 0

And even information from the WebApplication Pool 

PS > $SPSite = Get-SPSite -url http://moss; $SPSite.WebApplication.ApplicationPool | Select DisplayName, Status | Format-List; $SPSite.Dispose()


DisplayName : SharePoint - 80
Status      : Online

Try Pipe:ing the $SPSite object to Get-Mameber and check out all Available methods and properties available. 

PS > $SPSite = Get-SPSite -url http://moss; $SPSite | Get-Member; $SPSite.Dispose()

Get-SPWeb.ps1

The Get-SPWeb.ps1 Returns a Site instead of a Site Collection through the OpenWeb() method. Through it, we can modify the Title and description of a site, we can add Items, documents and lots more. Here’s an example on how you can change the Title and Descrition of a Site. 

PS > $OpenWeb = Get-SPWeb http://moss; $OpenWeb.Title; $OpenWeb.Dispose()

Home

PS > $OpenWeb = Get-SPWeb http://moss; $OpenWeb.Description; $OpenWeb.Dispose()

Home

PS >  $OpenWeb = Get-SPWeb http://moss; $OpenWeb.Title = "PowerShell Home"; $OpenWeb.Description = "Demo From PowerShell.nu"; $OpenWeb.Update(); $OpenWeb.Dispose()

Here’s What happened to my MOSS RootWeb Site after running these simple commands. 

Get-SPList.ps1

We’ve accessed The Site Collection and a MOSS Site, Let’s look at how to access a List within a Site. We can do this through the Get-SPList.ps1 Script. We can use it to Get or Set List Information and even Get or Set Items and Fields in the List. 

PS > $SPList = Get-SPList -url http://moss -List Announcements; $SPList.ItemCount; $SPList.Dispose()

3

PS > $SPList = Get-SPList -url http://moss -List Announcements; $SPList.Items | ForEach { $_["Title"] }; $SPList.Dispose()

Get Started with Windows SharePoint Services!
Announcement Added through PowerShell
Demo from PowerShell.nu

Get-SPField.ps1

A List Contains Field which tell us what kind of information we can add to our Items. When Accessing a Field you can use the Get-SPField.ps1 script. The Field holds alot of information such as Type. 

PS > $Field = Get-SPField -url http://moss -List Announcements -Field Expires
PS > $Field.Type

DateTime

You can even edit information in the Field. Here’s an Example on How to Hide the Field in Edit Form. When a User Tries to Edit an item in the Announcements List, he won’t see the Expires Field. 

PS > $Field.ShowInEditForm = $False
PS > $Field.Update()

Get-SPView.ps1

A List Contains a Variaty of Views. Here’s how you Access a List View in MOSS 2007 using the Get-SPView.ps1 Script. 

PS > $View = Get-SPView -url http://moss -List "Shared Documents" -View "All Documents"

The View contains alot of Methods and Properties. Let’s take a look at the Clone() Method. 

PS > [void]$View.Clone("My Cloned View",100,$True,$False)

With this Simple Command, I’ve Created a new View Called “My Cloned View”. It’s basically a Copy of the “All Documents” View. 

Get-SPItem.ps1

When Accessing Items within a List, you can use the Get-SPItem.ps1 Script. Storing the Item in a Variable Allows us to Get And Modify it’s properties. The script includes an -All Switch that retrieves All Items in a List instead of just one item. 

PS > $Item = Get-SPItem  -url http://moss -List Announcements -Item "Get Started with Windows SharePoint Services!"

Now That we have an Item stored in the $Item Variable, we can Modify it. 

PS > $Item["Body"]

Microsoft Windows SharePoint Services helps you to be more eff
ective by connecting people, information, and documents. For information on getting started, see Help.


PS > $Item["Body"] = "New Text in Body"
PS > $Item.Update()

Another Nice Trick is Looping through all Items. First let’s Store them in a variable: 

PS > $AllItems = Get-SPItem -url http://moss -List Announcements -All

Now Let’s Set the Body on All Announcements in the Announcements List.

PS > $AllItems | ForEach { $_["Body"] = "New Text"; $_.Update() }

Add-SPAnnouncement.ps1

Next, let’s add an Announcement to our RootWeb Site. Using the Add-SPAnnouncement.ps1 sript, we can add through a One-Liner in PowerShell. 

PS > Add-SPAnnouncement -url http://moss -List "Announcements" -Title "Demo from PowerShell.nu" -Body "<h1>PowerShell</h1><p />is Cool!" -Expires (Get-Date).AddHours(1)

Let’s say that you have multiple sites in your Site Collection and you want to add an Announcement on each site. This can be solved with a Simple ForEach: 

PS > $Sites = "http://moss/HR","http:moss/IT","http://moss/Production","http://moss/Sales"
PS > $Sites | ForEach {
>> Add-SPAnnouncement -url $_ -List "Announcements" -Title "Demo från PowerShell.nu" -Body "

is Coolt!" -Expires (Get-Date).AddHours(1)

This Code adds an announcement on each site in the $Sites Array. 

Add-SPCalendar.ps1

The Add-SPCalendar.ps1 script adds new Calendar Entries to a MOSS Calendar List. 

PS > Add-SPCalendar -url http://moss -List "Calendar" -Title "SharePoint - PowerShell Demo" -Location "Stockholm" -Description "PowerShell Demo" -StartTime (Get-Date) -EndTime (Get-Date).AddHours(4)

The -StartTime and -EndTime Parameters accept an [DateTime] object, which means that we can use the Get-date CmdLet to Add Dates. 

Add-SPLink.ps1

Here’s a Script that adds Links to a MOSS Links List. It sets the Link, the Description of the Link and the Notes Field. 

PS > Add-SPLink -url http://moss -List "Links" -Link "http://www.powershell.nu" -Description "PowerShell.nu - Blog" -Notes "PowerShell Blog"

Here’s what our Newly created Link Item looks like: 

Set-SPImageWebPart.ps1

On a Default installed MOSS, The Root Web uses the “Team Site” Template, which has an Image WebPart on the Right Displaying a SharePoint Services Image. Let’ go ahead and change the image using the Set-SPImageWebPart.ps1 Script. 

PS > Set-SPImageWebPart -url http://moss -WebPart "Site Image" -Image "C:\Demo\Files\PowerShell.jpg"

As you can see in the Image below, Our RootWeb Team Site looks a little PowerShelled. 

Set-SPTheme.ps1

Now that we’ve customized our Site with a New “Site Image”, let’s go ahead and change the Theme. We’ll use the Set-SPTheme.ps1 script to achieve this.

PS > Set-SPTheme -Url http://moss -Theme obsidian

And with a simple One-Liner, we’ve changed the Theme on our Site. Doing without the script takes about two lines of code, but i Added the script since I think it’s pretty cool. 

Upload-SPDocument.ps1

This Script lets you Upload Documents to a Document Library in MOSS. Here’s how it Works: 

PS > Upload-SPDocument -url http://moss -Folder "Shared Documents" -Document "C:\Documents\Excel SpreadSheet.xlsx"

If we look in our “Shared Documents” List, We can see that the Document is uploaded there now. 

But What it we want to Upload one hundred documents ? Well, since we are using PowerShell, we can do it with a One-Liner. 

PS > gci C:\Documents | ForEach { Upload-SPDocument -url http://moss -Folder "Shared Documents" -Document $_.FullName }

This really shows the Power of Microsoft PowerShell 

Add-SPFolder.ps1

Now That we’ve Uploaded a couple of Files, Let’s Add a New Folder to our “Shared Documents”. We can do this by using the Add-SPFolder.ps1 script. 

PS > Add-SPFolder -Url http://moss -List "Shared Documents" -Name "New Folder"

If we want to Upload Documents Directly to our Folder we can use the Upload-SPDocument.ps1 Script again, we just point it to our New Folder. 

PS > Upload-SPDocument -url http://moss -Folder "Shared Documents/New Folder" -Document "C:\Documents\Excel SpreadSheet.xlsx"

Add-SPTextField.ps1

Let’s add a couple of Fields to our “Shared Documents” List. First, we’ll add a Document Owner Field. In this example we’ll use a simple Text field, but you could obviously use a User field instead. We’ll get back to the User field a little later in this post. 

PS > Add-SPTextField -url http://moss -List "Shared Documents" -Name "Document Owner" -Description "Document Owner"

This Adds a TextField to our List named “Document Owner”, if you want the field to Require information, simply add -Required to the command above. 

Add-SPChoiceField.ps1

Next, We’ll add a Choice Field to our “Shared Document”. This can be done by using the Add-SPChoiceField.ps1 Script. Again, if you want the Field to Require information, just add -Required to the command. 

PS > Add-SPChoiceField -url http://moss -List "Shared Documents" -Name "Document Type" -Description "Type of Document" -Choices $("Excel","Word","PowerPoint")

Note the -Choices Paramteter. It takes an Array of arguments and Sets each argument as a Choice in the Field. Typing $(“Argument1″,”Argument2″) is a quick way to create an array and passing it as an argument to the script. 

Add-SPFieldToView.ps1

Now that we have two new Fields in our “Shared Documents”, let’s add them to the “All Documents” View by using the Add-SPFieldToView.ps1 Script. 

PS > Add-SPFieldToView -url http://moss -List "Shared Documents" -Field "Document Owner" -View "All Documents"
PS > Add-SPFieldToView -url http://moss -List "Shared Documents" -Field "Document Type" -View "All Documents"

If we check out our “Shared Documents” list now, we can see that the Fields are Added to the “All Documents” View. You can, of course, use this on any type of List in MOSS 2007. 

Set-SPItem.ps1

Here’s a Really Useful script when working with Items. The Set-SPItem.ps1 Script can either Create a New Item or Modify an existing Item. At first, Let’s take a look on how to Modify existing Items. By Default, the -field param is set to Title, but by changing it to Name, the script will check for a match in the Name Field and if it finds a match, it will update the Item, if it doesn’t find a match it will create a New Item. Note that when Creating Items in a Document Library you have to use the Upload-SPDocument.ps1 script. 

Note that the -Values takes a HashTable Array of Values to Set on the Item. Let’s say a List has Two Fields. A Title field and a Description Field. If I want to Create a New Item Called “New Item” and with The Description “My New Item Description” I could Simply type: 

PS > Set-SPItem -url http://moss -List "My List" -Name "New Item" -Values @{"Description" = "My New Item Description"}

If i Want to Edit the Item that i Created i Could reuse the Same Command, since it First looks for an Item Where the Title is Set to “New Item” 

Let’s say i Don’t know the Title of the Item but i Do know It’s Description. By using the -Field paramter i Could get the Correct Item and Modify it. 

PS > Set-SPItem -url http://moss -List "My List" -Name "My New Item Description" -Field Description -Values @{"Title" = "New Title"; "Description" = "Changed Title and Changed Description of Item"}

Let’s Take a Look at the Documents that we Added earlier. Here’s an example on adding MetaData on Documents in a Document Library:

PS > Set-SPItem -url http://moss -List "Shared Documents" -Name "Excel SpreadSheet.xlsx" -Field "Name" -Values @{"Document Type" = "Excel"; "Document Owner" = "Niklas Goude"}
PS > Set-SPItem -url http://moss -List "Shared Documents" -Name "Word Document.docx" -Field "Name" -Values @{"Document Type" = "Word"; "Document Owner" = "Niklas Goude"}
PS > Set-SPItem -url http://moss -List "Shared Documents" -Name "PowerPoint Presentation.pptx" -Field "Name" -Values @{"Document Type" = "PowerPoint"; "Document Owner" = "Niklas Goude"}

With these Commands I added information in the “Document Type” Field and the “Document Owner” Field on my three Documents, as the image below show. 

Let’s Use this Script to Modify the Announcement That we Added Earlier. We’ll Change the Body of the Announcement. 

PS > Set-SPItem -url http://moss -List Announcements -Name "Demo from PowerShell.nu" -Values @{"Body" = "<h2>Modified With Set-SPItem.ps1</h2>"}

Here’s what the Announcemet looks like now: 

Add-SPList.ps1

Now Let’s create our own Custom List. We’ll use the Add-SPList.ps1 Script to do this. Specifying the Type to “Custom List” tells the script to create a “Custom List”. You can, of course create any type of list available in MOSS through this script. 

PS > Add-SPList -url http://moss -Name "My List" -Description "My Custom Demo List" -Type "Custom List"

This Creates the List, but it doesn’t Add the List to the QuickLaunch Bar. Let’s check out how to Add a List to the QuickLaunchBar. 

Add-SPListToQuickLaunch.ps1

This Script adds lists to the Quicklaunch Bar in MOSS 2007. The Command below shows how you can use the script. 

PS > Add-SPListToQuickLaunch -url http://moss -List "My List"

This command adds the List to the QuickLaunch Bar. 

Set-SPQuickLaunchOrder.ps1

Let’s Change the QuickLaunch Order. We’ll use the Set-SPQuickLaunchOrder.ps1 Script that moves a List to the Top of the QuickLaunch. 

PS > Set-SPQuickLaunchOrder -url http://moss -List "My List"

If we look at our site now, We can see that our QuickLaunch Order has been Changed. The “My List” List is now on top. 

Now That we have a Custom List, Let’s Add a couple of different Fields, We’ll also add them to the “All Items” View with the Add-SPFieldToView.ps1 script. 

Add-SPCurrencyField.ps1

You can Add a Currency Field by using the Add-SPCurrencyField.ps1 Script. 

PS > Add-SPCurrencyField -url http://moss -List "My List" -Name Cash -Description "How much Money do you have?"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field Cash -View "All Items"

Add-SPDateTimeField.ps1

Here’s how we can add a DateTime Field to a List using the Add-SPDateTimeField.ps1 Script. 

PS > Add-SPDateTimeField -url http://moss -List "My List" -Name "Birthday" -Description "When is Your Birthday?"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field Birthday -View "All Items"

Add-SPNoteField.ps1

The Note Field Accepts Text on Multiple Rows. Here we add a Note Field using the Add-SPNoteField.ps1 Script. 

PS > Add-SPNoteField -url http://moss -List "My List" -Name Description -Description "About Me.."
PS > Add-SPFieldToView -url http://moss -List "My List" -Field Description -View "All Items"

Add-SPNumberField.ps1

We can also Add Numeric Fields to MOSS. This example shows how to do that using the Add-SPNumberField.ps1 Script. 

PS > Add-SPNumberField -url http://moss -List "My List" -Name Age -Description "How Old Are You?"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field Age -View "All Items"

Add-SPYesNoField.ps1

With the Add-SPYesNoField.ps1 script, We can add a Yes/No Checkbox Field to our List. 

PS > Add-SPYesNoField -url http://moss -List "My List" -Name "Windows 7" -Description "Do You Have Windows 7 Installed?"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "Windows 7" -View "All Items"

Add-SPUserField.ps1

Adding User Fields that point to a Active-Directory User, Can be Added through the Add-SPUserField.ps1 Script. 

PS > Add-SPUserField -url http://moss -List "My List" -Name User -Description "User"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field User -View "All Items"

Add-SPMultipleUserField.ps1

A User Field can Allow Multiple Selections. Here’s how to add a multiple User Field using the Add-SPMultipleUserField.ps1 script. 

PS > Add-SPMultipleUserField -url http://moss -List "My List" -Name "Multiple Users" -Description "Multiple Users"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "Multiple Users" -View "All Items"

Add-SPMultiChoiceField.ps1

Choice Fields can also accept Multiple Choices. Here’s an example on how to add a Multiple Choice Field using the Add-SPMultiChoiceField.ps1 Script. 

PS > Add-SPMultiChoiceField -url http://moss -List "My List" -Name "Favorite Music" -Description "Favorite Music" -Choices $("Country","Metal","Rock","Soul","Jazz")
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "Favorite Music" -View "All Items"

Add-SPLookupField.ps1

The Lookup Field Points to an Item in another List. In this Example we’ll Point it to the “Tasks” List.

PS > Add-SPLookupField -url http://moss -List "My List" -Name "My Tasks" -Description "My Tasks" -LookupList Tasks
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "My Tasks" -View "All Items"

Add-SPMultiLookupField.ps1

LookupFields Can also have multiple Values. We can add a Multiple LookupList through the Add-SPMultiLookupField.ps1 Script. Again, We’ll Use the Tasks List as Lookup. 

PS > Add-SPMultiLookupField -url http://moss -List "My List" -Name "Multiple Tasks" -Description "Multiple Tasks" -LookupList Tasks
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "Multiple Tasks" -View "All Items"

Add-SPURLField.ps1

Finally, Let’s Add an URL Field to our “Custom List”. 

PS > Add-SPURLField -url http://moss -List "My List" -Name HomePage -Description "HomePage"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field HomePage -View "All Items"

Now, Let’s see what our List Looks like. 

Let’s Add Two Task Items and then create a New Item in our “Custom List” using the Set-SPItem.ps1 Script. 

PS > Set-SPItem -url http://moss -List Tasks -Name "My First Task" -Values @{"Priority" = "(3) Low"; "Status" = "In Progress"; "% Complete" = "0.4"; "Assigned To" = "powershell\Administrator"; "Description" = "My First Task"; "Start Date" = "09/07/09"; "Due Date" = "09/08/09"}
PS > Set-SPItem -url http://moss -List Tasks -Name "My Second Task" -Values @{"Priority" = "(1) High"; "Status" = "Not Started"; "% Complete" = "0"; "Assigned To" = "powershell\Administrator"; "Description" = "My Second Task"; "Start Date" = "09/07/09"; "Due Date" = "09/08/09"}

Here’s our New Tasks up and running. 

Now Let’s Add a New Item in our “Custom List”. Note that Fields that Allow multiple Values are divided by a ; in the command below. For Instance, if I want to two values to a multiple Choice Field I would have to Type: @{“MultiChoiceField” = “Value1; Value2; Value3″}.

PS > Set-SPItem -url http://moss -List "My List" -Name "My First Item" -Values @{"Cash" = "10"; "Birthday" = "05/05/1982"; "Description" = "My First Entry"; "Age" = "27"; "Windows 7" = "Yes"; "User" = "powershell\administrator"; "Multiple Users" = "powershell\administrator; powershell\nigo"; "Favorite Music" = "Metal; Country"; "My Tasks" = "My First Task"; "Multiple Tasks" = "My First Task; My Second Task"; "HomePage" = "http://www.powershell.nu; My Blog" }

And Here’s what our Item Looks like in MOSS 2007. 

Set-SPView.ps1

Let’s Modify the Apperance of the “All Tasks” View in the Tasks List so that it Groups By Status. When Modifying appearance of a View, We change the View Query. This can be Done by using the Set-SPView.ps1 Script.

PS > Set-SPView -url http://moss -List Tasks -View "All Tasks" -Query ''

Here’s what our Tasks Look like now. 

Remember the “Shared Documents that We Added Fields to earlier ? Let’s Group the “All Documents” View by one of our New Fields. Note that the Name=”Document_x0020_Type” in the Query. It’s because the Field has Spaces in its Name. 

PS > Set-SPView -url http://moss -List "Shared Documents" -View "All Documents" -Query ''

And now our Documents are Grouped by “Document Type”. 

Add-SPSpite.ps1

With the Add-SPSite.ps1 Script, we can add New Sites to our Site Collection. There are a Couple of Different Templates that we can use. To get a list of all templates available, SImply type the following commands. 

PS > $OpenWeb = Get-SPWeb http://moss; $OpenWeb.GetAvailableWebTemplates(1033) | Select Name; $OpenWeb.Dispose()

Let’s Create a New Site For our IT Department. 

PS > Add-SPSite -url http://moss -weburl "IT" -Title "Information Technology" -Description "IT Department" -Template "STS#1"

Here’s What the Site looks like now. 

Since we used a STS#0 Template, the Site doesn’t contain any Lists or information. 

Add-SPGroup.ps1

If we want to Add a New Group to our Site Collection we can use the Add-SPGroup.ps1 Script. Here’s an example on using the Script. 

PS > Add-SPGroup -url http://moss -Group "New Group" -Role Read -Owner "powershell\administrator"

Now our “New Group” is Added to our Site with “Read” Permissions 

Add-SPUser.ps1

With our New Group set up, we can go ahead and add users to it. To accomplish this, we can use the Add-SPUser.ps1 Script. Here’s an example on adding a User to the “New Group”.

PS > Add-SPUser -url http://moss -Group "New Group" -Domain "powershell.nu" -sAMAccountName "goude" -mail "niklas.goude@zipper.se" -FullName "Niklas Goude"

If we look in the Group now, our User will be added. 

Add-SPSitePermission.ps1

Let’s Give our Group Full Permissions on The IT Site that we created earlier.

PS > Add-SPSitePermission -url "http://moss/IT" -Group "New Group" -Permission "FullMask"

Now all users in the Group have Full Permissions on the “IT” Site. On the RootWeb, they still have Read Permissions. 

Add-SPImageWebPart.ps1

Let’s Add a New Image WebPart to the IT Site that we just created. Here’s an example on how to do it using the Add-SPImageWebPart.ps1 Script.

PS > Add-SPImageWebPart -url http://moss/IT -Name "My Image" -Image "C:\Images\PowerShell.jpg" -ChromeType "None"

Now the Image WebPart is Added to the Site. There are a couple of parameters you can use with this script. simply type Add-SPImageWebPart -help to check out available parameters. 

PS > Add-SPImageWebPart -help

Add-SPListViewWebPart.ps1

The Add-SPListViewWebPart.ps1 let’s us Add list View WebParts to our Sites. The Script contains a couple of parameters that let’s you choose Chrome Type, Zone and a couple of other things. Here’s an example on Using the Script.

PS > Add-SPListViewWebPart -url http://moss -List "My List" -Name "Client Statistics" -ChromeType "None"

Here’s our New List WebPart in Action! 

Remove-SPField.ps1

If you want to Remove a Field From a List you can use the Remove-SPField.ps1 Script. Here’s an example on how to use the Script.

PS > Remove-SPField -url http://moss -List "Shared Documents" -Field "Document Type"

Remove-SPItem.ps1

If you want to Remove a List Item you can use the Remove-SPItem.ps1 script. The -name parameter matches with the Title field by default. If you want to match the name with another field, simply use the -field parameter.

PS > Remove-SPItem -url http://moss -List Tasks -name "My First Task"
PS > Remove-SPItem -url http://moss -List Tasks -name "Not Started" -Field Status

Remove-SPList.ps1

If you want to Remove an entire List you can use the Remove-SPList.ps1 script,

PS > Remove-SPList -url http://moss -List Tasks

This Command Removed the Tasks List from the RootWeb Site. 

Remove-SPSite.ps1

When Removing a Site from MOSS 2007 You can use the Remove-SPSite.ps1 script. This exmaple shows how to remove the IT Site that we created earlier.

PS > Remove-SPSite -url http://moss/IT

Export-SPSite.ps1

Let’s take a Backup of our Site Collection. We can either do this through Central Administration, through an STSADM Command or by Using PowerShell. This Example shows how to use a PowerShell Script to take a Backup of a Site Collection.

PS > Export-SPSite -url http://moss -file Backup.bak -Location C:\Backup\

The Command Places a Backup file in C:\Backup\Backup.bak. to automate this you could set up a Scheduled Task that takes a backup at specified weekdays. 

Import-SPSite.ps1

Now That we have a Backup, Let’s restore our Site Collection from the Backup file. To achieve this, we can use the Import-SPSite.ps1 Script. Here’s an example on how to use the script.

PS > Import-SPSite -url http://moss -file Backup.bak -Location C:\Backup\

Here’s a List of All scripts from this Post. Enjoy! 

Regards

Goude 

• Get-SPSite.ps1
• Get-SPWeb.ps1
• Get-SPList.ps1
• Get-SPField.ps1
• Get-SPView.ps1
• Get-SPItem.ps1
• Add-SPAnnouncement.ps1
• Add-SPCalendar.ps1
• Add-SPLink.ps1
• Set-SPImageWebPart.ps1
• Set-SPTheme.ps1
• Upload-SPDocument.ps1
• Add-SPFolder.ps1
• Add-SPTextField.ps1
• Add-SPChoiceField.ps1
• Add-SPFieldToView.ps1
• Set-SPItem.ps1
• Add-SPList.ps1
• Add-SPListToQuickLaunch.ps1
• Set-SPQuickLaunchOrder.ps1
• Add-SPCurrencyField.ps1
• Add-SPDateTimeField.ps1
• Add-SPNoteField.ps1
• Add-SPNumberField.ps1
• Add-SPYesNoField.ps1
• Add-SPUserField.ps1
• Add-SPMultipleUserField.ps1
• Add-SPMultiChoiceField.ps1
• Add-SPLookupField.ps1
• Add-SPMultiLookupField.ps1
• Add-SPURLField.ps1
• Set-SPView.ps1
• Add-SPSpite.ps1
• Add-SPGroup.ps1
• Add-SPUser.ps1
• Add-SPSitePermission.ps1
• Add-SPImageWebPart.ps1
• Add-SPListViewWebPart.ps1
• Remove-SPField.ps1
• Remove-SPItem.ps1
• Remove-SPList.ps1
• Remove-SPSite.ps1
• Export-SPSite.ps1
• Import-SPSite.ps1

  ]]> http://www.powershell.nu/2009/09/08/moss-2007-script-collection/feed/ 13 http://www.powershell.nu/2009/09/08/scripting-pdf-documents-through-powershell/ http://www.powershell.nu/2009/09/08/scripting-pdf-documents-through-powershell/#comments Tue, 08 Sep 2009 11:06:00 +0000 Niklas Goude http://www.powershell.nu/?p=801 [System.Reflection.Assembly]::LoadFrom("C:\itextsharp\itextsharp.dll") Step Two: Create a [...]]]> Microsoft Office Supports Scripting possibilities through Com Objects. But what about PDF Documents ? Luckily there is a DLL available for download that let’s us Create PDF documents through .NET

First you have to Download the ITextSHarp.dll

Next, Time for some PowerShell Magic.

Step One: Load the DLL.

PS > [System.Reflection.Assembly]::LoadFrom("C:\itextsharp\itextsharp.dll")

Step Two: Create a Variable holding the iTextSharp.text.Document Object

PS > $Doc = New-Object iTextSharp.text.Document

Step Three: Create a PDF Document with a connection to the $Doc variable

PS > [void][iTextSharp.text.pdf.PdfWriter]::GetInstance($Doc, [System.IO.File]::Create("C:\PDF\Goude.pdf") )

Step Four: Open The Document ( In order to add information to the PDF File )

PS > $Doc.Open()

Step Five: Create a Text Chunk and append Text to Display in Pdf Document

PS > $Chunk = New-Object iTextSharp.text.Chunk
PS > [void]$Chunk.Append(“Demo From PowerShell.nu”)

Step Six: Add the Chunk of Text, Set an Author with the AddAuthor() method and finally Close it with the Close() method

PS > $Doc.Add($Chunk)
PS > $Doc.AddAuthor("Niklas Goude")
PS > $Doc.Close()

Voila, you now have a PowerShell made PDF File. You can, of course, create far more advanced PDF files containing tons of information. I’ll get back to this in a later Post.

]]> http://www.powershell.nu/2009/09/08/scripting-pdf-documents-through-powershell/feed/ 3 http://www.powershell.nu/2009/09/04/scripting-mp3-metadata-through-powershell/ http://www.powershell.nu/2009/09/04/scripting-mp3-metadata-through-powershell/#comments Fri, 04 Sep 2009 20:24:56 +0000 Niklas Goude http://www.powershell.nu/?p=787 $TagLib = "C:\taglib\Libraries\taglib-sharp.dll" PS > [...]]]> Structuring up you Music Library can be a rather time consuming task. You can however script this rather easily through PowerShell using the taglib-sharp library.

Let’s start off by downloading the Tag-Lib Library
Next, We have to Load the Assembly from PowerShell in order to access the Classes.

PS > $TagLib = "C:\taglib\Libraries\taglib-sharp.dll"

PS > [System.Reflection.Assembly]::LoadFile($TagLib)


GAC    Version        Location
---    -------        --------
False  v2.0.50727     C:\taglib\Libraries\taglib-sharp.dll

Now that we’ve loaded the dll, we need a music file that we want to set properties on, in this example I’m going to use a mp3 file. If we check out the properties on the mp3 file, we can see that nothing is set.

Let’s change this through PowerShell. We have to create a variable using the [Taglib.File] Class and use the filepath as an argument to the Create() method.

PS > $Media  =  [TagLib.File]::Create("C:\Music\My Song.mp3")

The object contains a couple of Properties.

PS > $Media


Tag                    : TagLib.NonContainer.Tag
Properties             : TagLib.Properties
TagTypesOnDisk         : Id3v1, Id3v2
TagTypes               : Id3v1, Id3v2
Name                   : C:\temp\My Song.mp3
MimeType               : taglib/mp3
Tell                   : 0
Length                 : 0
InvariantStartPosition : 4608
InvariantEndPosition   : 7109078
Mode                   : Closed

The one that We’re interested in is the Tag property, which contains additional underlaying properties and methods. Let’s check it out:

PS > $Media.Tag


StartTag             : TagLib.NonContainer.StartTag
EndTag               : TagLib.NonContainer.EndTag
TagTypes             : Id3v1, Id3v2
Tags                 : {Audiograbber 1.83.01, LAME d
                       v2.PrivateFrame TagLib.Id3v2.
Title                :
Performers           : {}
PerformersSort       : {}
AlbumArtistsSort     : {}
AlbumArtists         : {}
Composers            : {}
ComposersSort        : {}
TitleSort            :
AlbumSort            :
Album                :
Comment              :
Genres               : {}
Year                 : 0
Track                : 0
TrackCount           : 0
Disc                 : 0
DiscCount            : 0
Lyrics               :
Grouping             :
BeatsPerMinute       : 0
Conductor            :
Copyright            :
Pictures             : {}
IsEmpty              : True
Artists              : {}
FirstArtist          :
FirstAlbumArtist     :
FirstAlbumArtistSort :
FirstPerformer       :
FirstPerformerSort   :
FirstComposerSort    :
FirstComposer        :
FirstGenre           :
JoinedArtists        :
JoinedAlbumArtists   :
JoinedPerformers     :
JoinedPerformersSort :
JoinedComposers      :
JoinedGenres         :

Let’s go ahead and set a couple of Values.

PS > $Media.Tag.Performers = "Goude"
PS > $Media.Tag.AlbumArtists = "Goude"
PS > $Media.Tag.Artists = "Goude"
PS > $Media.Tag.Album = "My Album"
PS > $Media.Tag.Genres = "Rock"
PS > $Media.Tag.Track = "1"
PS > $Media.Tag.Title = "My Song"
PS > $Media.Tag.Year = "2009"
PS > $Media.Tag.Comment = "PowerShell Demo"
PS > $Media.Save()

If we check out the file properties through Explorer we’ll see that the properties are set on the file.

So, editing one file is easy, but what if you want to edit a couple of thousand files..

When I did this on my Media Files i used the Folder and File Names as reference. The folder and file structure was set up accordingly:

C:\Music\Rock\Artist1 – Album\01 – First Song.mp3
C:\Music\Rock\Artist1 – Album\02 – Second Song.mp3
C:\Music\Rock\Artist2 – Album\01 – First Song.mp3

So with this information i could make a script that Used this information in order to set the Tags. The script uses the “Rock” folder name as Genre, Then it Splits the “Artist – Album” folder and sets Artist = Artist and Album = Album, finally it splits the file name “01 – First Song.mp3″ and sets Track = 01 and Title = First Song. I’ve also error handling in the script so that You can follow up on files that didn’t pass through the script.

Click Here to download the Script

Examples on Running the script:

PS > Set-Media.ps1 -Folder C:\MyMusic\Rock -LogFile C:\Log\SetMediaLog.txt

Note! You can always modify the script to fit your own environment and folder structure.

PS > $ComputerName = $env:COMPUTERNAME
PS > $Group = "Administrators"
PS > $LocalGroup = [adsi]"WinNT://$computerName/$Group,group"
PS > $LocalGroup


distinguishedName :
Path              : WinNT://Computer01/Administrators,group

Now that we’re connected to the Local Group, we can start of by adding a user. First let’s add a Local User.

PS > $Domain = "powershell"
PS > $UserName = "nigo"
PS > $LocalGroup.Add("WinNT://$Domain/$userName")

This adds the Domain user powershell\nigo to the local Administrators Group. If we instead want to add a Local User, we just replace the Domain Name with the Local COmputer Name.

PS > $ComputerName = $env:COMPUTERNAME
PS > $LocalGroup.Add("WinNT://$ComputerName/$userName")

And if we want to remove a User from a local Group, we use the Remove() method.

PS > $Domain = "powershell"
PS > $UserName = "nigo"
PS > $LocalGroup.Remove("WinNT://$Domain/$userName")

Here’s a script that automates these tasks.

Click here to download the script.

Here are some examples on running the script.

PS > Set-LocalGroup.ps1 -UserName nigo -Add

PS > Set-LocalGroup.ps1 -UserName nigo -Remove

PS > Set-LocalGroup.ps1 -UserName nigo -Group "Guests" -Domain powershell -Add

PS > Set-LocalGroup.ps1 -help

]]> http://www.powershell.nu/2009/07/06/managing-local-groups-through-powershell/feed/ 0