Monday, February 22, 2010

Sharepoint 2010 Installation & Configuration - Part 4

<<Sharepoint 2010 Installation & Configuration - Part3
<<Sharepoint 2010 Installation & Configuration - Part2
<<Sharepoint 2010 Installation & Configuration - Part1

  1. Office Web Application

    • Install “Office Web Applications”
      • Enter your Product Key (BQDC3-93DMP-HGJB2-MFFV8-622QJ)
      • Click “I accept the terms…”
      • Click “Continue”
      • Click “Install Now”
      • When Setup finishes, a dialog box prompts you to complete the configuration of your server.
        • Run the Configuration Wizard only if the SharePoint Post-Setup Configuration Wizard (PSConfig) has not been run with the original SharePoint installation.
          • Select the check box, and then click Close to start PSConfig.
          • Click “Next”
          • Click “Yes”
          • Click “Next”
          • Click “Next”
          • Click “Finish”
      • Note :
        • Activate the Office Web Apps services immediately after you run setup. When you run Wcsetup.exe, Office Web Apps setup takes control of the Default open behavior for browser enabled documents setting for all document libraries. If a user clicks on a document in a library in SharePoint Foundation after Office Web Apps setup has been run, but before Office Web Apps services have been activated, the user can get a broken link when opening a document in a browser. We strongly recommend that you activate the Office Web Apps services and the Office Web Apps feature immediately after you run setup or that you disable the Default open option until Office Web Apps feature and services have been activated.
        • You must install Office Web Apps by running WCSetup.exe on every server that will host Office Web Apps in the server farm.
    • Activate Office Web APPs
      • if you have never run the Farm Configuration Wizard prior to installing Office Web Apps, running the Configuration Wizard with Office Web Apps installation will automatically activate the required service instances, service applications, and service application proxies.
      • If you have run configuration wizard but haven’t crated any web application then you can run the Farm Configuration Wizard again to activate owa.Alternatively(if you have already ran Farm configuration and don’t want to re run it) you can do it manually
        • Open Central Administration
        • Click “Application management”
        • Click “Manage service applications”
        • Click “New->PowerPoint Service Application”
        • For name, type “PowerPoint Service”
        • For pool name, type “PPTPool”
        • Click “OK”
        • Click New->Word Viewing Service”
        • For name, type “Word Viewing Service”
        • For application pool type “WordViewingPool”
        • Click “OK”
        • On the service applications page, click “PowerPoint Service Application”
        • Click “new site collection”
        • For title, type “PPT Broadcast”
        • For the url, in the dropdown select “sites”
        • For the url textbox, type “PPTBroadcast”
        • For template, click “Enterprise”, select “PowerPoint Broadcast Site”
        • For site collection admin, type “administrator”
        • Click “OK”
        • Click “System Settings”
        • Click “Manage services on server”
        • Click “Start” for:
          • PowerPoint Service
          • Word Viewing Service
      • Else you can manually activate the appropriate service instances, service applications, and proxies using powershell. Manually performing these steps by using Windows PowerShell is required only if you installed SharePoint and ran PSConfig on a stand-alone server before you installed Office Web Apps.Activation Steps:
        • To run scripts in Windows PowerShell, you must set the execution policy to run scripts unrestricted.
          • Click Start, point to All Programs, point to Windows PowerShell, right-click Windows PowerShell, and then click Run as administrator.
          • In the Windows PowerShell console, at the command prompt, type set-executionpolicy unrestricted, and then press ENTER.
        • A service instance provides the physical location for a service application. For each server you want to run the Office Web Apps service applications; you must start the service instances. Start the service instances by running the following script in Windows PowerShell:
          $machinesToActivate = @(“contosoapp1”,”contosoapp2”)
          $serviceInstanceNames = @(“Word Viewing Service”, “PowerPoint Service”,
          “Excel Calculation Services”)
          foreach ($machine in $machinesToActivate) {
          foreach ($serviceInstance in $serviceInstanceNames){
          $serviceID = $(Get-SPServiceInstance | where
          {$_.TypeName -match $serviceInstance} | where
          {$_.Server -match "SPServer Name="+$machine}).ID
          Start-SPServiceInstance -Identity $serviceID
        • After the service instances have been started, the service applications and the service application proxies which connect the Web front-ends to the service applications must be created. Create the service applications and the service application proxies by running the following script:
          $appPool = Get-SPIisWebServiceApplicationPool
          –Name “SharePoint Web Services Default”
          New-SPWordViewingServiceApplication –Name “WdView” –AppPool $appPool |
          New-SPWordViewingServiceApplicationProxy –Name “WdProxy”
          New-SPPowerPointServiceApplication –Name “PPT” –AppPool $appPool |
          New-SPPowerPointServiceApplicationProxy –Name “PPTProxy”
          New-SPExcelServiceApplication –Name “Excel”
          -SPIisWebApplicationPool $appPool |
        • Office Web Apps require that the Office Web Apps feature be activated on every site collection for which the Web apps will be available. Activate the Office Web Apps feature for all site collections by running the following script:
          $webAppsFeatureId = $(Get-SPFeature -limit all | where {$_.displayname
          -eq "OfficeWebApps"}).Id
          Get-SPSite –limit ALL |foreach{
          Enable-SPFeature $webAppsFeatureId –url $_.URL }
        • After activating Office Web Apps, the Default click feature in SharePoint Foundation will point to the Office Web Apps instead of the Office client application. You can override this functionality in SharePoint Foundation at the site collection and document library levels.
          • Site collection - This example disables the Default click setting at all site collections:
            $webAppsFeatureId = $(Get-SPFeature -limit all | where {$_.displayname
            -eq "OpenInClient"}).Id
            Get-SPSite –limit ALL |foreach{
            Enable-SPFeature $webAppsFeatureId –url $_.URL }
          • Document library - This example disables the Default click setting at all document libraries in site1:
            Get-SPWeb –site http://foo/sites/site1 |% {}{$_.Lists}{$_.Update()} |% {$_.DefaultItemOp>en = $false}
    • 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. Please also note that Office Web Application needs to follow the edit of config.xml to install on Windows 7), 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
      • #(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
      • In the server's c:\windows\system32\inetsrv\config\applicationHost.config
        Add the line below in the end of the dynamicTypes.

      • IISRESET
  2. 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:
  3. Enable Sandboxed Solutions - If you are using SharePoint on Domain Controller, 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

Sharepoint 2010 Installation & Configuration - Part5 >> coming soon

No comments: