So let’s first learn how we check the current version of SharePoint.
Open Start –> All Programs –> Microsoft Office Server –> SharePoint 3.0 Central Administration
Switch to Operations tab –> Servers in Farm. This will show you all the servers in the farm with the version information
Another way of figuring out about versions is to issue the following SQL Query for any content database. Select * from dbo.versions
Yet another way to verify the versions and successful/unsuccessful install is to check it through Add/Remove Programs. Ensure that Show Updates checkbox is checked below.
All the three screenshots so far were of MOSS SP1 with April CU.
I want to install WSS SP2 followed with MOSS 2007 SP2 along with the patch that fixes trial issue.
The first command I would run on WFE1, WFE2 and AS is iisreset /stop
This is to ensure that no one is accessing any of the website while we update the farm.
I have already downloaded and extracted SP2 and June CU. The idea is to install it in the following order.
Just started binary installation of WSS SP2 on WFE1, WFE2 and AS
On every machine, once SP2 is installed you will be prompted with a wizard, click Cancel instead of Next.
It will give you another message box, click Yes.
Once done with WSS SP2 installation on all the machines, start with MOSS SP2 installation.
Once done with MOSS SP2 installation, you will get this dialog. Click Cancel again.
Press Yes.
Now that you are done with WSS SP2, and MOSS SP2 let’s fix the Trial Issue by installing another patch.
Okay, easy part done. Next step is not really hard, but somehow I always get butterflies when I do it. Anyways, since this is my VM I am not really worrying as much. If you are doing it in production, you better plan the update on a non-production farm, and test your SharePoint to ensure after SP2 to ensure there are no surprises. BEFORE you proceed, you MUST have a proper backup (if it is an existing farm).
Start with AS machine.
Start –> Run –> Type %moss%\bin\psconfigui.exe –> Click OK
Press Next, then click Yes
Press Next and click OK on the next prompt.
Notice that it would say “Initiating the upgrade sequence…” Wait until the wizard completes. If it is an existing server farm, it may take a long time. Be prepared and don’t start PSConfigUI on all the WFEs at once!
Wait until the wizard finishes.
In case there are some issues, %moss%\LOGS\Upgrade.log is your friend. There are other ULS Logs created as well which can be helpful.
Great, in my case it is successful, as you can see below…
Switch over to WFE1. Repeat the steps above starting from the following…
Start –> Run –> Type %moss%\bin\psconfigui.exe –> Click OK
Wait until the upgrade finishes on WFE1. Once done, switch over to WFE2 and repeat the steps for PSConfigUI.exe
After configuration is completed, you will find the information about SP2 in Add/Remove programs inside Control Panel.
If, by chance you would have forgotten patch 971620, because of SP2 your office setup will become Trial and to get rid of this problem install you will need to provide the Product Key and click OK
Final step now is to get June CU installed on this farm.
Installation Order in which I am doing it is as follows…
1. IISRESET /stop on all the servers
2. June CU – WSS on all the servers – only binaries (Configuration wizard should not be executed)
3. June CU – MOSS on all the servers – only binaries (Configuration wizard should not be executed)
4. Run PSConfigUI.exe on one of the servers – AS – Wait till it finishes
At this point, if you have been following my blog posts, you MUST do something EXTRA. This may not be required if you have already created some applications. But right now, since I have not created any Web Applications yet, if try to upgrade any of my WFE machines it will fail…
The error in Upgrade.log will read like this…
Don’t worry, this is by design (or design flaw if like to call it). It is happening primarily since there are no web applications created and you don’t have a web.config. What next?
On your WFE1 and WFE2 machine go to c:\program files\common files\microsoft shared\web server extensions\12\template\layouts… and copy/paste the web.config from \\as\c$\program files\common files\microsoft shared\web server extensions\12\template\layouts
5. Now, run PSConfigUI.exe one by one on all the remaining servers. My experience with setup was not good when I tried running the PSConfigUI on all the machines at one shot. So, I personally prefer doing it sequentially. I don’t even touch any other machine unless one machine is completely done.
Notice, that in the versions table for SharePoint databases, there will be one more entry for June CU – 12.0.0.6510
Central Administration –> Operations –> Servers in Farm should now show…
Awesome, we have just updated our Web Farm with the latest Cumulative Update available – June CU.
I believe, by now you would have become pretty comfortable in setting up a MOSS farm.
In the next few posts, we will configure our farm and I will tell you more about different features of MOSS 2007. The immediate next step would be to setup POP3 email and configure Outlook to send/receive email.
We will discuss about it in the next post. Stay tuned…
The more I want to get something done, the less I call it work. - Richard Bach
Subscribe