All about SharePoint best practice... ask me how
Notes on the recently released Infrastructure Update for SharePoint [ Posted on: 22-July-2008 ]

UPDATE [29 July 2008]: Infratsructure Update Known Issues

Please note that there are some issues with regards to this update and I highly recommend this update to be thoroughly tested prior to being deployed

Please notice that the Infrastructure Update [ http://support.microsoft.com/kb/951695 ] has been updated to include the following information with regards to AAM:

Known issues discovered after release of this update

  • Installing the Infrastructure Update in a SharePoint farm that uses Alternate Access Mapping with a reverse proxy or a network load balancer, such as in an extranet deployment, may cause some public URLs to become unresponsive.
  • Microsoft is aware of this issue and is developing a solution. Before installing the Infrastructure Update, customers who use this configuration should use a test environment to verify that public URLs remain accessible after the update is installed.

As previously mentioned here in my blog the infrastructure upgrade installation should be be planned since it will essentially take your SharePoint farm offline until the updates have been applied. The services that will be affected with this update include IIS, SharePoint Timer Service and the SharePoint Administration Service. These services will be stopped and started by the setup wizard during the update process.

Things you *Must* do when updating an existing SharePoint deployment

  • It is highly recommended that you have upgraded your server farm to WSS and MOSS Service Pack 1 level. (Honestly I think you must upgrade to SP1 before applying these updates)
  • You have to first install the WSS V3.0 update before installing the MOSS update.
  • Ensure that you use the correct version of each update on your farm. (Make sure to download the x86 update on x86 servers and x64 for the x64)

Infrastructure Update for Microsoft Office Servers (32-bit, 64-bit)

  • Logon with the "Setup Admin" account to each server when installing this update. This is the account that you used when you first installed SharePoint. If you don't know what this account is then it's time to find out. Don't even attempt to install this update if you don't have this account details. This should be a domain account in a farm deployment.
  • This update *must* be installed to all servers in your SharePoint server farm before running the configuration wizard. The recommended order for each server roles are as follows: Index server, Query server(s) and finally all Web front end servers.
  • Backup all of your Databases via your preferred backup method
  • Backup all of your Custom solution files that are deployed to your Web front end servers

This is an update and not a Service Pack hence the requirement to update WSS first then MOSS. You can skip the Config Wizard after the WSS install and install the MOSS update and run the wizard at the end.

If all goes well you should see the version number 12.0.0.6318 in the Servers in Farm page in Central Administration after the Config wizard finishes applying the updates.

Infra6318

 

Resources

On TechNet: Updates Resource Center for SharePoint Products and Technologies

Issues that are fixed in Windows SharePoint Services 3.0 by the Infrastructure Update

Description of the SharePoint Server 2007 issues that are fixed by the Infrastructure Update


Posted by Chandima Kulathilake | 4 Comments | Bookmark with:        
Tags: Administration, Deployment, SharePoint 2007

Comments and Feedback
Wednesday, 23 Jul 2008 08:12 by Josh
Regarding "This is an update and not a Service Pack hence the requirement to update WSS first then MOSS." I'm pretty sure that on Service Packs you most definitely have to upgrade WSS and then MOSS.
Wednesday, 23 Jul 2008 06:39 by Chandima
@Josh:
Yes you are correct. I meant to say for *new* installs you can get WSS SP1 and MOSS SP 1 builds separately
Thanks Josh
Friday, 25 Jul 2008 04:09 by David McKenzie
"Logon with the "Setup Admin" account to each server when installing this update. This is the account that you used when you first installed SharePoint. If you don't know what this account is then it's time to find out. Don't even attempt to install this update if you don't have this account details. " As I read it, this is a new requirement for SharePoint. It is entirely possible that the original installer account could have been deleted (say following termination). Are you saying that Microsoft has implimented maintenence which could not be applied in such circumstances?
Friday, 25 Jul 2008 10:18 by Chandima
@David
David: A MOSS or WSS install requires at least 4 or 5 set of accounts. These are called setup accounts. Typically in a deployment you create these in AD. You Never want to use a "Persons" account to install MOSS or WSS.
MSFT has not implemented anything of the sort you have implied. If you have not got the account details of the setup account then I suggest that you change these as per this article by Eli Robillard:
http://weblogs.asp.net/erobillard/archive/2007/07/06/how-to-change-service-accounts-and-their-passwords-in-moss-and-wss-3-0.aspx.
This is also documented on TechNet:
Plan for Administrative and Service Accounts:
http://technet.microsoft.com/en-us/library/cc263445(TechNet.10).aspx
Your Name: (Required)
Website URL:
Your Email:
(Will not be displayed)
Feedback and Comments: (Required)
Are you a person? Please enter the charachters in the box below.


 
View the privacy policy.

 
Tags
 
Affiliations
Microsoft MVP (Microsoft Office SharePoint Server)

MCTS - WSS/MOSS Configuration

CKS - Team Member Add to Technorati Favorites

View Chandima Kulathilake's profile on LinkedIn



Kindly hosted by:
Kindly hosted by Intergen





Chandima Kulathilake's Facebook profile