Skip to main content

Host Named Web Application



Normally when you create a web application in SharePoint its Url is:
“http://<Server Name>:Port” or “https://<Server Name>:Port”.

We can also create a web application that contains a URL that is not of the above format, instead it could be “http://mywebapp.sharepoint.com” or “https://mywebapp.sharepoint.com”.

In order to create, host named web application following steps is needed to be followed.

1.      We need to create a host name in the DNS. The host name will be the url, the site. In my case my host name will be “mywebapp”.
2.      You need to login to your Active Directory server to create new host entry in DNS.
3.      Create DNS entries



4.      Let’s go to the DNS server and create a new A Host with the “mywebapp.sharepoint.com” FQDN and pointing to the web front end.
 


5.      Now open Central Admin> Manage Web applications> New. Provide the created host name in the Host Header in creating web application form. In my case its “mywebapp.sharepoint.com”.


 
6.      Now, once your web application is created in case of SharePoint 2013 we need to add binding in IIS for the host named web application. If you are using SharePoint 2010 then no configuration is needed. Below are the IIS bindings needed for SharePoint 2013.
I.              Open IIS on SharePoint 2013 server.
II.            Select your site
III.          Click on edit bindings.
IV.         Select your site binding, click on edit. Add your host name as shown in below figure.


                    
           7.  That’s it, now reset IIS and your host named web application is created.




Regards,
Keyur Pandya

Comments

Post a Comment

Popular posts from this blog

Business Data Connectivity

I came to a requirement wherein I was supposed to get data from an 3 rd party portal using API’s and then bring them to SharePoint server. The first approach that I finalized was just to make BDC solution that will get data from 3 rd party portal and will deploy it to SharePoint. How to Create BDC solution in SharePoint? I found below link that is having really great description about hot to create and deploy the BDC solution to SharePoint. http://www.c-sharpcorner.com/uploadfile/hung123/creating-business-data-connectivity-service-using-visual-studio-2010/ After creating an POC I came to know that BDC model cannot be deployed on Multi tenant farm. So what can be done next? After some amount of googling I came to know that we can create BDC solution using WCF services also. So I created a WCF service solution that acted as a wrapper that used to fetch data from the portal. We can them publish that service to IIS or Server and use the servic...
2 comments
Read more

Identity client runtime library (IDCRL) did not get a response from the login server.

Recently I was doing some testing with a background PowerShell and encountered a weird error. “Identity client runtime library (IDCRL) did not get a response from the login server”. The error that you might encounter while working with PowerShell. This error is very misleading when it comes to identifying what could go wrong. After doing quite a good amount of research below are the probable causes for the error. Invalid Credentials MFA (Multi-Factor Authentication) Manage security defaults. Solutions Invalid Credentials Check if your credentials are wrong. Especially if you are using variables. MFA (Multi-Factor Authentication) Check if MFA is enabled on the account which you are using. These only affect you badly if you are developing PowerShell for a background Job. Go to Microsoft 365 admin center Users -> Active users -> Select the user -> Manage multifactor authentication -> Select the user -> Disable multi-factor authentication. M...
2 comments
Read more

Copying Footers Between SharePoint Sites Using PnP PowerShell

Recently, I have been extensively working with SharePoint and the Patterns and Practices (PnP) PowerShell module. PnP has significantly simplified various tasks by providing easy-to-use command sets and thorough documentation. One particular task that PnP has made straightforward is copying a footer from one SharePoint site to another. This process can be achieved with just a few commands. Why Use PnP PowerShell? PnP PowerShell is a set of cmdlets designed to work with SharePoint Online and SharePoint on-premises. It simplifies the management and automation of common tasks and provides commands for nearly every aspect of SharePoint administration. The PnP module is especially useful for tasks that would otherwise require complex scripting or manual intervention. Copying a Footer with PnP PowerShell To copy a footer from one SharePoint site to another, follow these steps. This process involves exporting the footer template from the source site in XML format and...
Post a Comment
Read more