• Call Toll Free: 1-855-909-3300

SharePoint Server 2013 – Methods to Managing Distributed Cache Service Discussed

Specific ordered procedures need to be essentially followed if you want to manage the Distributed Cache Service (DCS) in SharePoint 2013. In this post, we will take into account the various procedures a SharePoint server administrator needs to follow in order to perform management tasks on SharePoint Server’s Distributed Cache Service.

How to Start/Stop DCS Using Central Administration…

Starting or stopping the Distributed Cache Service is a normal task for an administrator. Let’s take a look at the method to start/stop DCS with help of Central Administration in the form of following flowchart –

SharePoint Server 2013

Alternatively, it’s also possible to start or stop Distributed Cache Service by typing appropriate command in the SharePoint 2013 Management Shell command prompt.

How to Add/Remove Server in Distributed Cache Cluster…

When a server is removed, two things happen –

  • Distributed Cache service stops
  • Distributed Cache service gets unregistered from the server

Exact reverse of above happens when a server is added; i.e. DCS gets registered on the server and finally starts. An administrator will be unable to see the DCS listed on Central Administration’s “Services on Server” page when DCS is unregistered.

In order to add or remove a server in Distributed Cache cluster, type & run following commands suitably in SharePoint Management Shell command prompt –

SharePoint Management Shell command

Unregistering the Distributed Cache Service implies that an administrator will not see the DCS listed on the “Services on Server” page given under Central Administration. On the contrary, registering DCS will make allow the administrator to view it as listed on the Services on Server page.

To know more about SharePoint Hosting, call : 1-855-909-3300

Some Don’ts you should Know while Managing DCS…

Failing to comply with the standard procedures of managing Distributed Cache Service in SharePoint 2013 may render the Cache service unrecoverable on non-functioning.

Rebuilding the server farm may be required in case the situation is too extreme. Windows Server AppFabric is a prerequisite for Distributed Cache and hence you need to avoid below points from bringing in practice –

  • Don’t administer the AppFabric Caching Service from the Services window given under Administrative Tools in the Control Panel.
  • Don’t deploy the applications in the folder “AppFabric for Windows Server” given on the Start menu
  • Don’t make use of service account names with the $ symbol

I am sure, the methods explained above will help SharePoint administrators manage the Distributed Cache Service (DCS) in SharePoint 2013 with optimum ease.

Tagged under:

2 thoughts on “SharePoint Server 2013 – Methods to Managing Distributed Cache Service Discussed”

Leave a Reply

Techarex NetWorks Products