SharePoint Farm Expansions

When I started my current position, I inherited a SharePoint mess. Before I arrived a tech was tasked with installing SharePoint development environment in preparation for a deployment. Due to hardware constraints or some such issue, the development installation and hardware soon became the production environment.

The first hurdle was actually licensing the software. The installation was done with a demo version. We purchased the requisite licenses under out volume license agreement, which of course means that activation failed. Remember, this is a production environment. A couple of weeks later we acquired the proper key and we were on our way.

Our production environment had less than 250 total users and less than 50 regular users for the last year and has humming along quietly. Then came the expansion project.

Now, the current installation was the default installation, which means that it was running off of SQL Server 2005 Express. The service accounts were all NETWORK SERVICE. (Again, and I cannot say this enough, this was done before I arrived!)

We had to expand (finally) our SharePoint Farm. OK, first things first, lets get those service accounts configured properly and put into production. Best practices aside, this is necessary as we will be standing up an additional SQL Server and the SharePoint service accounts are the credentials used to access the databases.

Set the service principle name for each SharePoint service account.

setspn -A HTTP/ServerFQDN DOMAIN\Account
setspn -A HTTP/ServerFQDN:80 DOMAIN\Account
setspn -A HTTP/ServerNetBIOSName DOMAIN\Account
setspn -A HTTP/ServerNetBIOSName :80 DOMAIN\Account

Now do it for each SQL service account.

setspn -A MSSqlSvc/ServerFQDN DOMAIN\Account
setspn -A MSSqlSvc/ServerFQDN:1433 DOMAIN\Account
setspn -A MSSqlSvc/ServerNetBIOSName DOMAIN\Account
setspn -A MSSqlSvc/ServerNetBIOSName :1433 DOMAIN\Account

Now that the accounts are created we need to swap out the credentials. Simple enough task, but it failed miserably. The error referenced that an update was currently in progress. I was a bit confused, as I was the only one in the system, but after a bit of research I located a fix.

Stop the “Windows SharePoint Services Timer” service. Navigate to C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\{GUID}. Backup the contents of this directory. After the backup completes delete everything except cache.ini. Open cache.ini and replace the contents with “1” and save the file. Start the “Windows SharePoint Services Timer” service.

Now to redirect the SQL Server. Open C:\windows\system32\cliconfg.exe. Added an alias on the application server redirecting the old instance to the new one. Stop the SQL services on the old server and copy the data and log files to the new server. Attach the databases on the new server.

SharePoint was still throwing a fit, so for good measure I rebooted both servers.

SUCCESS!!!

~Ron

Advertisements

0 Responses to “SharePoint Farm Expansions”



  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s





%d bloggers like this: