SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Tuesday, December 24, 2013

Setting Distributed Cache Service Managed Account in SharePoint 2013

As many of you are aware, the Distributed Cache Service is a new feature for SharePoint 2013. In effect, this service is used primarily by the App Fabric service.

Once again, the Global Development Center gets it half right - while adding this service to SharePoint, they once again opt for a Powershell solution over enabling the setting like every other service.

For most, this will appear when a warning shows up in the Health Analyzer - by default, this service will be assigned to the Farm Account (hopefully) or if you followed the misguided method of using an Installation Account. Regardless, this account should be set to whatever you are using as a standard services account.

The following Powershell enables you to set this account (remember to start Powershell using 'Run as administrator'). Note that the -Identity set on the third line should be the service account to assign (note that the domain name must be specified AND verify that this account has 'Run as a service' rights!):

$farmRef = Get-SPFarm
$dCacheService = $farmRef.Services | where {$_.Name -eq "AppFabricCachingService"}
$acct = Get-SPManagedAccount -Identity sicgtmp\SPServiceAcct
$dCacheService.ProcessIdentity.CurrentIdentityType = "SpecificUser"
$dCacheService.ProcessIdentity.ManagedAccount = $acct
$dCacheService.ProcessIdentity.Update() 
$dCacheService.ProcessIdentity.Deploy()

Be aware that when the .Deploy() command is executed be prepared to WAIT (and wait, and wait some more). This can take anywhere from a few minutes to 1/2 hour or more. Can't tell you why the delay nor why it varies so much.

For a quick reference on this, see the Technet article here:
       http://technet.microsoft.com/en-us/library/jj219613.aspx


No comments: