Dec 23
Create a Super User/Reader Account – Object Cache

By default the Portal Super User and Reader User accounts use the NT Authority\Local Service and all SharePoint service accounts should be isolated.

When a file is checked out, a query is made to this checked out version rather than the published version. The issue is that this creates a query to the checked out version and then the system cache makes another query to the published version of the file. As result this creates unnecessary requests which lead to performance issues. Having a reader account helps isolate this behavior.

This may also display as a Warning in the Application Windows logs Web Content Management Source.

Add a Domain Reader and User account to the Farm

  • Central Administration > Application Management > Manage web applications >Web Applications > Policy > User Policy
    • Click Add Users
      • From the Zones list, select All zones, and then click Next
        • In the Users box, type the user name for the Portal Super User account Domain\spsupusr
          • Give the account Full Control - Has full control
            • Click Finish.
    • Repeat the highlited red steps for the Portal Super Reader account domain\spsuprdr
      • In the Choose Permissions section, check the Full Read - Has full read-only access box.
    • Run the following stsadm syntax to add the Reader and User accounts to the Websites.
      • cd C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\BIN
        • stsadm -o getproperty -propertyname portalsuperuseraccount -url http://portal
          • If you receive "Property Exists 'No'" then run:
            • stsadm -o setproperty -pn portalsuperuseraccount -pv DOMAIN\spsupusr -url http://webappurl
            • stsadm -o setproperty -pn portalsuperreaderaccount -pv DOMAIN\spsuprdr -url http://webappurl
          • After receiving the Operation completed successfully
            • Run an iisreset using the command prompt


There are no comments for this post.

 ‭(Hidden)‬ Blog Tools