SharePoint 2013: Alternate Access Mappings
Alternate Access Mappings (AAM) allow to create additional Urls for the same web application and allow it to respond to them.
Reasons to us AAM
So, AAM can be required for the below mentioned reasons -
- Migrating from SP 2007 to 2010 and want change of names for the url
- Create a proper name for some web app, say http://centraladmin.prod.com instead of http://<server name>:<port number>
- External SharePoint Access.
Zones
There are five zones in SharePoint AAM -
- Extranet
- Intranet
- Internet
- Default
- Custom
Zones are container for alternate access mapping and they DO NOT configure security. They can be just said as labels. The names are all arbitrary and the Admins need to change the permission, just adding the Zones won't work.
Zone components
Zone Components:
- One Public Urls
- One or more internal Urls
We will see what the Public and Internal urls actually mean in the coming section below.
The Steps for Alternate Access mappings in brief are:
- Create Entry in DNS
- Update Binding in IIS
- Add Alternate Access Mapping - Either from CA or using Powershell
Steps
Step 1 : Create a DNS entry
Add a new host in Prod domain and in Name we enter CentralAdmin and the fully qualified domain name is centraladmin.prod.com and also enter IP address of the system and click on Add Host.
Step 2: Configure AAM
GO to CA --> Application Management --> Configure Alternate Access Mappings
Click on Edit Public Urls and then select Central Admin from the top right dropdown selection
Now in the Default zone enter the name http://centraladmin.prod.com:\<port number> and click on save.
Step 3: Binding in IIS
Now we go to Step 3: Binding in IIS
Open IIS or type inetmgr in run.
Expand the site and find Central Administration and click on Bindings.
Edit the Binding and in Host Name put centraladmin.prod,com
Now try to browse to http://centraladmin.prod.com:4242 and it should open your CA now.
That's it folks for now, will add more articles as soon as possible.