Sharepoint Advanced Tips: Migrating to SharePoint 2010

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">Introduction

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">This
post will show 2 possible scenarios to migrate from MOSS 2007 to SharePoint
2010. In order to demonstrate one of the worse case, we will start from a farm
running MOSS 2007 SP1 on 32-bit Windows 2003 server OS. I have
chosen two hybrid scenarios among those exposed in the Microsof documentation href="http://technet.microsoft.com/en-ca/library/cc263447.aspx">Determine
upgrade approach (SharePoint Server 2010) because their are safer
since for each scenario we will upgrade on a copy of the farm:

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">1:
Database attach with read-only databases
Lets you continue to provide
read-only access to content in your MOSS 2007 web sites during the upgrade
process. For this approach, you set the MOSS 2007 databases to read-only while
the upgrade is in progress on another farm where SharePoint 2010 is deployed.
This method reduces perceived downtime for your users.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">2:
In-place upgrade with detached databases on a separate Farm
Lets you take
advantage of an in-place upgrade's ability to upgrade content and settings,
while adding the speed of a database attach upgrade. For this approach, you use
an in-place upgrade to upgrade the farm and settings on a separate
farm that is a copy of the farm, and to detach and upgrade multiple
databases in parallel on this separate farm.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Before
detailing the steps required for these scenarios I would like to draw up the
list of the benefits and drawbacks of these hybrid scenarios comparatively to
the two basic approaches (in-place and database attach):

Safer : you upgrade the content for the environment on a
separate farm so you keep your old MOSS 2007 Farm intact.
More service availibility: Although the sites
of your old MOSS 2007 Farm that are involved in the migration process are in
read only mode, they still can display content to the users during the
migration process. The sites that are not involved can be used as usual. This
method reduces perceived downtime for your users.
Faster upgrade time: You can upgrade multiple content
databases at the same time, which results in faster upgrade times overall than
an in-place upgrade.
More flexibility: You can use a database attach upgrade
to combine multiple farms into one farm that allows you to take advantage of
the migration to reorganize your architectures.
Cleaner: as you have to replicate all the environment
configurations and customizations on the new farm, you will take advantage of
this work to move only the nece ssary files and perform only the necessary
configuration operations.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

More expensive : Except if you are using virtualization,
you will have to plan until twice more machines than for In Place upgrade.
More work : You will have to replicate all your old Farm
cutomizations on the new SharePoint 2010 Farm

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">1 -
Database attach with read-only databases
Pros
If you’re running MOSS, each
Shared Service Provider (SSP) and its settings will be upgraded and converted
into new service applications. Source: href="http://www.sharepointproconnections.com/article/sharepoint-server-2010/Migrating-to-SharePoint-2010-104619.aspx">Migrating
to SharePoint 2010
Cons
You will have to mount a MOSS 2007 farm on
64-bit, then use an In Place uprade on the new farm for the settings, finally
use an attach database upgrade for the content.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">2
- In-place upgrade with detached databases on a separate Farm
Pros
You
have not to upgrade your MOSS 2007 farm to 64-bit, then to upgrade it to
SharePoint 2010, you save one step
Cons
For those running MOSS 2007, you
should know that a database-attach upgrade won't fully upgrade your SSP into new
service applications. When you attach an SSP database, only your user profile
store is upgraded. Search settings, Excel Service settings, Business Data
Catalog (BDC) application definitions, and other settings must be recreated from
scratch. Source: href="http://www.sharepointproconnections.com/article/sharepoint-server-2010/Migrating-to-SharePoint-2010-104619.aspx">Migrating
to SharePoint 2010

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Conclusion
: if you have a lot of SSP settings like advanced search settings, wide use of
Excel Services,etc. consider to use the scenario 2 otherwise, scenario 1 is
quicker.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">Steps
of the migration

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">1
- ugrading the SharePoint Farm with MOSS 2007 SP2
2 - upgrading the
SharePoint Farm with MOSS 2007 October 2009 Cummulative Updates
3 - running
the pre-upgrade tool: pre-upgrade checker
4 - Scenario 1: performing database
attach upgrade with read-only databases
4.1 - Building a SharePoint 2010
Farm
4.2 - Determining how to handle customizations
4.3 - Moving the
customization to the SharePoint 2010 Farm
4.4 - Moving and Upgrading
the Content to the SharePoint 2010 Farm
4.5 - Restoring and Upgrading
the Content on the SharePoint 2010 Farm

5 - Scenario 2: In-place upgrade
with detached databases on a separate Farm
5.1 - Copying the MOSS 2007 farm
to upgrade to 64-bit
5.2 - Performing an in-place upgrade to upgrade the farm
and settings
5.3 - Moving the Content to the SharePoint 2010
Farm
5.4 - Restoring and Upgrading the Content on the SharePoint 2010
Farm
5.5 - Fixing the customizations.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">1 -
Ugrading the SharePoint Farm with MOSS 2007 SP2

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">1.1
The different operations list

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">One
of the prerequisites before migrating to SharePoint 2010 is to patch your
SharePoint farm to at least MOSS 2007 SP2. This requires several
operations:
Running the href="http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en">SP2
fo WSS
Running the href="http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=085e5ac8-58f6-4cf9-8012-33b95ee36c0f">WSS
SP2 for each Langauge Pack
Running the href="http://www.microsoft.com/downloads/details.aspx?FamilyID=b7816d90-5fc6-4347-89b0-a80deb27a082&displaylang=en">SP2
for MOSS 2007
Running the href="http://www.microsoft.com/downloads/details.aspx?displaylang=fr&FamilyID=01c6a3e8-e110-4956-903a-ad16284bf223">MOSS
2007 SP2 for each Langauge Pack
Doing all that for each server of the
Farm

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">1.2 A
sequence sample

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">There
will be a first warning informing the system administrator that IIS, SharePoint
Administration Service, SharePoint Timer Service may have to be started or
reset.
But, more important there will be another message that will inform
that the same upgrade operation has to be done on every Server of the Farm.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">1.3
Validating the Upgrade

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">First
of all let us check the version of our SharePoint Farm. You can check the
version number on the settings page of any SharePoint site of the Farm, or in
the Central Administration on the "Servers in Farm" Page.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">What
you have to check after having applied the WSS 3.0 SP2 upgrade,
is obtaining this new version number : 12.0.0.6421

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">What
you have to check after having applied the WSS 3.0 Language packs SP2
upgrade, is obtaining the updates information for the language packs
in the "Add and Remove Programs" pannel:

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">What
you have to check after having applied the MOSS 2007 SP2
upgrade, is obtaining the update information for MOSS 2007 in
the "Add and Remove Programs" pannel:

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">It
seems that there is no way to check the complete installation for MOSS
2007 language pack SP2, in my case, the "Add and Remove Programs" pannel did not
show the update information as you can notice on the above picture.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Now
is the time to navigate through SharePoint Portals of the upgraded farm in
order to check they still run perfectly well.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">2 -
Ugrading the SharePoint Farm with MOSS 2007 October 2009 Cummulative Updates

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">While
it is enough to upgrade a MOSS 2007 Farm with SP2 to be allowed to migrate to
SharePoint 2010, and that is the minimal step to get the SharePoint 2010 pre
udate checker installed, it is worth to uprade the Farm with October 2009
Cummulative Updates in order to have the best version of the tool.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Download
the href="http://blogs.msdn.com/b/sharepoint/archive/2009/10/29/october-2009-cumulative-update-packages-for-sharepoint-server-2007-and-windows-sharepoint-services-3-0.aspx">MOSS
2007 October 2009 Cummulative Updates

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">You
will have to register to obtain them. The link to them will be sent to you by
e-mail with the password to unzip them.
Then you will run them and the
sequence will be the same than for the SP2.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">3
- Running the pre-upgrade tool: pre-upgrade checker

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Now
that we have the best version of the SharePoint 2010 pre udate checker
installed, because we performed an update with October 2009 Cummulative Updates,
we can now run the tool.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Open
an command prompt and if the STSADM.exe path is registered in the environment
variable of the machine, type the following command:

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">If
we refer to the found blocking issues, they are totally normal since, the
machine OS is in 32-bit and is not a Windows 2008 version, and SQL Server 2008
is in 32-bit and was not updated. I have also several SharePoint artifacts
references in the content databases but the referenced files are no
more present in the file system of the server. I should have to clean them
although they are no more used by any site.
So what all does this mean ? It
means that we are not allowed to perform an upgrade on THIS machine (ie an In
Place Upgrade), but there is good chances that a database attach upgrade
works...

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">color=#808080 size=2 face=Arial>

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px">4
- Scenario 1: performing a database attach upgrade with read only databases

Having a SharePoint 2010 ready to use Farm to receive our machine
databases
Determine how to handle customizations

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">4.1
- Building a SharePoint 2010 Farm

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">In
order to train for building such an environement, you can use my previous post:
href="http://mosshowto.blogspot.com/2009/11/installing-sharepoint-2010-windows-2008.html">Installing
SharePoint 2010 on Windows 2008 Server R2 that is an example of how to mount
this kind of environment using only free and trial versions of the involved
products for a development machine. If you want to mount a real production
environment I have also provided links to the corresponding documentation.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Do
not forget to install the same href="http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=646e311a-aaf3-4d30-b03c-2f3c70d19a22">language
packs as in your SharePoint 2007 source farm.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">4.2
- Determining how to handle customizations

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">First,
this is the Microsoft recommendations: href="http://technet.microsoft.com/en-ca/library/cc263203.aspx">Determine how to
handle customizations

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Although
customizations for SharePoint come in many forms (Site templates , Site
definition, Feature, Workflows and server controls, Event handler, Web Parts,
Master pages and CSS files, etc.) I would like to focus now on the compiled
code.
There were many questions I have read on Forums and Blogs about "Do we
have to recompile or rewrite the code for a migration to SharePoint
2010 ?".
I have found several answers and the good news is that in many
cases neither rewriting the code nor even recompile it won't be necessary.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">but
I would like to display two excerpts of the Microsoft documentation that
illustrates what you have to deal with :

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Excerpt
1
[...
Existing applications

You must recompile existing 32-bit
applications and custom assemblies (for example, Web Parts and event receivers)
to run on the 64-bit architecture because the 64-bit edition of SharePoint
cannot load a 32-bit assembly. Before you recompile existing applications or
custom assemblies, verify that they are compiled to run on both architectures.
If this is the case, do not compile them for a single architecture. (In
Microsoft Visual Studio this build option is Any CPU.)

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">If
the existing applications are third-party applications, check with the
third-party vendor regarding 64-bit versions and compatibility. In the case of
custom contracted solutions for which you do not have the source, verify the
solutions in a test 64-bit environment to ensure compatibility.
..]

In
href="http://technet.microsoft.com/en-ca/library/dd622865(office.12).aspx">Migrate
an existing server farm to a 64-bit environment (Office SharePoint Server
2007)

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Excerpt
2
[...
Obsolete Classes and Namespaces

Because the changes to the
API in the upgrades are backward compatible, you should not have to make any
changes to your Windows SharePoint Services 3.0 or Office SharePoint Server 2007
custom solutions before you redeploy them in either SharePoint Foundation 2010
or SharePoint Server 2010. Some classes and namespaces are obsolete, but they
will continue to work as expected. If you want to start upgrading your
applications so that they use the most current classes and methods, recompile
your code. The compiler warnings will tell you which elements of the object
model are obsolete, and which newer alternatives you should use. Figure 3 shows
an example compiler warning and the corresponding mouse-over warning in Visual
Studio 2010.
..]

in href="http://msdn.microsoft.com/en-us/library/ee662217.aspx">Redeploying
Customizations and Solutions in SharePoint Foundation 2010 and SharePoint Server
2010

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">So
the philosophy is the following:
you can deploy a dll compiled for MOSS 2007
using the "Any CPU" or x64 build option on a SharePoint 2010 server and it
will work using the 64-bit process, but if you want an optimized code you should
recompile it with the new SharePoint 2010 object model. So in many case it won't
be necessary to recompile but it is recommended to do it to optimize your code
and to learn the new SharePoint 2010 object model.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">I
have published a first post on the topic: href="http://mosshowto.blogspot.com/2010/06/sharepoint-2010-dll-migration.html">Migrating
custom assemblies to SharePoint 2010 that explains some important concepts
to take into account and gives an example for a Web Part , and am planning to
detail some more operations for at least Event handler.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">I
have not performed advanced searches on topic until now, but am planning to do
it, and will certainly publish some posts on specific operations like I did for
custom assemblies. Looking to the table listing the diffrent kinds of
customizations and the migration impact on it, presents in the Microsoft
documentation (href="http://technet.microsoft.com/en-ca/library/cc263203.aspx">Determine how to
handle customizations ), I see 4 main important areas to review:

Information architecture - sites provisionning
Site
definition and site templates
Managed paths (inclusions/exclusions)
Look and Feel - UI Experience
Themes
Toolbar
actions
Master pages and CSS files
Custom code
Workflows and server controls
Event
handler
Web Parts
Services
Authentication providers
Search
provider or security trimmer
JavaScript
Features

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px"> 4.3
- Move Customizations to the SharePoint 2010 Farm

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Depending
on the decision you took about handling your customization, you can either move
it on the SharePoint 2010 target platform and test it or rewrite it for
SharePoint 2010 to take advantage of the new product benefits.
For the
current tests, I have deployed SharePoint solutions (.wsp), installed features
that was not packaged in .wsp, using the stsadm tool and typing exactly the same
command lines than in SharePoint 2007 and during my content database upgrade,
all the deployed files were retrieved by the upgrade process.

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px"> 4.4
- Move Content to the SharePoint 2010 Farm

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Once
your customizations are properly handled for SharePoint 2010, it is the time to
move the content. Here are the operations for an attach database upgrade.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">First
this is the Home page of one of the Web Application of the MOSS 2007 farm I am
going to migrate. As you may notice, I took a standard site definition : the
Collaboration Portal, with a few custom Web Parts and features as
customizations.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px"> 4.5
- Restoring and upgrading the Content on the SharePoint 2010 Farm

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">First
copy the back up of your SharePoint 2007 content darabase in the right folder to
prepare to restore this backup.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">color=#ff0000>Very important : grant the db_owner permissions to the Set-up
account the wich you will be logged-in with when you will perform the upgrade
for the new database, otherwise the upgrade will definitively fail!

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">color=#000000>[STSADM] [SPUpgradeSession] [ERROR] [5/31/2010 11:56:27 PM]:
Exception: Cannot open database "WSS_Content_WebApp81" requested by the login.
The login failed.
Login failed for user 'VMDEV-012\Administrator'.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Finally,
open a command prompt on a SharePoint 2010 server that hosts the SharePoint 2010
central Administration and type the following command:

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">color=#000000>stsadm -o addcontentdb -url yourWebApplicationUrl color=#000000>-databasename yourDatabasename color=#000000>-databaseserver yourdatabaseServerName

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">But
more interesting, a page especially dedicated to upgrade status is
available in the Central Administration Web site in SharePoint 2010 and
is refreshing automatically giving you the number of warnings and errors
encountered during the upgrade process, and informing you about the site that is
involved by the upgrade process.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">While
there are some errors the Status will be "Failed", but it does not mean that
your SharePoint site will not be available. For example, assume you
have provisionned some files or a list by using a feature and
that someone has removed the files or the list from the SharePoint site and
removed the feature from the file system of the source farm
without uninstalling it.
Your upgrade will be sucessful since the pages
provisionned are no more required, but the reference of the feature is still in
the SharePoint content database, and while the upgrade process does not find the
feature in your SharePoint 2010 file system you will have an error and the
upgrade will be set to "Failed", but you will be able to perfectly use all the
functionnalities of your upgraded Sharepoint 2010 site.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">In
my case for a native Collaboration Portal of Moss 2007 I obtained several
errors on missing features, because either they were missing in the MOSS 2007
farm file system anyway, or because I forgot to copy them in my new SharePoint
2010 server. But one was because it seems that the SharePoint 2010 release is
missing a MOSS 2007 feature.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">color=#ff0000>Warning : It seems that since the feature DocLibLanguageFiltering
is missing on the Sharepoint 2010 release, while performing an upgrade of a site
based on the document center site definition, you will always have this two
errors:

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">[STSADM]
[SPContentDatabaseSequence] [ERROR] [6/7/2010 1:01:32 AM]: Found a missing
feature Id = [00bfea71-e717-4e80-aa17-d0c71b360102]
[STSADM]
[SPContentDatabaseSequence] [ERROR] [6/7/2010 1:01:32 AM]: The feature with Id
00bfea71-e717-4e80-aa17-d0c71b360102 is referenced in the database
[WSS_Content_WebApp-81], but is not installed on the current farm. The missing
feature may cause upgrade to fail. Please install any solution which contains
the feature and restart upgrade if necessary.

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">So,
if you want a perfect upgrade without one single error, you will have to review
the upgrade error log file, fix the error, then
remove the content
db
Close its connection by detach re attach it in SQL
Server
Restore again the source fram content db backup
Set up the
Administrator permissions
Perform an upgrade

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px"> 4.5
- Perform a Visual Upgrade

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Now,
if you really want to have a complete upgrade that allows you to take advantage of
the new SharePoint 2010 user experiece, you have to perform a Visual Upgrade, so
locate the menu

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 31px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px"> 5
- Scenario 2: performing an "In-place upgrade"

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">5.1 -
Building a SharePoint Farm running MOSS 2007 64-bit on Windows server 2008
R2

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">5.2 - Moving
Customizations on SharePoint Farm running MOSS 2007 64-bit on Windows
server 2008 R2

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">5.3 -
Performing In Place Upgrade

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 26px; COLOR: #e9ab17; FONT-WEIGHT: normal; PADDING-TOP: 10px">5.1 -
Moving and Upgrading Content on SharePoint Farm running MOSS 2007 64-bit on
Windows server 2008 R2

style="PADDING-BOTTOM: 10px; MARGIN: 1px 0px; PADDING-LEFT: 13px; PADDING-RIGHT: 0px; COLOR: #e9ab17; FONT-WEIGHT: bold; PADDING-TOP: 10px"> 6
- Aknowledgements and useful links

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">Thanks
to href="http://www.sharepointproconnections.com/author/1891/RandyWilliams.aspx">Randy
Williams for his post : href="http://www.sharepointproconnections.com/article/sharepoint-server-2010/Migrating-to-SharePoint-2010-104619.aspx">Migrating
to SharePoint 2010

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">First,
the link on the topic in the SharePoint 2010 site ressource center: href="http://technet.microsoft.com/en-us/sharepoint/ee517214.aspx">Upgrade and
Migration for SharePoint Server 2010

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px"> A
good article in Technet magazine: href="http://technet.microsoft.com/en-us/magazine/ee677571.aspx">Get Ready for
SharePoint 2010

style="TEXT-ALIGN: justify; PADDING-BOTTOM: 18px; MARGIN: 1px 0px; PADDING-LEFT: 18px; PADDING-RIGHT: 5px; FONT-FAMILY: arial; COLOR: gray; FONT-SIZE: 10pt; FONT-WEIGHT: normal; PADDING-TOP: 5px">One
of the post of Joel Oleson href="http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=328">What NOT to
Migrate into SharePoint 2010 that has, by the way, published a href="http://oreilly.com/catalog/0636920010869">book on the topic.

Sharepoint Advanced Tips

Monday, June 7, 2010

Migrating to SharePoint 2010

No comments:

Post a Comment