A few weeks ago Joel Oleson, Shane Young and I provided some posts that walked you through updating your MOSS 2007 Beta2TR Farm to RTM. Because Joel and Shane did such a fine write up I’m not going to try and duplicate their efforts but what I do want to do is step into their steps and provide some clarity on Upgrading multiple servers in a farm.
So following the prescribed process you already ran all the steps that lead you to the reinstallation of MOSS 2007 and that is where we begin. In my Farm I am set up with the following topology:
Web Front Ends
Server1
Central Admin
KN Application Service
Windows Sharepoint Incoming Email
Windows Sharepoint Web Application
Server 2
Central Admin
KN Application Service
Windows Sharepoint Incoming Email
Windows Sharepoint Web Application
Server 3 (Index and Search Queries)
Central Admin
KN Application Service
Windows Sharepoint Incoming Email
Windows Sharepoint Web Application
Office Sharepoint Server Search
APPLICATION Servers
Server 4
KN Search Service
Incoming Mail
Web Services Web Application
Server 5
Excel Calculation Services
Windows Sharepoint Services Help Search
Incoming Email
Web application
Stepping into the procedure we will pick up after Task 2 has completed
1. Run Setup for the release version of Office SharePoint Server 2007.
2. Follow the steps to install the product. Be sure to select the same server type previously used for this server, and to enter a PID key corresponding to the same license type (Standard or Enterprise) that you selected when you installed Beta 2 Technical Refresh (you noted this information under "Record current server information," earlier in this article). Cancel the SharePoint Products and Technologies Configuration Wizard when it opens.
It’s at this point where you would want to run the Installation Package on your other Servers in the farm. I know this sounds obvious but I have received a couple emails regarding this and I want to clarify that you will do this at this point.
3. Install any Office SharePoint Server 2007 Language Packages. At the end of every language pack installation, cancel the SharePoint Products and Technologies Configuration Wizard when it opens.
4. Run the SharePoint Products and Technologies Configuration Wizard. Use the Central Administration account and password that you noted under "Record current server information," earlier in this article.
Personally I was never prompted for a password during this entire process. It could be that the account that I was logged in as has the necessary rights both on the local server as well as the Content Database where I was connecting to. In any case it is at this point that you would run the Sharepoint Products and Configuration Wizard on a Front End Server that hosts Central Administration… In my case I will always run this on the initial box I originally ran the install (Server1)
A message box appears to remind you that services will be started; click Yes.
A message box appears to remind you to run the wizard on each server in the farm; click OK.
Note Upgrade may only be run on one server computer in the farm at a time.
Ignore the warning displayed in the wizard that reads Failed to start search service SPSearchServinceInstance on this server after completing upgrade. Please start it manually. You will start this service in step 7.
5. Wait until upgrade has been completed successfully on this server computer.
So the Server has completed its upgrade and is now rejoined to the Configuration Database. Its at this point I want to start to upgrade the other boxes in my Farm. As a note I am not sure if the order of this upgrade really matters but I decided to Upgrade Server 3 next which is used to Index Content, Servers Search Queries and also runs the Office Search Service.
At this point you can log onto the other boxes in your farm (Do this one server at a time) and run the configuration Wizard. When you do run this on the additional farm servers you will simply need to select Next to complete the install…. The Database information is already set.
Once this is complete you can move onto the rest of the steps outlined by Joel and Shane and you should be in good shape.
Issues Encountered during my upgrade:
I ran into 2 strange issues and one I can’t explain.
Issue 1
When I ran the Configuration Wizard on one of the Application Servers (Server 4) It failed soon into the upgrade with a warning that it could not locate the HOSTS file in the _\System32\Etc folder. I simply copied the HOSTS file from one of the other servers to this box and reran the install which solved that issues
Issue 2
On that same server (Server 4) it was stuck on Task 8 of 9 and the event log was generating an Event ID 3351 and it claims the SQL Database Login Failed. “ Login failed for user ‘NT Authority\Anonymous Login’”. This seemed odd and after further investigation I took a look at the NT Services and found that the SP Timer service was set to run under the local account… I changed this to the Domain\SPService Account and reran the Configuration Wizard. It ran with no issue.
The bottom line here is I that if this were going to be a production environment I would never go through all of this…. I would obviously choose a fresh install all the way but….. For those of you out there running Pilots that will need to remain Pilots this should help you sort your way through the upgrade process on a multi server environment.
Hope this helps and feel free to ping me with any questions.