SharePoint 2010 upgrades!
0 likes355 views
Eric VanRoy discusses his experience upgrading SharePoint environments from 2003 to 2007 to 2010. He outlines several key lessons learned including preparing for database schema changes, updating custom code to support claims authentication, replacing deprecated functionality, and thoroughly testing the upgraded environment. The document emphasizes planning and testing at each stage of the upgrade process to minimize issues.
SharePoint 2010 upgrades!
- 1. SharePoint 2010 Upgrades! “Notes From The Field”
- 2. Introduction • Eric VanRoy – Skyline Technologies • Senior Portal Systems Engineer – 8 years of SharePoint • SharePoint 2003, 2007 and 2010 – Upgrades completed • 2003-2007 • 2007-2010 • 2003 – 2007 – 2010 – evanroy@skylinetechnologies.com
- 3. Upgrade Options • InPlace – This is where the 2010 setup is run directly on the existing SharePoint 2007 server – All prerequisite must be met – Seldom used
- 4. Upgrade Options –Database Attach • Process – Create new SharePoint 2010 farm – Dry Run to the new farm – “Fix” problems – Real migration of content • Benefits – Side by side, limits the downtime – Allows for fail back – Allows for restructure – Allows for testing of upgrade – Allows for user acceptance
- 5. Database lessons • Database Schema not valid – Upgrade from 2003 to 2007 to 2010 – Database Diagram clicked – Indexes created • Space needed – Unexpected growth depending on functionality • Attaching the database will require using Powershell or stsadm
- 6. Custom Code lessons • Authentication providers – Forms Based requires Claims based Authentication – Custom Authentication for Classic mode will not run as Claims based, requires code updates • Custom Controls/Third party software – Out of box solutions to replace functionality – 64 bit versus 32 bit compile
- 7. Support lessons • SQL supported versions – Ensure SQL server meets minimum • My Sites – Should be on Separate URL • Accounts used – Should use least privileged accounts – Check the security on content databases
- 8. User Interface lessons • Fab 40 no longer exists – No upgraded version – Content database will be approximately double original size • Site Templates – STP files are no longer functional • Customized interfaces – Almost all site with look and feel customizations will need to be redone. • Plan for training and UI changes
- 9. Structure Change lessons • Services configurations – New Structure will create a number of services, databases, etc. • Database security – Not all services set the security correctly on content databases. • Browser file handling – Needs to be set to permissive for to allow for files to “open” direction from web without saving first
- 10. How to Prevent - Pre upgrade • PLAN • Preupgrade Check • Test-SPContentDatabase on new servers • Clean up in 2007 • Understand the new features/services
- 11. How to Prevent -During upgrade • PLAN • Monitor servers – Disk space – Log files • Database upgrade can be run again
- 12. How to Prevent - Post Upgrade • PLAN • Review logs • Test • Run visual Upgrade • Test
- 13. Resources • Upgrade Planning - http://go.microsoft.com/fwlink/?LinkId=167099 • Keys to a Succesful upgrade – Joel Oleson http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=288 • Cleaning up Orphan Sites – Joel Oleson http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=291
- 14. Questions? • Eric VanRoy evanroy@skylinetechnologies.com Twitter @evanroy
Editor's Notes
- #4: Must have 64 bit hardware, Must be on Window 2006 serverMust be SQL 2008 or 2005 SP3 64bit.I have only used “in place” once in a test situation Was an out of the box site and it failed. – used Beta version.
- #5: Must have 64 bit hardware, Must be on Window 2008 serverMust be SQL 2008 or 2005 SP3 64bit.I have only used “in place” once in a test situation Was an out of the box site and it failed. – used Beta version.I normally recommend Database attach method. Either Method requires PLANNING…..
- #6: 2003 to 2007 – the database structure completely changed. 2007 to 2010 database gets flagged as extra tables exist.The preupgrade check will flag this and help you to find the error. log file is very helpful. Normally will tell you what the issue is. For example “EXTRA Table” with the table nameAs far as the Space needed. Items like FAB 40 will affect database upgrade size. Keep in mind that the size needed is about 4 times the data in original depending on “how” data was moved. Database Backup file is 1x, the restore to the new DB server is 2x, SQL temp database is 3x and allowing for growth during upgradde is 4x. This means that a 4 Gig database should be planned for 16G during the process. After completed I would plan for 8Gig. Attach can not upgrade through UI because of timeouts
- #7: FBA is an entirely different conversation. Will require rewrite in most cases. Need to test all custom code
- #8: This is most common when staying with SQL 2005. CU3, CU5 and above is supported, but not CU4My sites should be on its own URL, not as a subsite. This is because it requires self service site creation.Accounts used
- #9: Fab 40 no longer exists. The sites upgrade and some 3rd party person have updated, but no official MS upgrade. They were never intended to be used in production, they were meant to be examples of what can be done. Can be seen with ID of 75XXX as feature IDSTP files (save as templates) cannot be used after upgrade. This means that if you forget to create a site for each template you really have no way of getting the content out of that STP file.The Master Page in 2010 has been completely changed. You can keep the old masterpage, but it will not take advantage of new featuresOne of the most common items missed, is the Interface changes. The “ribbon” take a while to get used to so depending on your organization you will want to plan the training needed.
- #10: The service architecture is different. Not having “Shared Services” adds a little twist in the each element (User profiles, Search, Excel Services, etc). The Upgrade of the Shared Services database is smart enough to separate the componentsOne example is Excel services service account needs to be manually added to content databasePermissive file handling allows for “active” content to run.
- #11: The preupgrade Check is done on the existing servers and mainly checks to make sure the current system is OK annd to find what is brokenThe Test-spcontentdatabase is used on the new servers mainly to make sure that all the needed files exist on the new servers…. Solutions deployed, code items, web parts, etc.Oprhaned sites, Understanding the logs is criticalIf you don’t understand the new features and functions you may spend hours “fixing” something that is out of the box in 2010
- #12: It is a good idea to monitor servers during the upgrade process. If you did a dry run (which you should have) you should have a baseline of the amount of time needed. And potential disk space issues.Nice upgrade in Central Admin will let you track progress, use it. Upgrade-SPContentDatabase will allow you resume a failed upgrade.
- #13: Look at the logs on your dry run. Understand how they are set up so that you are not floundering with understanding the log and trying to complete an upgrade at the same time.If you do not have a test plan for your SharePoint system, now is a good time to create one. Items like, Searching for PDF, Check in, Check out, etc. If desired, run Visual Upgrade. In my opinion it is a waste to run an upgrade to 2010 and then not do the visual upgrade. You are missing out on some benefits. Keep in mind any site after this point will look like the 2010 sites and “not running” it will cause a disconnected feel