I was installing a new SharePoint 2013 farm using AutoSPInstaller and I noticed that the October 2014 CU was not installed by AutoSPInstaller. I prepared the following:
Placed the SharePoint 2013 with SP1 binaries in the 2013\SharePoint folder
Placed the (extracted) September 2014 CU in the 2013\SharePoint\Updates folder (slipstream scenario)
Placed the October 2014 CU files (3) in the 2013\Updates folder
When executing the AutoSPInstaller Laucher, it does not install the October 2014 CU files, because the script looks for files starting with a certain name:
$cumulativeUpdates = Get-ChildItem -Path "$bits\$spYear\Updates" -Name -Include office2010*.exe,ubersrv*.exe,ubersts*.exe,*pjsrv*.exe -Recurse -ErrorAction SilentlyContinue | Where-Object {$_ -notlike "*ubersrvsp2013-kb2767999-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrvprjsp2013-kb2768001-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrv2010-kb2817527-fullfile-x64-glb.exe"} | Sort-Object -Descending
But Microsoft now releases a monthly update also using the Windows Update service. The filenames are now different:
acsrvloc2013-*
coreserverloc2013-*
osfserver2013-*
The script does not recognize these files as a CU. Hence, it is not installed.
Comments: Sticking with support for "Uber" updates only for now.
Placed the SharePoint 2013 with SP1 binaries in the 2013\SharePoint folder
Placed the (extracted) September 2014 CU in the 2013\SharePoint\Updates folder (slipstream scenario)
Placed the October 2014 CU files (3) in the 2013\Updates folder
When executing the AutoSPInstaller Laucher, it does not install the October 2014 CU files, because the script looks for files starting with a certain name:
$cumulativeUpdates = Get-ChildItem -Path "$bits\$spYear\Updates" -Name -Include office2010*.exe,ubersrv*.exe,ubersts*.exe,*pjsrv*.exe -Recurse -ErrorAction SilentlyContinue | Where-Object {$_ -notlike "*ubersrvsp2013-kb2767999-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrvprjsp2013-kb2768001-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrv2010-kb2817527-fullfile-x64-glb.exe"} | Sort-Object -Descending
But Microsoft now releases a monthly update also using the Windows Update service. The filenames are now different:
acsrvloc2013-*
coreserverloc2013-*
osfserver2013-*
The script does not recognize these files as a CU. Hence, it is not installed.
Comments: Sticking with support for "Uber" updates only for now.