SharePoint 2010


PowerPivot (previously known as Project Gemini) is a Microsoft’s business intelligence (BI) solution, allowing business management and decision makers to collect and present business data in Excel or web based via SharePoint.  Many business executives have the capability to harness PowerPivot for Excel 2010 or SharePoint 2010 as they already either have the platforms in place or are a few steps away in getting this state-of-the-art BI solution by Microsoft.

I was asked to generate a list of SharePoint sites and their sizes via powershell and notify certain people via email. Here is some powershell that generates a html file with all the site collections in your farm and the sizes in MB and then emails it off to different people.

Unfortunately, at this point in time, there is no powershell to get sizes for ‘subsites’ (SP-Web), only for site collections.

IPv6 is becoming an issue and I hear more techs talking about it now than 5 or 10 years ago. I first learned about IPv6 and the IPv4 depletion issues about 10 years ago when I used to play with my own Cisco lab at home and aspire to be a Cisco Certified Internetwork Expert – CCIE :).

Now, as I have been working full time with SharePoint for years, I thought its a good time to pull out a little bit about SharePoint with IPv6 from the net…

When you install a new farm, you might be curious to find out what the Health Analyzer results are. Instead of waiting for the checks to happen (basically timer jobs scheduled at different intervals), you could force them to run all at one go, so you can review the results and address them.

You can easily run this in PowerShell. All it does is start all the timer jobs with ‘Health’ in its name. That fires off all SharePoint 2010 Health Analyzer jobs for your new farm in one go.

# Check to ensure Microsoft.SharePoint.PowerShell is loaded
$snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.Powershell'}
if ($snapin -eq $null) {
  Write-Host "Loading SharePoint Powershell Snapin"
  Add-PSSnapin "Microsoft.SharePoint.Powershell"
Get-SPTimerJob | Where {$_.Name -like "*Health*" -and $_.Name -like "*-all-*"} | Start-SPTimerJob


Ever wondered if there is a formula for calculating content database sizes? Want to have a start into learning more about SQL design and database capacity planning for SharePoint 2010?

Luckily, there is an awesome Technet document on SQL server design and capacity planning and it covers some great points to consider when planning your storage with SharePoint 2010.


I got a few requests to have this available online.. its a presentation file I put together on SharePoint 2010 High Availability options with SQL.

Here is a link as promised to my presentation (pptx) on SharePoint 2010 High Availability Options.
It covers some basics on Disaster Recovery, SQL database mirroring, log shipping and clustering with SharePoint with some Technet links.
SharePoint 2010 HA Options

If you can contribute to the links to this file or initiate a discussion, send me an email or comment here.
Appreciate your feedback!

This is a GREAT document if you want to look at capacity planning for FAST Search Server 2010.
If you have a multi-server SharePoint 2010 farm running on the Enterprise license with a dedicated Search Server, then your FAST Search Server 2010 would be of no extra licensing cost to you.
(Enterprise license is per server. Each FAST Search Server 2010 for SharePoint 2010 consumes one enterprise server license.  Disclaimer: please consult a Microsoft licensing specialist 🙂 ).

When you read this document, you will understand how to:

  • Define performance and capacity targets for your environment
  • Plan the hardware required to support the number and type of users, and the features you intend to deploy
  • Design your physical and logical topology for optimum reliability and efficiency
  • Test, validate and scale your environment to achieve performance and capacity targets
  • Monitor your environment for key indicators

I enjoyed this and I thought I would share this with you..

I was at a session by Maurice Prather on Secure Coding for the Administrator at the Australian SharePoint Conference 2011. It was a good session and there was a mention of the risks of PDF handling in the browser.

I did some more reading and found that Maurice had written an article which explains the risks of PDF (Pretty Dangerous Files) well.
In short.. you can embed javascript in a PDF document. Java script can be used to also delete/modify a wide variety of things in a SharePoint side through the client object model.

I thought this will be useful to make note of it in my blog. Here is a link to Maurice Prathers article on PDF (Pretty Dangerous Files):

You enjoy..