Link to home
Start Free TrialLog in
Avatar of Arnold Layne
Arnold LayneFlag for United States of America

asked on

Upgrading from SharePoint 2007 to 2010

I have to do an upgrade from SP 2007 to 2010 and I am looking for a really comprehensive guide for doing this which includes how to upgrade the config DB, Content DB, how to handle any customizations that don't transfer correctly and how to fix any possible errors that preupgrade check finds. I'm thinking about a migrate rather than in pklace upgrade as this sounds much safer.

I know that this might actually be an entire book or many pages, but I really need to study this very thoroughly before attempting this and there must be something out there like this that truly goes into all of the required detail as there must be others here that have had to do this and used a good source.

Also, any personal experiences or horror stories with non published "gotchas" would be most appreciated.

Thanks.
ASKER CERTIFIED SOLUTION
Avatar of Justin Smith
Justin Smith
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Arnold Layne

ASKER

I would be hired as a contractor when I do this, so "just dive in" would not be an option for me, especially in a semi large environment where this will occur. Much to consider and many expectations would be on me. I wish that I could do what you said. I have my own personal domain and SP in my own home which I use as my dev env, but it doesn't seem practical for me to uninstall 2010 Enterprise and install 2007 to practice upgrade, So I will need to know what I am doing without much practice, assuming that I even decide to do this. I can understand any tech notes as my understanding of these sort of things is actually good, which is why I realize all of the potential problems that can happen, but I need to have the right info as I am aware of all of the ways this can potentially go wrong, but I can't seem to find a good guide about what to do to prevent or fix these problems if they occur. They only seem to say what utilities to run and then tell you to look at the potential problems and fix them, but they don't seem to say the best or correct way to fix them. Maybe I'm making this more complex than needed, but again, I will have to go on to an unfamiliar farm and do this and I'm beginning to think that maybe I shouldn't.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I don't know as of yet. It is a contract job that I am considering. From what I know, SharePoint 2010 is .net 3.5, and this would be an upgrade from 2007 to 2010. Are you saying that some code might be .net 2.0? If so, could I merely import the code into VS 2010 and rebuild and redeploy it under 3.5? I'm glad you raise this point. Thanks.