Please install the SharePoint updates on your server
Seriously, you should install the updates before you have to set those clocks back an hour. Heck, if I am having to remind you this then I should also remind you to check the batteries in your smoke detectors. J
This is a security update! Yes, I know it fixes the annoying day light savings issues it also fixes some important security issues. Read the security bulletin. Does your server face the internet? Maybe as an extranet? Then you should of installed this yesterday.
Here are my brief yet kind of helpful instructions. There is nothing earth shattering here. I just know people like to know exactly what they are in for before doing an update. These instructions are only right if you are running One SharePoint Server. If you have multiple SharePoint servers you need to read these instructions. For WSS update and MOSS update. These instructions cover how to verify if you already have installed the patches, known issues, secure and farm scenarios, still in the middle of an upgrade from v2, how to use the updates folder for a fresh install, how to detach your content databases to speed up the update, and how to verify the install was successful.
If you have any issues after you install the updates then check out Bill Baer's post http://blogs.technet.com/wbaer/archive/2007/10/15/kb934525-troubleshooting.aspx It fixed one of my customer issues and some post on the MSDN Forums. But don't tell Bill it helped you, his head is getting too big already. ;)
You will have downtime while installing these updates! Plan accordingly. Some servers will even have to reboot, others will not. (I have been exactly 50-50 on this.)
Ok here is my setup that I am about to patch. Server 1 is the SQL 2005 SP2 database box. Server 2 is a Windows Server 2003 SP2 with MOSS 2007 Enterprise installed. I am doing everything on Server 2. I give you run times on the longer parts for reference points. Your times will vary!
- Backup SharePoint!
Download the software you need. For my servers I downloaded the 32 bit editions. You must install BOTH the WSS and MOSS update if you have MOSS installed.
- WSS v3 32bit update
- MOSS 2007 32bit update
- WSS v3 64bit update
- MOSS 2007 64bit update
Stop the World Wide Web Publishing Services to keep your users off the server.
- Start > Administrative Tools > Services
- Scroll to the bottom of the list, click World Wide Web Publishing Service
- Click the Stop button
Install the WSS update (total time less than 2 minutes)
- Find the downloaded file. For me this was wssv3-kb934525-fullfile-x86-glb.exe
- Double click to run the file
- Read the license terms, click accept
- Click continue
- At the reminder message click OK
- Now it starts processing the update.
- At the installation complete message click OK
- Now if you have just WSS skip to step 7
Install the MOSS update (total time less than 2 minutes)
- Find the downloaded file. For me this was Officeserver2007-kb937832-fullfile-x86-glb.exe
- Double click to run the file
- Read the license terms, click accept
- Click continue
- At the reminder message click OK
- Now the update process…
- At the end of my update I was greeted with a REBOOT message. If you are then click Yes to reboot. If not click OK at the installation complete message.
Run SharePoint Configuration Wizard (15 minutes)
- Start > All Programs > Microsoft Office Server > SharePoint Product and Technologies Configuration Wizard
- Click Next at the Welcome screen
- Click Yes at the warning about restarting services
- Click Next at the Completing the SharePoint Product and Technologies Configuration Wizard
- Your server is now processing step 1
- You will be prompted to now install the updates on other servers in your farm. Click OK since you only have 1 SharePoint server.
- Now your server is processing steps 2 through 9.
At step 8 I noticed this error. Best I can tell nothing bad happened. If you see this makes sure search still works. The install doc above covers how to restart search if you do have issues.
- Speaking of step 8 it took my server approximately 13 minutes to process 4.4 GB of content. I am sure your times will vary. Just don't panic on this step if it takes a while. It is essentially touching all of your content.
- At Configuration Successful click Finish
Check out Central Admin
- Restart the World Wide Web Publishing service you stopped in step 2. If you had to reboot this is not necessary.
- Click Operations tab
- Under Topologies and Services click Servers in farm
- Next to your server you should see Version 12.0.0.6039 not 12.0.0.4518. If you do you should be good to go.
That is it. :)
If you have question not covered contact me or check out Joel's Update FAQs
Shane – SharePoint Help