Sharepoint 2013 June Cu Download
I have a SharePoint 2013 environment with a dedicated SQL server and two SharePoint servers, one application and one web-fornt-end server. The SharePoint farm has service pack installed, and the build number is: 15.0.4569.1000. When i tried to install June 2015 CU, it failed after file extraction. Is it true that I also need to download the two.cab files from KB 3054866 and put them together under the same folder as the executable file? I did some search and found an reported issue for April 2015 CU. It is due to the different version of SP1.
Nov 22, 2013 Sharepoint 2013 and Cumulative Updates / Hotfixes. SharePoint >SharePoint 2013 - Setup, Upgrade, Administration and Operations. SharePoint 2013. Jun 25, 2013 Be aware that all Update for SharePoint 2013 require. June 2013 CU for SharePoint 2013 has been released. Download SharePoint Server 2013 June 2013. Find and manage updates for SharePoint Server 2016, SharePoint 2013, and SharePoint 2010 in one place. Use the links on this page to get more information about updates and then download the updates.
My SharePoint was built using the RTM version and then applied with SP1. But this issue is fixed in May 2015 CU. I assume June 2015 CU should have no such an issue. Am I correct?
While troubleshooting, I also found out that both SharePoint servers had March 2015 CU installed. So I had to run configuration wizard to apply March 2015 CU to the farm before installing June 2015 CU. This is my client's environment. The IT team claims that they didn't install any SharePoint update except Windows updates back in April this year. Is it possible that SharePoint 2013 CU is included in the Windows updates?
I thought Windows updates will only include some small security update for SharePoint, but not CU.
I’m facing strange problem. I need to do convert WA to claims as well, so installed June CU and ran the conversion. Individual log lines in ULS say – user migration started ->Killer Instinct Mugen Character Download Street on this page. ended and only those not existing in AD were skipped. So far so good. I also verified it in the dbo.UserInfo table. However, at the end of the conversion process, ULS log says: Statistics: ContentDatabases ‘1’, Site Collections ‘866’, Users Succeeded ‘0’, Users Failed ‘1377’.
Did Microsoft forget to fix counter?