Initially, our SPF server was an intranet-only appliance. We had a couple of Alternate Access Mappings:
- http:/ /intranet/
- http:/ /intranet.mycompany.local/
We really encouraged the first one - as it was super easy for users to simply type "intranet" in their browser. Then, we decided some folks from our law firm should have access to a special SharePoint calendar that our internal top brass like to use a lot. So, we set up a Unified Access Gateway and added a 3rd mapping:
- https:/ /intranet.mycompany.com/
Now, there have been occasions where Mr. Internal here at mycompany wants to send Mr. External a link to a document. The simple 'intranet' server name mapping may work just fine for Mr. Internal, but, as you guessed, totally fails once Mr. External tries to click on the link to said document from his mail box.
We are hoping to figure out a method:
- That will allow the first mapping to auto-redirect to the 3rd mapping (UAG)
- Thus, will permit the first AAM to continue to exist
- Thus, keep us from having to tell users to change a behavior we previously encouraged
I've noted that Microsoft offers a URL-rewrite add-on for IIS, and I've seen posts elsewhere on stackexchange that were wary of employing such tactics. I think it would be okay in this scenario, as I need more of a redirect than a re-write.
I realize a redirect isn't going to fix improper links that were previously sent to external users.. but, it should help on a go forward, once an internal user has punched up a sharepoint resource that he wants to share out, he should already have a UAG-ready URL to copy/paste out of the address bar, etc.