Add an Additional Web Front-end Server to an Existing SharePoint 2010 Farm using PowerShell

You’ve followed the instructions in my other three blogs and built a SharePoint 2010 farm (not a stand-alone installation) with one or more web front-end servers.

Per one of the notes in a TechNet article I found:  “As a best practice, we recommend the operating system on the new server should be at the same service pack level and have the same security updates and other hotfixes as the existing farm servers.”  This article also shows the steps that I’ll be demonstrating in this blog.

All of the normal tasks per your organization’s standards should be performed on this server before attempting to install SharePoint. This includes assigning a static IP address, adding it to the domain, running Windows Updates until no further updates are available, installing Antivirus, Backup Client, setting up a Backup Job, Monitoring, etc.

While not a requirement for SharePoint 2010, I’m installing the PowerShell ISE and enabling scripts on my SharePoint server since it’s one of the main tools I’ll be using:

Add the spNameFarm and spNameInstall accounts to the local administrators group on the SharePoint server:

Follow my entire blog on “Microsoft SharePoint Foundation 2010 Installation – Part 2”.

Verify you are logged into the server that you want to install SharePoint on as the spNameInstall account. Right click the PowerShell ISE and select “Run as administrator”:

Load the SharePoint PowerShell Snap-in:

Run the following Powershell script to add this new server as an additional web front-end server in the existing SharePoint 2010 farm. Enter the passphrase that was specified when the farm was initially created when prompted. If you’ve forgotten the passphrase, it can be reset by following my blog on resetting it.

If the command completes successfully, this server is now a web front-end server. You’ll need to setup load balancing or use round-robin DNS to distribute traffic between the web front-end servers.

Remember that any manual changes to your web front-ends such as adding a PDF icon must be made on each server or the end user experience will be inconsistent.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: