Comments on: Host headers for SharePoint / Rename Web Application

By: Host headers for SharePoint / Rename Web Application - IT odds and sods…saves me writing 'em down…! - My Useful Stuff

Tue, 16 Feb 2010 12:41:04 +0000

[...] Host headers for SharePoint / Rename Web Application [...]

By: Francois Souyri

Francois Souyri — Mon, 16 Nov 2009 16:28:42 +0000

Thanks for sharing.
Same as Aaron I found mixed results with just AAM, very often I had to add the host headers manually in IIS (or Host Binding in IIS7) and it was the safest way to have both URL work to point to same web app.

By: Aaron

Aaron — Fri, 06 Nov 2009 15:57:30 +0000

I’ve used this method in the past with mixed results. It always seems to go fine in a lab, but in production I’ve found that this method leaves residual references to the old url which go unnoticed until you try troubleshooting something.

A cleaner way to perform a rename is to extend the web app to a temp url using a different zone, remove the original, extend to the new url on the default zone, then remove the temp. It is a more convuluted process though, and any manual changes to web.configs or other files within the web apps virtual directory will need to be reconfigured.

By: Bruno Erni

Bruno Erni — Fri, 16 Oct 2009 14:45:17 +0000

Hi Jeremy

I renamed a web application in MOSS exactly how you described it, and accessing the application with the new URL works like a charm. However, the crawler cannot index the renamed application any more (it only indexes the default.aspx page at the root of the application, but nothing else).
Any ideas on why this happens and how this can be fixed?

Thanks, Bruno