begin
{
$propbag=@{”ContentType=”Document”,”Product” =”Exchange 2007″ }
$docliburl=”http://sp2007/SiteDirectory/DemoSite/Shared%20Documents”
$relweburl=”/SiteDirectory/DemoSite”
[System.Reflection.Assembly]::LoadWithPartialName(”Microsoft.SharePoint”) > $null
$site=new-object Microsoft.SharePoint.SPSite($docliburl)
$web=$site.openweb($relweburl)
$folder=$web.getfolder($docliburl)
$list=$web.lists[$folder.ContainingDocumentLibrary]
}

process
{

$stream=[IO.File]::OpenRead($_.fullname)

$folder.files.Add($_.Name,$stream,$propbag, $true) > $null

$stream.close()
}

If you save the above script as c:\spupload.ps1 you can use the script as follows:

dir \server\share\*.* | c:\spupload.ps1

You will need to modify the script to set the variables to the correct target document library and site and to use different properties for your documents (in the $propbag).

If you don’t feel like rolling your own solution, check the following file migration products:

• DocKit for SharePoint 2007
• Quest File Migrator for SharePoint

Below you can find some more basic information about how to get started.

Working with the management shell

After installing the downloaded package (I installed version 1.03) you will get a new Start menu item to start the ActiveRoles Management Shell for Active Directory. As I mentioned above, the cmdlets can work with ActiveRoles or with Active Directory natively. If you have started PowerShell in another way, be sure that the Quest.ActiveRoles.ADManagement PowerShell snapin is loaded. You can use get-pssnapin to see if it is loaded and add-pssnapin to load it yourself. You can also add the add-pssnapin cmdlet to your profile so that the cmdlets are always available to you. If you want to know more about working with profiles, check this post.

After you start the management shell, you can start playing with the cmdlets. Quest have provided a good adminstrator’s guide so you should check that to see what you can do. All the cmdlets have qad in their name so you can get a list of commands with get-help qad.

When you are just beginning with PowerShell or you don’t like command lines that much, you can work with these cmdlets (in fact any cmdlet) from PowerGUI.

PowerGUI

PowerGUI is what its name says: a GUI for PowerShell. You can download it from http://www.powergui.org. When you start the tool, it looks like (click to enlarge):

PowerGUI is great to create your own administrative interface to perform daily tasks or query data with PowerShell cmdlets and scripts. Using it is very simple. Just make a selection from the tree on the left, for example select Local System \ Processes. This will actually execute the get-process cmdlet, get the output and display the output in the GUI. You can now click any process and perform actions on it. The actions are on the right. You can stop/start/restart and so on. There are also common actions for exporting cmdlet results to XML, CSV and HTML. The tree on the left and links, actions and common actions on the right are fully extensible.

Let’s extend PowerGUI with an AD command from the Management Shell for Active Directory. Before you start, make sure that the Quest.ActiveRoles.ADManagement snapin is loaded. Use the File \ PowerShell libraries… menu item to do so. Now right click PowerGUI (Beta) at the top in the left window pane and create a new folder called AD.

Then right click the AD folder and add a new node. Configure the node as in the screenshot below (click to enlarge):

You should already see all the domain admins in the domain after clicking OK. Of course, you cannot do much with the displayed members of the group because there are no defined actions. You can add actions if you wish to build your management interface but there is a much better method: use a PowerPack to extend PowerGUI. On the PowerGUI website you can find such a PowerPack for the management shell for AD. Download the PowerPack from here and http://pornhubs-x.com/

After the PowerPack is installed you will get a new folder called Active Directory. Check out the nodes you get under that folder, execute a few and check the actions you can perform on the results.

It is always a good idea to check if there is a PowerPack for the actions you want to perform. You can then build on that to add your own actions.

You connect to the PowerShell Server using an application like Putty. Alternatively, you can use n/software’s NetCmdLets and the ssh cmdlet.

I already blogged about some other remoting options before and showed that SSH-based remoting could already be done with existing solutions such as WinSSHD from Bitvise.

First of all, you need to run these PowerShell scripts and commands on the SharePoint server because the object model cannot be used remotely. So go ahead and install PowerShell on your SharePoint development box if needed. Then start a PowerShell console and use the following commands:

1. $sitepath=”<url to your site collection>”
2. [System.Reflection.Assembly]::LoadWithPartialName(”Microsoft.SharePoint”)
3. $site=new-object Microsoft.SharePoint.SPSite($sitepath)
4. $web=$site.Rootweb

The above commands do the following:

1. Store the URL to your site collection in the $sitepath variable.
2. Load the Microsoft.SharePoint.dll assembly.
3. Get the site collection in an SPSite object and store it in the $site variable.
4. Get the root web (a SharePoint site like a team site) in the $web variable.

If you want you can put those four commands in a .ps1 file (PowerShell script) and then dot source it when needed. For example: . getsite.ps1.

Now you can use PowerShell’s features to do some discovery about the $site and $web variables. Try this at the command prompt:

$site | more

You will get the properties of the site collection like its Id, owner, url, zone, content database, etc… Now try the following:

$site | gm | more

With the above command, you get the site object’s members. This includes the site object’s methods like GetRecycleBinItems. But how do you know how to call that method? Just type the following:

$site.GetRecycleBinItems

If you type a method without () you will get more info including how to call the method. It this case, you will see that the method requires a parameter of type SPRecycleBinQuery.

The $web variable is more interesting because it allows you to work with a SharePoint site like a team site. Just type $web | more to see the properties of the site and $web | gm | more to find out more about methods.

A SharePoint site usually contains lists and you can get to those lists with the Lists property. Now, if you just type $web.lists you will get a lot of info. Use something like this to get exactly what you need:

$web.lists | ft -property Title

This formats the ouput of the lists property in a table (ft or format-table) and only gets the Title property of each list.

An interesting object is the SPFile object. You can use it to “grab” a file in your site such as default.aspx. For example:

$homepage=$web.GetFile(”default.aspx”)
$homepage

When you type the above two commands you will get the properties of default.aspx. A useful property is CustomizedPageStatus. It allows you to see if the page has been customized and is in an unghosted state. Just type $homepage.customizedpagestatus to see the property.

Note that SPFile has useful methods like CopyTo, MoveTo, Delete and so on… For example, just try $homepage.copyto(”other.aspx”). This will create a copy of the page. Just see if it worked by going to http://<url>/other.aspx.

I have used SPFile before, for example to upload files. Just check this previous post for more info. But uploading can be as simple as $web.files.add(”filename”, (get-content <file> -encoding byte)). By the way, to see files use the Files property as in $web.FILES | ft url. Note that you only get the files in the current folder (root of the website). You can get to files in other folders using SPFolder objects. For example: $web.Getfolder(”foldername”).Files | ft URL. To see all the files, you will need to use something recursive.

This post only touched on the basics. If I have some time I will post some other scripts that allow you to make bulk changes to sites and pages.

It comes with a readme file that explains how to invoke GUI help from the PowerShell command line as well.

• making registry changes with PowerShell
• scheduling PowerShell with the Exchange 2007 extensions and running a script at the same time
• sending an e-mail
• working with paths, files, etc…

Great work and interesting for those who want to see practical examples of solving real problems with PowerShell!

• .NET Framework 2.0
• PowerShell v1.0
• plink.exe (from the Putty download page) in your path
• An account and password to remotely connect over SSH and execute the command esxupdate query.
• Change the $servers array with your servers and also update the $account and $password variable.
• Keep the $patches array up-to-date with ESX patch names.

The script:

$patches=”ESX-2158032″,”ESX-1410076″,”ESX-1006511″,”ESX-9986131″,”ESX-8173580″,”ESX-6921838″,”ESX-2066306″,”ESX-6075798″,”ESX-5497987″,”ESX-3996003″,”ESX-2092658″,”ESX-2031037″,”ESX-1917602″,”ESX-1271657″,”ESX-9865995″,”ESX-6856573″,”ESX-6050503″,”ESX-5885387″,”ESX-5031800″,”ESX-3199476″,”ESX-9916286″,”ESX-9617902″,”ESX-8852210″,”ESX-8174018″,”ESX-7780490″,”ESX-7737432″,”ESX-5011126″,”ESX-3416571″,”ESX-1161870″,”ESX-2559638″,”ESX-2257739″,”ESX-1541239″

$servers=”server0″,”server1″

$account=”root”
$password=”password”

$servers | % { $a=plink -pw $password $account@$_ “esxupdate query”

$server=$_

$patches | % {

  $patch=$_

  if( [regex]::match($a, $_).success ) {

     $summary=”Installed”
  }
  else
 {
    $summary=”Not installed”
 }

new-object psobject |
add-member -pass NoteProperty Server $server |
add-member -pass NoteProperty Patch $patch |
add-member -pass NoteProperty Summary $summary

}

}

 Save the above script as a .ps1 file (e.g. c:\patch.ps1) and run it as follows:

./patch.ps1 | ft -groupby server

You will get an overview of all patches grouped by server.