A real scenario for Configuring Alternate Access Mapping inside SharePoint Server 2013

In my scenario, I have

The desired as follows

If I navigate to this URL “http://epm”, It should be pointed directly to web application URL.

In this article, I will demonstrate How to map an internal URL to be associated with a web application public URL by performing the following:

  1. Configure alternate access mapping via Central Administration.
  2. Configure SharePoint Site Bindings.
  3. Configure Hosts file
  4. Disable loop Back Check
  5. Add “A” record on DNS server for your URL

Finally, I’m gonna show some alternate access mapping considerations.

Steps:

1. Configure alternate access mapping

  • Open Central Administration as administrator > System Settings > Configure Alternative Access Mappings.

Configure AAM

  • The Alternate Access Mappings page should be shown.

Configure AAM URL

edit public url

  • Finally, Alternate Access Mappings should be like this. (Click on image to view it in original size)

AAM final1

2. Configure SharePoint Site Bindings

  • Open IIS Manager > From left side select SharePoint site > From right side, below Actions > Click on bindings.

IISbinding.png

iis binding edit

3. Configure Hosts file

  • Navigate to this path.
    • C:\Windows\System32\drivers\etc

driver path

  • Open hosts file via appropriate editor > add the current server IP > click Tab from keyboard >add the URL.

hosts file

4. Disable loop Back Check

  • Run Regedit.msc.

services.msc

  • Navigate to HKEY_LOCAL_MACHINE > System.

registry system

  • System > Control.

registry system control.PNG

  • Control > Lsa.

registry lsa

  • Right Click on Lsa to add a new key.

add key in registry

  • Rename key with DisableLoopbackCheck > Right-click on it > select Edit.
  • Change value data from 0 to 1 > click OK.

disableloop

  • Close Registry Editor and restart the server

4. Add “A” record on DNS server for your URL

  • Tell your system administrator to create “A” record on the DNS server for http://epm.domain.local to Point to SharePoint server with IP: xxx.xxx.xxx.xxx

To get SharePoint IP you should run this command “ipconfig /all”

You should now be able to connect to the web application URL via http://epm  inside your network.

**Alternate access mapping considerations.

  1. Alternate access mappings must be configured for load balancing, even though it generally does not apply to host header site collections. The default zone public URL should be set to a domain URL that is appropriate for all users to see. Unless you do this, the names of web servers or their IP addresses might be displayed in parameters that were passed between pages within SharePoint 2013.
  2. Host-named site collections can’t use alternate access mappings. Host-named site collections are automatically considered in the Default zone, and the URL of the request must not be changed between the user and the server.
  3. Alternate access mappings allow you to expose a web application in as many as five different zones, with a different IIS website backing each zone, some people mistakenly refer to this as having up to five different web applications sharing the same content databases. In reality, there is just one web application.
  4. There must always be a public URL for the default zone.
  5. You can’t delete the last internal URL for the default zone.

Enjoy 🙂

Advertisements

One thought on “A real scenario for Configuring Alternate Access Mapping inside SharePoint Server 2013

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s