Skip to main content

MOSS 2007 versions

Here is a list of MOSS patches, corresponding versions, and release month and year:

Office SharePoint Server 2007 : 12.0.4518.1016

October public update (2007) : 12.0.6036.5000

Service Pack 1 : 12.0.6219.1000

Post Service Pack 1 rollup : 12.0.6300.5000

Infrastructure Update (IU) : 12.0.6320.5000 (July 2008)

August Cumulative Update : 12.0.6327.5000

October Cumulative Update : 12.0.6331.5000 (October 2008)

December Cumulative Update : 12.0.6335.5000 (December 2008)

February Cumulative Update : 12.0.6341.5002 (February 2009)

Service Pack 2 : 12.0.6420.1000 (April 2009)

April Cumulative Update : 12.0.6504.5000 (April 2009)

June Cumulative Update : 12.0.6507.5000 (July 2009)

August Cumulative Update : 12.0.6514.5002 (September 2009)

October Cumulative Update : 12.0.6520.5000 (October 2009)

December Cumulative Update : 12.0.6524.5001 (December 2009)

February Cumulative Update : 12.0.6529.5000 (February 2010)

April Cumulative Update : 12.0.6535.5000 (April 2010)

June Cumulative Update : 12.0.6539.5000 (June 2010)

August Cumulative Update : 12.0.6545.5001 (August 2010)

For updated information, please refer:
http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx

Here is the recommended installation sequence of updates:

1. Latest available Service Pack for WSS 3.0
2. Latest available Service Pack for MOSS 2007
3. Latest available CU (Cumulative Update) for WSS 3.0
4. Latest available CU (Cumulative Update) for MOSS 2007

In a farm the updates can be applied on the SharePoint servers in the above sequence and PS Config wizard needs to be run on every SharePoint server in the farm.

More information on deploying software updates for SharePoint Server 2007 may be found here:
http://technet.microsoft.com/en-us/library/cc263467%28office.12%29.aspx

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker: ...
Post a Comment
Read more

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Page layout HTML changes not reflected in associated aspx

I had this issue for quite sometime with a SharePoint Online project I was working on. I use Design Manager to create a new layout page and add snippets to the html layout. I would create webpart zones, add my webpart snippets on to the html, save and publish but the resulting aspx page wouldn't have any of my webparts in it. I checked it from SPD 2013 and everything looks perfect, I can see all the code snippets in there. It was really strange and I had no clues. I had some content search webparts in the layout and one content editor webpart with a link to a text file with some css in it. After countless hours on the internet I read about few other people having similar issues when they had custom css on the layout pages to hide quick launch. I tried removing my content editor webpart and everything seems to be normal. A new page created using the layout had all the webparts in it and even the layout preview was displaying fine. I needed this css somewhere on the page and ...
Post a Comment
Read more