http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx
We're running SharePoint 2010 in a farm configuration with two web front ends, and two application servers. To properly update the environment, Microsoft recommended that we use the following procedure:
- As always, make sure you have a backup of the environment.
- Login to the servers with the same account you used to install SharePoint.
- Run the Foundation updates on all the servers in the farm and reboot.
- Run the Server updates on all the servers in the farm (presuming you have server installed). Microsoft told us running the Server updates alone might be fine, but they recommended running the Foundation updates first. Re-boot all servers after the second update is applied.
- Run the SharePoint Configuration Wizard on the server that hosts the Central Admin site.
- Run the SharePoint Configuration Wizard on the other servers.
- Note that you can also run the configuration wizard from powershell: PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
- You must restart the User Profile Synchronization service after installing this cumulative update. For more information see the Start the User Profile Synchronization service section in the Configure profile synchronization article in the library.
http://support.microsoft.com/kb/2459257
That should be all. Let us know if you have any issues.
1 comment:
After the Config wizard failed and I confirmed it was the UPS Sync in the log mentioned in the wizard.
Central Admin didn’t work but an IISReset fixed that.
I manually started the UPS Sync service in “Manage Services on Server” which failed.
I then remembered the Farm account needed to be a local admin on the Central Admin web server but realised I forgot to remove it so it wasn’t that (this is required to start the service thought). I added the Farm account to the Local Admin group on the SQL server just in case and restarted both (don’t know if this made the difference).
I then went to start the UPS Sync service and it said it had started; only the Forefront Identity Manager Service hadn’t started. Thinking this was strange I stopped the UPS Sync service and the User Profile Service then started the User Profile Service and the UPS Sync service (in that order) and they started along with both the Forefront services as expected. The UPS Sync started much faster than it used to.
An IISReset is then required before the User Profile Service in “Manage Service Applications” will load.
The Profile Synchronization Status should say Idle. I then did an incremental sync to confirm it was working. This worked but didn’t seem faster unfortunately as I was under the impression at least one of the fixes for the UPS was a Sync performance fix.
“When you perform a user profile synchronization from Active Directory Domain Services (AD DS) to a SharePoint Server 2010 server, the contacts of AD DS are resolved in the SharePoint server instead of the Forefront Identity Manager (FIM). Therefore, the synchronization process is very slow.”
I then loaded my MySite.
Hope this helps someone.
Mike
P.S. Don’t forget to remove the Farm Account from the Local Admin Group on you central admin and SQL server and do an IISReset!
Post a Comment