Archive for SharePoint 2010 Tips and Tricks

Dog Food Conference Columbus, Ohio

I will be presenting the following topics at the Dog Food Conference at the Microsoft Columbus, Ohio office.


  • SharePoint Diagnostic Studio 3.0 – Some uses in your SharePoint 2010 environment.
  • SharePoint Search Administration – How to help drive user adoption and maximize your SharePoint investment.
  • Managed Metadata – How to leverage this aspect in your SharePoint Information Worker world!

Please visit Danilo Casino’s blog for more information about this great event!



WinMerge is a great, open source tool that can run on the Windows platform.

How does this help you with SharePoint Administration?  An example is to compare web.config files.

The tool can highlight what line or lines of code are different between the files in comparison. 

There are any other uses.  Please visit the website for more information and free download.

Tony Maddin

Cincy SPUG Presentation – November 3, 2011

SP 2010 admin tool to add to your toolbox

While working on a client project, I was refreshing SharePoint 2010 environments to support our various QA and Development teams.

I implemented the SharePoint 2010 content hub for this project.  While detaching/attaching content databases to the staging environment; the Metadata Term Store data did not transfer.

This term set was a key feature in our project.

I searched the internet and came across this tool on CodePlex.  This tool was easy to use and fixed my issue.

I was able to export the term set from the source SharePoint 2010 farm.  Then transfer the CSV file to the destination.  Installed the tool again and the term set uploaded with no issues.

[box type=”info”]This is a must have tool to add to your Admin toolbox.

The tool is called the termsetimorter.exe but it also exports the term set as well. [/box]

My Presentation – SharePoint Saturday Columbus, Ohio – August 20, 2011

SharePoint 2010 In Plain English Video

Another must have SharePoint admin tool – ULS Viewer

As many of you are aware, reviewing log files are a necessary practice in our information technology industry.  But your standard NotePad on a Windows Server just cannot keep up when it comes to reviewing log files.

This tool has been around since 2009.   However, I when diagnosing a SharePoint 2010 farm, it was the tool of choice to help find the problem.  Here is the link.

Overcome Test-SPContentDatabase “Database too old error message”

Ok, I was thinking that I could quickly take a SharePoint 2007 content database, apply the minimum Service Pack 2 for WSS 3.0 and MOSS 2007, and then perform a database attachment within SharePoint 2010 in minutes while basking in the glory of the easy process.   I should have known this is SharePoint and everything is earned in this world.  🙂

I rebooted all the web front end servers and application servers just to make sure my little SharePoint 2007 world had the right build number of within Central Admin.   So I did a backup of the database and then moved the BAK file to the SharePoint 2010 Database instance and performed a simple restore.  For extra incentive and I was the DBO in the environment, I placed the SP Farm Account DBO to make sure the attachment goes ok.

I ran the PowerShell commandlet Test-SPContentDatabase to verify the database.  Then I got the error.

[box type=”warning”]Category: DatabaseValidation Error: True UpgradeBlocking: False Message: This database [SSPBeta] is too old and cannot be upgraded. Remedy: Upgrade this database to Windows SharePoint Services Version 3, SP2 or later. [/box]

[box type=”info”]So after I read multiple blogs, forums, etc.; I wanted to think outside-of-the-box. I tried an idea. “Maybe the commandlet needed a build number newer than”

So I got the April/2009 Cumulative update for WSS 3.0 and MOSS 2007. So I applied these two CU’s to the SharePoint 2007 Environment.

I verified I was on build number [/box]

Just like washing your hair.  Rinse and Repeat. 

So I did a backup of the database and then moved the BAK file to the SharePoint 2010 Database instance and performed a simple restore.  For extra incentive and I was the DBO in the environment, I placed the SP Farm Account DBO to make sure the attachment goes ok.

I ran the PowerShell commandlet Test-SPContentDatabase to verify the database.

 [box type=”shadow”]Then Poof!!!   The Test-SPContentDatabase command liked this minor build update.[/box] 

 Resources for review:

I welcome any feedback.

SharePoint 2010 Attach Content Database – Alerts not working now FIXED

So I took a SharePoint 2007 SP2 compliant and tested content database and placed it into a SharePoint 2010 enviornment.  All the content was there.  The permissions were fine.  However, by database attachment went to a new SharePoint 2010 web application that had a different URL name.

Example: SP 2007 content database was attached to

This URL change throws off alerts.  You can delete the alerts and add them back in but that is just crazy to think about that scenario.  And guess what…..there is a PowerShell commandlet to fix this issue. But unfortately, this answer is buried on search engines.

Anyway, there is the PowerShell commandlet.

[box]Invoke-AlertFixup -site <NewURL> -oldurl <OldURL> [/box]

Here is the exact Technet article to reference.

Open Source eMail Server


I found on a discussion thread on a great, open source email server to install in a development enviornment.  This is nice to have so you do not have to become a Microsoft Exchange guru.


How to connect Access to SharePoint 2010 if the feature within a view and/or list is missing.

Anyway, when I went to list view; the button to “Open with Access” was greyed out. I went into my settings and tried to create a new view with Access. It wasn’t there either.

Steps below:

  • So I opened up Access 2010.
  • Then chose the OPEN feature.
  • What is cool is in the drop down area; there was a item called, “SharePoint Foundation Services.”
  • I copied and pasted the URL to the SharePoint calendar that I needed to update…….

And then *POOF!* *MAGIC!* I can then update data via Access.

Happy SharePoint-ing!


A must have PowerShell statement inside your PowerShell Script for SharePoint 2010

The past few weeks, I have been writting a lot of PowerShell scripts so I can automate as many SharePoint administrative tasks that I can so I can enjoy other aspects of SharePoint during the business day.  🙂

I found a must have statement from the book, “PowerShell for Microsoft SharePoint 2010 Administrators“, book.

Here is the statement.  This statement is important if you have a scheduled task or a program that kicks off programs.

I have a template now to make sure I have this statement right underneath my opening comments area. 

[box type=”info”]Example: If (-not(Get-PSSnapin | Where-Object { $_.Name -eq “Microsoft.SharePoint.PowerShell”})) {Add-PSSnapin Microsoft.SharePoint.PowerShell;}[/box]

How to add Content Type to a SharePoint 2010 Wiki Library

 I wanted to use content types to drive navigation to a Wiki Library in SharePoint 2010.  I thought this would be the same thing just like any plain ole’ Document Library.  But no its not.  🙂  It’s buried and I happen to find it by trial and error.

[box type=”info”]

Go to the default home page of the wiki site. It is usually named, “Home.aspx” Edit the page.

Add a web part.

I used the Wiki Library I created as the item to add to the page.

In SharePoint 2010 in the ribbon, you will see new areas. Editing Tools, Library Tools, and Web Part Tools.

In the Library Tools area, you can now get to the proper Document Library Property page.

Now you can modify the Wiki Library as a Document Library have the content types in the library.


Contact me if you have questions about this information.

Here is the Microsoft Forum that I placed my information to help out the user community. 

Believe me, I rely on this community all the time.  It feels good when I can give back.