Office System migraatio

1
(No Transcript)
2
Office System -migraatio

• Ilija Lazarov
• TSP Office Platform
• Microsoft

3
Technology Convergence
4
Design Goals

• Provide clean Microsoft Office SharePoint Portal
  Server 2003 (SPS) to Microsoft Office SharePoint
  Server 2007 (MOSS) upgrade
• 2001 -gt 2007 tools being developed CodePlex
• Minimize user impact
• Reduce outage duration
• Limit number of users impacted for any outage
• Support customizations to SPS
• Custom site definitions web parts
• Pages customized using Microsoft Office FrontPage
• Provide resource use choices to admins
• Enable upgrading existing farm
• Support migrating to new farm
• Provide single clear set of UI options
• Both GUI and command line
• Consistent approach for both products

5
Understand Upgrade Options

• In-place upgrade
• Updates existing databases and servers
• Easiest approach, environment offline while it
  runs
• Gradual upgrade upgrade site collections
• Granular control one to many site collections at
  a time
• Run old and new versions side-by-side rollback
  to SPS supported
• More complex and resource intensive
• Content DB migration upgrade into separate farm
• Attach SPS content database to MOSS farm and
  upgrade runs
• SPS stays available and untouched by upgrade
• Content only, requires new farm, has many manual
  steps

6
Before Upgrade Handling FrontPage customizations

• Important consideration keep customizations or
  move to MOSS
• Custom pages kept by default during upgrade
• SPS themes are not preserved
• Reset to Site Definition
• Returns page to layout in site definition
• Option exists to reset all pages during upgrade
• Available in site settings or within SharePoint
  Designer
• Works for any page edited in SharePoint Designer
  or FrontPage

7
In-Place Upgrade
Search UserProfiles
Search UserProfiles
Run setup, choose upgrade in-place
Web Server
Web Server
SPS Web App
MOSS Web App
SPS Web App
MOSS Web App
SPS ConfigDB
Repeat setup upgrade on each server in farm
SPS Content DB(s)
SPS no longer available after upgrade
SPS Search User Profiles
8
Maintaining Customizations Example
Pre-upgrade
Upgraded
9
Maintaining Customizations Example
Does not match rest of site Lacks new features
Navigation Site actions menu Security trimmed
UI Recycle bin Etc
10
Gradual Upgrade StepsUpgrade content

• Choose if resetting files to template version
• Can change selection with each group of sites
  upgraded
• Select first group of sites to upgrade
• Must include the root site of the domain in first
  group
• Note storage (number of MB) to be upgraded
• During upgrade, redirect to WSS v2 URL is removed
  
• WSS v3 site is now live
• Automatic - no admin action needed
• Review log files after each upgrade groupTip
  Upgrade duration is in logs. Number of MB /
  duration is good approximation for subsequent
  upgrade durations.
• Repeat steps 1-3 for all sites
• Command line available to automate

11
Additional SPS ConsiderationsSite structure

• Areas
• Areas are upgraded to regular sub-sites
• All areas under a given portal must be upgraded
  at once
• URLs
• Portal URLs change after upgrade
• In MOSS URLs follow the logical navigation
  structure navigation changes are now reflected
  in the URL
• E.g. http//sample_site/c16/marketing changes to
  http//sample_site/marketing
• Redirects links through Internet Explorer will
  be redirected Office Client apps will not

12
Additional SPS ConsiderationsSite content

• Listings
• Listings in SPS Portal Listings list
  Listings web part
• Listings in MOSS Links list items Content By
  Query web part
• Consider creating MOSS summary links from
  upgraded listings to leverage new page features
• Create new summary link control/web part
• Manually copy over listing content and order
• Pages
• Area homepages (e.g. default.aspx) are upgraded
  to the new page template model
• By default, all pages will use the installed page
  template after upgrade

13
Additional SPS Considerations Site applications

• News
• News listings are upgraded to Links list items
  and pages
• List items/pages are rolled up Content by Query
  Web Part
• Site directory
• Site is upgraded to new UI
• Sites List schema changes
• New columns added to Sites List for categories
• Single sign-on (SSO)
• No schema changes for MOSS
• Gradual configure MOSS to point to SPS SSO db
• Content DB Migration backup, restore SPS SSO db
  to MOSS farm

14
Additional Considerations for SPS Search and
Alerts

• Search
• Indexes not upgraded full crawl of all content
  required after upgrade
• All content sources default to a single index
  (MOSS has one index per SSP)
• Duplicate start addresses in content sources will
  be ignored
• Conflicting crawl rules between SPS indexes will
  be ignored (if item included in any index, it
  will be preserved)
• Search scopes, scope groups not upgraded
• SPS Alerts
• SPS alerts preserved but not automatically
  upgraded

15
Additional Considerations for MySites

• All upgrade approaches
• My Sites are upgraded to MOSS look and feel, new
  features (Colleagues, Memberships, Blogs)
• Consider moving My Site to its own web
  application which uses the MySite host template
• Gradual Upgrade-specific
• Until users personal site is upgraded, entire
  MySite experience remains SPS
• Once SPS Shared Services are upgraded, changes to
  SPS profile will not be copied to upgraded MOSS
  SSP

16
Additional Considerations for SPS with Shared
Services

• Search
• Two crawls running
• Recommend manually modifying SPS/O12 start
  addresses to prevent double-crawling
• Keywords, site-level scopes only available for
  upgraded MOSS sites
• User profiles/Audiences
• Gradual upgrade Changes in MOSS pushed down to
  SPS - does not include new properties and
  audience rules
• Review Managed Properties list for people search
  scope
• Review upgraded audiences consider deleting
  those built on DLs/SGs as those groups can be
  used directly

17
Migration Strategy

• Planning
• Analyze old application
• Map custom solutions to new features
• Migrate
• Use the Content Migration feature
• Post-migration tasks
• Check, refine migrated site
• Re-brand site
• Incrementally migrate new content

18
Migration Strategy
19
What Is Content?
20
Migration Profiles

• Contains the settings for the migration of a
  site
• CMS 02 database connection information
• Top-level channel to migrate
• Site collection to migrate into
• By running the profile, content gets migrated to
  Microsoft Office SharePoint Server 2007
• Dont need CMS 02 installed on your Microsoft
  Office SharePoint Server 2007 farm
• One profile for every migration

21
Common CMS 02 Implementations

• One CMS 02 install -gt One web site
• One CMS 02 install -gt Multiple web sites
• Each site in a top level channel
• Possibly using host header mapping
• Depending on the CMS 02 structure, your
  migration profile configuration will change
  slightly

22
One Web Site
Site Collection
23
Multiple Web Sites
24
Code Migration

• Moving from the CMS APIto SharePoint Object
  Model
• No backwards compatibility
• We are providing whitepapersto help customers
  through this

25
Code Migration - Custom code
26
Code Migration - Custom placeholders

• HTML Placeholders are migrated to HTML Field
  controls
• Custom Placeholders need to be migrated to Field
  controls
• The XML Placeholder isnt supported
• If you are using it, you need to create a custom
  field control

27
Code Migration - Metadata

• Channel Properties
• Move to a Property Bag on the site
• Access through API
• Posting Properties
• Become fields on the page
• Only visible in page edit mode

28
CMS Assessment ToolOverview

• Creates an inventory of your applications use of
  the CMS Publishing API (PAPI)
• Creates an inventory of the CMS Repository
• Collects Statistics about the CMS Repository
• Pre-Migration Analyzer
• Reports are in XML and Microsoft Office Excel

29
(No Transcript)