Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I've heard of people doing scripted installs of SharePoint. Is this common and how far can you take it? Can you actually build your web apps and site collections? I would like to see some examples.

share|improve this question
add comment

3 Answers

up vote 3 down vote accepted

If you are doing a full SharePoint environment with dev test, integration test, pre-prod and prod (possibly with staging environment too) scripted installs are the bomb! Every farm can contain of 2-5 or more SharePoint servers!

What scripted installs will give you is a reproducable install, that can be done from environment to environment without having to fear human errors and mal-configurations. In other words you can trust your install when a bug occurs in one environment but not in the other, and can concentrate on issues that differ from environment to environment (an example here could be that the OS wasnt a scripted install and had different regional settings, which would cause string formatting to vary on environments).

Also creating farm after farm through environments, easily more than 10 servers and often more than 25 for a medium farm with full environments. Installing that amount of farms is tedious and error prone.

On my latest project we faced an even larger number of installs and ended up with a powershell script that read values from an excel document. This proved very helpfull for the non-sharepoint ITPro's at the customers, since they only needed to configure an excel sheet to change settings.

Also Ben Curry got a nice VBscript for installing SharePoint that we have used with success before: http://www.mindsharpblogs.com/ben/archive/2008/03/08/4411.aspx

hth Anders Rask

share|improve this answer
add comment

I am surprised nobody mentioned this already, but I would recommend AutoSPInstall from Codeplex. This powershell script works like a charm! Believe me, I tried it the hard way - it is difficult to find all of those different services and figure out their settings and all.

Honestly, I don't know if it gets better or easier than this. This package has 22 reviews (scroll down after you follow the link) and every single one of them are 5-stars!

Here is my review:

Being new to Sharepoint Server, and only ever having done one installation of Sharepoint Services 2007, I was rather new. I went through the installation of Sharepoint Server 2010 Enterprise (alone!) and found many things that did not get started right. After doing it the hard way, I decided to try AutoSPInstaller - that was the right choice! So I add my five stars to the other 22. Thank you!

Here are a few of the reviews:

I am very new to SharePoint in general. I was very happy with this utility and my understanding of the installation process was greatly improved from using it. Excellent work I appreciate all the hard work that was put into this utility. I have never installed SharePoint before By the end of the day we had SharePoint installed and did not have to use the MS Wizard. Awesome!

Just can´t state often enough how helpful this project is. Especially when you have to consistently set-up three farms (Prod/stage/test) with a total of 10 servers in parallel. tripplelike

Awesome release, it took 58 minutes to install prerequisites, SharePoint binaries, SP1 and June 2011 CU on an i5 8GB RAM laptop with 3 vmware workstation VM's. UP Sync also works flawlessly with the newly introduced feature to script the connection creation.

share|improve this answer
add comment

I think it is hard to say what the best way is since it really depends on your situation and what kind of install you are looking to do. There are some that have scripted the install process. I haven't had a need to do that since I don't bring up new environments very often.

Gary Lapointe has a sample of how he scripts it: http://stsadm.blogspot.com/2008/03/sample-install-script.html

Once the system is installed, provisioning apps, sites, etc can either be done via stsadm or PowerShell. I would encourage you to try the PowerShell path since it is a little more robust and is becoming the preferred path for these things.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.