Now that SharePoint 2010 Beta and Office 2010 Beta is available to download from MSDN, TechNet and Connect website, points to note (for self reference) from Jie Li’s Blog post.

  1. This beta is not supported and you CANNOT upgrade the installation to RTM when it’s released. This Beta should only be used for evaluation purpose.
  2. Windows Server 2008 R2 requires a hotfix which is not yet released to have the service applications running so I don’t recommend to use that now. Web Server Editions are not supported.

Before you install SharePoint 2010 Beta

  1. Install WCF FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (Windows Server 2008, Windows Server 2008 R2 – link not activated yet)
  2. On Windows Server 2008, additional files are needed.
    1. .Net Framework 3.5 SP1 .NET Framework 3.5 Service Pack 1 (Full Package) KB959209 KB967190
    2. PowerShell V2 RTM
  3. Prepare SQL Server 2005/2008 environment.
    1. SQL Server 2005 SP3 and CU3
    2. SQL Server 2008 SP1 and CU2
  4. Pre-requisites for SharePoint 2010 Beta
    1. Microsoft SQL Server 2008 Native Client:
    2. Microsoft "Geneva" Framework Runtime
    3. Microsoft Sync Framework Runtime v1.0 (x64)
    4. Microsoft Chart Controls for Microsoft .NET Framework 3.5
    5. Microsoft SQL Server 2008 Analysis Services ADOMD.NET


Install SharePoint 2010 Beta

  1. Setup the farm using complete farm installation.
  2. Go with configuration wizard to setup all service applications.
  3. Read Config Profile Synchronization to setup profile sync.


Additional Steps for SharePoint Installation on a DC

  1. If you are using SharePoint on DC, the following Windows PowerShell command would need to be run to enable Sandboxed Solutions.
    $acl = Get-Acl HKLM:\System\CurrentControlSet\Control\ComputerName
    $person = [System.Security.Principal.NTAccount]"Users"
    $access = [System.Security.AccessControl.RegistryRights]::FullControl
    $inheritance = [System.Security.AccessControl.InheritanceFlags]"ContainerInherit, ObjectInherit"
    $propagation = [System.Security.AccessControl.PropagationFlags]::None
    $type = [System.Security.AccessControl.AccessControlType]::Allow
    $rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type)
    Set-Acl HKLM:\System\CurrentControlSet\Control\ComputerName $acl


Additional Steps for Office Web Applications Installation on a DC

  1. If you are trying to use Office Web Applications on DC, then the following commands need to be run to make the services work.

    $e = Get-SPServiceApplication | where {$_.TypeName.Equals("Word Viewing Service Application")}
    $e.WordServerIsSandboxed = $false

    $p = Get-SPServiceApplication | where {$_.TypeName.Equals("PowerPoint Service Application")}
    $p.EnableSandboxedViewing = $false
    $p.EnableSandboxedEditing = $false

    In the server’s c:\windows\system32\inetsrv\config\applicationHost.config
    Add the line below in the end of the dynamicTypes.
    <add mimeType="application/zip" enabled="false" />



Enable Developer Dashboard

  1. Enable Developer Dashboard and turn to OnDemand for troubleshooting page performance issues.

    1. STSADM: stsadm -o setproperty -pn developer-dashboard -pv OnDemand

    2. Windows PowerShell:





All content for this post is from Jie Li’s blog post more as note to self, for installing SharePoint 2010 Beta and Office 2010 Beta.