0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
JPPINTO
  • Home
  • Blog
  • Certifications
  • About
  • Contact
  • Shop
  • Gallery
  • Current Setup
Contact

Search

July 8, 2010 / SharePoint 2010

SharePoint 2010: Create Web Application

Tags: create web application, load balance central administration, sharepoint 2010 farm build, sharepoint 2010 farm installation
Featured image for 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 (http://www.borghoff.com) 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 – sp.pintolake.net
    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”

Testing

You should be able to navigate to the site collection which in my case is http://sp.pintolake.net

Post Views: 427
<- C# Windows Form is Busy (Waiting Cursor and Progress Bar)
SharePoint 2010: Installation Overview – Table of Contents ->

Categories

  • Active Directory (5)
  • AI (3)
  • Amazon Cloud Services (1)
  • AWS (2)
  • Blazor (1)
  • C# (C-Sharp) (3)
  • CI/CD Pipelines (1)
  • Cloud (1)
  • Cloudflare (2)
  • Codex (1)
  • Containers (4)
  • Deployment (2)
  • Development (5)
  • DNS (1)
  • Docker (3)
  • Email (1)
  • Family (1)
  • General (5)
  • IIS 6.0 (4)
  • IIS 7.0 (10)
  • IIS 8.0 (1)
  • Infrastructure as Code (IaC) (1)
  • Kubernetes (3)
  • Linux (9)
  • Microsoft 365 (2)
  • MySQL (1)
  • Office 2010 (1)
  • PHP (1)
  • PowerShell (11)
  • Productivity (1)
  • Security (1)
  • Servers (9)
  • SharePoint 2007 (8)
  • SharePoint 2010 (19)
  • SharePoint 2013 (2)
  • SharePoint Online (1)
  • SMTP (4)
  • SQL Server 2008 (1)
  • SQL Server 2008 R2 (1)
  • SQL Server 2012 (2)
  • SQL Server 2019 (1)
  • SSL (1)
  • Travel (1)
  • Troubleshooting (1)
  • Ubuntu (9)
  • Uncategorized (1)
  • URL Rewrite (2)
  • Visual Studio 2019 (1)
  • Visual Studio Code (1)
  • Windows 10 (7)
  • Windows 2003 (9)
  • Windows 2008 (18)
  • Windows 2012 (6)
  • Windows 7 (3)
  • Windows Firewall (1)
  • Windows Vista (1)
  • WordPress (3)
  • WP-CLI (3)

Recent Posts

  • GPT-5.6 Sol Changes How We Prompt—and How We Write AGENTS.md
  • Protect a Domain That Does Not Send Email with SPF, DMARC, and Null MX
  • Turning Our Atlanta Vacation Photos into a Video with PowerShell
  • Bulk Create Cloudflare Origin CA Certificates with PowerShell
  • Test a Cloudflare Global API Key Connection with PowerShell

Advertisement

Tags

agents.md ai coding agents aws bash cloudflare cloud storage codex context engineering developer workflow dev to production dns externalize blob externalize sharepoint data full installation http redirect https IIS IIS installation index server configuration installing cumulative updates linux load balance central administration microsoft 365 nginx powerpoint powershell redirect http to https s3 server setup sharepoint 2010 cumulative updates sharepoint 2010 farm build sharepoint 2010 farm configuration sharepoint 2010 farm installation sharepoint data externalization SMTP ssl storagepoint ubuntu web server windows Windows 7 windows server 2008 wordpress wp-cli x86
© 2026 JPPinto.com. All rights reserved.