Kendra Thorpe’s VU Blog

SharePoint Rollout – The biggest accomplishment this month was inadvertently “fixing” the SharePoint performance issues we’ve been having. I don’t think I have enough time to list all of the things we have tried and the money we have spent to resolve the performance issues plaguing our SharePoint implementation. So here is how it went down, we are in the process of implementing Systems Center Operations Manager 2007. I installed the agents on the SQL 2005 cluster but SCOM was not able to monitor any of our clusters. I put in a change to configure the SQL cluster computer and service accounts for Kerberos in an effort to allow SCOM to monitor SQL. My team member Roland listed the steps I came up with to configure Kerberos on a SQL cluster in his blog so I won’t repost that information. Monday morning people were complimenting us on how fast SharePoint was running. SharePoint and fast were two words I’d never thought I’d hear in the same sentence. So that’s how we inadvertently fixed our SharePoint performance issues, SCOM! We still have not configured our SharePoint web applications to use Kerberos, they are still using NTLM. However, from SharePoint servers to the SQL cluster is Kerberos. I verified this by running the following SQL script:

select auth_scheme,client_net_address
from sys.dm_exec_connections

This will yield the following results:
KERBEROS 192.168.0.56
KERBEROS 192.168.0.92

Upgrade VCMS to 2.5 – We were successful in upgrading VCMS to version 2.5 this time. The upgrade process took about 15 hours total to complete, so I’m glad that we decided to upgrade the backup server first and copy the upgraded database to the production database server then run the upgrade on the production VCMS server. The upgrade ran on the backup VCMS server took 11.5 hours to complete.

Upgrade ESX Servers to 3.5 – I really didn’t have to do much on this. I simply ran the upgrade script on two our ESX servers.