1 / 22

System requirements

System requirements. Chris Gideon Architect Microsoft. Hardware Requirements. Web & Application Servers | Single Server Farms. Load balanced or routed requests. Minimum Hardware Requirements Processor: 64-bit, 4 cores RAM: Single server installation – 24GB

jerom
Download Presentation

System requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. System requirements Chris Gideon Architect Microsoft

  2. Hardware Requirements

  3. Web & Application Servers | Single Server Farms Load balanced or routed requests Minimum Hardware Requirements Processor: 64-bit, 4 cores RAM: Single server installation – 24GB WFE or app server in a three-tier farm – 12GB Hard disk: 80 GB free for system drive Maintain 2x free space as available RAM Web tier Web servers with query component Application tier • Application servers with: • Central Administration • Search administration component • Crawl component Database tier • Database server with: • Central Administration configuration and contentdatabases • Content databases • Search administration database • Crawl database • Property database

  4. Database Servers Load balanced or routed requests Minimum Hardware Requirements Processor: 64-bit, 4 cores for “small” deployments 64-bit, 8 cores for “medium” deployments RAM: 8 GB for “small” deployments 16 GB for “medium” deployments Overall RAM depends on usage models and data size Hard disk: 80 GB free for system drive SP Data Storage dependent on corpus size, performance requirements, etc. Web tier Web servers with query component Application tier • Application servers with: • Central Administration • Search administration component • Crawl component Database tier • Database server with: • Central Administration configuration and contentdatabases • Content databases • Search administration database • Crawl database • Property database

  5. Software Requirements Dependencies and prerequisites

  6. Web & Application Servers Minimum Software Requirements • 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise or Data Center • Windows Server 2012 Standard or Datacenter Preparation tool installs the following prerequisites:

  7. Database ServersMinimum Software Requirements 64-bit edition of Microsoft SQL Server 2008 R2 Service Pack 1 OR Microsoft SQL Server 2012 For BI scenarios SQL 2012 SP1 is required 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Data Center OR Windows Server 2012 Standard or Datacenter

  8. Client side software requirements Compatibility and Support Considerations

  9. Office Client Minimum Software Requirements Office 2010 or Office 2013 For full offline and integrated experience SharePoint Designer SharePoint Designer 2010 only works for 2010 mode sites SharePoint Designer 2013 works for both 2010 and 2013 mode sites SharePoint Workspace SharePoint Workspace 2010 work for 2010 mode (“14 mode”) sites 2013 introduces new SkyDrive Pro to replace this product – part of the Office client installation

  10. Browser Support Matrix

  11. WCM features in 2013 provide deep level of control over markup and styling Designers can target browser compatibility based on user agents • Includes different mobile devices IE6 or standards based (IE 8+, Firefox 5.x, etc.) Design Manager for easy mark up editing and modification for different browsers Browser Compatibility for Publishing Sites

  12. Setup considerations Installation & Setup

  13. Install The Bits – Follow the Basic Steps • Plan and Prepare; Verify hardware and software requirements • Install the required software updates on all farm servers • Install the SharePoint 2013 prerequisites on servers in the application and Web tiers • Install SharePoint 2013 on the application server and the Web servers • Create and configure the SharePoint farm • Provision service applications as needed • Complete post-deployment tasks as required

  14. Prepare the Servers • SharePoint Preparation Tool • Checks for presence of prerequisites • Installs and configures required packages • Requires internet connection to pull down missing prerequisites otherwise will pinpoint missing prerequisites • Can be run w/o internet connection to check for missing prerequisites • Public Updates and Hotfix Packages • Update WFE & App servers as appropriate • Ensure SQL Updates installed • Ensure all SharePoint servers are at the same patch level

  15. Running the Preparation Tool • Run on Web and Application servers • Ensure you are logged on as local admin • If running from bits on a file system, locate and run prerequisiteinstaller.exe from the SharePoint 2013 bits folder • Otherwise, if you install from bootable image click Install software prerequisites • May require several server reboot – however preparation tool will continue to run after restart • Click Finish on the Installation Complete page

  16. SharePoint 2013 Preparation Tool

  17. SharePoint 2013 Preparation Tool

  18. Install prerequisites from a network share(alternative) • Verify that you have an accurate list of the required software and download them • Create a shared folder on a computer that can be accessed by the servers on which the prerequisites will be installed • Copy the files that you downloaded from the Internet to the shared folder • Execute PrerequisiteInstaller from command prompt with appropriate switches • Full list of switches - PrerequisiteInstaller.exe /? • Example - PrerequisiteInstaller.exe /SQLNCli: "\\o15-fi-admin\SP_prereqs\sqlncli.msi" /IDFX: "\\o15-fi-admin\SP_prereqs\Windows6.1-KB974405-x64.msu"

  19. Additional KB’s to install • After completing Preparation tool you must also install following KBs • KB 2554876 - The SharePoint parsing process crashes (for Windows 2008 R2 SP1) • KB 2708075 - FIX: IIS 7.5 configurations are not updated when you use the ServerManager class to commit configuration changes (for Windows 2008 R2 SP1) • KB 2472264 - You cannot customize some TCP configurations by using the netsh command (for Windows 2008 R2 SP1) • KB2759112 Hotfix: ASP.NET race condition in .NET 4.5 RTM (for Windows 2008 R2 SP1) • KB2765317 Hotfix: ASP.NET race condition in .NET 4.5 RTM (for Windows 2012) • Install these KB’s before actually running the Setup wizard for SharePoint installation

  20. Installing SharePoint 2013 • Login as local administrator using specific Setup account • Installation steps similar to SharePoint 2010 • Install on all SharePoint WFE & Application servers • Run Configuration Wizard when setup is finished on all servers • Configure diagnostic logging/usage health data/etc. • Configure service applications and other required services • Farm configuration wizard exists like in 2010 for automating this in developer, test and sandbox environments • PowerShell and manual creation of service applications in production environments • Create Web apps, site collections/sites, based on requirements

  21. Installation of language packs • Download language pack from Internet • Login using Setup account which you used for initial installation of SharePoint • Run setup for language pack • Run SharePoint 2013 Configuration Wizard • Repeat steps on each server of the farm

  22. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related