Monthly Archives: March 2014

Distributed Cache Service In SharePoint 2013

When planning your SharePoint 2013 farm topology you need to plan for the Distributed Cache service.  This feature provides in memory caching for features such as: newsfeeds, authentication, OneNote client access, security trimming and page load performance.

It’s important that you don’t run the Distributed Cache service on servers running SQL Server, Project Server, Excel Services and Search services.  This is because these services require large amounts of memory and therefore compete with the Distributed Cache service for memory.

Don’t use Dynamic Memory with virtual machines in SharePoint 2013 as the cache memory allowance is calculated based on the total memory of the server and the cache isn’t automatically re-sized if more memory is added. Additionally, all servers running the Distributed Cache service must have exactly the same amount of memory.  You can have a dedicated cache host, or run the service on multiple hosts in a cache cluster.

For more information on planning and configuring the Distributed Cache server see follow these links:

Manage the Distributed Cache service in SharePoint Server 2013

Plan and use the Distributed Cache service in SharePoint Server 2013

Advertisements

Installing SharePoint 2013 SP1 on Windows Server 2012 R2

With the release of SharePoint 2013 SP1, Windows Server 2012 R2 is now a supported platform.  In order to use Windows Server 2012 R2, download the SharePoint 2013 SP1 ISO from MSDN or Microsoft Volume Licensing as slip-streaming SP1 into non SP1 media is not supported.  Installing SharePoint 2013 on Windows Server 2012 followed by SP1 and upgrading to Windows Server 2012 R2 isn’t supported either.

I’ve found that the prerequisite installer within the SP1 media isn’t fully compatible with Windows Server 2012 R2 as it errors when enabling the Web Server and Application Server roles.  In order to install the prerequisites, open PowerShell as an administrator and run the following commands, updating the sources parameter to point to the SXS directory on your Windows Server 2012 R2 media.

Import-Module ServerManager

Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 -Source %SXSFOLDER%

Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer,Windows-Identity-Foundation -Source %SXSFOLDER%

Reboot to complete the installation of the roles, then run the prerequisite installer within the SP1 media to install the other prerequisites.