Managing the Distributed Cache

Question

In MS documentation I often see this(or something similar)
"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. "
In many blogs including technet, I see this command always used
Restart-Service -Name AppFabricCachingService
I often see this when updating timeout settings.
Are these considered the same thing?
This is an example, how would you perform these steps.
Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache
$DLTC = Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache
$DLTC.requestTimeout = "3000"
$DLTC.channelOpenTimeOut = "3000"
$DLTC.MaxConnectionsToServer = "100"
Set-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache $DLTC
Restart-Service -Name AppFabricCachingService

Answer 1

I haven't seen a clear statement about disabling the DC. It provides many essential caches where there are otherwise no replacements. Using the restart cmdlet isn't likely to cause you to need to rebuild your farm, Microsoft just doesn't want you touching
the Distributed Cache outside of SharePoint, basically.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.