The main idea behind this post is the wish of getting a configured SharePoint farm which has friendly and standardized names for the databases created during the configuration process.
Below I will post only the PowerShell scripts that I used to provision the services that don’t offer the possibility of configuring the database name(s).
If you are searching a fully automated SharePoint installation solution, please check AutoSPInstaller on CodePlex.
Central Administration Provisioning
The following script provisions the central administration. Run it on the first SharePoint server within your farm, on the server that is going to host the Central Administration web application.
It all started with my wish to use SharePoint Online included in my Office 365 Subscription to manage and organize my self-employed activity. So having in mind the “Eating your own dog food” principle I designed a simple SharePoint Intranet Solution which included:
|SharePoint Site||Site Template||Description|
|Home Site||Team Site||Contains some personal resources, useful links and the official calendar.|
|Finance||Blank Site||Contains a customer list, invoices and contracts which are related to the coresponding customer.|
|Templates||Blank Site||Contains document and presentation templates.|
|Documents||Document Center||Contains all my project archive documentation and a drop-off library for content routing.|
|Wiki||Enterprise Wiki||Contains my personal KB with articles and links which I consider to be very useful.|
|Search||Enterprise Search Center||A search center to help me find information.|
When I wanted to implement a custom excel template for my Invoice content type in SharePoint online, I found out the hard way that challenges might appear if I used Microsoft Office 2010 64-bit. Rephrased: it did’t work at all. Then I discovered another interesting thing: it was not possible to switch to Datasheet View in my document library.
Basically the error message was:
– A datasheet component compatibile with Microsoft SharePoint Foundation is not installed.
– You Web browser does not support ActiveX controls.
– A component is not properly configured for 32-bit or 64-bit support.
First of all we have to download the SharePoint 2010 Language Packs from Microsoft. Before clicking the Download button please select from the Change Language drop down the language you want to implement.
You could also search for the localized version of the Language Packs, directly. For example – German version of the SharePoint 2010 Language Packs.
One observation – you can use this file too add language packs for the following products too:
- Microsoft SharePoint Server 2010
- Microsoft Project Server 2010
- Microsoft SharePoint Search Server 2010
- Microsoft SharePoint Search Server Express 2010
- Microsoft Office Web Apps 2010
There are 652 SharePoint Server 2010 PowerShell cmdlets. Please find bellow a short list with the ones that I use.
Before starting please verify that you meet the following minimum requirements:
1. Your user account is a member of the SharePoint_Shell_Access role on the configuration database.
2. Your user account is a member of the WSS_ADMIN_WPG local group on the computer where SharePoint Server 2010 is installed.
Please open SharePoint Server 2010 Management Shell. To acomplish this please follow the steps:
1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint Server 2010 Products.
3. Click SharePoint Server 2010 Management Shell.
To create a new Web Application using PowerShell just use:
New-SPWebApplication -Name <Name> -ApplicationPool <ApplicationPool> -ApplicationPoolAccount <ApplicationPoolAccount> -Port <Port> -URL <URL>
Create a Site Collection
To create a new Site Collection using PowerShell first you have to chose a template. To do that just use the following command to list all the templates available within SharePoint:
Then replace <template-name> with your selected template and use the following command to create the site collection:
$template = Get-SPWebTemplate <template-name>
New-SPSite -Url <URL for the new site collection>-OwnerAlias <domain\user> -Template $template