<Update 2010.02.23 Re-ordered provisioning steps to fit with supported test cases> NEW! Looking for a simplified process for working with SharePoint and PowerShell? Check out: SPModule.
<Update 2009.11.20 Initialize-SPResourceSecurity and Install-SPApplicationContent> This post will take you down the process of configuring your SharePoint farm while introducing the new administrative functionality shipping in the PowerShell provider. During the SharePoint Installation, make sure you choose “Server Farm” and then “Complete” install. This will allow you to create a SharePoint farm rather than a standalone server. After the install completes, the setup program will ask you if you want to run the SharePoint Technologies Configuration Wizard (default is checked). Uncheck the box to NOT run the wizard. Under the Start Menu, browse to Microsoft SharePoint 2010 Products. Right-click on SharePoint 2010 Management Shell and choose Run as administrator Notice: Since we have not created a farm yet, the shell will load with an error that the local farm is not accessible. This is expected. First…, run the following command to create a new configuration database and central admin content database. Note: One of the main reason we are using this method, versus the UI is because we can specify the central admin content database name. In the UI, you cannot specify the name and it is created with a GUID. <— DBA’s hate this
After the process runs, you can test that the server has been added to a farm, by reloading the PowerShell window. Close and repeat the “Run as administrator” step above. It should load with no warning message. Next, we need to install the help files
After that command completes, we need to secure the files and registry entries on the server otherwise we we will receive a whole bunch of weird security errors.
Next, we need to install the features on the server.
Next, we need to provision the central admin web application on our desired port. This will also link up the web application with the admin content database we created in the previous step.
Next, we need to install all of the application content
Just what I was looking for. Thanks!
When I run "Install-SPFeature –AllExistingFeatures" I get an error for Feature OSearchCentralAdminLinks\Feature.xml:
WARNING: Feature OSearchCentralAdminLinks\Feature.xml had failed to install for
the following reason: Object reference not set to an instance of an object..
WARNING: Feature SharedServices\feature.xml had failed to install for the
following reason: Office Server service not found..
Install-SPService -Provision seem to only work for Standalone mode.
Me again. So I ran all the commands, but the Install-SPService -Provision command will not run, on amything other than standalone mode.
So how do i configure my services? I go to the Service Applicaotn page in CA, but the 'New' does not do anything. No drop-down off all the service types.
Ok, so If I just run Install-SPService (without -Provision), it will install the services, and then I can provision from the UI!
Sorry, the post has been updated now. You need to run Install-SPService and then the second time add in the -Provision switch to actual provision them.
My SQL server is on a different domain than my SP server. When it asks for farm credentials is there any way to specify sql credentials as well?
If you mean SQL Server Authentication (username/password) you can specify this with the -DatabaseCredentials paraemter. It works just like farm credentials, accepting a PSCredential object.
The script is working fine
Thanks a ton just 30 minutes to install my farm.
This script is the best I've seen by far. Thank you for postin it.