Horizons' Event: SharePoint 2013 upgrades-Notes from the Field
Upcoming SlideShare
Loading in...5

Horizons' Event: SharePoint 2013 upgrades-Notes from the Field






Total Views
Views on SlideShare
Embed Views



1 Embed 1

https://www.linkedin.com 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Use very graphical slides. <br /> All notes are included in a PDF at the end of the presentation. <br /> Will send out link to presentation <br />
  • Pre-Upgrade (Detective Work) <br /> Gather authentication providers and authentication modes that are being used <br /> Incoming and Outgoing E-mail <br /> Customizations <br /> Use stsadm -o enumallwebs -includefeatures, -includesetupfiles, includewebparts, -includeeventreceivers, -includecustomlistview <br /> Check for orphans <br /> Stsadm -o databaserepair <br /> DON&apos;T use -deletecorruption at first, let the tool give you a report <br /> Certificates <br />
  • Pre-Upgrade (Clean out the Cobwebs) <br /> Get 2007 to SP3 and 2010 to SP2 <br />
  • So this is your typical SharePoint database…not very big with one or more site collections. Nothing to worry about. <br />
  • Site collections about 100GB should be in a content database by themselves. You can move site collections to different databases. <br /> For 2007: for normal general collaboration usage of SharePoint, site collections should not exceed 100GB (soft limit) <br /> Main purpose is for backup and recovery. <br />
  • In general for 2010, for normal general collaboration usage of SharePoint, site collections should not exceed 200GB (soft limit) <br /> Good database sizing article: http://technet.microsoft.com/en-us/library/cc298801.aspx <br /> Get databases properly sized (overall size and number of site collections) <br /> Lots of SCs: more than 5,000, get back down to about 1,000 per content database <br /> 2013 gives warning at 2,000 and has a limit of 5,000 <br />
  • Do SQL database maintenance (DBCC CHECKDB, rebuild indexes (80 fill factor) <br /> Standard version will take indexes offline <br /> Remove PowerPoint Broadcast Sites <br /> Large lists <br /> More than 5,000 items or views with more than 8 special joins <br /> Talk about not changing settings (bad, bad, bad) <br /> Talk about indexing or using search <br /> Give example of a small list may use a group by off of calculated column but a large list may have a workflow that runs calculation on updates and stores permanently. <br /> Wide lists (row wrapping) <br />
  • Throw out any unused stuff <br /> In 2010, check for 2010 sites that are still using visual upgrade (PowerShell) <br />
  • If need to convert masterpage, http://startermasterpages.codeplex.com/ is a good start. <br /> Add to and then test regularly. Don&apos;t try to build whole master page and then test. <br /> If public facing, you can use www.modern.ie to test pages for IE compatibility <br /> Review new options and settings and determine how you want to use and set them. <br /> Review What’s New articles <br />
  • Only option is database attach or third-party migration tools. <br /> Set up a test farm <br /> Note changes to recommended architecture <br /> Position of service applications <br /> Use Claims (it is the default and works) <br /> Host-named site collections and single web application <br /> Use separate service accounts model including separating farm and setup account. <br /> Use the same URLs as the real farm (update HOSTS file) <br /> Use different names for servers than the real farm <br /> Use a separate SQL server (don&apos;t cross the streams) <br /> Use AutoSPInstaller and AutoSPInstallerGUI <br /> Make search service account administrator during farm setup <br /> Document and move over CA settings. <br /> Use something like WinDiff or BeyondCompare to compare real hive with test hive <br /> Do NOT configure outbound e-mail except with great care <br /> Did you turn off Workflow Auto Cleanup timer job? If so, turn off in 2013 <br />
  • Install customizations <br /> Talk about compatibility switch <br /> Install-SPSwitch -CompatilityLevel <br /> The default behavior if this parameter is not specified is to install the solution only to the version directory based on the version tracked in the manifest of the solution&apos;s cab file. <br /> If at 2010, upgrade to claims on the 2010 side first. It at 2007, wait. <br /> Verify success in 2010 environment <br /> Use Convert-SPWebApplication <br />
  • Upgrade databases <br /> Move over databases using SQL Backup and Restore <br /> Be sure to either restore using the farm account or use ALTER AUTHORIZATION to change the DBO before you connect to SharePoint <br /> If you don&apos;t, disconnect, drop user and make DBO. <br /> Upgrade service application databases <br /> From 2010 to 2013, recommend you can upgrade BDC, Managed Metadata, PerformancePoint, Secure Store, Search (don&apos;t recommend usually), User Profile (prefer UPRE if no MySites). <br /> From 2007 to 2013, recommend you can upgrade BDC, Secure Store, User Profile (lots of work and likely not worth it) <br /> Run test-spcontentdatabases <br /> Review what they find and need to fix and how to fix-tells them about missing customizations <br /> Upgrade database <br /> Talk about how to go from 2007 to 2013 and that you only upgrade database 2013 <br /> Review logs <br /> Can restart upgrades using "upgrade-spcontentdatabase" <br /> Upgrade to claims if coming from 2007 (see above) <br /> Can use MigrateUserstoClaims property if only doing single database <br /> Upgrade site collections <br /> Talk about options, gui versus PowerShell <br /> Talk about straight conversion versus test upgrade process <br /> Review logs-placed in the site collection and the log directory of the server which ran the upgrade (these logs have more detail). <br /> Site won&apos;t render? Try going to /_layouts/settings.aspx to see if SC is working in general <br /> Test all important and high traffic sites but you can&apos;t test it all <br /> Will talk about some tools that will help later <br /> Rinse and repeat until all issues are addressed-in most cases, it will take several times <br />
  • Resolve Issues <br /> Tools to gather information <br /> Microsoft IIS Log Parser and GUI tools <br /> http://www.microsoft.com/en-us/download/details.aspx?id=24659 <br /> http://www.lizard-labs.net/log_parser_lizard.aspx <br /> http://visuallogparser.codeplex.com/ <br /> Analytics (SharePoint, WebTrends, Google, etc.) <br /> Tools to find problems <br /> Duplicates List Field Scripts <br /> http://blog.sharepoint-voodoo.net/?p=142 <br /> HTTrack: used to dump site to all HTML <br /> http://www.httrack.com/ <br /> WAPT: Load Testing Tool <br /> http://www.loadtestingtool.com/index.shtml <br /> XENU: Find Broken Links <br /> http://home.snafu.de/tilman/xenulink.html <br /> Tools to Fix Problems <br /> Correlation IDs are your friend in 2013! <br /> Travel all the way back to the SQL server <br /> Consistent across all servers in farm <br /> Use Merge-SPLogFile to gather logs from across multi-server farm <br /> Developer Dashboard is your friend! <br /> To turn on, you need the Health and Usage Application service application configured <br /> Use this PowerShell <br /> $svc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService <br /> $dds = $svc.DeveloperDashboardSettings <br /> $dds.DisplayLevel = "On" <br /> $dds.Update() <br />   <br /> ULS Viewer <br /> http://archive.msdn.microsoft.com/ULSViewer <br /> SharePoint Manager <br /> http://spm.codeplex.com/ <br /> Feature Administration and Clean Up Tool <br /> http://featureadmin.codeplex.com/ <br /> Telerik&apos;s Fiddler <br /> http://www.fiddler2.com <br /> Reflectors <br /> Telerik&apos;s JustDecompile <br /> http://www.telerik.com/products/decompiler.aspx <br /> ILSpy <br /> http://ilspy.net/ <br /> Large Text File (LTF) Viewer <br /> http://www.swiftgear.com/ltfviewer/features.html <br />
  • Not free but good tools <br /> TFS and the Microsoft Feedback Client <br /> http://msdn.microsoft.com/en-us/library/vstudio/hh362461.aspx <br /> Atlassian&apos;s JIRA and JIRA Capture <br /> https://www.atlassian.com/software/jira/#! <br /> https://www.atlassian.com/software/jira-capture/overview <br /> Beyond Compare <br /> http://www.scootersoftware.com/moreinfo.php <br />
  • Things to know <br /> Upgrade speed is going to be effected by number of site collections, sites, lists, rowspan within list, document versions, documents, links or large databases over 100GB <br /> If upgrades take a long time, use Upgrade Logs to determine what pieces are taking longest time and see if items can be cleaned up from database. <br /> Upgrade speed is greatly determined by storage performance. <br /> Record how long it takes along the way. Needed to make a reasonable upgrade schedule. <br /> Ensure you have a rollback plan and know what time to back out. <br />

Horizons' Event: SharePoint 2013 upgrades-Notes from the Field Horizons' Event: SharePoint 2013 upgrades-Notes from the Field Presentation Transcript

  • SharePoint 2013 Upgrades: Notes from the Field Presented by: JD Wade, Lead SharePoint Consultant, MCTS, MCSE Mail: jd.wade@hrizns.com Blog: http://www.wadingthrough.com LinkedIn: http://linkedin.com/in/jdwade Twitter: @JDWade
  • • Cleaning Up • Conversion Work • How to Test Upgrade • Resolve Issues • Don’t Forget SharePoint • Detective Work
  • SharePoint
  • SharePoint
  • SC SC SC SC Content Database
  • SC Content Database
  • SC Content Database
  • SharePoint
  • SharePoint
  • SharePoint
  • SharePoint
  • SharePoint
  • SharePoint
  • SharePoint
  • SharePoint
  • SharePoint
  • SharePoint Saturday St. Louis Saturday, January 11, 2014 http://www.sharepointsaturdaystl.com http://www.hrizns.com http://www.wadingthrough.com/presentations
  • SharePoint Notes in PDF format Double click