2015年1月12日 星期一

Oracle DBA 維護指令


open trackbacks list 引用列表 (0)

留言列表 (0)

發表留言
您尚未登入,將以訪客身份留言。亦可以上方服務帳號登入留言
其他選項

2015年1月7日 星期三

SharePoint 2010: Event ID: 7362: The super user account utilized by the cache is not configured

SharePoint 2010: Event ID: 7362: The super user account utilized by the cache is not configured

Table of Contents

Problem

You encounter the following error appears in the Windows Application event log:
Log Name:      Application
Source:        Microsoft-SharePoint Products-Web Content Management
Date:          <date>
Event ID:      7362
Task Category: Publishing Cache
Level:         Warning
Keywords:     
User:          <username>
Computer:      <server>
Description:
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 unnecessary 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: [MachineName]\system SharePoint 2010 is hosted on this machine.

Solution

On new installations, the SharePoint super user account is configured to run under the machine's local System account.  However, this causes complications and thus the warning.  This should be addressed during setup, but isn't included in the setup wizard.  Anyway, resolving it is simple.  There are two ways: using STSADM or using Powershell.  We'll go through both here.
Step 1: Create Super User and Super Reader Domain Accounts
Create super user and super reader domain accounts
Example: DOMAIN\sp_superuser, DOMAIN\sp_superreader
Step 2: Configure Accounts in SharePoint Central Administration
Go to SharePoint CA: Central Admin -> Manage Web Application -> User Policy
Add DOMAIN\sp_superuser – Full Control
Add DOMAIN\sp_superreader – Full Read
Check to make sure these accounts have similar access to the SharePoint databases.  Next, use one of the following steps: A or B.
Step 3A: Using STSADM
Open a command prompt
Execute:
stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue DOMAIN\[sp_superuser] -url [WEBAPPURL]
And
stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue DOMAIN\[sp_superreader] -url [WEBAPPURL]
Step 3B: Using SharePoint Management Shell
Open a shell
Execute the following commands:
1.$wcm = Get-SPWebApplication -Identity http://[webappurl/]
2.$wcm.Properties["portalsuperuseraccount"] = “DOMAIN\sp_superuser”
3.$wcm.Properties["portalsuperreaderaccount"] = “DOMAIN\sp_superreader”
4.$wcm.Update()
Close the shell.
Step 4: Reset IIS
Reset IIS either from the GUI or executing "IISReset" at the command prompt.
Step 5: Test
Open a command prompt
Execute the following:
stsadm -o getproperty -propertyname portalsuperuseraccount -url [WEBAPPURL]
Output should read:
<PropertyExist=”Yes” Value=”DOMAIN\sp_superuser” />
Similarly for the super reader account.  The references below provide good background.
Happy Computing!

References


Sharepoint 經驗分享

$w = Get-SPWebApplication –Identity http://sp/
$w.GrantAccessToProcessIdentity("TW\administrator")


even
Go to :\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES
Open TaxonomyPicker.ascx in any text editor (such as Notepad)
Locate the following line :
<%@ Control className=”TaxonomyPickerControl” Inherits=”Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker,Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
Replace ‘,’ with a comma i.e. ‘,’ , the correct line should look like:
<%@ Control className=”TaxonomyPickerControl” Inherits=”Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker,  Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>

2014年10月30日 星期四

Hyper-V Server 2008 R2基礎安裝指南

Hyper-V Server 2008 R2基礎安裝指南

王偉任
雖然Windows Server 2012日前已經正式上市,不過目前大多數的企業仍然採用Windows Server 2008 R2作業系統居多。而在Windows Server 2008作業系統內,不管是GUI圖形介面或是文字介面的Server Core,也都內含了Hyper-V虛擬化技術。
事實上,Windows Server 2008也有一個具備Hypervisor虛擬化平台功能的免費版本,也就是本文所要討論的Windows Hyper-V Server 2008 R2。以下將講解如何安裝及初始化Hyper-V Server 2008 R2。

我們可以將Windows Hyper-V Server 2008 R2視為是Server Core版本的「精簡版本」,只是正常版本的Server Core能夠安裝其他角色及功能服務,但Hyper-V Server 2008 R2僅具備「Hyper-V伺服器角色」和「容錯移轉叢集功能」(圖1)。


▲圖1 Windows Server 2008元件架構。(圖片來源:Windows Server Blog - Building an Optimized Private Cloud using Windows Server 8 Server Core)


在硬體裝置支援上,Hyper-V Server已經包含Windows Server Driver Model,所以只要是Windows Server 2008 R2能夠識別的硬體裝置,Hyper-V Server 2008 R2也可以正確識別。

實作環境所需作業系統及軟體


Hyper-V Server不只是一款可以「免費」使用的Hypervisor虛擬化平台而已,除了能夠進行簡單的「伺服器合併(Server Consolidation)」作業外,還提供了其他更多的功能。

撇開實體主機支援超大容量記憶體空間1TB和Dynamic Memory功能不說,更支援虛擬化技術中的高可用性容錯移轉叢集(Failover Clustering)、快速遷移(Quick Migration)和即時遷移(Live Migration)等等功能。

值得一提的是,Hyper-V Server虛擬化技術平台的Hypervisor雖然精簡,但仍然需要進行安全性更新的動作。以採用Server Core來相比GUI圖形介面,安全性更新的數量大約可以減少40∼60%。

如圖2表格中的Months without reboots欄位,顯示一台安裝Windows Server 2008/2008 R2的Server Core版本,從產品發布到進行部署之後平均約10至13個月才需要重新啟動。倘若只安裝關鍵性安全性更新,還可更進一步減少主機重新啟動的頻率。


▲圖2 Windows Server 2008/2008 R2 Server Core安全性更新數量比較表。(圖片來源:Windows Server Blog - Building an Optimized Private Cloud using Windows Server 8 Server Core)


相較於GUI圖形介面約每隔兩個月就需要重新啟動主機,這種做法大幅減少了主機重新啟動的機會。況且,Hyper-V Server是比正常Server Core更加精簡的版本,因此需要安全性更新的數量更少。 由此可知,由於需要重新啟動的次數大量減少,所以在Hyper-V Server虛擬化平台上所運作的VM虛擬主機也可減少遷移的頻率。

下列表格為針對Windows Server 2008的各種版本(Hyper-V Server、Standard、Enterprise、DataCenter)功能性進行整理的功能清單。




至於作業系統中的Hyper-V版本該如何區分,其實很簡單,區分方法如下:
Hyper-V 1.0:Hyper-V Server 2008、Windows Server 2008
Hyper-V 2.0:Hyper-V Server 2008 R2、Windows Server 2008 R2
Hyper-V 3.0:Windows Server 2012 

MS SQL 指令、語法與管理