Levels of browser support
Web browser support is divided into two levels: level 1 and level 2. Although administrative
tasks on SharePoint sites are optimized for level 1 browsers, SharePoint Server 2010 also
provides support for other browsers that are frequently used. To ensure that you have complete
access to all functionality, we recommend that you use a level 1 browser for administrative tasks.
Level 1 Web browsers
Level 1 Web browsers take advantage of advanced features that are provided by ActiveX
controls and provide the most complete user experience. Level 1 browsers offer full functionality
on all SharePoint sites, including the SharePoint Central Administration Web site. Level 1
browsers include those in the following table.
Operating System Browser
Windows XP, Windows Vista, Windows Server Internet Explorer 7, Internet Explorer 8 (32-
2003, Windows Server 2008 bit), Mozilla Firefox 3.5
Windows 7, Windows Server 2008 R2 Internet Explorer 8 (32-bit), Firefox 3.5
Note:
Some ActiveX features, such as list Datasheet view and the control that displays user presence
information, do not work in Mozilla Firefox 3.5.
Level 2 Web browsers
Level 2 Web browsers provide basic functionality so that users can both read and write in
SharePoint sites and perform basic site administration. However, because ActiveX controls are
supported only in level 1 browsers and functionality is different between browsers, level 2
browsers might provide a different user experience than level 1 browsers provide. Level 2
browsers include those in the following table.
Operating System Browser
Apple Safari 4. x, Mozilla Firefox
Apple Mac OS X Snow Leopard
3.5
Windows XP, Windows Vista, Windows Server 2003, Internet Explorer 7, Internet
Windows Server 2008 Explorer 8 (64-bit)
Windows 7, Windows Server 2008 R2 Internet Explorer 8 (64-bit)
UNIX/Linux 8.1 Firefox 3.5
Browser compatibility for published sites
For published sites, the Web Content Management features built into SharePoint Server 2010
provide a deep level of control over the markup and styling of the reader experience. Page
designers can use these features to help ensure that the pages they design are compatible with
additional browsers, including Internet Explorer 6, for viewing content. However, it is the page
designer's responsibility to create the page to target the browsers they want to support.
A standards-based browser, such as Internet Explorer 8 or Firefox 3.x, is required to author
content.
Logical architecture components (SharePoint Server 2010)
- Know what your sharing and isolation goals are. Evaluate the tradeoffs for each choice.
Server farms – physical isolation
Service applications – share & isolate services
Web Application
IIS Web site
Extend up to 4 times.
Separate content available to anonymous users & auth user
Isolate users
Enforce permissions through policies
Optimize database performance
Optimize manageability
Zone
Logical paths of gain access to same web application
Up to 5 per web application (default, intranet, internet, custom or extranet)
Each zone represents different site in IIS
Content Database
Up to 100 content database per web application
Establish target size for content database with size-warning thresholds
Site Collection
Set of web sites have same owner & share administration settings
1 top-level site & multiple subsite
10,000 site collections per content database
A site collection CANNOT span multiple database
Design consistent URLs across organization
Create logical division of content
Site
Consists related web pages & other items
5,000 sites per site collection
Server Farm
Web Web
Application Application
Site Site Site
Collection Collection Collection
Site Site Site Site Site
Plan for Backup & Recovery
Business Requirement
1. Recovery point objective (RPO) – max time between last backup & any potential failure point.
Amount of data the business can afford to lose.
2. Recovery time objective (RTO) – max time a data recovery process will take. Amount of time the
business can afford for site to be unavailable.
3. Recovery level objective (RLO) – whether you must be able to recover the entire farm, web
application, site collection, site, list or library, or item.
Component SharePoint Microsoft SQL System Center File
backup Server 2008 with Data Protection system
Service Pack 1 (SP1) Manager backup
and Cumulative (DPM) 2010
Update 2
Farm Yes
Search Yes
Web application Yes
Content databases Yes Yes Yes
Site collection Yes1, 2 Yes1, 2 Yes
Site Yes2 Yes2
Document library Yes
List item or document Yes2 Yes2
Content stored in Yes3 Yes3 Yes3
remote BLOB stores
Customizations Yes2 Yes2
deployed as solution
packages
Changes to Web.config Yes2 Yes2 Yes4
made by using Central
Administration or an
API
Configuration settings Yes2 Yes2
(SharePoint)
Customizations not Yes
deployed as solution
packages
Changes to Web.config Yes4
not made by using
Central administration
or an API
IIS configurations not Yes5
set through SharePoint
1Farm-level and database-level backup and restore can be used for site collection recovery if a
single site collection is stored in a database.
2Farm-level and database-level backups can be used with SharePoint unattached database
recovery to restore site collections, sites, items, and configurations.
3Content stored in remote BLOB stores is backed up and restored with other content, as long as
the Remote BLOB Storage (RBS) provider in use has this capability.
4Changes to Web.config can be backed up by using file system backup from DPM 2010.
5IIS configurations can be recovered by using a bare metal backup from DPM 2010.
Proposed Logical architectures
Server Farm 1 Server Farm 2
Web Web
Application 1 Application 2
Staging Site Staging Site Production Site Production Site
Collection Collection Collection Collection
(FoMD) (Departmental) (FoMD) (Departmental)
Production Production
Staging Site Staging Site
Internet Site Internet Site
(FoMD) (Departmental)
(FoMD) (Departmental)
Figure 1 - Production
Server Farm
Web Web
Application 1 Application 2
Staging Site Production Site
Collection Collection
(Departmental) (Departmental)
Production
Staging Site
Internet Site
(Departmental)
(Departmental)
Figure 2 - Testing
Separate web application for Staging & Production - Security, Backup
Separate site collection for main Faculty website & other sites – Security, Backup (separate content database), Master
page implementation
Server Farm 1 Server Farm 2
Web Web
Application 1 Application 2
Authoring site Authoring Site Staging Site Staging Site Production Site Production Site
Collection collection Collection Collection Collection Collection
(FoMD) (Departmental) (FoMD) (Departmental) (FoMD) (Departmental)
Production Production
Authoring Site Authoring Site Staging Site Staging Site
Internet Site Internet Site
(FoMD) (Departmental) (FoMD) (Departmental)
(FoMD) (Departmental)
Servers:
1. Med-SP2010-Test (Farm)
o Processor: 64-bit, 4-core, 2.5GHz per core
o RAM: 4GB
o C: Drive: 80GB
o D: Drive: 20GB
o OS: Window Server 2008 R2 (64 bit)
o Web Server (IIS) Role
o Application Server Role
o Microsoft .NET framework version 3.5 SP1
(http://go.microsoft.com/fwlink/?LinkID=131037)
o Hot fix for .NET framework 3.5 SP1 (http://support.microsoft.com/kb/976462,
http://go.microsoft.com/fwlink/?LinkID=166231)
o Microsoft “Geneva” framework (http://go.microsoft.com/fwlink/?LinkID=165752)
o Microsoft Sync framework runtime v1.0 (x64)
(http://go.microsoft.com/fwlink/?LinkID=141237&ccicid=0x409)
o Microsoft Filter pack 2.0 (http://go.microsoft.com/fwlink/?LinkID=166504)
o Microsoft Chart controls for Microsoft .NET framework 3.5
(http://go.microsoft.com/fwlink/?LinkID=141512)
o Windows PowerShell 2.0 CTP3 (remove Powershell 1.0 before installation)
(http://go.microsoft.com/fwlink/?LinkID=165758)
o SQL Server 2008 Native Client (http://go.microsoft.com/fwlink/?LinkID=166505)
o Microsoft SQL Server 2008 Analysis Services (ADOMD.NET)
(http://go.microsoft.com/fwlink/?LinkID=130651)
o ADO.NET Data Services v1.5 CTP2 (http://go.microsoft.com/fwlink/?LinkID=159780)
2. Med-SP2010-SQL
o Processor: 64-bit, 4-core, 2.0GHz per core
o RAM: 4GB
o C: Drive: 40GB
o D: Drive: 20GB
o E: Drive: 20GB
o OS: Window Server 2008 R2 (64 bit) (* with Window Server 2008 R2 FIX :
http://go.microsoft.com/fwlink/?LinkID=166231)
o SQL Server 2008 with SP1 & Cumulative update package 2
(http://go.microsoft.com/fwlink/?LinkID=165962)
Publishing Portal
o A starter site hierarchy that you can use for an Internet site or a large intranet
portal. You can use distinctive branding to customize this site. It includes a home
page, a sample press releases site, a Search Center, and a logon page. Typically,
this site has many more readers than contributors, and it is used to publish the
Web pages by using approval workflows.
o This site enables content approval workflows, by default, for a more formal and
controlled publishing process. It also restricts the rights of anonymous users so
that they can see only content pages, and they cannot see SharePoint Server
2010application pages.
o This template is available only at the site collection level.
Publishing Site with Workflow
o A site for publishing Web pages on a schedule by using approval workflows. It
includes document and image libraries for storing Web publishing assets. By
default, only sites that have this template can be created under this site.
o This template is available only at the site level when the Publishing Portal
template is used to create the top-level site.