Figure: FARM结构。

第一步：需要有Windows Server 2008的环境

第二步：安装SQL SERVER 2008 R2.

Install SQL Server 2008 R2

Figure: Setup Support Rules.

Figure: Accept the License terms

Figure: Setup Support Files.

Figure: Install the highlighted features.

Figure: Disk Space Requirements

Figure: Server configuration | Fill the msraccsql account.

Figure: Error Reporting.

Figure: Install configuration rules.

Figure: Ready to install

Figure: Installation Progress.

Figure: Installation complete.

第三步：配置SQL SERVER 2008

Figure: Open SQL Server Configuration Management | Enable the TCP/IP Protocol

Figure: Set all IPs enable and configure the TCP port as 1433

Figure: Go to control panel | Firewall | Advance | New Rule.

Figure: Choose the type of the rule as Port.

Figure: Choose the TCP | Fill the port 1433

Figure: Allow the connection.

Figure: All checked.

Figure: Fill the name as SQL Server inbound

Figure: The new created rule will appear in the rules list.

安装SharePoint Server CA 站点。

Figure: Run the PrerequisiteInstaller.exe

Figure: Run the setup.exe

Figure: Complete install all compomnents

Figure: Installation Process

Figure: Configure the Center Admin | configure DB

Figure: Create a new farm

Figure: Configure the configuration database

Figure: Specify farm security settings.

Figure: Configure the SharePoint CA WEB Application

Figure: Run the 10 steps wizard.

Figure: Install SharePoint Successfully.

Figure: Go to CA site | Configure everything myself.

第四步骤：让WFE加入到FARM

Figure: Install SharePoint

Figure: configure the admin site and db.

Figure: Connect to existing farm.

Figure: Join the farm.

Figure: farm info.

Figure: 9 steps of the wizard

Figure: configure successfully for the WFE.

Figure: Go CA site | Configure everything myself.

当用POWERSHELL, STSADM,或者是VS 2010部署SOLUTION的时候会出现这样的错误，试过用重启VS, APPLICATION POOL 但是结果仍然没有反应，于是想了下，之前系统更新了下，怀疑是刚刚装了SharePoint的一个更新， 于是在成功跑完CONFIGURATION  Wizard，然后再次部署SOLUTION这个时候就可以了。

当需要编辑SharePoint User的Work Email 以及 About Me 字段， 当点击用户| Edit User 的之后弹出的模态窗口只显示一个字段其不能够编辑。

最近因为在做OPS的工作，自然PS 少不了， 问题的原因就是SharePoint 的隐藏字段了。

   1:        $LaunchSite = Get-SPSite XXXXXX

   2:        $LaunchUserList = $LaunchSite.RootWeb.Lists | ?{$_.Title -eq "User Information List"} 

   3:        $WorkEmailField = $LaunchUserList.fields | ?{$_.Title -eq "Work e-mail"} 

   4:        $WorkEmailField.ReadOnlyField = $false 

   5:        $WorkEmailField.Update() 

   6:        $AboutMeField = $LaunchUserList.fields | ?{$_.Title -eq "About me"} 

   7:        $AboutMeField.ReadOnlyField = $false 

   8:        $AboutMeField.Update()

自动部署一个工作流的模板的时候，发现一个很奇怪的问题就是当更新CONENT TYPE工作流关联的时候 会出现异常 Column ows_ does not exist.  

   1: private void CreateContentTypeAssociation(SPWeb web, SPWorkflowTemplate tmpl, string listName, string contentTypeName, string wfName)

   2:          {

   3:              try

   4:              {

   5:                  SPList taskList = web.Lists["Workflow Tasks"];

   6:                  SPList historyList = web.Lists["Workflow History"];

   7:                  if (tmpl != null)

   8:                  {

   9:                      SPWorkflowAssociation association = SPWorkflowAssociation.CreateListContentTypeAssociation(tmpl, wfName, taskList, historyList);

  10:                      if (association != null)

  11:                      {

  12:   

  13:                          association.AllowManual = true;

  14:                          association.AutoStartCreate = true;

  15:                          association.ContentTypePushDown = true;

  16:   

  17:                          var associationListContentType = web.Lists[listName].ContentTypes[contentTypeName].WorkflowAssociations.GetAssociationByName(wfName, CultureInfo.CurrentCulture);

  18:                          //site.RootWeb.Lists["Institutions"].ContentTypes[0].WorkflowAssociations.Remove(asscociation);

  19:                          if (associationListContentType != null)

  20:                          {

  21:                              associationListContentType.Enabled = true;

  22:                            //  web.Lists[listName].WorkflowAssociations.Update(associationListContentType);

  23:                           

  24:                               

  25:                          }

  26:                          else

  27:                          {

  28:                              web.Lists[listName].ContentTypes[contentTypeName].WorkflowAssociations.Add(association);

  29:                          }

  30:                          

  31:                          web.Lists[listName].WorkflowAssociations.UpdateAssociationsToLatestVersion();

  32:                      }

  33:                  }

  34:              }

  35:              catch (Exception ex)

  36:              {

  37:                  Log("Create WF {0} Failed ({1}-{2})", wfName, ex.Message, ex.StackTrace);

  38:              }

  39:          }

发现Stefan的博客当中记录了此问题 http://bit.ly/kOniXy.

问题的原因是超了 LIST THRESHOLD 的瓶颈 Lookup Fields +  WF Status  + PersonGroups.

先删除已有的Workflow Association

到CA站点 Application Manager | General settings | Resource Throttling

然后给”List View Lookup Threshold”设置一个较大的值

IIS 重启 然后把工作流的关联重新关联下就行了.

遇到过$.trim() 去不掉空格的情况吗？ 如果去不掉空格的话可以把整个STRING 编码然后看看空格生成的是什么吧.

encodeURIComponent(str)
我遇到的情况是空格变成了 %C2%A0 而并非 20%。这样先将%C2%A0替换成 20% 然后在用decodeURLComponent(str) 最后用$.trim()就可以去掉空格了.

如果碰到这类问题的话需要将STATE Service在CA中配置下 或者通过PowerShell 来完成配置。

Figure: Form cannot be rendered.

Figure: Go to CA site | Run the configuration wizard | Check the State Service.

或者通过PS来完成

$serviceApp = New-SPStateServiceApplication –Name “State Service”

New-SPStateServiceDatabase -Name ”StateServiceDatabase” -ServiceApplication $serviceApp.

New-SPStateServiceApplicationProxy -Name ”State Service” -ServiceApplication $serviceApp -DefaultProxyGroup.

在FEATURE 激活事件中具体怎么样引用SPSite 对象呢， 有的时候我们会选择用SPContext.Current.Site 来完成引用，这样的写法的局限性就是和SPCONTEXT绑定在一起了， 在FEATURE激活的时候有一个对象就带有这么一个SPSite类型的属性了。  这样的话，我们在POWERSHELL中或者在站点中激活FEATURE都是可以获得到SPSITE对象了。

SPSite site = properties.Feature.Parent as SPSite;  //更通用的写法