Sometimes, I look in my server Windows Viewers, and I’m puzzled. Like for this Event ID 7362 or commonly known: “Object Cache: The super user account utilized by the cache is not configured.” First let’s take a look of the warning message itself.

Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
To configure the account use the following command ‘stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl’. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.
Additional Data:
Current default super user account: SHAREPOINT\system

I understand the meaning of it, but why it isn’t asked when we configure SharePoint Web Application. So, I need to figure find out a service account and I’ll configure it as the cache super user account using STSADM. What STSADM??? Why not PowerShell. Strange no? In fact, this warning message is a relic of MOSS 2007. This was commonly known and the same kind of configuration need to be done with SharePoint 2010.
 
Fortunately, there is a TechNet article on how using PowerShell to achieve it. But let have a closer look about this article. I don’t need one account, but two: One Portal Super User and one Portal Super Reader. And there’s a clear statement on what kind of account it should be.

The Portal Super User and Portal Super Reader accounts must be separated accounts, and they must not be accounts that will ever be used to log in to the site.

But, I don’t want to create more services accounts, can I used some already configured? I’ve decided to user the Search Crawl Read Account for the Portal Super Reader and the SharePoint Farm account for the Portal Super User Account.

Based on my decision, I’ve changed the procedure a little to configure the accounts using PowerShell.

1. On the Central Administration Web site, in the Application Management section, click Manage web applications.
2. Click the name of the Web application that you want to configure.
3. On the Web Applications tab, in the Policy group, click User Policy.
4. In the Policy for Web Application window, click Add Users.
5. From the Zones list, select All zones, and then click Next.
6. In the Users box, type the user name for the Portal Super User account.
7. Click the Check Names icon to ensure that the account name can be resolved by the authentication providers on the application server.
8. In the Choose Permissions section, check the Full Control – Has full control box.
9. Click Finish.
10. Repeat Steps 5 through 8 for the Portal Super Reader account.
11. In the Choose Permissions section, check the Full Read – Has full read-only access box.
12. Click Finish.

Make note of how the names for the Object Cache Super Reader and Object Cache Super User accounts are displayed in the User Name column. The displayed strings will be different depending on whether you are using claims authentication for the Web application.

To add the user accounts to the Web application by using Windows PowerShell

• Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
• Copy the following code and paste it into a text editor, such as Notepad:

[codesyntax lang="powershell"]

$wa = Get-SPWebApplication -Identity "<WebApplication>"
$wa.Properties["portalsuperuseraccount"] = "<SuperUser>"
$wa.Properties["portalsuperreaderaccount"] = "<SuperReader>"
$wa.Update()

[/codesyntax]

• Replace the following placeholders with values:

<WebApplication> is the name of the Web application to which the accounts will be added.

<SuperUser> is the account to use for the Portal Super User account as you saw it displayed in the User Column field mentioned in Step 14 of the previous procedure.

<SuperReader> is account to use for the Portal Super Reader account as you saw it displayed in the User Column field mentioned in Step 14 of the previous procedure.

• Save the file, naming it SetUsers.ps1.

Note:
You can use a different file name, but you must save the file ANSI-encoded as a text file whose extension is .ps1.

• Close the text editor.
• On the Start menu, click All Programs.
• Click Microsoft SharePoint 2010 Products.
• Click SharePoint 2010 Management Shell.
• Change to the directory where you saved the file.
• At the Windows PowerShell command prompt, type the following command: ./SetUsers.ps1
• Reset Internet Information Services (IIS).