SharePoint 2010 support will end on October 2015

SharePoint 2010 support will end on October 2015

In case if  your still have SharePoint environments running on SharePoint 2010:

Mainstream support for SharePoint 2010 will end on October 13th, 2015:
https://support.microsoft.com/en-us/lifecycle?p1=14944

 

After this date only security fixes will be provided for SharePoint 2010. That means if you are running into an issue after October 13th which is caused by a problem in SharePoint 2010 and which has not already been addressed before you will no longer be able to request a hot fix.
Not the best situation if you are using SharePoint 2010 as a business critical application.

 

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.

July 2015 CU for SharePoint 2013 is available

 July 2015 CU for SharePoint 2013 is available

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

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

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hot fix Download Available link in the KB article for the release.

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

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

• KB 3054931 - SharePoint Foundation 2013 July 2015 CU
• KB 3054937 - SharePoint Server 2013 July 2015 CU
• KB 3054933 - SharePoint Server 2013 with Project Server July 2015 CU
• KB 3054930 - Office Web Apps Server 2013 July 2015 CU

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

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

Note:

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

2.   Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation CU. And the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.

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

4.   This CU includes all SharePoint 2013 fixes released since RTM. The CU does not include SP1. You can install SP1 before or after installing this CU.

Build Nimber : 15.0.4737.1000

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.

July 2015 CU for SharePoint 2010 is Released

July 2015 CU for SharePoint 2010 is available for download 

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

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

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

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

• KB 3054983 - SharePoint Foundation 2010
• KB 3054975 - SharePoint Server 2010
• KB 3054972 - Project Server 2010

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

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

Note:

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

2.   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.

3.   Be aware that the July Cumulative Update for SharePoint 2010 is a Post-SP2 hot fix. It is required to have SP2 installed before installing the July CU.

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

5.   Attention: this CU no longer supports SP1! It is required to have SP2 installed for the base product and all installed language packs to install July 2015 CU for SharePoint 2010.

6. It is required to have SP2 installed for the base product and all installed language packs to install July 2015 CU for SharePoint 2010.

 


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.

Farm configuration Restores in Sharepoint 2013.

Farm configuration Restores in Sharepoint 2013.

Using Windows Power Shell to restore a farm's configuration in SharePoint

You can use Windows Power Shell to restore a farm’s configuration.

To restore a farm's configuration by using Windows Power Shell 

1.    Verify that you have the following memberships:

o    securityadmin fixed server role on the SQL Server instance.

o    db_owner fixed database role on all databases that are to be updated.

o    Administrators group on the server on which you are running the Windows PowerShell cmdlets.

An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.

2.    On the Start menu, click All Programs .

3.    Click Microsoft SharePoint 2013 Products.

4.    Click SharePoint 2013 Management Shell.

5.    At the Windows Power Shell command prompt, type the following command:

Restore-SPFarm -Directory <RestoreShare> -RestoreMethod Overwrite -ConfigurationOnly

<RestoreShare> is network location where the backup file is stored

 


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.

Keep on saying that “A system restart from a previous installation or update is pending” at the pre-requisites installation for SharePoint 2013

Keep on saying that “A system restart from a previous installation or update is pending” at the pre-requisites installation for SharePoint 2013.

                                   

Issue: Keep on saying that “A system restart from a previous installation or update is pending” after the pre-requisites installation for SharePoint 2013. After I run a prerequisiteinstaller.exe successfully and download all pre requests During a SharePoint 2013 install. I got the error "A system restart from a previous installation or update is pending".  even if I already rebooted.

Solution: Please follow the steps below to resolve the issue.

1.    Open the Registry editor (run > regedit)

2.    Navigate to this path “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager“

3.    Rename the “PendingFileRenameOperations” value to “OldPendingFileRenameOperations“

4.    Reboot the server

Solution 2: If you see the issue still, Then Delete the key as below and check again.

1.    Open the Registry editor (run > regedit)

2.    Navigate to this path “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager“

3.    Rename the “PendingFileRenameOperations” value to “OldPendingFileRenameOperations“

4.    Reboot the server

  

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.