Jie Li, Technical Product Manager, SharePoint at Microsoft wrote the following Article about how to install the 2010 public beta
Installation Notice for SharePoint 2010 Public Beta
[11/17 - updated with some details about installation errors]
Since SharePoint 2010 has been made available for MSDN/TechNet subscriber now, here’re some steps you would like to follow to get a successful installation. But keep in mind: 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.
- Read hardware and software requirement article on TechNet.
- Prepare a Windows Server 2008 x64 machine with 8GB memory. 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.
- Get your AD ready. Create a new account for services, for example contoso\sp_admin.
1. Open Active Directory Users and Computers
2. Right click domain and select “Delegate Control”
3. Click Next
4. Click Add
5. Enter object name (i.e. contoso\sp_admin)
6. Click Ok
7. Click Next
8. Select “Create a custom task to delegate”
9. Click Next
10. Check Replicating directory changes”
11. Click Next
12. Click Finish - 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) . Please note the 2008 fix also applies to Vista, while the 2008 R2 fix also applies to Windows 7.
If you don't have this fix installed, you will get "Unrecognized attribute 'allowInsecureTransport'" error in ULS log. And most of the service applications will not run properly. - Prepare SQL Server 2005/2008 envoriment. If it is on a different box, don't forget Windows Firewall settings. For SQL Server on Windows 2008/R2, you can use the script in KB968872 to open all necessary ports.
- SQL Server 2005 SP3 and CU3
- SQL Server 2008 SP1 and CU2
- Run Pre-Requisition Installer to download and install required components. You can also download them seperately. I listed all download links in SharePoint 2010 Pre-Requisites Download Links. The links are also available in requirement article, or by clicking “Learn more about…” in the installer.
- Setup the farm using complete farm installation. Standalone installation is not recommended, and should be only used when you want to install SharePoint 2010 on Windows 7/Vista for dev purpose.
- Go with configuration wizard to setup all service applications. Use the user you created in step 3 as SharePoint Managed Account for services and web applications.
- Read Config Profile Synchronization to setup profile sync. Dave Pae is going to post complete steps for Profile Sync on SharePoint Team Blog.
- 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)
$acl.AddAccessRule($rule)
Set-Acl HKLM:\System\CurrentControlSet\Control\ComputerName $acl - If you are trying to use Office Web Applications on DC(Office Web Application need to be installed seperately, like a language pack or an update), then the following commands need to be run to make the services work. Please note that in different languages, Service Application names could be localized. You can find them out by Get-SPServiceApplications, and then change the names in the script as necessary.
$e = Get-SPServiceApplication where {$_.TypeName.Equals("Word Viewing Service Application")}
$e.WordServerIsSandboxed = $false
$e.WordServerIsSandboxed
$p = Get-SPServiceApplication where {$_.TypeName.Equals("PowerPoint Service Application")}
$p.EnableSandboxedViewing = $false
$p.EnableSandboxedEditing = $false
$p.EnableSandboxedViewing
$p.EnableSandboxedEditing
In the server's c:\windows\system32\inetsrv\config\applicationHost.config
Add the line below in the end of the dynamicTypes.
IISRESET
- Enable Developer Dashboard and turn to OnDemand for troubleshooting page performance issues. It can be done by STSADM or SharePoint 2010 Management Shell (Windows PowerShell).
- STSADM: stsadm -o setproperty -pn developer-dashboard -pv OnDemand
- Windows PowerShell:
$svc=[Microsoft.SharePoint.Administration.SPWebService]::ContentService
$ddsetting=$svc.DeveloperDashboardSettings
$ddsetting.DisplayLevel=[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand
$ddsetting.Update()
