Host Header Site Collection and Web App Setup - Thoughts

I am trying to understand relation between AAM and web app extension .Please share your expert opinion. I have not seen any TechNet article talking about it clearly.
Here it goes: in 2010 it was recommended Not to use AAM with IIS bindings without extending the web application. This was mentioned in several TechNet articles also its a known “Mistake #4” on TechNet articles.
So question is, is that still the same case in 2013?
Most of the times it is recommended to remove web app host header from IIS if you are using this web app for HHSC, otherwise sites will not be accessible. I have find no issues by leaving web app host header and adding more bindings for host header site
collections any thoughts on this ?
Thanks.

Hi,
I found some articles for helping understand Extend web application and
Alternate access mappings.
“If you want to expose the same content in a Web application to different types of users by using additional URLs or authentication methods, you can extend an existing Web application into a new zone. When you extend the Web application into a new zone,
you create a separate Internet Information Services (IIS) Web site to serve the same content, but with a unique URL and authentication type. An extended Web application can use up to five network zones (Default, Intranet, Internet, Custom, and Extranet). For
example, if you want to extend a Web application so that customers can access content from the Internet, you select the Internet zone and choose to allow anonymous access and grant anonymous users read-only permissions. Customers can then access the same Web
application as internal users, but through different URLs and authentication settings..”
After you extend web application, there is a new site created in IIS but the content are the same. We extend it to a new zone for different authentication methods, so that we could support different security between Internet site, Intranet site and Extranet
site.
“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.”
AAM is to offer different urls to users to access one site. Sometimes the url of a site is not easy to remember , we could use AAM to create simple url.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Similar Messages

Best Practice for Host Named Site Collections and Web Apps

Looking for advice on setting up the host named site collections. If I am reading many of the technet articles and blogs correctly I should 1) have only 1 top level web app for host named site collections and 2) not have a host header for that web
app. If that's correct I am looking for advice. We have 7 separate domains that we support in our farm. Currently each of those domains is divided into web applications based on the domain, *.contoso, *.trains.com, *.bakers.com, etc.
Is the concept now that all of the host named site collections fall under that one web app? How do we deal with the SSL for each of those separate domains which all have their own certificates?
Thanks in advance for your comments.
NLewis

Yes, for creating host named site collections, first you create a host header less web app and then create host named site collections under that web app. However this is only for the cases where all the host named site collections ends in one domain. So
you can create host named site collections as intranet.contoso.com, my.contoso.com, portal.contoso.com etc as they are all ending in *.contoso.com.
As per your environment, if you have web apps which caters to different domains like *.contoso.com, *.trains.com, *.bakers.com, you need to create separate web apps as they are all ending in different domains. Then you can have a separate wildcard SSL certificate
for each of those web apps.
Hope this helps.
Thanks
Mohit

Moving host header site collections to a different URL

Background:
We have a SharePoint 2010 farm with a single web app. Within this web app, we have over 40 site collections. Unfortunately when they were created, they were all put under their own explicit managed path. So now we have over 40 managed paths
and the recommended number of managed paths is 20. We are planning to create wildcard managed paths and move site collections from
https://servername/sitename to
https://servername/U/sitename to reduce the number of managed paths.
The implications of this are clear for site collections that are not host header site collections. Site collection admins will have to adjust any URLs that refer to items in the site collection. It is less clear for host header site collections.
From the user's point of view, the host header URL itself will not change.
1. Will internal links in the host header site collections need to be adjusted like in regular site collections?
2. Will the e-mail address of e-mail enabled lists and libraries change?
I would be grateful if anybody has an answer to this.
Sheila

If you moved http://sitename.webapplication.domain.com (ie. a host named site collection) to http://webapplication.domain.com/managedPath/sitename then it would obviously have a different URL.
That is not what you were describing in your first post, the terminiology is a little specific and I think you're getting it a bit wrong. A web application (often) has a host header, that will not change moving a site from an explicit path to a wilcard path.
A host named site collection is very different and more complicated
If you are planing on converting
http://webapplication.domain.com/site1
http://webapplication.domain.com/site2
http://webapplication.domain.com/site3
to
http://webapplication.domain.com/sites/site1
http://webapplication.domain.com/sites/site2
http://webapplication.domain.com/sites/site3
Then you are not using Host Named (or host header) Site Collections, those are bog standard managed path site collection addresses.
Now to answer your question: for users to access the sites after the move they must use the /sites/siteX version, if they use an old link then it will not work.
There is a trick in SharePoint that will keep links that exist within the site collection consistent so that some URLs will be maintained. This is called a relative URL and means that URLs that are within the same Site Collection will automatically work
with the new URLs.

Open list form across host header site collections via Modal Dialog window

Hello, I have a web application that has two host header site collections in it. When a user is on Host Header A, I need to open a list's display form that's located on Host Header B. I'm using the JS function SP.UI.ModalDialog.showModalDialog(options)
to open a dialog window to the host header B list's display form. It loads and shows all the columns, but there are a couple issues.
1) The scroll bar on the dialog window is not active (can't scroll up or down to see all the columns). This is an issue on all browsers (IE 8 &9, Chrome, FF)
2) In IE, the SP ribbon does not display. In Chrome and FF the ribbon does display and the buttons work fine.
There's no errors in the ULS logs, and if I use IE8, there's a JavaScript "Access Denied" error. I've confirmed the user account has permissions on both sites & list.
My first thought had to do with anonymous access being turned on at the web application level (not the site level) and the credentials not being passed to the new site collection. But this isn't the case because in Chrome, the ribbon shows and the
buttons are security trimmed correctly based on the users permissions. So I know the credentials are getting passed through the dialog window. And when I use the "Edit' button on the ribbon in chrome, it opens a new dialog window and everything
works correctly (Scroll bar and ribbon).
Has anybody been able to successfully open a list form across two separate host header site collections?

I ended up getting around the cross site collection in the modal window issue by using a custom ASPX page that works as a redirect using JS.
The link the end user clicks pops open the aspx page in a dialog window. I then pull the URL of the list item I want to open from the URL and have JS open that form in the modal window. The key seems to be to open the redirect aspx page under
the same site collection as the list item you want to view.
Here's the JS that's in the aspx page.
<script type="text/javascript">
// We name the current dialog windown
window.name = "newSiteWindow";
// wait until we know the the JS lib is loaded
ExecuteOrDelayUntilScriptLoaded(loadNewSite, "sp.js");
function loadNewSite() {
//grab the list item URL from the URL of the dialog window using a pre created function
newURL = GetUrlParmByName("listItem");
//append our dlg query to the end so everything displays correctly. If you do not use IsDlg=0, the ribbon does not display and the window will not scroll.
newURL = newURL + "&IsDlg=0";
//use the current window to open the list item we want to go to.
window.open(newURL, "newSiteWindow");
</script>

Site search and web app search !

how can I get a one web app search function to search all the fields within the web app. It seem I need a search field for each data fiefield in the web app.
Ideally my clinet wants a holistic search so that it will search all content within the site - most of which is within web apps ?
also does anyone know hoew you can edit the the result results icon - so if the web app is a news instead on the box I could put a news icon ?

Liam, thanks for your response. Unfortunately, the client wants a single search in the header of the entire site that will search both pages and web app content (without missing the custom field data), So I guess i am/was looking for a work around rather than a replacement.

Access denied for all (most?) users in all site collections of web app

Hi,
I have a Sharepoint 2010 farm pre-SP1 (yes should be updated!) and for all site collections of a web app, all users are getting access denied.
Now in my title I said "most?" because I have found one user in another office who does not have this issue. This web app/site collections also do not go through f5 or any proxies.
Even if I add myself as a site collection admin via central admin, I get the same result. I've looked at everything, windows time on the server (not using kerberos), errors in event log (nothing), uls logs just say access denied (very helpful!), etc...
I can try what's suggested at http://social.technet.microsoft.com/Forums/en-US/e66f1b09-605d-4546-a581-2a9283c238c0/access-denied-for-all-users-and-for-site-collections-owner?forum=sharepointgeneralprevious but when asking colleagues, there's been no
changes, let alone with those accounts? I can do a get on the property tomorrow to find if there is a value set first, however.
Any suggestions on this?

Hi,
Please try logging in the site with farm account.
If it works, please make sure you have superuser and superreader accounts in CA > Application management > web application policy. If not, please add both accounts with the powershell script in the article below, this can cause all users denied when
access the site:
http://technet.microsoft.com/en-us/library/ff758656.aspx
Here is a similar thread:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/a49b1ab8-273f-41e4-a0b8-be0e31c6733b/all-users-including-site-collection-admins-receiving-access-denied-from-one-site-collection?forum=sharepointadminprevious
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Host Named Site Collections and www

I currently have a hostnamed webapp that uses Windows Auth(Claims) in the default zone and it is extended for anonymous
access(Internet Zone)
I have siteinternal.com and www.sitexternal.com
The users also want to use siteexternal.com without the www.
There is no way to add the site again to the Internet Zone.
Adding it to another zone results in it using windows auth and prompts, as per the default zone.
Is there a way to handle this? is the www handled as a different site in SP eyes?
themush

This adds a AAM to the HNSC teams.contoso.com of teamsites.contoso.com.
So if you have siteexternal.com and want to add www.siteexternal.com, run:
Set-SPSiteUrl (Get-SPSite ‘http://siteexternal.com') –Url ‘http://www.siteexternal.com' –Zone Internet
Make sure DNS is properly configured with the "www" A record in the siteexternal.com zone.
Trevor Seward, MCC
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How can I create a host name site collection when I have a 443 web application already created for App model?

Hi all,
I have a 2013 farm set up with the App model
1 web application for path based site collection using host name
1 web application with SSL (no host name)
1 web application for mysite
My business request is that I need to migrate SSL enabled 2007 content to this farm and use host name site collections. I tried to create one more web application for this without any luck (the 443 IIS folder is already used by another web application).
I thought I bind the previous 443 web application with another IP address should be fine. Seems like the IIS site is taken (https://server name:443) so it will not let me create one more. How can I solve this problem so I can create the web application
to host those host name site collections? Any suggestion is greatly appreciated.
Thanks in advance.
Sally

Hi Trevor,
Thanks again for your quick reply. I try the option 2 right after your post. I use my front end server name for public URL (https://WFEName:443) and it fails again. The error message is:
The directory C:\inetpub\wwwroot\wss\VirtualDirectories\443 is already being used by another IIS Web Site. Choose a different root directory for your new Web application.
After reading more, I saw mix Hosted Name Site collection and Path-based site collection aren't recommended. Unfortunately I already have Path-based site collection created with App model web application
(the web application without host name) in my farm. In my Option 2, that web application without host name is used for App routing. This takes the root folder 443 which will not allow any other web application to use the same name again.
Does that mean we can't create Host Named Site collection in the same farm? Is there any configuration I need to check?
Thanks again.
Sally

Load balancing host named site collection

I am jumping into the realm of host named site collection. While the learning experience has been good, still there are some questions unanswered. Please bare patience since my questions are long.
- I have a non host header site on port 80 that has https certificate added to IIS for supporting app store in https mode.
- I tried to created the host name site collection using https in this default port 80 non host header web application and was greeted with error. Then i extended the web app to different zone with port 443 . Then created the host header site collection
with https with web application name for extended 443 one. Creation went in fine.
- I tired to use IPs on now extended IIS site and bind certificates on that one. The site does not load. I do the same again in the default zone iss site, bind ips on that one and site loads. Now question is even though host header site collection was created
using extended web application url , why binding had to be done on default zone IIS site?
- Second test, i changed the authentication mode for extended, no effect on host named site collection but as soon as i changed it in default zone it reflected in host named site collection. I am confused why it needs extended zone url to create the https
site but every change done in default zone is getting reflected on this host named site collection.
Now for load balancing , it works fine with IP? But how to load balance these host named site collection using url. I talked with f5 team and they said i need to send some reply query string from each site. Where do i do that? Or is it even needed?
Accoring to this link : https://devcentral.f5.com/articles/name-based-virtual-hosting-with-ltm
. If the site hosts an application, though, the monitor should request a dynamic page on each webserver which forces a transaction with the application to verify its health and returns a specific phrase upon success.
For application monitoring, the recommended best practice is to create such a script specific to your application, configure the monitor Send string to call that script, and set the Receive string to match that phrase.
Has any one done this before? I tired to search for resource regarding this for iis or sharepoint but was not able to get anything.
Thank you for your patience for reading such a long question.
Adit

first part of question:
Default Web Appliction in port 80: Creating https host named site collection fails.
Extend default web application on port 443 : Https hostnamed site collection created when web application name is passed for extended web application on port 443. This means this site collection is associated with this extended web application correct? But
all the changes made in IIS only reflect if it is made to port 80 web application. Also changing authentication scheme from Central Admin, only changes on default zone reflects on site collection not the one in extended web application? Why if the site
was only created on extended web application paremeter, changes on default are reflecting on it but not from extended.
Second part of question:
Each Hostnamed site collection when load balanced thorough f5 using IP for 3 WFE uses 3 IPs for each. This way we will run out of IPs pretty soon. I want to know if there is way to load balance these sites using Hostname or anyother paramenter through f5
and if any body has done it?
https://devcentral.f5.com/articles/name-based-virtual-hosting-with-ltm link talks about sending reply string
from application but i do not know where to set it up or how to do it? No resources in the net. Just asking if any one else has done it.
Adit

Crawl issue - warning: "This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of ....a start address"

Hello all,
I have a multi-tenant environment in SharePoint 2010 server. Different tenants are hosted by one web app.
One content source has been created to crawl the all shared environment. (the only URL added in the content source settings = URL of the
web app)
Crawl everything under the hostname for each start address has been selected when creating this content source.
Now I have created a new tenant hosted by the same web app. For this new tenant I want to have a different crawl schedule. Simple , I just create a new content source and add the host URL of this tenant. With the same settings has the other content source.
After having started a full crawl I get 0 success and 1 warning : “This URL is part of a host header SharePoint deployment and the search application is not configured to crawl
individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.”
The first content source is well crawling the new tenant freshly created. Could you tell me where I’m wrong?
Thanks in advance
Regards
Baldo

Baldo,
In the configuration that you described you now have 2 content sources set to crawl the same content. If you have a content source with a start address of http://servername/ then it is going to crawl everything past that address. If you are now changing
the crawl schedule based on the individual site collections, you will need to move your start addresses further down the URL.
For Example:
1st Content Source:
http://servername/ as a start address would now become
http://servername/site1
http://servername/site2
2nd Content Source:
http://servername/site3
Also remember that all crawling must happen on the default zone. If you are trying to crawl a zone that the web application has been extended into, that will not work.
ScottC - Microsoft SharePoint Support

Setup Team Foundation Server - Team Site Collection - SharePoint Web Application Settings failed with error TF205014, TF250025

Hi
I have TFS server installed and working with other SharePoint farm. (TFS installed, SharePoint extension installed and Granted Access for TFS.
When Setup TFS - SharePoint Web Application Settings, It ask for the three values:
Web Application URL:
Central Administration URL:
Default Location of team project collection sites:
What notice about the TFS sites that are working is that they are Path Based Site Collection. Created with SharePoint Web Application managed path (like
http://spserver/sites/tfs_site1) and so it easy to see it will work.
Web Application URL: http://spserver
CA URL :   http://spserver:portnumber
Default Location : Sites or any managed path
We start using Host Name Site Collection (HNSC) to get the benefit of multiple unique site name without having multiple web application for each. Work great but when we tried to setup and extend TFS service on the HNSC, we could
not get them to work and got errors when trying different variation of path URL.
After doing lot of searching on this, I came up pretty empty and I don't know if that is possible so my question is Have anyone able to setup TFS to work with SharePoint 2013 Host Name Site Collection?
If you have, a simple yes will be great but please share or even if anyone think it is possible or not possible, please share too.
Thanks in advance for any comment / suggestion.
Swanl

Hi Swanl,
I’m afraid that we cannot setup TFS to work with SharePoint 2013 Host Name Site Collection.
Also you can initial a new thread in Visual Studio Team Foundation Server forums：
Team Foundation Server – General: http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=tfsgeneral
More experts for Team Foundation Server will assist you, then you will get more information relation to your issue.
For integrating SharePoint 2013 with Team Foundation Server 2013 you can have a look at the following blog:
http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Eric Tao
TechNet Community Support

Configuring Apps for SharePoint 2013 - Host Header Sites

Hi All
I am busy planning our Apps for SharePoint deployment and one gotcha seems to be sites that use host headers. Our current deployment consists of the following:
2x WFE's (WFESRV1 and WFESRV2)
2x App Servers (APPSRV1 and APPSRV2)
The WFE's are load-balanced and we have 2 sites, portal.intranet.com and mysite.intranet.com. Both use host headers. I have gotten to the point where I will have a DNS zone called companyapps.com and a CNAME *.companyapps.com.
To which site do I point the CNAME to and what if I need both sites to be App enabled? Also, a lot of sites mention I need a empty site collection on a separate IP in order to use Apps with host headers. How would I use this empty site collection and
what would I name it?
We are on the March 2013 update.

May Be I understand your question as *.companyapps.com should be pointed to sharepoint server but where in IIS binding would you map *.companyapps.com
Actually, When you configure the APPS on server, the central admin > apps > you have to mention this *.companyapps.com. Now all apps will be "(yourname)-guid.companyapps.com"
Then you will have to create a app catalog where all the app related details will be stored
When App service application is created it is automatically added to default service connection. and this service connection to mapped to other web application(Application management, you see service connection)
If all is configured well apps will automatically work for all web apps

Managed path for host named site collection is farm level or web application level?

Hi,
I would like to get advice.
I created a webapplication for host named site collections.
these are my host named site collections (except http://sp2013) under my webapplication
Root Site Collection: http://sp2013
Site Collection: portal1.sg
Site Collection: portal1.sg/research
Site Collection: portal1.sg/intranet
research and intranet managed paths are farm level
all my host named site collection will be accessed by http and https except "intranet" site collection will be only accessed by https
so I changed the Intranet zone for site collection using Set-SPSiteUrl
Set-SPSiteUrl (Get-SPSite "http://portal1.sg") -Url "https://portal1.sg" -Zone Intranet
Set-SPSiteUrl (Get-SPSite "http://portal1.sg/research") -Url "https://portal1.sg" -Zone Intranet
Set-SPSiteUrl (Get-SPSite "http://portal1.sg/intranet") -Url "https://portal1.sg/intranet" -Zone Intranet
Now I need to create "search" site collection for "Enterprice Search Center"
My question is that for the "search" managed path ... should i use farm level or web application level?
"search" site collection will be will be accessed with both http and https also.
Thanks a lot!

managed path for HNSC is farm level and u can have 20 managed path
while managed path for path based is 20 per web application in your case if you are going to have a a separate web application for search then u will use web app
Kind Regards,
John Naguib
Technical Consultant/Architect
MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation
Please remember to mark your question as answered if this solves your problem

Robots.txt and Host Named Site Collections (SEO)

When attempting to exclude ALL SharePoint Sites from external indexing, when you have multiple web apps and multiple Host Named Site Collections, should I add the robots.txt file to the root of each web app, as well as each hnsc? I assume so, but, thought
I would check with the gurus...
- Rick

I think, one for each site collection as each site collection has different name and treated as web site.
"he location of robots.txt is very important  It must be in the main directory because otherwise user agents (search engines) will not be able to find it.  Search engines look first in the main directory (i.e.http://www.sitename.com/robots.txt)
and if they don’t find it there, they simply assume that this site does not have a robots.txt file"
http://www.slideshare.net/ahmedmadany/block-searchenginesfromindexingyourshare-pointsite
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Content Search Web Part over HTTPS for a Host Named Site Collection

Hello
I have a host named site collection http://media.contoso.com which is a media portal that stores videos and pictures. On my parent site collection http://site.contoso.com homepage I have a Content Search Web Part that displays videos from the media portal.
Both sites work over https.
When I edit the content search web part and enter the URL http://media.contoso.com in the 'Change Query' box, search returns the results as expected but when I enter the URL as
https://media.contoso.com no results are returned.
I have removed the binding in IIS to point to http://media.contoso.com.
I need it to be https so that I don't see "HTTPS security is compromised by http://media.contoso.com" on my site collection homepage.
Any idea why this is happening?
Thanks
Yoshi

http://technet.microsoft.com/en-us/library/ee792873%28v=office.15%29.aspx
In the Search SSL Settings dialog box, do one of the following:
If you do not want the crawler to crawl a site when there is an SSL certificate warning, make sure that the
Ignore SSL certificate name warnings check box is cleared. For security reasons, the check box is cleared by default.
If you want the crawler to crawl a site even if there is an SSL certificate warning, make sure that the
Ignore SSL certificate name warnings check box is selected.
If this helped you resolve your issue, please mark it Answered. You can reach me through http://freeit-support.com/

Host Header Site Collection and Web App Setup - Thoughts

Similar Messages

Maybe you are looking for