Presentation is loading. Please wait.

Presentation is loading. Please wait.

A deployment experience overview Published: May 2007 Microsoft Office SharePoint Server 2007 Hosting.

Similar presentations


Presentation on theme: "A deployment experience overview Published: May 2007 Microsoft Office SharePoint Server 2007 Hosting."— Presentation transcript:

1 A deployment experience overview Published: May 2007 Microsoft Office SharePoint Server 2007 Hosting

2 Microsoft IT hosts all Microsoft internal sites, internal portals, and extranet data services. The team wanted to improve management of site content; provide effective search, auditing, and file- recovery tools; and reduce costs. Microsoft IT hosts all Microsoft internal sites, internal portals, and extranet data services. The team wanted to improve management of site content; provide effective search, auditing, and file- recovery tools; and reduce costs. Solution Overview Business Challenge Solution Results/Benefits Microsoft IT worked with the Microsoft Office SharePoint Server 2007 product team to test new features and functionality as they were developed. Microsoft IT is deploying SharePoint Server 2007 across the entire organization. Microsoft IT worked with the Microsoft Office SharePoint Server 2007 product team to test new features and functionality as they were developed. Microsoft IT is deploying SharePoint Server 2007 across the entire organization. 30% reduction in server hardware 30% reduction in server hardware 20–25 fewer person- hours per week and 75% fewer database touches due to user- accessible recycle bin 20–25 fewer person- hours per week and 75% fewer database touches due to user- accessible recycle bin Ability of content owners to manage their own sites efficiently Ability of content owners to manage their own sites efficiently Easier publishing Easier publishing

3 Products and Technology ● Windows Server 2003 ● Windows SharePoint Services 3.0 ● Office SharePoint Server 2007 ● 2007 Microsoft Office system ● Office SharePoint Designer 2007

4 Background on SharePoint Use at Microsoft ● SharePoint Server 2007 facilitates knowledge sharing and improves organizational effectiveness ● Thousands of Microsoft employees use SharePoint Server 2007 daily ● Search and People search are popular ● Extranet sites enable Microsoft partners to participate in the collaboration cycle ● Microsoft IT deployment included an upgrade, a new service offering, and a new server farm

5 Technologies That Support Office SharePoint Server 2007

6 Previous SharePoint Environment ● Minimal governance and IT management of customization ● Need for additional Web content management services ● Lack of comprehensive life-cycle management ● Difficulty protecting sensitive data ● Absence of recycle bin ● Continued use of MyDocs ● Lack of consistency in SharePoint adoption

7 Service Goal ● Web-based solution that supports collaboration, publishing, and dashboard functionality ● Scalability to meet the needs of individual, team, and enterprise audiences ● Availability to all users connected to the corporate network and facilitation of collaboration with third- party partners ● Security for content based on varying sensitivity levels

8 Supported Audiences ● Office dwellers ● 25,000 employees, 40% of full-time staff ● Campus nomads ● 25,000 employees, 40% of full-time staff ● Remote users ● 15,000 employees, 20% of full-time staff ● Business partners ● 100,000 users

9 Desired Features ● Ability to customize how team or project content is stored or shared ● Improved and discussion functionality ● Better programmability and an improved administration user interface ● More granular Information Rights Management ● Two-way synchronization for tasks, calendars, and discussions ● Better people functionality

10 Desired Features ● Improved search crawling and relevance ● Out-of-the-box integration between LOB data and services and portals ● Integration with business intelligence functions ● Improved workflow and document life-cycle management features ● A two-step recycle bin available to end users ● Offline content support ● A clear difference between team and portal sites

11 Business Benefits of the Move to Office SharePoint Server 2007 ● Easier publishing ● Improved site-level management ● Business data integration ● Fewer user requests to Microsoft IT for document recovery ● Real-time access to Excel Services ● Less coding

12 Business Benefits of the Move to Office SharePoint Server 2007 ● Automatic synchronization ● Improved content policies and regulatory compliance ● Scheduled content approval and deployment ● Improved search ● Lower costs ● Server consolidation

13 MACS Team Responsibilities

14 Solution Design: Server Farms

15 Solution Design: Distribution of Users

16 Architecture ● Portals and team sites are now hosted together ● Infrastructure provides an SSP farm in each region to provide services to child farms ● Reasons for a dedicated SSP model include: ● Consolidation of servers ● Clarity of administrative roles ● Performance ● Security ● Database throughput requirements

17 Overview of SSP Model

18 ● Child farms host sites and portals ● Communication between child farms and SSPs occurs through Web service calls and direct database connections ● Excel Services must run on a local server ● Solution relies on a 64-bit SQL Server 2005 infrastructure

19 Overview of SSP Model ● To accommodate customer requests, Microsoft IT defined three tiers of service for the solution: ● Platinum tier ● Gold tier ● Silver tier ● User-provisioned model for the majority of the organization’s intranet needs enables Microsoft IT to focus on maintaining the higher-level tiers of support for critical services

20 Overview of Deployment Process ● Choosing an upgrade ● Planning ● Scheduling ● Preparing the environment ● Performing the upgrade ● Communication ● Post-upgrade support

21 Choosing an Upgrade Method ● In-place upgrade ● All SharePoint sites upgraded at once ● Gradual upgrade ● Site collections upgraded individually ● Microsoft IT method for team sites ● Database attach ● In-place upgrade on a copy of the content ● Microsoft IT method in most cases

22 Upgrade Performance Content migration Time Database attach for Windows SharePoint Services 3.0 shared services 40–60 GB per hour Gradual upgrade for Windows SharePoint Services 3.0 team sites 15 GB per hour Database attach for Office SharePoint Server 2007 personal sites 3–6 seconds per site Database attach for Office SharePoint Server 2007 shared services Less than 10 minutes per server, but some re-indexing must occur after the upgrade because it does not bring across the search catalogs

23 Planning ● Planning was essential for a successful enterprise-wide upgrade ● Testing helped identify potential problems, verify fixes, and validate settings and configurations ● Dry runs helped identify orphan and problematic sites before an outage ● Planning phase yielded valuable lessons learned

24 Scheduling ● Upgrade schedule had to minimize impact on day-to-day business ● Detailed schedules had to allow for flexibility in dealing with problems ● Microsoft IT had to allow for backups during the upgrade schedule in some instances

25 Preparing the Environment ● Optimizing the infrastructure made upgrades easier to perform and helped maximize hardware consolidation ● Microsoft IT: ● Performed a thorough audit ● Balanced content loads among databases ● Merged and split databases ● Consolidated server farms ● Used the prescan tool

26 Performing the Upgrade ● From an operational standpoint, Microsoft IT discovered that these were useful: ● Redundant skill sets among team members ● Consistently labeled logs of the entire process ● Microsoft IT did not force reghosting ● Microsoft IT set databases, temporary databases, and log files to autogrow

27 Communication ● Communication was essential because the upgrade affected nearly everyone at Microsoft ● Communication was a learning process ● Established triage process helped Microsoft IT track and assign open issues

28 Post-upgrade Support ● Preparations during upgrade made addressing post-upgrade issues easier ● Three teams monitor the SharePoint Server 2007 environment by using Microsoft Operations Manager 2006 and add-in packs ● Microsoft IT uses an SLA to prioritize support issues

29 Deployment Results SharePoint Portal Server 2003 service offering CountSize SharePoint Server 2007 service offering CountSize SharePoint Portal Server portals 340 GB SharePoint Server portals 1.07 terabytes Windows SharePoint Services 2.0 team sites 84,424 site collections 277,975 sites 5.71 terabytes Windows SharePoint Services 2.0 team sites Windows SharePoint Services 3.0 team sites SharePoint Server 2007 sites 52,310 site collections 185,781 sites 9.35 terabytes Personal sites 52,826 site collections 86,056 sites 462 GB Personal sites 62,542 site collections 101,366 sites 1.26 terabytes Extranet sites 7,355 site collections 12,656 sites 410 GB Extranet sites 9,558 site collections 24,781 sites 1.49 terabytes

30 Performance File size MPL User compliance 1 MB 10 seconds 80% 5 MB 35 seconds 96%

31 Services ● Performance goal for crawling is 20 documents per second on average ● Average response time to search requests is two seconds per query ● Most Silver-level farms have dedicated Excel Services servers that are part of the child farm ● Microsoft IT is implementing Business Data Catalog conservatively to balance crawl impact and server load with the business benefit

32 Services ● Full Active Directory profile import happens once a week; incremental imports happen once a day ● Microsoft IT added custom code to replicate user changes to personal sites worldwide in seconds ● InfoPath 2007 is a child farm feature ● Microsoft IT plans include implementing technologies that will improve services and enable more testing

33 Lessons Learned ● A process that encourages efficient decisions about exceptions and open issues will help keep the project on schedule ● Upgrading is an excellent opportunity to organize and solidify the collaboration infrastructure ● Upgrading customizations and Web Parts so that they function properly can be time-consuming ● Performing dry runs helps identify and resolve key issues

34 Lessons Learned ● Backups should be performed and validated before upgrades begin ● Roles and responsibilities should be defined beforehand ● Required language packs should be identified and installed beforehand ● End users benefit from a pre-defined support and escalation policy

35 Best Practices for Initial Activities ● Thoroughly audit products and platforms that the upgrade may affect ● Optimize and clean up current environments ● Make sure that level settings are consistent ● Identify and install missing language packs ● Document initial activities and discoveries made during the process

36 Best Practices for Planning ● Use the prescan tool in advance ● Account for unexpected events in the schedule ● Have a contingency plan for roadblocks ● Base database upgrades on free space ● Rank exceptions ● Frequently update the calendar ● Perform backups beforehand ● Schedule time and resources for testing ● Schedule upgrades based on the number of sites

37 Best Practices for Planning ● Communicate restrictions beforehand ● Solidify information before communicating ● Avoid committing to specific dates where possible ● Use images to instruct non-technical personnel ● Notify site owners/administrators often ● Implement a post-upgrade plan ● Define the support process ● Invest adequately in user training ● Determine whether to reghost

38 Best Practices for the Upgrade Process ● Perform a dry run whenever feasible ● Do not avoid testing because of limited hardware resources ● Increase databases to appropriate sizes beforehand ● Watch for problems caused by full-text search ● Maintain a list of which sites have been upgraded ● Move exception sites to a new content database via Stsadm.exe

39 Best Practices for the Upgrade Process ● Bounce SQL Server computers between SQL Server instances ● Maintain a copy of the previous environment ● Do not finalize the upgrade until the upgrade is finished ● Allow only one administrator at a time to change the configuration database

40 Best Practices for Validation ● Document the entire process in as much detail as possible ● Develop custom user guides ● Lock previous site versions after the upgrade

41 Conclusion ● SharePoint Server 2007 helps streamline business processes and make information easy to share ● Microsoft upgrade efforts included making the infrastructure more simple, more robust, and less expensive ● Meticulous planning minimized the inconvenience to end users during the upgrade

42 For More Information ● Additional content on Microsoft IT deployments and best practices can be found on ● Microsoft IT Showcase Webcasts ebcasts ebcasts ebcasts ● Microsoft TechNet

43 This document is provided for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. Microsoft, Active Directory, Excel, Groove, InfoPath, Internet Explorer, Outlook, PerformancePoint, SharePoint, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.


Download ppt "A deployment experience overview Published: May 2007 Microsoft Office SharePoint Server 2007 Hosting."

Similar presentations


Ads by Google