Tag Info

Hot answers tagged

8

What you're looking for is the host named site collection, which enables you to assign a unique DNS name to site collections. Or alternatively create an AAM for existing Site collection to achieve it. For example, you can address them as http://hr.mycompany.com or http://sales.mycompany.com. The sample PowerShell code creates a new web application listing ...


2

Creating web applications when targeting Host Named Site Collections SHOULD NOT have a HOST HEADER (http://blogs.msdn.com/b/kaevans/archive/2012/03/27/what-every-sharepoint-admin-needs-to-know-about-host-named-site-collections.aspx). From the script it seems you've considered the -HostHeader $hostHeader parameter


2

All (related) host named site collections are sharing the same web.config as they are all located under a single web application (= entry within IIS). Look into the web application list (central administration) to find the parent web application and then adapt the relevant web.config within IIS. Please be aware that I'll have impact on all other HNSC.


2

Specify the host header what you want it to look like while creating new web application. or you can always use Alternate access mapping to look like http://hr.mycompany.com.


2

You need to create a new web application and specify this as the URL, yes you could use an existing site collection an extend it using AAM but if you are starting from scratch a new web app and site collection is best. Thanks Matt


2

The simple answer is: It just works. You can enable the self site creation feature using central administration (also set "Start a Site" to "be hidden from users"). You need a root site collection in the primary web app (even if the web app is not used and is only a container for HNSC) to set this in the central admin page. If you don't want a root site ...


2

For what I have seen so far, the need for three different web applications generally comes from the authentication requirements more than scalability/performance requirements. Ofcourse there is a performance hit if we isolate the app pools for different web applications as they end up reserving more memory. However, you get the option of configuring ...


2

Apparently it is not possible to switch to HTTPS after setting up the root HNSC web application without SSL (-SecureSocketsLayer parameter) - see "SPSite.Rename not working from HTTP to HTTPS (HNSC)". The solution: You will have to delete the existing HSNC web application (make sure to not delete the content databases[!!!]) and recreate it with the ...


1

In my experience, the sites are separated for a variety of very good reasons. The internal sites (intranet publishing site and the collaboration sites) are usually given different URLs more for a user experience perspective so that users immediately know that what they can do on the Intranet Portal is significantly different from what they can do on ...


1

Well, previously I was thinking No, but the more I read, the more it points to Yes. Read this SharePoint 2013 Host-Named Portal article. These are recommended solutions for deploying SharePoint 2013. The SharePoint 2013 Host-Named site collections looks to be recommended with only one web-application. Excerpt: The recommended configuration for deploying ...


1

As mysites use self service site creation to automatically create sites when a user first navigates to them, it is not recommended to use Host Named Site Collections for user's mysites. This is because you either need to pre-create all mysites (and then manually create sites for new users) using powershell, or use custom code to manage the provisioning ...


1

The following (brand new) article by Wictor Wilen might be helpful to you: http://www.wictorwilen.se/sharepoint-specifying-content-database-for-new-site-collections-when-using-host-named-site-collections He talks about how to create a custom site creation provider.



Only top voted, non community-wiki answers of a minimum length are eligible