SPS 2010 Public Beta Install and Setup Notes

Ok, all in one, these are the order of steps to be done when you want to install and start successfully the Public beta of SharePoint 2010!

1. Read “Determine Hardware and Software requirements”


2. Check the preliminary requirements for software and patches as described here: SPS 2010 Setup Requirements


3. Prepare your Server 2008 accordingly with all patches and service packs as needed
   
          If you want to run all on one machine, you should have at least 8GB of RAM. 
          (I have prepared my setup with two machines, one for SharePoint with all roles and services, 4GB RAM, two cores and aother one with seperate SQL 2008, 4GB RAM, two cores)
   
   


4. Prepare your AD:
   – create an account for the services, i.e.  domainsps_svc
   – Open Active directory “users and Computers”
   – right click “Domain” and select “Delegate Control”
   – Click “Next”, “Add”
   – type in the object name, i.e. domainsps_svc
   – Click “Ok” and “Next”
   – Check the “Replicating directory changes” box
   – Click “Next” and “Finish”
   Create additional accounts as needed like Application Pool account, Search service account, farm administrator account etc.
   It is not recommended to use the farm admin account as well for the service applications or the application pool identity!
   
   


5. Ensure that you have all patches and fixes installed as described in SPS 2010 Setup Requirements
   


6. Setup the farm with “Complete farm installation”. A standalone setup is only recommended for test- and Dev purposes like running it on Worksation (Win 7/Vista)
   You should now see the config wizard similar to the MOSS 2007 Setup. Just follow it, enter the product key and all other stuff when prompted, connect to SQL server etc.
   same like in MOSS 2007.
   


7. Once, the wizard finished, the new “Central Admin page” should start and you’ll be prompted for participating in CEIP (Customer experience Improvement Program)
    
   


8. Now the Central Admin page shows up with this screen and for first use and test purposes you should choose the “Walk me through the settings using this Wizard”
   
   


9. You will be asked to specify a new managed account, or use the current one. Default options here will configure all Service Applications except Lotus Notes.
   Click Next to start the farm config wizard
   


10. On this screen you have to type in either an existing account as prepared on step 4 above or create a new one. All services will be configured with this account!
     
    This will take some time, so here you could go for a coffee 😉
    
    


11. Once complete, you’ll be prompted to create a new site collection. The farm wizard already created a default web application on port 80.
    
    


12. After all finishing with no errors, you should get that screen:
    
     


13. Click finish and your farm has been done for the moment. You should have a ready central admin page and a web app and site on port 80  😉
     
    
      

Cheats and Tricks:

A.)  If you are using SharePoint on a DC, the following Windows PowerShell command would need to be run to enable Sandboxed Solutions:

   1: $acl = Get-Acl HKLM:SystemCurrentControlSetControlComputerName 

   2: $person = [System.Security.Principal.NTAccount]“Users” 

   3: $access = [System.Security.AccessControl.RegistryRights]::FullControl 

   4: $inheritance = [System.Security.AccessControl.InheritanceFlags]“ContainerInherit, ObjectInherit” 

   5: $propagation = [System.Security.AccessControl.PropagationFlags]::None 

   6: $type = [System.Security.AccessControl.AccessControlType]::Allow 

   7: $rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type) 

   8: $acl.AddAccessRule($rule) 

   9: Set-Acl HKLM:SystemCurrentControlSetControlComputerName $acl 

—————————————————-

B.)  If you are trying to use Office Web Applications on DC 

Note:
Office Web Application need to be installed seperately  and needs to follow the same edit of config.xml as to be installed on client OS.

Then the following commands has to run to get the services working. 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

#(Please use the below script for PowerPointServiceApplication – You need to enter “Y” for the answer of each cmd)

Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedViewing $false

Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedEditing $false

On server, go to  c:windowssystem32inetsrvconfigapplicationHost.config
Add the line at the end of the dynamicTypes:   <add mimeType=”application/zip” enabled=”false” />

Do an IISRESET and it should work now.

—————————————————-

C.)  Enable Developer Dashboard to turn on OnDemand troubleshooting, you can do this via STSADM or PowerShell:

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

2. Windows PowerShell:

$svc=[Microsoft.SharePoint.Administration.SPWebService]::ContentService 

$ddsetting=$svc.DeveloperDashboardSettings 

$ddsetting.DisplayLevel=[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand 

$ddsetting.Update()

—————————————————-

For further information and known issues, please review the site “Microsoft Office Servers Beta 2 Known Issues/ReadMe“

More on this series of 2010 Guides you’ll find here with a complete list of the related posts on SharePoint 2010 Resource Guide topics.

Have fun and happy SharePointing 😉

Steve Chen,
Sr. Support Engineer, SharePoint