Change Automatic Update on the SharePoint Server

This may not look like a good idea to some system or network administrators due to the security concerns. However, any patches installed to your SharePoint server may bring up issues that give you errors in the even log every couple minutes. The worst thing could happen other than your server explode or transform into a robot is, of course, stop working as you expected.



I have read people from the on-line communities talking about how an installed patch brought down the server or made certain features stop functioning as before.



If your environment does not have a centralize system or process to evaluate the updates sent by Microsoft, change the update service from install to download and notify you instead. You will have chances to review them and stop any potential problems before you are certain.

Two tips to install SharePoint

Since last summer I have spent some time to answer questions on a web site to help others with SharePoint. Some of the problems or questions I came across were pretty common: web site broken after update installed and server account stopped working.

Especially for those who was using Small Business Server (SBS), it happened more often than regular Windows 2003 implementation.

So, here are two tips for you if you would like to learn or start SharePoint (WSS, 2003 or MOSS 2007) installation:

1. Do not use the Default Web Site in your IIS. Especially if you are sharing a server with other applications. You may break other application or vice versa. Create another web application and use it for your SharePoint sites. This has nothing to do with using port 80.

2. Remember to use real user accounts to install and configure your SharePoint and/or database. If the environment is under a domain, use domain user accounts. If it attaches to a workgroup, use real user accounts. Do not use any machine or system service accounts in your application pools, search and indexing services.

Enjoy your trip with SharePoint.