SharePoint 2010


A few recent migrations I worked on required me to export and import all Farm Solutions from one SharePoint farm to another SharePoint farm. There are a few blogs and tools available to get this done.

However, I came across Shane Young’s brilliant one line PowerShell command to get the job done!


Export all of the Solutions from your farm:

(Get-SPFarm).Solutions | ForEach-Object{$var = (Get-Location).Path + "\" + $_.Name; $_.SolutionFile.SaveAs($var)}


Import all of the Solution into another farm

Get-ChildItem | ForEach-Object{Add-SPSolution -LiteralPath $_.Fullname}

Note: Shane’s blogpost has the third step to deploy all these solutions. Not all Web Applications may need to have farm solutions deployed to them. So – you might want to plan this one, rather than deploy all these solutions in one go.


Check out Shane’s blogpost:

There has been some confusion on which SharePoint ULS log viewer to use when troubleshooting SharePoint issues. In May 2010, I blogged about the SharePoint 2010 ULS Log viewer published by Microsoft (

SharePoint 2013 Alert: In August 2014, I blogged about a re-released ULS Viewer for SharePoint 2013 enhanced by Microsoft.

Read more about it here:

In this post, I have discussed all the ULS log viewer tools here with screenshots and my final verdict..

A good practice is to move IIS off the system drive to another such as D:

Ok, so you tell your Server guys but they miss out on an important step such as updating the registry to the new D:\inetpub… location. You dont check this since you think they know what they are doing and go ahead and install SharePoint and once you are done, you realise that your Central Admin website has been installed and its virtual directory is located on C: – the system drive.

What now?

This is a reminder for SharePoint Admins, DBAs and Developers to ensure that they have taken the necessary steps recommended by Microsoft when it comes down to SharePoint 2010 database maintenance.

A few years ago, I posted out a similar ‘reminder’ for SharePoint (MOSS) 2007.

More recently, last year, Microsoft (Bill Baer and Bryan Porter) published a document on SharePoint 2010 database maintenance. Continue reading to get a summary of what is involved in maintaining databases for SharePoint 2010…

When troubleshooting SharePoint 2010 issues, you often find the need to have a tool that can give you performance, availability and usage metrics over a period of time across the farm.

One such tool is Microsoft’s SharePoint Diagnostic Studio 2010 that comes free as part of the SharePoint 2010 Administration Toolkit v2.0.
Download here: