Here's a link to a video of the recording of the Webcast: SharePoint Upgrade Best Practices and Lessons Learned. Dave Coleman introduced me, and provided some helpful question banter along with the way. He recently wrote a whitepaper on migrating to SharePoint 2010.
Here's Dave's writeup on the webcast including an inline copy of the video recording. (No registration required.)
Here's some Q&A that came out of the session. Thanks for participating!
Q: Any gotchas if my 2007 farms are NTLM auth and I want to go Kerberos or (gasp) claims on 2010 farms? Should I do that before migrating content or after (or never)?
A: Going from NTLM to Kerberos can happen at any time. Going from either NTLM, Kerb or any classic authentication to Claims will require some work. I'd suggest you do it after the upgrade. I'm not suggesting you do it. I'd avoid it if you can. It is a downgraded but decent experience for many extranet environments, but I'd rarely if ever recommend it for an Intranet environment. Forms to Claims does require work as well.
MSDN: Claims Walkthrough: Creating Forms-Based Authentication for Claims-Based SharePoint 2010 Web Applications Using Custom Membership and Role Providers
Q: Did you use a third party to assist with your upgrade? Any issues with who you chose?
A: I didn't use any third party tools, but there are lots of good ones that can give you
Q: Is the Database Attach upgrade mutually exclusive from the Visual Upgrade or are you supposed to do both?
A: Great news for you on this one. Default is you do visual upgrade as a second step. It's delegated by default to Site Administrators. I put together a blog on this one.
- The Updateuserexperience parameter of the Mount-SPContentDatabase Windows PowerShell cmdlet.
- The preserveolduserexperience parameter of the addcontentdatabase stsadm operation.
Q: How can you tell what users are on sharepoint 2007? Can you kick them out before you make the database read only?
At the Windows PowerShell command prompt, type the following command:
$sc = Get-SPSite http://machinename/sites/collectionname | $sc.GetVisualReport() | Format-Table
Q: How do I handle SP sites that have SSRS integration? My sites have MS reporting services integrated with SP 2007. Thanks
A: You'll need to consult with your SSRS side of things. Basically that part hasn't changed until SQL 2012. If you're doing DB attach you'll need to reconnect and reinstall. I haven't done much on this so I suggest consulting the documentation.
Q: to add on that... MS even said they have a silent bug list.. which they solve in the CU's but not made public
A: There are definitely fixes that are not documented.
Q: Dont laugh about the MS question ;)
Q: Why should I upgrade Profiles, and not go with a clean User Profile service and depending DB;s ?
Q: Did you scale the servers ,which where handling the migration, especially for the migration of the 1 TB?
A: Yes, be sure to consult the minimum requirements for SP2010. Don't spare it. Many will need double the recommended hardware. 8GB of RAM is the old 4 and 16 the new 8.
Q: Was there no complaint from the users, if the visual upgrade is handeled on different time tables?
A: If you've done it right the users may not even notice! We sent videos and encouragement and many have ignored it. We'll likely need to do the visual upgrade for many of our site collections as well. No major complaints that users didn't get visually upgraded.
Q: I've done multiple upgrades, and had some weird issues, reported them to MS Support. I got an answer from MS where they said "well.. its a known bug but we didnt post it in a KB". Did you ever encountered this as well?
A: Sure. Microsoft doesn't necessarily reveal everything they know in KBs. Their list of Bugs/Known issues is NOT reflected by every KB article for sure…
Q: WEll... when you go from NLTM/Kerberos to claims, you have to transform the user accounts to the new claims user. This will take alot of time. Do you have the same experience?
A: Claims and NTLM are not the same user experience, especially when it comes to client integration. Be sure to do testing and do your research. I've got a user complaining they can't use SharePoint Designer, and they are a claims user. Sorry.