September 2015 CU for SharePoint 2010 is Released.

September 2015 CU for SharePoint 2010 is Released.

For September 2015 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

The KB articles for September CU should be available at the following locations in a couple of hours:

• KB 3085530 - SharePoint Foundation 2010
• KB 3085521 - SharePoint Server 2010
• KB 3085517 - Project Server 2010

The Full Server Packages for September 2015 CU are already available through the following links:

• Download SharePoint Foundation 2010 September 2015 CU
• Download SharePoint Server 2010 September 2015 CU
• Download Project Server 2010 September 2015 CU

Note:

1. Be aware that CU is a Post-SP2 hotfix. It is required to have SP2 installed before installing the CU.
2. It is required to have SP2 installed for the base product and all installed language packs to install September 2015 CU for SharePoint 2010.
3. This CU includes all SharePoint 2010 fixes (including all SharePoint 2010 security fixes) released since SP2. The CU does not include SP2.
4. After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.
5. Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.
6. That means only one package has to be installed for the SharePoint 2010 product family.

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

SQL high available failover

SQL high available failover:

Description: Most of the administrators think that the failover should do in SQL HA by the Windows Cluster, but it’s not true. we need to do the failover by the HA method which is configured in SQL.

In this article I am providing the steps to do the failover.

Steps: Please follow the steps below to do failover in HA.

As per below screen ,Secondary Don’t have any resources so patch first in secondary.

                                 

 Once patching done successful in secondary do failover resources to secondary, then  primary becomes secondary.

Do patch in other secondary now.

Failover steps:

1.      Logon to the SQL server with SQL account

2.      Go to SQL management studio.

3.      Expand availability groups as per the screen below.

4.      Right click the DB

5.      Click on Failover

6.      Click on next in introduction

7.      Select a new primary replica->next

8.      connect to replica->click next.

9.      successful

                                 

 

 
I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.