IIS Work Around 301 Redirects

[DigitalMkt]

We are redirecting page-level content (about 500 pages) from several sub domains to our main site. With IIS, It’s my understanding that file locations must match.

For example:

subdomain/pathA/filename1
mainsite/pathA/filename1

Since the sub domain files are not on the main site, this means we'd create up to 500 zero byte dummy files on the new server and replicate the sub domain directory structure.

With IIS is there a work around for handling page level redirects without duplicating the file location?

In the case of white papers, videos and case studies, we'll imlement directory level redirection.

Thanks in advance.

[Hurf]

My recollection is that you can do this redirect page bu page under IIS Admin (inetmgr) as follows:

1. Browse the website you want to do the redirect for.
2. In the right
pane, right click on the file you want to redirect, and click "Properties"

3. Under the "File" tab, hit the radio selection "A redirection to a URL"

4. Put the target in the "Redirect to" textarea.
5. Make sure "The exact
URL entered above" and "A permanent redirection for this resource"

I don't have IIS installed locally otherwise I would test this for you - but this method is referenced in a few places as above.

Let me know if this helps you!

I have attached a YouTube video below as a visual walkthrough - I am not the creator, just the ermm, locator? ;o)

watch?v=FdU_bBp6KX0