Enter the Page Viewer web part (aka the iFrame web part). How does this technological wonder better our lives? Watch and learn.

1. Find a YouTube Video. Ricky Gervais’s opening monologue from the 2012 Golden Globes should do nicely. Once you’ve located your target video, click Share, followed by Embed. Leave the window/tab open, we’ll come back to it in a moment..
2. Go to the page in your SharePoint site where you want to add the video (I’m using a publishing page).
   
3. Add a Page Viewer Web Part (located in the Media and Content category).
4. Open the tool pane. We’ll need to fill in the values for the Link, Height, and Width fields.
5. Back to our YouTube window/tab, select the embed options you would like to use (480×360 video in my case).
6. Locate the embed HTML code and copy the URL. It should look like the following:

   <iframe width="480" height="360" src="http://www.youtube.com/embed/h_OnK0SrtC8" frameborder="0" allowfullscreen></iframe>
   

7. Back in the window/tab containing your SharePoint page, paste the url to the YouTube video in the Link field in your web part. Adjust the Height and Width fields accordingly. Save your web part options. Your web part should render with the video inline.
8. Publish/Save/Stop Editing your page and bask in the glory of your embedded YouTube video (without the use of a content editor or any external text file).

Gallery

Organizations of all sizes are begging their technical departments to setup SharePoint 2010 so that they’re able to make use of some of the capabilities introduced within the SharePoint 2010 platform. While designing, implementing, configuring and deploying a system in and of itself has its own set of challenges, migrating into that shiny new SharePoint can be even more difficult.

In this session, Scott and Dan will share some of their experiences and lessons learned tips, tricks and pointers for ensuring that you’ve considered the various aspects of challenges that arise during a migration effort. Further, as a bonus they’ll share how to not fall prey to some of these pitfalls but rather be able to show that you’re a well rounded professional that’s thought things through before pressing the enter key.

The following configuration steps will allow you to connect to the BPOS OCS servers:

1. Install the Lync for Mac 2011 client.
2. Open the preference pane and select the Account tab.
   Click the Edit… button under the Server Settings heading.
3. In the Advanced Server Settings dialog, enter pool1.oconline.microsoftonline.com:443 in both the Internal Server Name and External Server Name fields.
4. Close the preference pane and select the Microsoft Lync window. Enter the following information:
   • Email Address: user@contoso.com
   • User ID: RED001\user_contoso.com
   • Password: Your password

   

5. Click Sign In and …

Reference

• Lync for Mac 2011
• Microsoft Online Services Client Computer Requirements
• How to troubleshoot Office Communicator authentication issues

Trials and Tribulations of Managed Metadata

Pitfalls of Migrating to SharePoint 2010

In it’s default configuration, SharePoint (2007 and 2010) will delete workflow associations after 60 days (e.g. the information found on the Workflow Status page). There are times when you may want to alter this functionality and retain the association for a longer period of time.

In SharePoint 2007, the recommendation from Microsoft (per TechNet), is to disable the Workflow Auto Cleanup timer job. The Workflow Auto Cleanup timer job is a web application scoped timer job. As such, disabling the job is often not the optimal solution; as disabling the job will ensure that cleanup is not occurring for all of the site collections within the web application for which the timer job was disabled.

The Solution

Thankfully, there is a property (SPWorkflowAssociation.AutoCleanupDays) that is exposed with the workflows associated with a given list/content type. And once again, PowerShell comes to the rescue, giving us the ability to manipulate the cleanup days at a more granular level. This ensures that we do not disable the timer job for an entire web application.

Presented as two functions, we can manipulate the workflow association settings for either the workflows associated with a list or the workflows associated with a content type attached to a list.

Set-SPListWorkflowAssocationCleanup

The following function allows us to set the AutoCleanupDays for all of the workflows associated with a given list.

Set-SPListWorkflowAssocationCleanup -WebUrl "http://intranet" -ListName "Shared Documents" -CleanupDays 365 -ReportOnly:$false

function Set-SPListWorkflowAssocationCleanup {
    param (
        [string] $WebUrl = $(Read-Host -prompt "Enter a Url"),
        [string] $ListName = $(Read-Host -prompt "Enter a List Name"),
        [int32] $CleanupDays = $(Read-Host -prompt "Enter the number of Cleanup Days"),
        [switch] $ReportOnly = $true
        )        

    $web = Get-SPWeb $WebUrl;
    if ($web -eq $null) {
        Write-Error -message "Error: Web Not Found" -category InvalidArgument
    } else {
        $list = $web.Lists[$ListName];
        if ($list -eq $null) {
            Write-Error -message "Error: List Not Found" -category InvalidArgument
        } else {
            [Microsoft.SharePoint.Workflow.SPWorkflowAssociation[]] $wfaMods = @();
            foreach ($wfa in $list.WorkflowAssociations) {
                $message = "Found Workflow Association for " + $wfa.Name + " with AutoCleanupDays set to " + $wfa.AutoCleanupDays
                Write-Verbose -message $message -verbose

                if ($ReportOnly -eq $false) {
                    $wfa.AutoCleanupDays = $CleanupDays;
                    $wfaMods = $wfaMods + $wfa;
                }
            }

            if ($ReportOnly -eq $false) {
                foreach ($wfa in $wfaMods) {
                    $message = "Setting AutoCleanupDays for " + $wfa.Name + " to " + $CleanupDays
                    Write-Verbose -message $message -verbose
                    $list.WorkflowAssociations.Update($wfa);
                }
            }
        }
    }
}

Set-SPListContentTypeWorkflowAssocationCleanup

The following function allows us to set the AutoCleanupDays for all of the workflows associated with content type for a given list.

Set-SPListContentTypeWorkflowAssocationCleanup -WebUrl "http://intranet" -ListName "Shared Documents" -ContentTypeName "Document Content Type" -CleanupDays 365 -ReportOnly:$false

function Set-SPListContentTypeWorkflowAssocationCleanup {
    param (
        [string] $WebUrl = $(Read-Host -prompt "Enter a Url"),
        [string] $ListName = $(Read-Host -prompt "Enter a List Name"),
        [string] $ContentTypeName = $(Read-Host -prompt "Enter a Content Type Name"),
        [int32] $CleanupDays = $(Read-Host -prompt "Enter the number of Cleanup Days"),
        [switch] $ReportOnly = $true
        )        

    $web = Get-SPWeb $WebUrl;
    if ($web -eq $null) {
        Write-Error -message "Error: Web Not Found" -category InvalidArgument
    } else {
        $list = $web.Lists[$ListName];
        if ($list -eq $null) {
            Write-Error -message "Error: List Not Found" -category InvalidArgument
        } else {
            $ct = $list.ContentTypes[$ContentTypeName];
            if ($ct -eq $null) {
                Write-Error -message "Error: Content Type Not Found" - category InvalidArgument
            } else {
                [Microsoft.SharePoint.Workflow.SPWorkflowAssociation[]] $wfaMods = @();
                foreach ($wfa in $ct.WorkflowAssociations) {
                    $message = "Found Workflow Association for " + $wfa.Name + " with AutoCleanupDays set to " + $wfa.AutoCleanupDays
                    Write-Verbose -message $message -verbose

                    if ($ReportOnly -eq $false) {
                        $wfa.AutoCleanupDays = $CleanupDays;
                        $wfaMods = $wfaMods + $wfa;
                    }
                }

                if ($ReportOnly -eq $false) {
                    foreach ($wfa in $wfaMods) {
                        $message = "Setting AutoCleanupDays for " + $wfa.Name + " to " + $CleanupDays
                        Write-Verbose -message $message -verbose
                        $ct.WorkflowAssociations.Update($wfa);
                    }
                }
            }
        }
    }
}

Conclusion

By manipulating the workflow associations for a list at the list/content type level the default configuration of a SharePoint farm can be retained (e.g. Workflow associations removed after 60 days) and in those cases where there is a business need, the workflow associations can be maintained for a longer period of time.

Reference

• SPWorkflowAssociation.AutoCleanupDays Property
• SharePoint Timer job reference (Office SharePoint Server)
• Timer job reference (SharePoint Server 2010)
• SharePoint Workflow History “Disappears”

Tokens

Microsoft.SharePoint.SPCustomActionElement.ReplaceUrlTokens

internal static string ReplaceUrlTokens(string urlAction, SPWeb web, SPList list, SPListItem item)
{
	if (string.IsNullOrEmpty(urlAction))
	{
		return urlAction;
	}
	if (item != null)
	{
		int d = item.ID;
		string str1 = d.ToString(CultureInfo.InvariantCulture);
		if (list.HasExternalDataSource)
		{
			str1 = item["BdcIdentity"] as string;
		}
		urlAction = urlAction.Replace("{ItemId}", str1);
		urlAction = urlAction.Replace("{ItemUrl}", item.Url);
		string recurrenceID = str1;
		if (!string.IsNullOrEmpty(item.RecurrenceID))
		{
			recurrenceID = item.RecurrenceID;
		}
		urlAction = urlAction.Replace("{RecurrenceId}", recurrenceID);
	}
	if (web != null)
	{
		urlAction = urlAction.Replace("{SiteUrl}", web.Url);
	}
	if (list != null)
	{
		urlAction = "{ListId}".Replace(Guid guid = list.ID, guid.ToString("B"));
		if (list.RootFolder != null)
		{
			urlAction = urlAction.Replace("{ListUrlDir}", list.RootFolder.Url);
		}
	}
	HttpContext current = HttpContext.Current;
	if (current != null && current.Request != null)
	{
		string rawUrl = current.Request.RawUrl;
		Uri contextUri = SPAlternateUrl.ContextUri;
		if (!string.IsNullOrEmpty(rawUrl) && null != contextUri)
		{
			string str2 = null;
			if (!SPUtility.StsStartsWith(rawUrl, "/"))
			{
				str2 = string.Concat(contextUri.GetLeftPart(UriPartial.Authority), "/", rawUrl);
			}
			else
			{
				str2 = string.Concat(contextUri.GetLeftPart(UriPartial.Authority), rawUrl);
			}
			urlAction = urlAction.Replace("{Source}", SPHttpUtility.UrlKeyValueEncode(str2));
		}
	}
	urlAction = SPUtility.GetServerRelativeUrlFromPrefixedUrl(urlAction);
	return urlAction;
}

Reference

• CustomAction Element
• UrlAction Element
• UrlAction Tokens Of The CustomAction Feature

The following script (credit to Bryan Hart) will update the certicate in a single elevated PowerShell prompt.

###################################
# Apply Certificate to FAST
###################################
write-host "Applying Certificate to FAST" -ForegroundColor Yellow

Add-PSSnapin AdminSnapIn
Add-PSSnapin Microsoft.FASTSearch.PowerShell
Add-PSSnapin Microsoft.SharePoint.PowerShell

stop-service FAST*

$installerdir = $env:FASTSEARCH + "installer\scripts"

cd $installerdir

$pw = ConvertTo-SecureString -AsPlainText -force pass@word1

.\ReplaceDefaultCertificate.ps1 -generateNewCertificate $true -certificatePassword $pw

$cert = @(dir cert:\LocalMachine\My -recurse | ? { $_.Subject -eq 'CN=FASTSearchCert' })[0]

$thumb = $cert.Thumbprint

Start-service FAST*

.\SecureFASTSearchConnector.ps1 -certThumbprint $thumb -ssaName "FASTContent" -username "contoso\administrator"

Reference

• Remember to give your SharePoint 2010 Information Worker Virtual Machine a fresh certificate

• Excel Services
• FAST Search Server
• Office Web Apps
• PerformancePoint Services
• Project Server
• Search Server
• SharePoint

With thousands of document libraries in an established farm, the prospect of visiting thousands of List Settings pages was not at all appealing. PowerShell to the rescue.

The Script

The following script accepts a parent web and enumerates all of its children (optional), altering the libaries that match the criteria “Not a System/Style/Hidden library” and “has minor versioning currently enabled”. The matching libraries are updated to force document checkouts and accept an unlimited numer of major versions (Governance decision, no listening to reason there).

function Reset-SPDocumentLibaries {
	param (
		[string] $WebUrl = $(Read-Host -prompt "Enter a Url"),
        [switch] $ProcessChildren
	) 

	$web = Get-SPWeb $WebUrl;

	ProcessWeb $web $ProcessChildren;
}

function ProcessWeb($web, $processChildren) {

	Write-Host "Processing Web",$web.Title,"(",$web.Url,")" -foregroundcolor "Green";

	$lists = @($web.Lists | Where-Object { ($_.BaseType -eq "DocumentLibrary") -and ($_.BaseTemplate -eq "DocumentLibrary") -and ($_.IsSiteAssetsLibrary -eq $false) -and ($_.EnableMinorVersions -eq $true) -and ($_.Hidden -eq $false) -and ($_.Description -notlike "*system*") -and ($_.Description -notlike "*style*") })

    if ($lists.Count -gt 0) {
    	foreach ($list in $lists) {
    		if ($list.Title.Length -gt 0) {
    			Write-Host "   Processing List",$list.Title -foregroundcolor "Green";

    			$list.EnableVersioning = $true;
    			$list.EnableMinorVersions = $false;
    			$list.MajorVersionLimit = 0;
    			$list.ForceCheckout = $true;

    			$list.Update();
    		}
    		else {
    			Write-Host "   Invalid List Encountered" -foregroundcolor "Red"
    		}
    	}
    } else {
        Write-Host "   No lists matching filter were found" -foregroundcolor "Red"
    }

    if ($processChildren) {
    	foreach ($subWeb in $web.Webs) {
    		ProcessWeb $subWeb $processChildren
    	}
    }
}