I concluded creating a SharePoint farm yesterday to check out my SharePoint 2010 automation scripts to find out if they’ve held up and so far it looks excellent. The documentation’s not however up on TechNet, nevertheless the function I did explaining config.xml last year in Automating the SharePoint 2010 set up looks for being the identical. I employed exactly the same config.xml (using a SharePoint 2013 item crucial) and ran an unattended installation. Once the documentation turns into obtainable I hope there to become couple of modifications.


I have a script that i use to at first create the configuration databases and Central Administration site which i blogged about before this year in Create a SharePoint 2010 farm with PowerShell, I wish to contact it the SharePoint Configuration Powershell Wizard in that it generates a brand new farm and does each of the associated jobs done from the configuration wizard. I examined it out yesterday in opposition to SP2013 RTM and it labored without any issue.

I’ve produced some advancements because then so let us endure them and see how this script operates.

Initial I exploit my credential hash desk to outline the qualifications for accounts I’ll use within the farm. There is certainly the farm account, a service account to the services software swimming pools, an additional to the web software.

Up coming I setup a SQL Server consumer alias. I contain this listed here since I like to reuse my scripts and i do not ever need to overlook to use an alias. The script I exploit is predicated on Zach’s publish Develop a SQL Alias having a PowerShell Script. Notice that on this example, I’ve a SQL Server isntance on the identical server. With a few adjustments you can stage the alias to another server or an instance over a non-standard port.

Now that the alias is in place we can start with the farm configuration.

Let’s define our values for the farm passphrase, SQL Server name, configuration and Central Administration database names, and the CA port and authentication:

 We’ve prepared everything we need, let’s create the farm:

There is some error dealing with to examine in the event the farm is developed right after running the New-SPConfigurationDatabase cmdlet. If there was some kind of mistake the script will stop at this time as there’s no stage in continuing and permitting your display replenish with crimson exception textual content. Whilst tests this with SP2013 I obtained problems like:

  1. SQL Server was the wrong model (SQL Server 2008 R2 RTM). It informed me the version was not enough also to upgrade (I upgraded to SP2)
  2. The configuration databases currently existed (from the previous configuration try) which it couldn’t be employed since it presently experienced a schema
  3. SQL Server had the wrong “max diploma of paralelism worth. It stated it ought to be a price of one and that i established this by working the next query in SQL Server:

This SQL question and much more information concerning the max degree of parallelism option are within the MSDN: max degree of parallelism Choice

With SP2010 I often knowledgeable an exception since the New-SPConfigurationDatabase unsuccessful to run. This was generally after i was repeatively re-running my script during tests. I didn’t encounter the issue yesterday however, if it had happend the script might have stopped.

Generally when it does quit there exists a configuration databases which has been partly developed in SQL Server. In order to operate this script again you will have to delete the prevailing databases or rename the database in your script. Obviously, if the script cannot connect to SQL Server there will not likely be a database to delete, even though the script will cease at this point so you can troubleshoot the connectivity.

Given that we have developed the configuration databases and Central Administration, we need to complete the other five or 6 jobs that Central Administration does, particularly:

  • Install Help Collections
  • Initialize security
  • Install services
  • Register features
  • Install Application Content

How do I know the configuration wizard does these things? Microsoft documented it for SharePoint 2007. They used to have a page that detailed setting the farm up with PSCONFIG.EXE and listed all these steps.

psconfig.exe –cmd configdb
–cmd helpcollections
–cmd secureresources
–cmd services
–cmd installfeatures
–cmd adminvs
–cmd evalprovision
–cmd applicationcontent

You can disregard evalprovision, which is for standalone installations only. In the event you required any additional purpose to by no means use standalone manner, note what that command does: “Provisions this server like a stand-alone (analysis manner) server.” Standalone manner is for analysis, it isn’t intended to become for almost any real production use.

The other command you can ignore may be the adminvs command which sets up Central Administration. Those other commands (helpcollections, secureresources, solutions, installfeatures, applicationcontent) would be the exact same kinds I’ve identified as duties we must operate subsequent:

Now we have a farm! It doesn’t do much, pretty much all we can do is continue configuring it. But to do that we need to register our service accounts as managed accounts:

And with that, we can open up Central Administration and start creating web applications and services or we can continue setting everything up with PowerShell.

Oh, and before I forget, I did a quick check to see what the RTM build numbers are:

PS> (get-spfarm).buildversion

Major Minor Build Revision
—– —– —– ——–
15 0 4420 1017
And Central Administration reports the same, RTM is build 15.0.4420.1017

Welcome SharePoint 2013!

For reference, here’s the full script: