Hotfixes, service packs, and password resets
Some great content has recently been pushed out to TechNet and in the KBs. While we haven't announced the timing for SP1, you may have heard some customers have been beta testing it and internal testing that's been going on. There was also a post on the team blog around the DST fix with updates to the time tables which impact most of the world.
TechNet Articles related to updates (hotfixes and service packs)
Deploy software updates for Windows SharePoint Services 3.0
Deploy software updates for Office SharePoint Server 2007
Check for Updates
Microsoft Update (also known as Windows Update) - This will check core Microsoft products including Windows, .NET Framework, etc...
Office Update - Check to see if you need any updates. Note this works with Windows 2000 and Windows 2003 servers to check for Office SharePoint Server and SharePoint Portal Server updates as well as Windows SharePoint Services and SharePoint Team Services Updates.
"The Office Update service is maintained to support previous versions of Microsoft Office and for compatibility with older operating systems. Microsoft Windows Vista users can now get all Office XP, Office 2003, and 2007 Office system updates via the Microsoft Update service. For Windows Vista users using Office 2000, you can manually download updates from Downloads on Office Online." Vista itself has a special page for updates. You will be redirected there automatically.
Latest Hotfix/Rollup
MS07-059 Important Security Public Update for WSS 3.0 and MOSS 2007
Update for Windows SharePoint Services 3.0 (KB941422) (includes latest hotfixes, including the DST (daylight savings time zones) The XML file will allow it to be much more easily managed and changed if necessary for future time zone changes.) Note: This applies to MOSS 2007 standard and enterprise editions as well.
KB 888253 How to configure time zone information in Windows SharePoint Services by modifying the Timezone.xml file
KB 941422 Description of the Windows SharePoint Services 3.0 Hotfix package: August 24, 2007
This package includes the following:
-
Fix to address a problem with Timer Jobs failing to run in the US daylight saving time (DST) change window beginning October 28th, KB 938663.
-
Non-DST related fixes for volume shadow copy writer service, KB 935605.
A fix to address database creation failures after Internal Database Engine SP 2 is applied to Basic installations.
-
Other top support issue fixes including KB 937038 where configuring Inherit Permissions causes HTTP 500 - Internal server error.
-
A primary fix for 941422 expands the capabilities of SharePoint such that TZMOVE can address future Time Zone changes in SharePoint timezone.xml for US or international Time Zones, KB 939809.
Some may ask what happens if there is a critical hotfix for WSS? Since it is in Windows it would be available via Windows Update. If the server was set to auto update it would be auto applied. For this reason I would recommend being notified when an update was available in a smaller shop that isn't tracking these, but in no circumstances would I recommend auto applying the hotfixes. There are just too many chances that the box would want to reboot and when it came back up, all the services may not come back online, not as a result of the hotfix, but some environments require an F1 to initialize a disk array or various things like this. I have applied hotfixes and service packs in the past that installed some of the binaries but as a result of something being in use, it was not able to be fully applied until after the reboot which then didn't get a chance to apply changes to the database. Most hotfixes maybe even all won't make changes to the schema, and may simply be binary updates. Service packs and some hotfixes may need to increment the version in the config and content databases or other databases and having the database listed version different than the binary versions can cause problems.
One of the more common requests I've seen around downtime and trying to recover is related to passwords. Either someone who built out the farm and used their account left the company, or someone lost the password and everyone is afraid for the SharePoint environment... you get the picture. Password resets is much, much easier in this version. I think you'd be suprised how many times you find out that something went bad a while back and only resetting the services exposes it. Here's an excellent KB with usage on the commands with examples for resetting the service accounts, crawl accounts, db connection passwords, etc...
How to Change Service Accounts and Passwords in MOSS 2007 and WSS 3.0 KB 934383 (September 21, 2007)
<update 10/11/07>
Note the above steps include changing it once in on one server via the command line and leveraging timer jobs to change it across the farm. Be sure to verify. Very cool. It also includes syntax for changing passwords on the SSP, and search/content access account.
One common issue with Hotfixes and service packs is failure to upgrade either the binaries or the databases, or one forgets one server in the farm. There are a few ways to tell you have this situation, one the version numbers don't match, another when you browse you notice 404s.
To verify the version of WSS is updated easiest way to do this is by checking Central Administration, Operations tab, Servers in Farm page.
From Gabe: The most common failure we saw in WSS 2.0 was that the web server administrator did not have adequate permissions to SQL server to upgrade the databases. Keep in mind that when you run psconfig.exe you do so in the context of the logged in account. That account must be a web server administrator and either be an administrator on the SQL server or have Database Creators and Security Administrators roles and have Database Access to all of the SharePoint databases.
This quote from a recent hotfix KB (MS07-059) explain some update tips in more detail.
"Note: On a MOSS server if you browse directly to the full URL of the site at /pages/default.aspx you will receive a blank white page with an error stating. An unexpected error occurred. A 404 error can indicate where a hotfix or service pack has not been fully applied to one or more servers. If you encounter a problem check the upgrade.log files for errors. Most likely the schema version and the binary version (code) don't match. You may see event ID 5617 if psconfig (see command below) was not run.
Log files are stored in <system drive>\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS
This problem can occur for a number of reasons:
· The web front end administrator does not have permissions to the SQL server and psconfig cannot update the databases
· SQL database engine is temporarily unavailable for any reason and psconfig cannot complete the upgrade
· Permissions on the file system or registry are incorrect and upgrade cannot get past permissions problem to do the upgrade
· Customer restored a WSS content database in place rather than going through Manage Content Databases to add the database
· Customer has a server farm and forgot to run psconfig on one or more of the servers
Correct any problems detected and then force the upgrade to run:
|
To force a software update |
|
1. Force a software update operation by opening a command prompt, and changing to the directory:
%programfiles%\common files\Microsoft shared\web server extensions\12\bin\
1. Type the command:
psconfig –cmd upgrade –inplace b2b –wait –force |
"
If that doesn't work try it via STSADM, this will upgrade the binaries first, then look at the databases and update them per the software on the server. Be sure to do the psconfig first.
stsadm -o upgrade -inplace -forceupgrade
(b2b as in build to build)
Public Updates:
The public updates install similar to Hotfixes in that they install binaries on the web front end and then upgrade the databases and database versions by using the SharePoint Products and Technologies configuration wizard or psconfig.exe command line utility
psconfig –cmd upgrade –inplace b2b –wait –force
For Basic installs (single server with MSDE) of WSS and MOSS, customers with AutoUpdate turned on will get the updates automatically and the configuration wizard will automatically run silently to update the databases. For any installation other than Basic the customer will need to go to the download center to acquire the update. Public updates will not install via AutoUpdate on a server farm (multi server) installation. Support will try to include links to these public updates for ease of use, but they will be included on download center.
You may find that after a reboot, upgrade may not have completed and running the above command helps complete the command when files were in use for example.
</update>
