All postings, articles, and other content on this blog are provided ”AS IS” with with no warranties, and confer no rights. Any sample on this blog is subject to the terms specified at Microsoft
I would like to highlight some points concerning Distributed Cache and SharePoint 2013:
The Distributed Cache service can end up in a nonfunctioning or unrecoverable state if you do not follow the procedures that are listed in this article. In extreme scenarios, you might have to rebuild the server farm. The Distributed Cache depends on Windows Server AppFabric as a prerequisite. Do not administer the AppFabric Caching Service from the Services window in Administrative Tools in Control Panel. Do not use the applications in the folder named AppFabric for Windows Server on the Start menu.
On a server that has more than 16 GB of total physical memory, allocate a maximum of 16 GB of memory to the Distributed Cache service. If you allocate more than 16 GB of memory to the Distributed Cache service, the server might unexpectedly stop responding for more than 10 seconds.
The Distributed Cache service can run on either a physical or virtual server. When using virtualization, do not use Dynamic Memory to manage shared memory resources among other virtual machines and the Distributed Cache servers. The memory allocation for virtualized Distributed Cache servers must be fixed.
When your server farm has a dedicated Distributed Cache server. Use the following method to calculate how much memory can be assigned to the Distributed Cache service:
Determine the total physical memory on the server. For this example, we will use 16 GB as the total physical memory available on the server.
Reserve 2 GB of memory for other processes and services that are running on the cache host. For example, 16 GB – 2 GB = 14 GB. This remaining memory is allocated to the Distributed Cache service.
Take half of the remaining memory, and convert it to MB. For example, 14 GB/2 = 7 GB or 7000 MB. This is the cache size of the Distributed Cache service
Use the following procedure to update the memory allocation accordingly.
Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA
It's ready to download August 2013 CUs for SharePoint 2013
SharePoint 2013 (Build 15.0.4517.1005)
REMEMBER TO INSTALL FIRST MARCH 2013 PU IF YOU ARE UPDATING FROM RTM
After installing the updated you should run the SharePoint Config Wizard in every server of the farm.
If SPS 2013 installed you must only install the SPS 2013 CU because it includes the Foundation one.
It's ready to download August 2013 CUs for SPS 2010
SharePoint 2010 (Build 14.0.7106.5000)
(REMEMBER TO INSTALL FIRST SP2)
If SPS 2010 installed you must only install the SPS 2010 CU because it includes the Foundation one.
After you install this hotfix, you must restart the User Profile Synchronization Service for profile synchronization to function correctly.
To work around this issue, follow these steps:
1.Visit Central Administration. 2.Click Manage Services on the System Settings section. 3.Find User Profile Synchronization Service in the list of services and then click Stop if its status is Started. Click Start and provide the credentials to start the User Profile Synchronization Service as soon as its status is Stopped.
For more information, see the Start the User Profile Synchronization service section in the Configure profile synchronization article in the library.
As you may know WSS 3.0/MOSS2007 are in extended support for several months http://blogs.msdn.com/b/calvarro/archive/2012/10/09/life-cycle-wss-3-0-amp-moss-2007-move-to-extended-support.aspx .So there will not be new CUs for the product and from now on, there will be only security updates for WSS 3.0/MOSS 2007 and the will be called Public Updates.