Skip to content

Redirects for SharePoint 2010

Todd Klindt wrote the definitive article on SharePoint redirects. You can find it here: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?List=56f96349-3bb6-4087-94f4-7f95ff4ca81f&ID=48&Web=48e6fdd1-17db-4543-b2f9-6fc7185484fc

While most of it still holds true, there are a couple things to watch for with SharePoint 2010. The concept is the same: a user enters a simple URL with a friendly name like http://ProjectBigTime.contoso.com and the browser goes to http://SharePoint.contoso.com/finance/projects/BigTime/default.aspx.

Here’s how to make it happen:

Open up IIS Manager.

Highlight “Resource Pools” in the connections pane

In the Actions pane, select Add Application Pool…

Create an application pool

Select Classic from the Managed pipeline mode drop-down menu.

Now you have your application pool created. You can use this same application pool for all redirects. Todd Klindt recommends the separate app pool to avoid excess memory usage. I recommend it because the “Managed pipeline mode” can cause trouble if you have it set to something necessary for an actual SharePoint site.

Next, create a redirect site. Highlight Sites in the Connections pane, and then Add Web Site… in the Actions pane. I named all my sites something like “Redirect Foo,” so the names group all the redirects together in the Connections pane. Pick any folder for a physical path. We will change this really quickly, so no matter what you put in there, IIS won’t be using it. For the host name, enter the simple/easy URL that you want users to type into their browsers, the “ProjectBigTime.contoso.com” or whatever. Click OK.

Site Creation settings

Now, Redirect BigTime shows up in the Connections pane. Highlight it. Then select HTTP Redirect in the IIS section in the center pane. Enter the URL of the actual site, like https://sharepoint.contoso.com/Finance/Projects/BigTime/default.aspx and click the checkbox for” redirect all requests to exact destination.” Click “Apply” in the actions pane.

You of course have to add a DNS entry for your simple URL and point it at the IP address of your SharePoint server.

Now, give the URL a try. You might see something like this: HTTP Error 500.0 – Internal Server Error Calling LoadLibraryEX on ISAPI filter “C:\Program Files\Microsoft Forefront Protection for SharePoint\FSSPUsernameFilter.dll” failed.

500 error

Well, that’s not so good. Let’s go back into IIS Manager. Highlight the redirect site in the Connections pane and double-click on the “ISAPI filters” icon under IIS in the center pane. This will bring up something like this:

ISAPI Filter - delete everything here

Just delete everything in here. Highlight a choice and click “Remove” in the action pane. This is just a simple redirect. It needs no Forefront or ASP or .NET. Get rid of it all.

Now give the simple URL a try. It should redirect you to your real site with the annoyingly long URL. Success!

Advertisements

Esoteric Enterprise SharePoint Stuff

I’ve been a SharePoint administrator for 4 years, and I just finished a migration from SharePoint 2007 to 2010. I’ve had to fix a few big problems, and Google and Bing and the Technet SharePoint forums weren’t much help for some of the particular challenges I faced. So I thought I’d find some place to blog some articles about the trickier problems in the hope that someone else might find it useful.

I felt like I should build my own SharePoint installation and get a domain and put all this up on it. But I’m not a consultant. I don’t have a test environment under my control that I can make publicly available (at least, not without the scrutiny of my corporate overlords). So WordPress is a quick and easy way to write about the lessons I’ve learned.