Bookmark and Share Subscribe Bookmark and Share



SharePoint 2010: Create Web Application


 « »    

I am logged on to LAB-INDX as PINTOLAKE\Service-SharePoint. LAB-INDX is one of the servers where Central Administration is located, to avoid double hops. I will configure the farm directly on the server which hosts Central Administration

Open “SharePoint 2010 Central Administration” from the “Microsoft SharePoint 2010 Products” under All Programs

Under “Application Management” select “Manage web applications”

Delete Default Web Application

The first thing we are going to do is delete the “SharePoint -80” site, that’s the default web application. We will be making our own.

Select “SharePoint – 80”

Select “Delete” from the ribbon menu on top

Select “Delete content databases”

Select “Delete IIS web sites”

Press “Delete”

Create New Web Application

Select “New” from the top ribbon menu

When creating Web Application I like to use a naming standard my colleague Jeff Borghoff ( created. WSS_SITEFUNCTION you will see it’s quite useful as I describe it below. We will set the NAME of the site, the VIRTUAL DIRECTORY, the APPLICATION POOL and the DB to all use the same WSS_SITEFUNCTION name.

  1. Authentication
    1. Select Classic Mode Authentication – this means it will use Kerberos or NTLM, if you select Claims it will use Forms based authentication
  2. IIS Web Site
    1. Name – WSS_INTRANET
    2. Port – 80
    3. Host Header –
    4. Path – append WSS_INTRANET after VirtualDirectories\ (remove the default)
  3. Security Configuration
    1. We will leave the defaults – NTLM, no Anonymous access, no SSL.
  4. Public URL
    1. Removed the :80 from the host header URL, I know I don’t need to but it frightens me (really it does)
  5. Application Pool
    1. Name – WSS_INTRANET
    2. Set it to use the PINOTLAKE\Service-WebApp account – we need to select the “Register New Managed Account” link
  6. Database
    1. Server – LAB-SQL
    2. Name – WSS_Content_INTRANET (this is not following the naming standard however if I have a separate crawl DB, I can name it WSS_Crawl_INTRANET)
  7. Failover Server
    1. This is for SQL Server Database mirroring, we are not using this so it will stay blank
  8. Service Application Connections
    1. We will leave the defaults. This is one place where you can associate a Web Application to a Service Application
  9. Customer Experience Program
    1. Select No

Press “OK”

A dialog box will pop up, enter the PINTOLAKE\Service-WebApp account and password.

Be sure to select the account after it is created.

Continue on with the configuration.

SharePoint will now process your request

Once the Web Application is create you need to create a site collection

Click “Create Site Collection”

Enter “Title” and Description”

Select “Site Template”

Select “Primary Site Collection Administrator”

Select “Secondary Site Collection Administrator”

Click “OK”

Press “OK”


You should be able to navigate to the site collection which in my case is

Series NavigationSharePoint 2010: Load Balance Central Administration

    Did I save you time and headaches? Buy me a cup of coffee.
    The more coffee I drink the more articles I can write.

4 Comments so far

    • parvathi said:
    • Posted on February 1st, 2013 at 11:26 pm
    • Reply
    • Permalink

    nice to understand this document

    Thank you

  1. Very Nice Article. It helped me a lot. Thanks a lotttttttt…….

    • Tapan Desai said:
    • Posted on April 12th, 2011 at 2:05 pm
    • Reply
    • Permalink


    Sorry i could not post on comments so spliting it up,

    3) After we perform all steps, created few top level web apps and sites under it. IIS on Primary web server started giving some error “username/password is wrong. Do you wish to change…” or something. We had snapshot so we reverted back primary web server to its last state but now it’s not in sync with secondary web server. When I was creating my web apps initially on primary web server, I noticed that it was automatically replicating everything on secondary web server. Is there a way to force this replication other way (secondary web server to primary web server)? I can bring all my servers back to its last stable snapshot but this will help me understand what happens if something goes wrong in future on one of server.
    I know I am asking too many things in one shot but I am desperate for help at this movement.


    • Tapan Desai said:
    • Posted on April 12th, 2011 at 2:05 pm
    • Reply
    • Permalink


    This article is really helpful and easy to follow with all screen shots you have provided. We want to implement same architecture in our 2010 installation and hence I have followed all steps and done my production install. I am facing number of issues. I would really appreciate if you can help me.

    1) Is it okay to follow same method for production server/installation?
    2) We are using different service account as mentioned to do installation, for some reason after performing installation IIS site stops which has svc_farm account as owner. Once I set owner to svc_sharepoint (local admin) it works fine. I am not sure what exactly I am doing wrong.

    Tapan Desai

Leave a comment

Trackbacks on this post