Skip to content

Redirects for SharePoint 2010

December 7, 2011

Todd Klindt wrote the definitive article on SharePoint redirects. You can find it here:

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 and the browser goes to

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 “” 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 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!


From → Uncategorized

  1. Forrest permalink

    I have a distributed SharePoint 2010 farms in 3 countries – Singapore (SG) Thailand (TH) and Indonesia (ID). I used as my guide.

    Using AAM, I have set http://portal in each country’s farm to point to that Country’s http://. So, if I am sitting in Bangkok and type http://portal I want to get http://TH_Server_name but still see http://portal in the address bar. This is nice so that when I “email a link” to a file it will show up as http://portal/… not http://TH_Server_name.

    If I fly to Singapore, connect to the network, and type http://portal I want to get http://SG_Server_Name but again… still see http://portal in the address bar.

    Each DNS for each Country has “portal” pointing to the correct Web Front End IP, and by default for Win7 clients… “Enable Netmask Ordering” is set to the desired behavior. So, http://portal in Bangkok should be default go to the Bangkok server… but it doesn’t. It jumps around between Singapore and/or Jakarta.

    I applied the Redirect described here and it now does exactly what you said… it expands to the long ugly server name and correctly goes to the right server in the right country… but I’m back to an ugly URL in the address bar and I get the undesired server name when I “email a link”.

    Any ideas on how to get what I’m after?

    • Unfortunately, you can’t do what you are trying with the method I’m describing. I think you were on the right track with your first method, using the DNS for each country pointing to that country’s local WFE. I’d try to troubleshoot why DNS isn’t routing to the right WFE. Flushing the DNS cache on end users laptops might fix the issue.

  2. Elton permalink

    Thanks for this instruction. Really very helpful

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: