Alternate Access Mapping(AAM) and SharePoint 2013 SSL web Applications

-
In environment were exposing the web applications to Internet there is a need to have certificates installed either on SharePoint servers or through load balancer.

Once having certificates installed some URLs are not translated as required causing misbehavior for the SharePoint web applications, like when trying to publish InfoPath form that will fail.

To resolve that we need to have Alternate Access Mapping Configured.

What is Alternate Access Mapping?
Alternate access mappings direct users to the correct URLs during their interaction with SharePoint 2013. Alternate access mappings enable SharePoint 2013 to map web requests to the correct web applications and sites, and they enable SharePoint 2013 to serve the correct content back to the user.


Each web application can be associated with a collection of mappings between internal and public URLs.

The three components of  AAM:

  • The public URL is the URL that the clients outside in the world knows
  • The internal URL is the URL that the SharePoint Server understands,  Many internal URLs can be associated with a single public URL in multi-server farms.
  • A Zone is a container for a public URL with a property like "Extranet".


Each web application supports five zones (default, intranet, extranet, Internet, and custom).
When the web application receives a request for an internal URL in a particular zone, links on the pages returned to the user have the public URL for that zone


How to Configure Alternate Access Mapping for Web Applications with SSL?

1. Navigate to Central Administration > Configure alternate access mappings.
2. From the Alternate Access Mapping Collection, select the Web Application that you have certificate installed.
3. Click Edit Public URLs
4.Remove any URL in this screen
5. In the Default field, enter the FQDN of the Web Application. Be sure to use the HTTPS . Then, click Save.
6. Then Click Add Internal URLs
7. In the URL, protocol, host and port field, enter the FQDN of the Web Application. Be sure to use the HTTP . Verify that the Zone is set to Default and click Save.
8.Make sure to Update the IIS bindings if needed.



Does the same thing applies for Host Named Site Collection?
In Host Named Site Collection this is handled in other way as AAM doesn't work with HNSC instead we add zones and URL mappings by using this PowerShell command:
Set-SPSiteUrl (Get-SPSite 'http://teams.contoso.com') -Url 'http://teamsites.contoso.com' -Zone Intranet

Note:
Crawlers works with Default zone.
__________________________________________________

Comments

Post a Comment

Popular posts from this blog

Adjust the Search SharePoint Performance level

-
-Set-SPEnterpriseSearchService -PerformanceLevel PartlyReduced On all search app servers -Open NodeRunner process configuration file below in Notepad C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config. Update  <nodeRunnerSettings memoryLimitMegabytes=”0 ″ /> . This is the configuration to limit NodeRunner process memory usage, replace  0  to 500 or 1000 -Restart  SharePoint Search Host Controller  service
Read more

SharePoint 2013 User Profile synchronization versus import

-
Reference is : 2013 advanced Training User Profile Service administrators in SharePoint 2013 can use profile synchronization to manage and synchronize the user and group profile data stored in the SharePoint 2013 profile store with profile data stored in directory services and BDC systems. There are two distinct forms of profile import and synchronization available in SharePoint 2013: ·          One-way profile import. This is a new implementation of a simple import process that was first provided in SharePoint Server 2007. It uses the SharePoint Active Directory Import option to import user profile data from Active Directory Domain Services (AD DS). Note: One-way profile import only works with Active Directory and does not support other directory services. ·          Two-way profile synchronization. This uses the SharePoint Server 2013 profile synchronization method that was first introduced in SharePoint Server 2010. It uses Microsoft Forefront Identity Manager (FIM)
Read more

Usage and Popularity Trends Report not showing correct numbers

-
Recently came into issue that popularity trends showing zero while users are accessing documents so I have that there is a parameter called TailTrimming as mentioned in this reference blog   https://blogs.technet.microsoft.com/tothesharepoint/2014/01/23/view-and-configure-usage-analytics-reports-in-sharepoint-server-2013/ For example, for the Views usage event the TailTrimming parameter is by default set to 3. This means that the usage analytics reports will be updated for an item when the item has been viewed a minimum three times within the last 24 hours. For example, if the item Fabrikam Laptop16 M6000 has been viewed twice within the last 24 hours, these two views won’t show up in the usage analytics reports. If within the next 24 hours the Fabrikam Laptop16 M6000 item is viewed 4 times, the usage analytics report will be updated with 4 views. to adjust it needs to run the following commands $SSP = Get-SPEnterpriseSearchServiceApplicationProxy $tenantConfig = $SSP.GetAn
Read more