May 2015 CU for SharePoint 2010 has been released

May 2015 CU for SharePoint 2010 has been released

The product group released the May 2015 Cumulative Update for the SharePoint 2010 product family.

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

Be aware that the May Cumulative Update for SharePoint 2010 is a Post-SP2 hot fix. It is required to have SP2 installed before installing the May CU.
It is required to have SP2 installed for the base product and all installed language packs to install May 2015 CU for SharePoint 2010.

This CU includes all SharePoint 2010 fixes released since SP2. The CU does not include SP2.

The KB articles for May CU are available at the following locations:

• KB 3017815 - SharePoint Foundation 2010 - This is also a security fix!
• KB 3015569 - SharePoint Server 2010
• KB 2999496 - Project Server 2010

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

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

After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.
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.

May 2015 CU for SharePoint 2013 has been released

May 2015 CU for SharePoint 2013 has been released 

The product group released the May 2015 Cumulative Update for the SharePoint 2013 product family.

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

ATTENTION: 

May CU solves the problem with the different SP1 baselines introduced in April CU. May CU can be installed as well on the old and on the new SP1 baseline!

Another issue that is resolved in May CU is that the server proofing tools no longer have to be updated separately. They are included in the relevant server packages listed below.

Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 to be installed first.

This CU includes all SharePoint 2013 fixes released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.

The KB articles for May CU are available at the following locations:

• KB 3039747 - SharePoint Foundation 2013 May 2015 CU
• KB 3039780 - SharePoint Server 2013 May 2015 CU
• KB 3039753 - SharePoint Server 2013 with Project Server May 2015 CU
• KB 3039748 - Office Web Apps Server 2013 May 2015 CU - This is also a security fix!

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

• Download SharePoint Foundation 2013 May 2015 CU
• Download SharePoint Server 2013 May 2015 CU
• Download Project Server 2013 May 2015 CU
• Download Office Web Apps Server 2013 May 2015 CU

After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.

  

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.

Active directory Federation Services.

Active directory Federation Services.

Active Directory Federation Services (ADFS) is a software component developed by Microsoft that can be installed on Windows Server operating systems to provide users with single sign-on access to systems and applications located across organizational boundaries.

AD FS is a standards-based service that allows the secure sharing of identity information between trusted business partners (known as a federation) across an extranet. When a user needs to access a Web application from one of its federation partners, the user's own organization is responsible for authenticating the user and providing identity information in the form of "claims" to the partner that hosts the Web application. The hosting partner uses its trust policy to map the incoming claims to claims that are understood by its Web application, which uses the claims to make authorization decisions.

I found a very detailed article about the configuration and setting up of ADFS.     

https://sharepointobservations.wordpress.com/2013/08/19/sharepoint-2013-how-to-install-and-configure-adfs-2-0/ 

 


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.

Document conversion load balancer unavailable

Issue: Document conversion load balancer unavailable

Summary:   The Document Conversions Load Balancer Service manages the availability of document converters. Stopping the service stops the document conversion process and turns off the Document Conversions Launcher Service. To resume the document conversion process, you must restart the Document Conversions Load Balancer Service, and then start the Document Conversions Launcher Service.

Symptoms:   One or more of the following symptoms might appear:

1.     Documents are not being converted.

2.     Only one server seems to be converting documents.

3.     The Document Conversions Load Balancer Service is not running.

Cause:   The Document Conversions Load Balancer Service is no longer running. This can occur when an administrator unintentionally stops the service or the server runs out of RAM.

Resolution:   Restart the Document Conversions Load Balancer Service

1.    On the SharePoint Central Administration Home page, in the System Settings section, click Manage services on server.

2.    On the Services on Server page, click Document Conversions Load Balancer Service.

3.    In the Select Server section, verify that the server that you want is selected. If it is not selected, on the Server menu, click Change Server.

4.    On the Select Server page, click the name of the server on which you want to run the Document Conversions Load Balancer Service.

5.    In the Communication Scheme section, select the scheme that you want the load balancer to use for communication. The default is http.

6.    In the Port Number section, type the port number that you want the load balancer to use for communication. Choose a port number that is not used by other services on the server, but which is open in the firewall on the server.

7.    Click OK.

Resolution:   Restart the Document Conversions Launcher Service

1.    On the SharePoint Central Administration Home page, in the System Settings section, click Manage services on server.

2.    On the Services on Server page, click Document Conversions Launcher Service.

3.    In the Select Server section, verify that the server that you want is selected. If it is not selected, on the Server menu, click Change Server.

4.    On the Select Server page, click the name of the server on which you want to run the Document Conversions Launcher Service.

5.    In the Communication Scheme section, select the scheme that you want the launcher to use for communication. The default is http.

6.    In the Port Number section, type the port number that you want the launcher to use for communication. Choose a port number that is not used by other services on the server, but which is open in the firewall on the server.

7.    Click OK.

Note: You must be a member of the Farm Administrators SharePoint group to perform the following task

 


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.