SharePoint 2010 Upgrades and Deployments…A Learning Experience…

The past few months I’ve been playing architect and admin, rather than developer.  I have worked with a couple 2010 environments for play and work and at least one upgrade.  So here are just a few tidbits that you might not know that I’ve found…

  • When working with the blank site definition you have to activate the taxonomy features through stsadm if you want to use managed metadata.  Here is a good article: http://neoassyrian.blogspot.com/2009/11/enabling-taxonomy-features-on-site.html
  • There is a bug if you want to attach the Profile Synchronization Service to a Service Application that uses your old Shared Service Provider Database.  Until they fix the issue it’s not worth the trouble unless you have a lot heavily invested into your old SSP.  You can migrate the database and write a custom script or look into a third party tool to do the trick.
  • Spence Harbars article on setting up the User Profile Services is the best one out there.  I have read it and memorized most of the article at least 50 times.  If you are implementing this feature go here: http://www.harbar.net/articles/sp2010ups.aspx.  This is the most painful piece of SharePoint 2010.  No matter how many times I work with this functionality it always seems to surprise me.
  • Managed metadata is great for organizing and creating a document library structure that is by far better than a folder system.  You need to make sure all the taxonomy features are turned on and the service application is setup.  It was by far one of the easiest features to setup.
  • FAST Search is the second most painful feature to use with SharePoint 2010.  You need to follow the Technet article to the letter.  If you see something in the service application that states you are missing and administrative component delete the service applications that you created.  The service applications must run under the search service account.
  • SharePoint Designer is still not quite where I would like it to be in the permissions department.  You can go into General Settings in Central Administration, but all the checkboxes feel like all or nothing.  You can give no one the ability to use SharePoint Designer or people with design rights and full control the ability.  I wish there was a checkbox in permissions that said “allow SharePoint Designer access” and if it was not checked that person did not have the ability.  If you turn off the ability to use client side programs, then the users can no longer launch office documents.  I am very disappointed.
  • The “Fabulous 40” does not always migrate well despite what some of the blog posts say.  It’s going to be a trial and error when you upgrade.  You might get a good outcome and you might not.  These templates were meant for demos and not for production.  I would just dump them and move on.  There are some third party versions for 2010, but they are not officially sanctioned by Microsoft.  They may or may not work.  Use them at your own risk.
  • My Sites…The database may upgrade, but there is a little trick.  You have to get the users to click on the my sites.  If you are deploying you need to make sure that you go to the application and add a path for “personal” (or whatever path you are using) and check the “wildcard” box.  Then you need to make sure that you create a site collection with the template called “My Site Manager” under the “Enterprise” templates.  You need to turn on “Self Service Site Creation” under the my site application too.  If you do not go in and set these options, then users cannot create my sites.  It’s not quite as easy as it used to be.

Some of these things I’ve told you might help you out.  Some of them might not.  I figure it never hurts to throw a couple items into a blog post that you learn.  Someone in a few months or a few years might find these items helpful.  Some of you might never read this blog, but that’s ok.  The two of you who are reading thanks for the support.  I’ll try blog more as I learn more about 2010.  Just because they dropped the Office in MOSS doesn’t mean I’m switching names.  It’s all about nostalgia.

Print | posted on Sunday, September 19, 2010 12:35 AM

Feedback

# re: SharePoint 2010 Upgrades and Deployments…A Learning Experience…

Left by Pim at 9/20/2010 1:18 PM
Gravatar Interesting reading. Can you also share some experiences on time it took to migrate. We currently have a Large sp2007 site running 20k users. Microsoft estimations to migrate are 1 year. I find this hard to believe since IT took half à year to implement.
What's your experience on this?

# re: SharePoint 2010 Upgrades and Deployments…A Learning Experience…

Left by SharePoint Tutorial at 6/11/2011 8:05 AM
Gravatar Thanks for the post...

@Pim: Migrating SharePoint doesn't take 1 year if it's just SharePoint and you have enough experienced resources for that job.

If you are going to migrate your AD for example besides SharePoint than it takes a lot of time since there are more things to do than just migrating SharePoint.

If you have lazy admins needing 1 week to setup an IIS then maybe it takes 1 year.

Your comment:





 
 

Copyright © MOSSLover

Design by Bartosz Brzezinski

Design by Phil Haack Based On A Design By Bartosz Brzezinski