SharePoint 2013 and April CU 2014 issues.

Due to the problem identified in SP1, the  global installation package has not been released yet an. If your business has some urgency to have this issue fixed you can install the single package without any impact in your supportability.

Our full-server packages (SharePoint Server and Foundation) are not yet available and therefore you could install only “sub-packages”. From support perspective we are always suggesting to install full-server packages, but in case you need an important April 2014 CU hotfix, just for your info.

SharePoint contains not only SharePoint components and therefore the following list may not exhaustive.

General information you can find here: http://support.microsoft.com/kb/2953733

Access Server Download Link
Contains fixes when SQL Server 2014 will be used.

OWAS 2013 has an own kb article:
2863899    Description of the Office Web Apps Server 2013 hotfix package (Wacserver-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863899
For this package you need to have a SlipStream installation of OWAS2013 including SP1 or you can install it on top of any other former CU.

SharePoint Server 2013 Oserver package
2760265    Description of the SharePoint Server 2013 hotfix package (Oserver-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2760265

SharePoint 2013 / Word Server
2768332    Description of the SharePoint Server 2013 hotfix package (Wdsrv-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2768332

SharePoint Server 2013 Coreserver package
2863887    Description of the SharePoint Server 2013 hotfix package (Coreserver-x-none.msp; Projectserverwfe-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863887

SharePoint Server 2013 Client Components package
2863895    Description of the SharePoint Server 2013 Client Components SDK hotfix package (Spdevsdk-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863895

More Info
http://blogs.msdn.com/b/joerg_sinemus/archive/2014/04/09/sharepoint-2013-and-09-april-2014-status.aspx

 

 

Does SharePoint supports SQL Server 2014 RTM ?

It was announced that the RTM release of SQL 2014 will be generally available April 1st
http://blogs.technet.com/b/microsoft_blog/archive/2014/03/18/sql-server-2014-released-to-manufacturers-will-be-generally-available-april-1.aspx

Currently we dont have any change to our official article for that but i can say unofficially YES , Starting with SharePoint 2013 SP1 + April 2014 CU will be supported.
You can follow the article that would be updated soon.
http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx

SharePoint 2013 SP1 FAQ

My colleague Stefan has prepared Q/A for SharePoint Sp1 installation  :
You can reach the original Article below link:
http://blogs.technet.com/b/stefan_gossner/archive/2014/02/27/sp2013-sp1-faq.aspx

Question: Is March 2013 PU required to install SharePoint 2013 SP1?
Answer: No. SP1 can be installed as well on the RTM baseline and on the March 2013 PU baseline (means all CUs later and including to March 2013 PU).

Question: Which version is SharePoint 2013 SP1?
Answer: The official version number is 15.0.4569.1506. You can see this version number e.g. in Control Panel – Programs.

Question: Which version number will I see in the Central Admin?
Answer: The configuration database version showing up in the Central Admin is 15.0.4569.1000

Question: Do I have to install as well SharePoint Foundation SP1 and Sharepoint Server SP1?
Answer: No. SharePoint Server SP1 includes SharePoint Foundation SP1.

Question: Do I have to install as well SharePoint Server SP1 and Project Server SP1?
Answer: Yes. The Project Server SP1 does NOT include SharePoint Server SP1

Question: Do I have to run the SharePoint Configuration Wizard after installing SP1
Answer: Yes. The configuration wizard has to be run after updates, including Service Packs, CUs and Security Fixes.

Question: Does SP1 now support installing SharePoint 2013 on Windows Server 2012 R2?
Answer:No. The SP1 update which is currently available for download does not allow the installation on Windows Server 2012 R2 as it is not possible to create a slipstream installation for SP1. You need to wait for the release of SharePoint 2013 with SP1 included.

Question: When will SharePoint 2013 with SP1 (also known as “slipstream version”) be released?
Update 28/02/2014
Answer:”You need slipstream version”. You can now download SharePoint 2013 with SP1 from MSDN and VLSC and MPN.
Note:
Please avoid doing this as this is unsupported due to a change in the package layout which was introduced with March 2013 PU. Due to this change in the package layout it is not guaranteed that the manually created slipstream version will update all modules correctly. Ensure to download the official SharePoint 2013 with SP1 from one of the above listed sites.

Question: I have SharePoint 2013 installed with 3 language packs. Do I have to install also SP1 for all installed language packs?
Answer: Yes. Unlike Cumulative Updates the SharePoint Server 2013 SP1 package does not include the updates for additional language packs. You need to install the service pack for each installed language separately.

Question: Where can I find the list of all Fixes included in SP1 since RTM?
Answer: There is no consolidated List for all Fixes since RTM. Here you can find all fixes which are unique to SP1. Fixes included in earlier CUs are documented in the KB articles of these CUs.

Question: Where can I find information about SP1 for other Office Products?
Answer: The following three articles have information about SP1 for Office Client, Office Server and Exchange

Service Pack 1 for SharePoint 2013 is now available

SP1 provides fixes to improve general stability, functionality, and security in Office, SharePoint Server, and related products. Among the functionality improvements and changes are the following:

  • Compatibility fixes for Windows 8.1 and Internet Explorer 11.
  • Better support for modern hardware, such as high DPI devices and the precision touchpad.
  • New apps for Office capabilities and APIs for developers.
  • Power Map for Excel, a 3D visualization tool for mapping, exploring, and interacting with geographical and temporal data in Excel, is now available to Office 365 ProPlus subscription customers. You can learn more about Power Map general availability on the Power BI Blog.
  • Improvements to the Click-to-Run virtualization technology that installs and updates Office 365 desktop applications.
  • SkyDrive Pro is now OneDrive for Business.

For KBs and Download links
http://blogs.technet.com/b/stefan_gossner/archive/2014/02/26/service-pack-1-for-sharepoint-2013-is-now-available-for-download.aspx

For more details .
http://blogs.technet.com/b/office_sustained_engineering/archive/2014/02/25/announcing-the-release-of-service-pack-1-for-office-2013-and-sharepoint-2013.aspx

SharePoint AAM is deprecated , really ?

If you read following artile you may be confused.

Because the features of alternate access mapping are deprecated, we recommend that you use host-named site collections over alternate access mappings.”
http://technet.microsoft.com/en-us/library/cc261814.aspx

First it is not true !!!  For path based site collections you will use AAM because you have no other possibility. So basically this sentence not aims directly to SharePoint 2013 on-premise solutions.In SPO yes in SPO architecture based on Host named sites collections and AAM usage not necessary but this is not configurable by customers anyway in SPO .I hope, this article will be changed soon . You be sure that AAMs will be around for a long time.

Keynotes for Distributed Cache on SharePoint 2013

My colleague Hector has created a very good article by compiling different issues with Distributed Cache.
You can read the orginal article below link:
http://blogs.msdn.com/b/calvarro/archive/2013/08/29/points-to-consider-with-distributed-cache-on-sharepoint-2013.aspx

Here is the key notes:

  • NEVER admin the distributed cache from the admin console
  • Maximum capacity of memory is 16 GB per host cache
  • Dynamic memory is not supported in SharePoint 2013 environments nor APP fabric servers
  • The prodcuct after being installed allocates 10% of the physical RAM memory available at the sever. It can be configured following the next point.
  • It’s recommended to allocate 2 GB for other services.
  • It’s not supported to develop code against the Distributed Cache of SharePoint 2013.
    “If you are using custom applications in SharePoint Server 2013 which use the AppFabric client APIs, or are creating custom caches, you should create a separate AppFabric cache cluster to support your custom applications. Do not use the AppFabric cache cluster supporting your SharePoint Server 2013 farm. Run your separate AppFabric cache cluster for your custom applications on separate servers from the servers dedicated to your SharePoint Server 2013 farm.
    http://blogs.msdn.com/b/calvarro/archive/2013/06/05/supportability-of-custom-developments-in-sps-2013-and-appfabric-cache.aspx
  • Install the latest APP Fabric CU if possible. Right now we are in CU 4

SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging

The following change was made to the December 2013 Cumulative Update from the previous SharePoint Server 2013 rollup updates. Previously, SharePoint 2013 Cumulative Updates included both the executable and the .CAB file in the same self-extracting executable download. Due to the file size, the SharePoint Server 2013 package has been divided into two separate downloads in December 2013. One package contains the executable file (identified as ubersrv2013kb2850024fullfilex64glb), while the other contains the .CAB file (identified as ubersrv_1). Both are necessary and must be extracted to the same folder to successfully install the update. Both are available via the same Hotfix Download Available link in the KB article for the December 2013 SharePoint Server Cumulative Update release.

For more information:
http://blogs.technet.com/b/office_sustained_engineering/archive/2013/12/20/change-sharepoint-2013-rollup-update-for-the-december-2013-cumulative-update-packaging.aspx