After the virtual server is created, edit the properties.

This is only temporary, so you can point it anywhere. You'll have to point it to a local directory. Create a new virtual server in IIS Manager and give it a descriptive name like 'Software Redirect.' When you're walking through the wizard you'll take the defaults. To do this kind of redirection I use IIS directly, I don't get SharePoint involved at all. Of course the URL your users will eventually get to will be the long URL, but the jumping off point will be easy to remember. If you do want short URLs you can have them forward to deep SharePoint sites. They want to use something like and have it forwarded to To set expectations correctly, you should just come to terms with the fact that you aren't going to write SharePoint URLs down, you'll pass them along via or IM. SharePoint URLs can get long and unmanageable and admins want URLs that their users can remember. One of the most common requests I see is for vanity URLs. Enough with the introduction, let's get down to it.

For each of the methods I discuss below I will provide examples of the situation you would use it in. When deciding which redirection method to employ, you need to determine what you're redirecting from and what you're redirecting to. Then when you find yourself needing to, you can use the method best suited for your situation. In this blog post I will show you several different to redirect users in SharePoint. While you can in certain circumstances most likely you will want to use a different approach. Usually they're in the context of 'I want to redirect users, can I do this with an Alternate Access Mapping?' SharePoint admins know that if they don't set their AAMs up correctly that SharePoint will bounce their users around like a SuperBall, so they hope they can harness that power for good, instead of evil. I see questions about redirecting users in SharePoint all the time.

Redirected min hero