What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Nigel — Wed, 07 Mar 2007 01:59:46 GMT

Hi Troy i have been waiting for this article for the last 6 months ! Great ! Be aware to ensure that the ISA Server passes through the host header from the client. We recently had situation where a check box had not been checked on the ISA Server and the host header that was being passed by the ISA Server was in fact the internal IP address of the MOSS Server ! - Network Monitor to the rescue to diagnose the problem.

Nigel

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Luis Du Solier G — Wed, 07 Mar 2007 04:53:51 GMT

Great post, thanks Troy

Regards,

Luis Du Solier G.

http://www.sharepointblogs.com/ldusolier

What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

harbar.net — Wed, 07 Mar 2007 12:29:38 GMT

What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Rajesh — Thu, 08 Mar 2007 02:18:08 GMT

Nice post.. I have been experimenting with AAM for few other scenarios with little success

If I have an existing site say http://abcd.mydomain.com in *scalable hosting mode*, Can AAM be of any help in acheiving the following?

Effectively rename http://abcd.mydomain.com to http://<someothername>.mydomain.com after which i should be able to use http://abcd.mydomain.com for some other site?

Also, can AAM be used for the following?

I have a sitecollection at http://abcd.mydomain.com/site/

Can I access http://abcd.mydomain.com/site/default.aspx as http://<somename>.mydomain.com/default.aspx?

Please let me know

Rajesh CKR

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Troy Starr [MSFT] — Thu, 08 Mar 2007 04:54:50 GMT

Hi Rajesh -

Ah, good question about host-named site collections (what we used to call "scalable hosting mode" in WSS v2). Host-named site collections short circuit much of the AAM functionality, including the URL remapping functionality. They're always considered to be in the Default zone, and their URL is always the same URL you supplied when creating the site collection. You cannot use host-named site collections with off-box SSL termination, port translation, or host header manipulation scenarios.

So no, you won't be able to use it to rename host-named site collection URLs. However, you can take a site collection backup of your host-named site collection using the stsadm.exe -o backup command. Then you can delete the original site collection and restore that backup to a new URL using the stsadm.exe -o restore command. Be sure to include the -hhurl parameter to restore it as a host-named site collection.

For your second question, no, I'm afraid SharePoint doesn't support asymmetrical paths, so AAM cannot be used to perform path translation. The path (i.e. "/site/default.aspx") must be the same from the end user's point of view and the SharePoint server's point of view.

If anyone is interested in learning more about SharePoint's host-named site collection feature, you might want to take a look at this blog post: http://weblogs.asp.net/hosterposter/archive/2007/01/31/sharepoint-for-shared-hosting.aspx. It contains a link to a very helpful whitepaper for web hosters. We'll also be publishing more information about this feature on TechNet in the coming weeks.

- Troy Starr

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Mark — Sun, 11 Mar 2007 11:57:27 GMT

Great Post Troy.

You set of the host header of the extended site to be the interal host name. Why is this not enought for sharepoint to workout that it should map requests to http://sharepoint.dmz.contso.com to that web application. Put it another way, why is the manual AAM required. So if I missed something.

Alternate Access Mappings

Johnwe's SharePoint WebLog — Sun, 11 Mar 2007 19:53:22 GMT

With the new capabilities to support SSL termination provided since SP 2 of 2003/WSS 2.0 and out of the

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Troy Starr [MSFT] — Tue, 13 Mar 2007 05:34:23 GMT

Hi Mark -

This would indeed be enough information for SharePoint to automatically add an internal URL, but we didn't end up taking it that far. It's a little tricky to say we'll add an internal URL if you specify a host header, but not if you don't. And to support IP-bound IIS Web sites, we require you to enter a temporary host header in that field and then remove it later. Automatically adding it to AAM would mean you'd need to manually remove it as well.

Still, we'd like to hear your feedback for the next version of SharePoint. Should we automatically add the internal URL if you fill out the host header field? Let us know what you think!

- Troy Starr

Alternate Access Mapping (AAM) With SharePoint

TheKid.me.uk — Fri, 16 Mar 2007 03:43:09 GMT

I was going to write a small article about alternate access mapping within SharePoint, but it was never

What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Microsoft SharePoint Products and Technologies Team Blog — Mon, 19 Mar 2007 07:42:37 GMT

In Part 1 of my blog series on Alternate Access Mappings, I gave a brief introduction to the feature

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

sarav — Tue, 03 Apr 2007 20:05:54 GMT

nice post buddy, well i have problem in AAM.like i have created a portal with the <sysname>:<portnum> now i want to change the name of that portal to <somename.net> is it possible to do like this.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Troy Starr [MSFT] — Sun, 08 Apr 2007 22:32:29 GMT

Hi Sarav -

If all you need to do is change the URL that users browse to, without changing the IIS bindings (protocol binding, host header binding, or port number binding), then you can just go into AAM and modify the URL into a new URL. However, if the IIS bindings need to be updated, then it is best to remove the web application from that zone and then re-extend the web application to that zone using the new URL and bindings.

- Troy Starr

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Ted Vreeland — Tue, 10 Apr 2007 23:32:52 GMT

Hi Troy,

Excellent article, but I do still have a question regarding this alternate access mappings.

Let's say you want to create an external URL that looks like this "http://www.troyrocks.com" and this internet address needs to point to your sharepoint site but you don't want users to see the sharepoint junk in the url that internal users can see("http://internal.troyrocks.com/pages/"). I guess what I'm asking is whether it's possible to set up the mapping down a level (if that makes sense).

Thanks in advance,

Ted

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Troy Starr [MSFT] — Wed, 11 Apr 2007 20:39:35 GMT

Hi Ted -

Hmm... I'm not sure I follow your question. My response to Rajesh in an earlier comment of this blog post might address your question, though. Also, AAM applies to the whole web application, not a subset of it. If that doesn't address your question, let me know. :-)

- Troy Starr

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Joe — Sat, 14 Apr 2007 07:01:24 GMT

Here's what I'm trying to do - I'm wondering if you can help.

I have a server "spserver1.mydomain.com" where I have MOSS 2007 installed.

I want end users to be able to go to "portal.mydomain.com" (instead of our internal naming convention of "spserver1").

So I set up a record in DNS for "portal.mydomain.com" to go to the same IP address as "spserver1".

Now "portal.mydomain.com" gets me to MOSS, but the URL in IE changes to "spserver1.mydomain.com". I want

it to stay as "portal.mydomain.com".

So I went into Central Admin/Operations/Alternate Access Mappings and

changed the default URL to "portal.mydomain.com".

That seems to work from a user point of view. Users can go to "portal.mydomain.com", and the browser address bar stays as "portal.mydomain.com".

However, now when I go into Central Administration and click on SharedServices1 to administer Shared Services, it challenges me for a login and password, and it will not accept even a valid login and password. In the challenge window, the title

says "Connect to spserver1.mydomain.com", but in the window itself, it is referring to "portal.mydomain.com", which I am assuming is the source of the problem.

If I type in the URL "spserver1.mydomain.com/ssp/admin", it works properly - I can get into the Shared Services Admin.

Is there a way that I can make it use portal.mydomain.com, yet have Central Admin continue to work correctly?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Troy Starr [MSFT] — Sun, 15 Apr 2007 23:06:53 GMT

Hi Joe -

A couple of questions...

1. When you updated the AAM URL to be "portal.mydomain.com", did you do it for each web application, including the SSP Admin web application?

2. What kind of authentication is configured for the SSP Admin web application? If it is Negotiate/Kerberos and you're using a domain account as the application pool account, you may need to register a new service principal name for the "portal.mydomain.com" domain name for authentication to succeed. You could try temporarily switching the authentication from Negotiate/Kerberos to NTLM via the Authentication Providers page in Central Administration to see if that's the cause.

- Troy Starr

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Joe — Tue, 17 Apr 2007 05:33:41 GMT

I did eventually get it working (somehow) but to answer your questions:

1. I did not change each web application, but I don't see how that would help with the SSP Admin - it's not running on a separate port. It's running on port 80 also (spserver1.mydomain.com/ssp/admin). The only things I can change (in AAM) are the Sharepoint application itself (port 80), the My Sites application (running on port 8080) and the Central Admin application (running on port 43861).

2. It is Kerberos.

What I ended up with that works are two entries in AAM for the portal:

#1:

Internal URL: http://spserver1.mydomain.com

Zone: Default

Public URL: http://spserver1.mydomain.com

#2:

Internal URL: http://portal.mydomain.com

Zone: Intranet

Public URL: http://portal.lptdomain.com

I suppose my mistake was continuing to try to use spserver1.mydomain.com as the "Internal URL".

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Ian Moran — Wed, 18 Apr 2007 04:46:13 GMT

Thanks for the post Troy. Quick question. I'm running into a lot of confusion when ports othetr that port 80 are used in terms of AAM.

Specifically I have an internal site - http://server:6000/sites/intranet which I'd like to publish as http://sharepoint.company.com - is this possible drectly using AAM or must I move the site to a new web app on port 80 ?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Brian Gough — Wed, 18 Apr 2007 23:59:13 GMT

This is great information, thanks you for taking the time.

My question is regarding the best way to add SSL to a site. We have a WSS 3.0 site being used as an internet site. Curently it doe snot use any SSL certificate. We would like to enable SSL on the site without having to recreate everything nad hopefully set it up so that if users have already bookmarked http://oursite.com they will automatically be sent to https://oursite.com. When we extend the site to add SSL, it creates a second IIS instance. Does this have to be the case or is there a better way to do this?

Can you recomend the best way to accomplish this?

Thank you!

What every SharePoint administrator needs to know about Alternate Access Mappings (Part 3 of 3)

Microsoft SharePoint Products and Technologies Team Blog — Thu, 19 Apr 2007 03:14:37 GMT

In Part 1 of my blog series on Alternate Access Mappings, I gave a brief introduction to the feature

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Tiffany — Tue, 24 Apr 2007 05:42:38 GMT

Thanks for the great post, Troy! I'm a little be bit lost on the "extend web application highlighted.png" image though... If the site that I want to extend is http://sharepoint.dmz.contoso.com at port 80, then when I extend it, I will give it a different port and URL? If so, then which one will I use for the Internal Hostname and Port #? Thanks!!!

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

k0D — Tue, 24 Apr 2007 14:25:05 GMT

Here's what Im trying to do:

- The server with sharepoint services 3.0 is called (de-applserv).

- I want users to go to (wss.domain.com) instead of the netbios server name (de-applserv).

- I've setup a DNS record on DC to forward (wss.domain.com) to (de-applserv) ip address.

- Every time I go through (wss.domain.com) it asks me for credentials whitin domain environment but if I go through the netbios name (de-applserv) it doesn't ask me. Basically I don't want WSS to prompt for credentials if Im connecting whitin the domain using (wss.domain.com).

- I'm using NTLM, Windows Authentication and default application pool (local service), in host header I use the dns record I've setup (wss.domain.com) also if I setup the host header with (de-applserv) and the public url with (wss.domain.com) it doesn't work, when I type the domain in IE it popup 400Error.

- I've tried everything (creating different web applications with different settings) and didn't work, when I try to use kerbebos it prompts for l&p and even with correct credentials it doesn't authenticate me.

- Also I've try simply add an AAM (wss.domain.com) to an existing web application but when I type the full address it comes with 400 Error.

Need help here, can you please tell me step by step what should I do 2 have it working.

Regards

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

marc — Tue, 24 Apr 2007 20:31:38 GMT

Hi Troy thanks for the nice post!

Do you know, why sharePoint not just uses relative links?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Steve Cage — Fri, 27 Apr 2007 16:41:43 GMT

Hi Troy,

Do you have an example of setting up AAM when using a Cisco router. I have been trying to set alternate authentication for the same content. NTLM for internal and Basic for External.

I followed your example as best I could but evertime I connect to the new site it is returning the default name instead of the name accessible from outside.

Thanks

How to configure Alternate Access Mappings (AAM) successfully

Duray Akar's Blog — Sat, 28 Apr 2007 00:50:57 GMT

To avoid many questions and simplify troubleshooting, I would suggest this order when configuring AAM,

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

PL — Tue, 22 May 2007 13:07:14 GMT

How can use this for Project Server. I have created my Project Web Access site i.e.. http://intranet/pwa. I cannot edit the host header in the Project Web Access settings. Is there a way around this where i can use AAM?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Jimmy — Tue, 22 May 2007 15:23:28 GMT

Hi Troy

Thanks for the post, I have a question thou. Must we have a proxy server?

How will this work with a front end server?

Will all the links became https:// even if you are in the internal network.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Dave — Fri, 25 May 2007 06:10:19 GMT

I still don't understand how to make http://xyz.com and https://xyz.com to work side by side without limitation to web content editor web parts barking about can't save changes or unsecure/secure content messages.

Using a reverse proxy for this.

Thanks

Still having problems.

dano88 — Wed, 30 May 2007 00:05:48 GMT

Thanks for all the info on this topic. I unfortunately am still having issues.

I have WSS installed on the DMZ interface of my Cisco firewall. I am trying to connect from the inside interface. I am using NAT to map 74.8.14.153 to 172.14.1.23 ( the IP of the sharepoint box). DNS is configured for gza-sharepointx.gza.com to 74.8.14.153.

AAM Mappings are as follows:

http://gza-sharepointx Default http://gza-sharepointx.gza.com

http://gza-sharepointx.gza.com Default http://gza-sharepointx

http://74.8.14.153 Default http://gza-sharepointx.gza.com

I am getting "Unable to determine IP address from host name for gza-sharepointx.gza.com".

Any idea as to what I am doing wrong?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Mats Larsson — Thu, 31 May 2007 15:52:39 GMT

Nice article,

I like to have the same address both on the inside and the outside, say: http://page.company.se

So in SharePoint I have a web application called http://page.company.se and I have a extended I with the name http://extpage.company.se

In the ISA I have a rule translating external http://page.company.se to internal http://extpage.company.se

Until now everything works well beside some links on the outside is not correct so lets try to correct this by entering a rule in AAM solving this.

But this cant be done because it is not possible to add such a rule in AAM, it seams the external and internal name can not be the same or am I missing something?

Is there a solution for this scenario.?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

MarkB — Fri, 01 Jun 2007 02:13:48 GMT

I have SharePoint services 3 and ISA 2006. I published the internal site http://server1 as">http://server1 as https://name.domain.com. Everything else works great except for the Document Library. If you mouse over the name of the document, the status bar shows the correct external name and the path to the document. But, if you try to open the document, the url now shows as the internal server name, that is http://server1/folder/name.doc">http://server1/folder/name.doc, instead of https://name.domain.com/folder/name.doc. So from an external URL, it goes back to an internal URL, which causes the opening of the document to fail.

I have the following in AAM:

Default: https://name.domain.com

Intranet: http://server1

Internet: http://server1ext

Custom: http://server1:2240

What could be going wrong? In ISA, the "Forward the original host header..." is unchecked. There is no additional manual link translation mapping configured, aside from the automatically created one when I created the SharePoint rule.

What every SharePoint and EPM administrator needs to know about Alternate Access Mappings

Christophe Fiessinger's Blog — Thu, 07 Jun 2007 23:50:19 GMT

Useful links if you need to configure reverse proxy for instance: ¾ http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

DDuff — Tue, 12 Jun 2007 17:03:44 GMT

Great article-

We have a website that we want to integrate with Sharepoint 3.0. http://test:8080/sites/ is the site that we created, but we need to get rid of the port number in the url. Is the scenerio above the best solution to accomplish this. We want http://server name/sharepoint and http://www.servername.conarc.com/sharepoint. Another question: In personal mode, can we have 1 web part where employees can change a url, such as www.yahoo.com. I noticed it only lets you change url's in shared mode. Any help would be appreciated. Thanks.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

shive72 — Mon, 18 Jun 2007 21:51:25 GMT

Great article

Going kind of of topic but would I need to have my Sql server in the DMZ ?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

gheatly — Fri, 22 Jun 2007 06:35:40 GMT

Not sure if this Blog is still being monitored but I will say great post Troy.

My issue is that my internal Sharepoint site works just fine but my public facing site is having issues with the directory index files displaying. Here is my post on several forums:

I have installed and configured my SharePoint Server 2007 successfully on my Windows 2003 Server Standard box (named server01) and works great on my local network (i.e. http://server01/site01 (subsite site01 used in this example)). However, when attempting to access the site remotely on the web (i.e. http://www.somedomain.com/site01) I get the dreaded "The page cannot be displayed" error. Yet when I call the site up adding the default.aspx to the end as http://www.mydomain.com/site01/default.aspx it comes up just fine. I checked the documents setting on IIS for the site(s), I see default.aspx listed there as an accepted directory index file for the server to look for. This issue would not be such a big deal except that a lot of the navigation links in Sharepoint rely on this working.

Anyone have any ideas and/or can you also point me to a good site that discusses preparing Sharepoint for access via the web??

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Jeeves — Tue, 26 Jun 2007 19:47:42 GMT

Hello,

Great post. Helped me out tons. I however, have one small problem. I am able to access my SharePoint server remotely and pretty much do what I want, however anytime I try to access MySite it points back to my internal address. This happens to everyone. Not sure why. Any suggestions?

Also, I am using ISA 2000. I have read on some sites that publishing SharePoint 2007 through ISA 2000 will have some limitation. I am not sure what it is exactly. I was unable to find a SharePoint Publishing Wizard in ISA 2000. Am I missing something? Is the MySite issue I have related to this? Anything would be great. Thanks in advance.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Mats Boisen — Wed, 27 Jun 2007 12:54:31 GMT

We host web sites for a long list of external companies (> 100). They all have their own public url (www.customerA.com...). Now we want to use the same Sharepoint web application for them all since they share a lot of data. Since AAM only allows 5 public urls I cannot give each customer their own. I can give them their own internal url but then Sharepoint will redirect to and include links to the external url (www.mysharepoint.com) and not the customer url. How am I supposed to set AAM up to allow > 100 customers with their own host headers to access the same web application and have Sharepoint generate links (and so on) that points to the customer url and not our internal? // Mats

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Kevin — Tue, 10 Jul 2007 16:49:58 GMT

Mats I have the same requirement for our environment. I need more than 5 Public URL's, have you found a soultion for this?

Troy do you know a way to do this in MOSS?

Thanks

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Alex Chow — Fri, 13 Jul 2007 13:08:16 GMT

This is a great post. I configured my site as follow:

Default: http://server:4000/

Public URL: https://portal.abc.com/ (Internet Zone)

AAM Internal URL: http://moss.abc.local:4000/ (Internet Zone)

I have SharePoint publishing rule created as above.

However, when sps generate email alerts, the URL within the email is using "moss.abc.local" rather then "portal.abc.com". Therefore, those URLs are not accessible for internet users.

Did I miss configured something?

Thanks

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Jason — Wed, 08 Aug 2007 20:21:24 GMT

Is is a requirement that ISA Server 2006 be installed in conjunction with MOSS 2007 to be able to access it across the internet without errors and deadlinks?

too many authentication challenges

sham — Sat, 11 Aug 2007 00:07:53 GMT

We have wss 3.0 environment. We have multiple domains, one server farm with basic authentication. Will alternate access mapping solve the situation where the user is required to enter user and login everytime a document is loaded from the document library

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Sara Porter — Tue, 14 Aug 2007 17:23:44 GMT

I have 2 sharepoint front ends load balanced by an F5 appliance. I built the initial site on an IP published through F5 - http://server.college.edu, and this works great. I extended it to a new IIS site (which I let sharepoint create- sharepoint also put in the AAM) called https://server2.college.edu and am publishing that through ISA. However, sharepoint did NOT put a host header on this web application in IIS(even though I entered one where it asked for it when extending) and if both servers are in the pool the website times out. Any ideas?

All you need to know about Alternate Access Mappings (AAM)

Mirrored Blogs — Fri, 17 Aug 2007 23:04:34 GMT

Troy Starr of the WSS Test Team has written an excellent 3-part article detailing AAM. The details can

Tips from Top Support Calls

Joel Oleson's SharePoint Land — Thu, 30 Aug 2007 01:12:48 GMT

I was in a thread recently where Gabe Bratton was looking through top support issues and looking at ways

re: AAM Lookup Column Problems in Datasheet View

Benjamin Hill — Fri, 07 Sep 2007 18:04:29 GMT

Hello. Thanks sooooooo much for the AAM article. It has been very helpful in getting AAM working. I have run into an issue that I haven't been able to resolve. I have a List with a Column that does a lookup to another list within the same site. Everything works fine internally using the //server address, but when I go outside to a FQDN that is relying on AAM, my Lookup Columns are populated, but there are no options to change the values and if any other field is modified, it gives "The text entered for FieldName isn't an item from the list. Select an item from the list, or enter text that matches one of the listed items." Again, this is ONLY in Datasheet view and ONLY from the FQDN that uses AAM. I have a dedicated WSS box behind ISA 2004. Any ideas where to start looking for a solution?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Cezary — Fri, 07 Sep 2007 23:21:42 GMT

Helo Troy.

Thanx for the article. I want to ask you if AAM works fine with a diffrent languages packs. I have an English site and "extended" for let say port 1818. Created site collection in french language. (previously installed).

When I go to let say http://server:1818 french language site is completely displayed and all magmt is also french. however when used a AMM and point to internet let say http://www.domain.com it does display site in french however mgmt tasks are in english.

Am I doing something wrong ???

Thanx

Všetko o Alternate Access Mappings (AAM)

Cvalik's blog — Sat, 15 Sep 2007 12:24:54 GMT

Troy Starr napisal velmi pekny 3-dielny serial o AAMČasť 1Časť 2Časť 3

WSS 3.0 & MOSS: Recopilación de enlaces interesantes (VII)

Blog del CIIN — Mon, 17 Sep 2007 09:44:33 GMT

Retomando el clásico recopilatorio de recursos y enlaces que sobre WSS 3.0 & MOSS venimos realizando

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

gi — Sat, 13 Oct 2007 21:18:21 GMT

I created AAM for my central admin site. During that time I entered http://1server:5678 instead of http://server1:5678. Now I can't access the central admin. Central admin display error message. Need your help.

Thank you,

gi.

MSDN/TechNet forums for SharePoint at http://mssharepointforums.com - the place for Q&A and discussions!

Microsoft SharePoint Products and Technologies Team Blog — Mon, 22 Oct 2007 21:33:43 GMT

Since the SharePoint 2007 products (WSS 3.0, MOSS 2007, and SPD 2007) released about 11 months ago, there

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Pankaj Sharma — Tue, 23 Oct 2007 10:05:10 GMT

Great Post Troy Starr!

It helped us to implement our intranet on public server.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

zullu — Wed, 24 Oct 2007 05:44:00 GMT

Jumbo!!!

Nice reading the whole lot of information on this topic.

Thanks for starting the thread...Troy.

You are awesome !

I will love to have this implement in my environment.

Keep on going.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Sandeep Nahta — Wed, 31 Oct 2007 12:57:05 GMT

Hi Troy

Please answer the post. Lot of question are not answered and maps to common senerios. Appriciated.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Arjan — Sun, 04 Nov 2007 16:20:21 GMT

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Hello,

---------------------------------------------

The error listed below is the exact same situation as we experience...

We use ISA 2006 publishing with Alternate access mappings on sharepoint.

We have used the MS procedure found on MSDN and technet.

However we find that when a site is in a top-level site container as with the self service site creation /sites/ we are redirected to the internal link.

Please give me help on this.. We use HTTPS on the isa internet listener and the internal website is HTTP.

Arjan L.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Jason Miller — Thu, 15 Nov 2007 20:47:29 GMT

I am facing a situation where I will have multiple portals in an extranet dmz. They all require SSL.

Question:

1. Given that I do not have ISA and only F5 Switch, should I do SSL termination at the F5 layer? If so, what other steps would I need to perform in order to have all three portals set up correctly?

2. Are there any other options if I cannot do SSL termination at F5 layer?

Thanks for any feedback.

Troubleshooting WSS Search - EventID 2424 & 2436

Mirrored Blogs — Tue, 20 Nov 2007 02:57:06 GMT

Corpo: Olá pessoal, Bom, este é um artigo muito interessante ... basicamente por tratar de alguns detalhes

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Gavin Ramm — Wed, 05 Dec 2007 01:58:50 GMT

This was helpful but I'm trying to use SQL 2005 Reporting Services in Sharepoint Integration mode. I'm running into an issue where the SQL Reporting Service webpart brings back an error "The request failed with an empty response." I've followed the above to setup ISA 2006 and Sharepoint for Alternative Access.

Has anyone got the following setup working?

isa 2006 + sharepoint 2007 *published via isa2006* using Alternative Access with Reporting Services in Sharepoint Integrated mode?

What every SharePoint administrator needs to know about Alternate Access Mappings

ramin — Tue, 11 Dec 2007 18:29:25 GMT

I'm running into a lot of confusion when ports othetr that port 80 are used in terms of AAM.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Darryel — Wed, 12 Dec 2007 18:08:14 GMT

Hello Troy I am a newbe at SharePoint 2007, I loaded the software and every thing when great until I went to login, I got an unexpected error occured, and my default web site will not start in IIS.

HELP Please.

Darryel

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Matthew Mueller — Mon, 07 Jan 2008 05:02:36 GMT

Hi! I've just installed WSS 3.0 on my server and can't figure out how to have the main site with a short url - like it was before with WSS 2.0 ->http://companyweb

Is there a kind soul to help or direct me to the right answer (steps) to have something more friendly than http://server:port/site/sharepoint.

Thanks in advance

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Nikhil Shah — Thu, 10 Jan 2008 21:26:38 GMT

I have setup a MOSS Site. I have been attempting to open it up externally. I have added a DNS record that points sharepoint.smartonline.com to the public IP address. I have also added that site as internet in AAM. For some reason i can not access this site externally. The server hosting this site is secured but we have openned it up for http/https only. Any insight?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

brent.flesner@illinois.gov — Tue, 05 Feb 2008 18:41:25 GMT

Should users be prompted to logon again when editing or creating new documents? Users are accessing Sites over the Internet via ISA 2006 Forms Based Authentication via AD (SSL Termination and AAM configured) with SSO enabled. We have the ISA rule Authentication Delegation configured for Negotiate (NTLM\Kerberos). Users can navigate from one web application to another without being prompted until they try and edit or create a new document in a document library.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

bbeer — Fri, 08 Feb 2008 07:29:59 GMT

Is it possible with AAMs to have the one URL redirects to a sub site path of another URL

For Example

I have two domains x.com and y.com

x.com is a WSS site. Under x.com I create a subsite x.com/y_site. Can I configure sharepoint to redirect requests to y.com to x.com/y_site if the IP of both are the same without the browser showing the redirect?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

AlexM — Mon, 25 Feb 2008 03:38:42 GMT

So a huge hurdle we've never figured a way around is how to put both MySites and the "main" web app both on port 80 and yet on their own individual web apps, BEHIND ISA, without using the expensive kludge of a "wildcard SSL Cert."

I guess that this post (if it's still open) would be among the rare few that would know what that sentence above even means. I have applied link translation, and the links still come through with the HH URL of the mysites virtual server, not the translated / AAM URL.

One intriguing idea that Troy posted above was to stsadm -o restore and "Be sure to include the -hhurl parameter to restore it as a host-named site collection." But would this be a good idea with thousands of MySites?

Eagerly awaiting any thoughts anyone might have on this topic.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

AAM — Mon, 25 Feb 2008 20:11:18 GMT

I have a portal wich have a lot of sites... one of them http://www.myportal.com/subsite1/ have to be open by a diferent name. for example when I type http://www.other.com has to open http://www.myportal.com/subsite1/ ,... how I can do that??? That a diferent domain opens a subsite?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Son Dao — Thu, 06 Mar 2008 00:30:36 GMT

If I turn off "Forward the original host header" option in ISA, KPI List View (KPIListViewPage.aspx) will fail with "Value does not fall within the expected range". Do you know how to resolve it without have to turn the forward option On

Whatever happened to parts 2 & 3 ?

Mark Mills — Mon, 10 Mar 2008 22:06:47 GMT

Whatever happened to parts 2 & 3 ?

where can I find them.

Your title after all was "What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)"

Parts 1, 2 and 3 are now found

Mark Mills — Mon, 10 Mar 2008 22:11:11 GMT

Oops- I posted too soon, I just found the links to the parts 2 and 3 of this article....

http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

http://blogs.msdn.com/sharepoint/archive/2007/03/19/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-2-of-3.aspx

http://blogs.msdn.com/sharepoint/archive/2007/04/18/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-3-of-3.aspx

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

RW — Wed, 12 Mar 2008 23:48:37 GMT

Hi Troy, great piece of information. I was reading thru this blog and found this part: "...For your second question, no, I'm afraid SharePoint doesn't support asymmetrical paths, so AAM cannot be used to perform path translation. The path (i.e. "/site/default.aspx") must be the same from the end user's point of view and the SharePoint server's point of view..."

is this for real? disappointing my question is how people implement MOSS in their organizations I pretty much have problem seeing our users typing path like http://servername.domain.com/sites/home/pages/default.aspx it's crazy don't you think? I tried to create HTML redirect page and place it on IIS in MOSS website under Documents - Enable default content but this gets ignored in sharepoint configuration any other web application we use it will read default doc but sharepoint.. do you have any ideas how to make MOSS recognize http://server.domain.com and redirect to /sites/home/pages/default.aspx ?

since I get bad request page cannot be displayed I try to use URL /sites/home/pages/default.aspx instead of default IE error this did not work either.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

ISAMBERT Patrick — Mon, 17 Mar 2008 18:01:41 GMT

Hi,

We test MOSS 2007 on Windows 2K8 for an extranet project for an university.

We have a lot of problème with AAM. The configuration is the same you described.

Default : http://www.sitemire.net (anonymous possible)

ISA server route to http://www.ext.sitemire.net (web application extension in Internet zone, farm url https://www.sitemire.net, no anonymous)

Internal Adresse added http://www.ext.sitemire.net (Internet zone, https://www.sitemire.net)

Here is the sum-up of the problems :

A> On the site with anonymous logon on http, none in https :

1> When we made a postback via https (in administrative tasks for example), we are redirected to http://www.sitemire.net (with an display error) but the code behing the postback is executed. If we modified in url, http:// by https://, it's ok.

2> When we connect from ISA with https://, we are also redirected to http://. We must click on connection in the top right.

B> Other Problems from Internet

1> when we have a subject in discussion with accent, it is impossible to reply. In Intranet, no problem.

2> it's impossible to setup a personal site form Internet. In Intranet, all goes well.

Does someone can help us ?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Tim Niemann — Mon, 31 Mar 2008 16:33:03 GMT

Good post, maybe someone can help. We have a MOSS 2007 site in our DMZ and want to make it our internet server. After Network guys changed DNS, the www.homesite.com resolved to http://servname/ as opposed to www.homesite.com and get access denied. Internally we could type www.homesite.com and it would chnage to http://servername and worked fine.

Any ideas on what to do?

Thanks

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Darrel — Wed, 02 Apr 2008 21:11:53 GMT

This article gets referred to quite a bit as a reply to a question we've been stuck on. Alas, it's not quite specific to our case.

We're using off-farm SSL termination (Netscaler) which then communicates with the MOSS farm via HTTP.

What, exactly, are we supposed to have in AAM to handle this?

Is the AAM supposed to handle the rewriting of HTTP links into HTTPS for us? Or is that something the load balancer (which has the SSL certificate) is supposed to do?

I see mention of host-named site collection issues. We ARE using host names for the web application, but not site collections themselves, so I don't know if that's the issue we're having or not.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

t niemann — Wed, 02 Apr 2008 22:50:00 GMT

How does AAM work with the MOSS Enterprise Search?

Thanks

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

smith kennedy — Thu, 03 Apr 2008 23:01:41 GMT

What about those of us who need to do exactly this (Because we are using the same IIS Server to push mail.domain.com/owa and portal.domain.com) out to the public internet? It breaks OWA every time we get it mapped out but leaves portal.domain.com working.

We do not use ISA Server.

Microsoft SharePoint Products and Technologies Team Blog : What every SharePoint administrator needs to know about Alternate Access Mappings

SharePoint Thinks, Links and Clinks — Wed, 09 Apr 2008 16:14:06 GMT

A series of three posts regarding configuring and understanding one of the top reasons that SharePoint

How to publish sharepoint site with ISA 2006

MCPBlog — Tue, 06 May 2008 18:34:09 GMT

Body: If you're have trouble to handle Alternate Access Mappings and configure them so that outside

MOSS Form Based Authentications

Man On The Way — Wed, 21 May 2008 07:35:54 GMT

MOSS Form Based Authentications Part 1 - http://msdn2.microsoft.com/en-us/library/bb975136.aspx Part 2 - http://msdn2.microsoft.com/en-us/library/bb975135.aspx Part 3 - http://msdn2.microsoft.com/en-us/library/bb977430.aspx MOSS Alternate Access Mappings

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Pete — Thu, 29 May 2008 02:35:45 GMT

I have MOSS running with My Sites but there is a problem with the config somewhere giving me trouble with the My Sites link.

From the LAN when I click on the My Sites link it sends me out to the public address.

I reviewed the AAM's and have the public ip set as extranet. It was formerly Internet but we had the same issue.

I removed this link last week and put it back the next day. All worked fine for a day then it started happening again.

Removing and putting the external AAM back did make a difference but it didn't last.

Is this an AAM problem or should I be looking elsewhere?

Zones, Alternate Access Mappings, and Internal URL's...Oh My!!!

Blog-Mania — Sat, 31 May 2008 03:45:00 GMT

Zones, Alternate Access Mappings, and Internal URL's...Oh My!!!

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

yd — Wed, 11 Jun 2008 15:57:32 GMT

I have a sharepoint 2007 server with 2 IPs. I used one IP for a web site with SSL. It works fine. Then I used the other one for two web sites. Both the web sites work fine on my computer, all the computers in our office (~10) and some computers on other subnet(i.e. x.x.133.x), but we couldn't access the two sites through other subnets(even some PCs on x.x.133.x). I don't know it is a web site configuration issue or a network issue.

Thanks in advance.

Great post... the DMZ name and mapping are key!

Mike Knowles — Tue, 24 Jun 2008 23:12:31 GMT

Great post on a very confusing and sparsely documented area of MOSS administration. Those screenshots are gold.

Very important to follow the steps exactly. The first time through I thought I could skip the additional dmz entry and instead just map directly to the machine site (http://sharepoint). I then stumbled on the problem discussed in part 2 of where if the additional dmz entry is not created, you get random pages not returning correctly. For me these pages (Publishing site) were Manage Content and Structure and trying to start a workflow on a document added to the doc library. Also, the http://sharepoint url was showing up in emails e.g. added to approval group, click here to view workflow status, etc.

For the additional dmz entry (sharepoint.dmz.contoso.com) what I did was to add an entry to the hosts file on the ISA and Sharepoint server that pointed to the address of the Sharepoint server so that I would not have to add an IP to DNS. It seems to work just as well. All the problems I had initially are working now.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

John — Tue, 01 Jul 2008 18:13:29 GMT

Hi, congratulations for the post. I have this situation: I want that my sharepoint reply to requests for some documents that reside in a Sharepoint Library. This requests are made from servers in a different newtork, that cannot authenticate in my Active Directory.

How can I accomplish this? Any ideas?

Regards

John

Alternate Access Mappings Unvieled

Coding Times of a .Net Developer from Yard — Tue, 29 Jul 2008 16:34:44 GMT

Wanna know what SharePoint is doing when you change and/or use the Alternate Access Mapping Feature?

AAM and Cisco Load Balancing

Matthew McDermott — Tue, 05 Aug 2008 23:02:19 GMT

For those of you looking for answers to the Cisco Load Balancing question I posted this: http://blogs.catapultsystems.com/matthew/archive/2008/08/05/aam-and-ssl-termination-1.aspx

HTH

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Marc — Thu, 07 Aug 2008 05:23:11 GMT

OK, newbie here to MOSS 2007, but have worked with WSS 2.0 for a few years now. I am working on upgrading to MOSS 2007, and I need this to be accessible to our users from home via the Internet. In the past, it was as simple as pointing a public IP to the server and connecting. Now, I run into an issue with the site. I have the public IP poiting to the server, and it will connect, but only if I use the full address. So, if I try to go to http://publicIP, I get a page can not be diaplyed. If I enter http://publicIP/default.aspx, I am able to get the login screen and then into the site. Trouble is the navigation in the bread crumbs does not point to the full address, but only the http://publicIP. Is this where the mappings help me out? Thansk to anyone who can help!

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Bryan — Thu, 21 Aug 2008 01:55:08 GMT

I have a load balancer on the front that is terminating SSL and things weren't working right until I configured things as you described here. This is the only place I have been able to find the answer. Thanks for this post. It saved my life...

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Murali — Tue, 16 Sep 2008 05:19:10 GMT

we have internet facing portal and using AAM we have used a custom name to portal. Entire Portal works perfectly except the search results.

They still show the sitecollection name in their URL. Due to this we are unable to browse search results. To Avoid that we have created a Redirector in IIS even, but still the search pages dont get redirected as expected.

What mistake could have happened. please let me know so that issue can be solved at the latest.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Felipe Ferreira — Fri, 19 Sep 2008 15:58:24 GMT

Hello,

I had configured the AAM feature. now I can access sharepoint correctly from inside and outside...but I can't create new websites and access the usage log reports.

Sharepoint throws an error about File Not Found. If I try to create the site using the internal URL, then it works fine..

have any thoughts on this?

thanks,

Felipe Ferreira < felipe.ff at msn.com >

Hey please help me regarding this issue

Bhuvana — Tue, 23 Sep 2008 08:38:19 GMT

Please give me answer to my following issue:

There is a link to another website in my portal. If i open my portal as intranet site, then the link should also open as intranet site and if i open my portal as internet site,then the link should also open as internet site.

Tell me how to do this?

Распространенные ошибки при настройке Sharepoint

Bong's Blog — Sun, 19 Oct 2008 10:48:47 GMT

Очень интересный пост , в котором приведены наиболее частые проблемные вопросы при обращениях в службу

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

Frost — Tue, 02 Dec 2008 07:18:37 GMT

Thanks, it works perfect. appreciate it. Impressive article.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

knrfmd — Thu, 12 Feb 2009 00:10:09 GMT

*** BUMP ***

So has anyone found a solution to the mysite problem???

*****

Eagerly awaiting any thoughts anyone might have on this topic.

Understanding extranet setup for MOSS 2007

SharePoint — Wed, 04 Mar 2009 20:08:04 GMT

Links: Design extranet farm topology (Office SharePoint Server) Downloadable book: Planning an Extranet

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

sparames — Thu, 14 May 2009 20:05:18 GMT

Hi Troy,

Your article was very helpful. We are configuring our shpt farm with the offbox SSL on an f5 device. I have question about IP addresses for each of the urls listed above

: Public URL : Virtual IP address on F5

: Internal URL : Can this share the same iP address as public URL

: MOSS web application: what should the ip address be ?

THe issue is the web applications are hosted out of 3 load balanced web front ends - which are currently loadbalanced using the f5 device

I would really appreciate your input.

Thanks

Saumya

Useful Sharepoint Links

a blog or 2 — Tue, 16 Jun 2009 17:45:58 GMT

Useful Links · MOSS Video Demos (Total 14 Modules) · Before You Begin with SharePoint Server 2007 · MOSS

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

sohbeti — Thu, 02 Jul 2009 01:28:31 GMT

sesli sohbet ses sohbeti - sesinizi açın sesli sohbetler - sesli sohbet siteleri.

web tasarım

web tasarım — Sun, 09 Aug 2009 18:12:19 GMT

super thank you http://www.parcakontorbayiniz.com mıracle