IT-Spirit Knowledge Base

To content | To menu | To search

Tag - SharePoint 2010

Entries feed - Comments feed

Sunday 14 November 2010

SQL Server Check List for Sharepoint 2007/2010 installation

By Michael on Sunday 14 November 2010, 15:33 - MS-SQL2008

This article review all things you need to think when you plan to install a SQL server for an Sharepoint 2007/2010 infrastructure.

Check list before the installation: 

_Virtual or physical server? Keep in mind that is not recommended to install SQL server for SP into a virtual machine due that SP consummes more disk i/o, storage, processor and memory.

_High avaibility? What else? It's strongly recommended to install SQL server in cluster, but now with SP 2010 you can use the SQL mirroring technologies to provide high avaibility if you do not want to use the MS cluszering technologie.

_Which version about SQL? Avoid SQL 2005 installation definitively. Focus your efforts on SQL 2008 installation. The First question is SQL 2008  or SQL 2008 R2? If you install a MOSS 2007 then choose SQL 2008 but if you plan to install SP 2010 then install SQL 2008 R2 or SQL 2008 SP1 with CU2 (this is mandatory for SP 2010). If your SQL servers have at maximum 8 CPUs, 64 Gb of memory and only two nodes in case of cluster installation choose SQL 2008/R2 Standard edition, if you have servers with more resources you must install the Enterprise edition.

_Dedicated SQL instance or not? For Sharepoint infrastructure you must have dedicated SQL instance and no other programs or applications installed on the SQL server because SP consume more disk i/o and storage. For SP 2010 it is recommended to install one SQL instance for the content databases and another instance for search databases.

_Plan your storage. Choose if it's possible a storage with great performance about disk i/o, plan to format each lun with 64K cluster size, and provision one lun for databases system + tlogs, one or many luns for SP content databases, one or many luns for tlogs about content databases. Apply the same policy for search databases, with SP 2010 it's better to have an another SQL instance to hosts the search databases. For better performance you can isolate the SP config and admin content databases on a separated and dedicated lun. 

_Plan your backup.  For the tool who backup your databases, I prefer to choose MS SCDPM, but if you don't have this tool, you can script a backup with the stsadm command line or by powershell cmdlet in SP 2010. In other case you can backup your databases with you backup software. To restore it, plan to have an another farm (recovery farm), that means to have sufficient storage on this farm and this farm ust have the level about templates, features, solutions, etc.

That all! This article has been write as is and provides some basics information for your governance plan about your infrastructure and to ask you the rights questions.


Saturday 30 January 2010

Configuring your web application with IIS 7.0 and Kerberos

By Michael on Saturday 30 January 2010, 17:46 - Windows SharePoint Service 3.0

This Article describes how to set Kerberos for your SharePoint Web Application, we consider that the kerberos is correctly confugured on the SQL side: SQL Service run with an Active Directory Account and the associated SPN is configured...

To create and configure web application with kerberos follow these steps:

  1. Create an Active Directory user account to run the IIS application pool.
  2. Set the SPN on this account.
  3. Trust Kerberos delegation on this account.
  4. Grant the rights "Local and Remote Activation" on the application pool account for the following DCOM object: IIS WARMREG ADMIN (for all web front end servers).
  5. Add the application pool account into the User Rights Assignments: "Act as a part of Operating System" (for all web front end servers).
  6. Create the web application with Host Header and select Kerberos for the authentication methods. Run the application pool with the application pool account created before.
  7. Edit the ApplicationHost.Config file on all web front end servers, locate this tag: <local path="name of yoursite">, next locate <windows security...> and modifify this tag as follow: <Windows security=.... UseAppPoolCredentials="TRUE" UseKernelMode="TRUE">
  8. Your are done.

Friday 22 January 2010

MOSS 2010 and Farm Configuration Wizzard Utility

By Michael on Friday 22 January 2010, 11:02 - MOSS 2010

A nice feature has been introduced with MOSS  2010: The farm configuration wieeard, this tools configure quickly your farm, web application and site collections, in our case we discuss about the service account and the rights granting by this wizzard into the system....

Go to your Central Admin page and read the following article.

After clicking on the Configuration Farm Wizzard, the system ask you for a service account, please create this account first in the Active Directory with no privilege only Domain Users.

Choose your services...

Note: In your example, we skip the site collection collection....

Ok now we have services configured, we look on our server the privileges granted by this setup for this account:

This account is member of: IIS_IUSRS, WSS_WPG, Performance Monitor Users.
This account have the following privileges: Adjust a Memory Quotas for a process, Logon as service, Replace a level token.

Sunday 10 January 2010

SharePoint 2010 Beta - First Contact

By Michael on Sunday 10 January 2010, 15:03 - MOSS 2010

Prerequisites

First thing when you decide to test MOSS 2010 is to install an W2k8 64 bits, the SQL server must be a SQL 2008 64 bits SP1 with CU2.
After that launch the setup and read the following instructions (In our Case SQL and MOSS are installed on the same machine).
We decide to install the Farm in Kerberos authentication procotol.

Before to begin the MOSS installation you must install the following hotfix:

http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=21953

Good Thing

You can install prerequistes software automaticlally through internet!!!! The setup module Install IIS7 and configure it transparently!!!!
During the installation prerequistes the setup install the following softwares:

• Windows Server 2008 Service Pack 2

• Application Server Role, Web Server (IIS) Role

• Microsoft SQL Server 2008 Native Client

• Microsoft .NET Framework 3.5 SP1

• Windows PowerShell(TM) V2 (CTP3)

• Microsoft "Geneva" Framework Runtime

• Microsoft Sync Framework Runtime v1.0 (x64)

• Microsoft Chart Controls for Microsoft .NET Framework 3.5

• Microsoft Filter Pack 2.0

• Microsoft SQL Server 2008 Analysis Services ADOMD.NET

 

After Installing the prerequisites softwares, launch the setup installation MOSS program and choose the following options:

 

_Installation choice step, please choose Server Farm, look the Web Front options is not here....

_Server type step, please choose Complete install and leave the default options.

 

SharePoint Products Wizzard step

 

Before to launch the wizzard, please create two Active Directory accounts: One for setup MOSS and another one for Farm Admin purpose, for the Farm Admin account please set the SPN, grant this into IIS WarmReg Dcom object with local and remote activation. Grant the farm admin account local admin of the MOSS server. For the Setup MOSS account grant this into SQL with the following roles: DBCreator, SecuriyAdmin.

After that, log on the MOSS server with the setup account credentials and apply the following procedure:

 

_Create a New Farm.

_Specify the SQL instance and give theFarm Admin credentials.

_Wait few minutes,the setup is creating your farm.



New Security features during the setup wizzard: Passphrase to secure communication between farm, data and servers:



 

As you can see no great news about the installation, the new things is just to simplify the setup process with no choice between complete, web front or stand alone, juste Server Farm or Stand Alone and the last thing is the setup process is capable to dowlnload the requirement.