ShareParts LLC ... Yukon Energy Corporation. SharePoint 2010 Migration Plan. Situational Analysis and Proposed Approach for SharePoint 2010 Migration

Transcription

1 . ShareParts LLC Yukon Energy Corporation SharePoint 2010 Migration Plan Situational Analysis and Proposed Approach for SharePoint 2010 Migration

2 . Yukon Energy Corporation SharePoint 2010 Migration Situational Analysis and Proposed Approach for SharePoint 201 Migration Prepared by Arnold Villeneuve of Networkologist with assistance from Hemant Risbud, YEC SharePoint Administrator June 10, 2011 Prepared for Philippe Cashaback, I.T. Manager Yukon Energy Corporation Box 5920, Whitehorse, YT Y1A 6S7 Phone: (867) Fax: (867)

3 Table Of Contents Background... 4 Objectives... 4 SharePoint 2010 Migration... 5 The SharePoint 2010 Migration Challenge...5 GOAL...5 Microsoft Approved SharePoint 2010 Upgrade and Migration Methods 6 SharePoint 2007 to SharePoint 2010 Migration Issues... 9 Sites That Could Not Be Imported...9 Sites That Were Not Imported Due To Permissions or Compatibility Incompatible Features Incompatible SharePoint 2010 Site Templates WebParts That Require Reinstallation Assemblies That Require Reinstallation Web Templates That Require Reinstallation Custom Views That Will Require Rebuilding Custom Fields That Will Require Development Large Lists That Will Require Manual Upgrade Time Line of Activity Report Summary

4 . Background Yukon Energy Corporation (YEC) has engaged the SharePoint 2010 Migration consulting services of Arnold Villeneuve through Networkologist. The requested services were defined and outlined in several s and during recent meetings. Between May 25 th and May 30 th Mr. Villeneuve met in Whitehorse with YEC I.T. Manager Philippe Cashaback and SharePoint Administrator Hemant Risbud to discuss the project objectives and desired outcome. Objectives The objectives of this project are as follows: 1. Facilitate a total migration of the SharePoint 2007 to SharePoint 2010 site all at once over a weekend. That is to say that ALL SharePoint sites will be migrated at the same time, most likely over a long weekend. 2. Evaluate the different Microsoft approved methods available to assist YEC in migrating from SharePoint 2007 to SharePoint 2010 with Item 1 above in mind. 3. Advise YEC on the best approach to take given their heavy reliance on the current SharePoint 2007 environment. 4. Identify those elements that cannot be migrated due to compatibility or other non-compliance issues and provide resolution recommendations. 5. Develop a migration time line that includes the following phases: a. Test Migration of existing SharePoint 2007 site with compatibility resolutions put in place. b. Provide End User Training for the new SharePoint 2010 environment. c. Preform final migration to Production ready environment. d. Be on hand to assist with any post migration issues that arise. e. Develop in-place documentation for the final SharePoint 2010 solution. i. Documentation may include all or some of the following elements 4

5 SharePoint 2010 Migration The SharePoint 2010 Migration Challenge If only it were that simple! Since the implementation of SharePoint 2007 many organizations have customized their SharePoint sites. While SharePoint makes these easy it also has created an unexpected challenge now that they are ready to migrate to SharePoint Specifically not all of the Microsoft SharePoint 2007 components are upwards compatible and most certainly many third party or custom SharePoint 2007 components are not compatible with SharePoint While Microsoft has created two approaches to moving from SharePoint 2007 to SharePoint 2010 both have their limitations: In place upgrade assumes the existing hardware and software infrastructure can support SharePoint 2010, rarely does it Migration to new SharePoint 2010 hardware and software infrastructure In both cases Microsoft has assumed that the client s existing SharePoint 2007 implementation is very plain and uses only Microsoft s SharePoint elements. This is rarely the case in most organizations today. The YEC SharePoint 2007 upgrade / migration will prove particularly challenging in our opinion because of the significant amount of modification and customization it has gone through over the years. Furthermore the customization has been done by different people and different organizations. In some cases, YEC does not have original source code for some of the customization which only further increases the challenges it faces moving to SharePoint Additionally we need to acknowledge that the look and feel of SharePoint 2010 is significantly different from 2007 and that the current view of the site may not readily migrate. That is to say that any customizations that have been made to the look and feel of SharePoint 2007 will need to be redone post upgrade and/or migration. GOAL Ensure the migration to SharePoint 2010 brings over as much of the current SharePoint 2007 environment and data as possible and address any incompatibility issues to resolve those elements which do not migrate. Accomplish the migration of all YEC SharePoint sites at the same time and switch all users over to the new SharePoint 2010 environment at the same time. 5

6 . Microsoft Approved SharePoint 2010 Upgrade and Migration Methods There are two basic approaches to upgrade: in-place and database attach. In addition, there are various techniques you can use to combine aspects of these basic approaches to mitigate downtime or potentially improve performance. The following table compares the in-place and database attach approaches. Approach Description Pros Cons In-place upgrade You can install SharePoint Server 2010 on the same hardware. You can also upgrade the content and settings in the server farm as part of a single process. Farm-wide settings are preserved and upgraded. Customizations are available in the environment after the upgrade, although manual steps may be required to upgrade or rework them. Servers and farms are offline while the upgrade is in progress. The upgrade proceeds continuously. Consequently, you must allocate enough time for all content to be upgraded in sequence. Database attach upgrade You can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users. You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. You can use a database attach upgrade to combine multiple farms into one farm. The server and farm settings are not upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm. Any customizations must also be transferred to the new farm manually. Any missing customizations may cause unintended losses of functionality or user experience issues. Copying databases over a network takes time and bandwidth. You must plan for that. You need direct access to the database servers. The following table lists the downtime mitigation techniques that you can use during upgrade to reduce the amount of time that users cannot access their content or to potentially increase upgrade performance. Technique Description Pros Cons Parallel upgrade You can attach and upgrade multiple databases at a time to speed up the upgrade process overall. The maximum number of parallel upgrades depends on your hardware. This technique works for either inplace or database attach upgrades. Faster upgrade times for your overall environment. This is a manual process that requires additional steps and monitoring. 6

7 Hybrid approach 1: Database attach with read-only databases Lets you continue to provide read-only access to content during the upgrade process. For this approach, you set the databases to read-only while the upgrade is in progress on another farm. This method reduces perceived downtime for your users. The existing farm can continue to host nonupgraded sites (in readonly mode) while you upgrade the content. As a result, there is minimal downtime for users. You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. You can upgrade hardware in addition to software. The server and farm settings are not upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm. Any customizations must also be transferred and upgraded manually. Any missing customizations may cause unintended losses of functionality or user experience issues. Copying databases over a network takes time and bandwidth. You must plan for that. You need direct access to the database servers. Hybrid approach 2: In-place upgrade with detached databases 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 inplace upgrade to upgrade the farm and settings, and to detach and upgrade multiple databases in parallel (on the same farm or a separate farm). Farmwide settings can be preserved and upgraded. Customizations are available in the environment after upgrade, although manual steps may be required to upgrade or rework them. You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. Copying databases over a network takes time and bandwidth. You must plan for that. You need direct access to the database servers. Be aware that you can also combine these techniques. For example, you can set your original farm to readonly mode, create a copy of the farm and upgrade it without the content databases, use parallel upgrade to rapidly upgrade all the user content, and then finally switch users to the new farm after upgrade is completed. Networkologist Recommendations We have reviewed the two main Microsoft approved approaches with the YEC SharePoint Administrator. We have concluded that the SharePoint In Place upgrade approach is not acceptable for the following reasons: - Current MOSS01 and SQL01 Operating Systems are Windows 2003 and would require a complete upgrade to Windows 2008 prior to any upgrade - While the MOSS01 and SQL01 servers are virtualized the VMWare ESX hardware these virtual machine servers are running on is now close to five years old (warranty expiration time) 7

8 . - We will face the same issues with the In Place Upgrade that we will face with a Migration approach, only more of them as we will also have to replace the hardware and software first which will required that we take down the SharePoint system while both are replaced. This approach will take longer than the Migration approach. - Finally, the current location of the SharePoint 2007 Infrastructure is not idea as it is outside the secure YEC perimeter yet behind a firewall. All SharePoint infrastructure should be within the secure YEC perimeter. Therefore, we recommend that the SharePoint 2010 Database Attach migration method approach be used by YEC for the following reasons: - It has already implemented new hardware and software to support the SharePoint 2010 environment because it has been acknowledge that the current SharePoint 2007 infrastructure cannot support SharePoint The Database Attach migration approach will allow YEC to leave the current SharePoint 2007 environment in place so that we can fall back to it should the initial migration to Production fail (this of course will be after two prior test migrations, so it will be unlikely but none the less we need to be prepared for such an eventuality and the migration approach affords us that luxury.) - Several processes can, and have been run, that will allow us to properly identify which Sites, Solutions, Features, Webparts, and Lists will not migrate. In turn, we can plan an appropriate course of action to address those matters during our test migrations so that we are properly prepared to do so during the final migration to Production. 8

9 SharePoint 2007 to SharePoint 2010 Migration Issues The YEC SharePoint Administrator has run several Microsoft processes to properly identify any issues with the selected Database Attach Migration approach. They include the following: Tests Details Qty PreUpgradeCheck PreUpgradecheck 1 Attach DB method Test Content DB 1 Sites 15/189 Features 49/147 Site Templates 8 WebParts 15 Assemblies 6 Web Templates 8 Views 1728 Field Types 10 Large Lists 4 The details of the PreUpgradeCheck report are included in the Appendix. The remainder of this report will focus on those areas that have been identified as requiring attention to successfully re-implement, replace, and rebuild those Sites, Solutions, and Webparts that are not compatible with SharePoint Sites That Could Not Be Imported "/Departments/info_tech/change_mgmnt" Can be replaced with 2010 version "/Departments/info_tech/DRPBCP/avp" Will be replaced with Phoenix 2010 Can be partially replaced with 2010 version of "/Departments/info_tech/HD" IT Team Template minus customization "/Departments/info_tech/helpdesk_projects" Same as above Supplied with 2010 but data will have to be "/News" re-entered "/training" Not required 2007 Training "/training/learner" Not required 2007 Training "/training/report" Not required 2007 Training "/training/trainer" Not required 2007 Training "/sites/drp/compliance" Not required 2007 Training "/sites/drp/project" Not required 2007 Training 9

10 . The above list details the main Sites that were NOT imported during the Database Attach Migration approach. Sites That Were Not Imported Due To Permissions or Compatibility "/Departments/President" "/Departments/President/records" "/Departments/info_tech/ITWorkspace/Weekly IT Meeting" The above sites could not be imported by the YEC SharePoint Administrator due to current permissions or incompatibility with possible customized List. Based on our analysis with the Microsoft PreUpgradeChecker the remainder of the Sites and their data should migrate successfully. However, there are Solutions and Webparts, as well as Custom Code, that will not migrate and will need to be either reinstalled on the new SharePoint 2010 server or redeveloped to be compatible with SharePoint Incompatible Features The following is a list of incompatible Features for SharePoint Not to worry as some of them are not required as their functionality is already included in SharePoint However, some level of reconfiguration will be required. On the other hand, some of these Features will require the purchasing of a SharePoint 2010 compatible version. ApplicationTemplateCore.wsp ResourcesList HelpDeskTasks BugCategoriesList CompProcCompReg HelpDeskSupportFaqList KBProvisioningFeature ProjChangeModules ProjIssues HelpDeskListInstances ReservationsModules CompProcTasks PostProvisioningFeature AVMResponsibilityAdoptionList ProjChangeRisksList ProjTasks ITTeamListInstances ApplicationTemplateCore.wsp 10

11 ProjChangeListInstances TSATypes ProjChangeRequestStatusList KnowledgeBaseKnowledgeBaseList HelpDeskInIssuesList ITTeamModules HelpDeskExpertsList ITTeamBugList ListPropertyFeature HelpDeskServiceRequestsList ReservationsList CompProcProjects CompProcIssues StkFeatureReceiver Dundas Chart feature Change Status VASCSiteAction HelpDeskTasks Incompatible SharePoint 2010 Site Templates All of the following Site Templates are related to the SharePoint 2007 Training Kit and as such are not required within the SharePoint 2010 environment. SiteTemplates\SPSSTKHOME\default.aspx SiteTemplates\SPSSTKHome\stkhome.master SiteTemplates\SPSSTKLEARNER\default.aspx SiteTemplates\SPSSTKLearner\stklearner.master SiteTemplates\SPSSTKREPORT\default.aspx SiteTemplates\SPSSTKReport\stkreport.master SiteTemplates\SPSSTKTRAINER\default.aspx SiteTemplates\SPSSTKTrainer\stktrainer.master SPSSTKHOME SPSSTKHOME SPSSTKLEARNER SPSSTKLearner SPSSTKREPORT SPSSTKREPORT SPSSTKTRAINER SPSSTKTrainer WebParts That Require Reinstallation The following WebParts (GUID ID ONLY) will require reinstallation within the SharePoint 2010 environment. 09e df-f82e-8c39-01bf8ae2e24e 11

12 . 2adbd0af-a82e eca fa66 45e03caa c11a-df76637ba43a f88-81dc-d409-3bdd144a7761 5e5d1080-9dbd-578a-0d4e- 66b150ab41c c63-514d-a645-2d07-7acdc39542b a3e ba-ac9d- 196badd9e7a c99-5be1-720f-8d0f-8b239c8ec312 a9b17c0e-bfa a-9bf895d25620 ccee27f1-18c5-a884-12aa-a86876b33efc d08d e5bc-7bf9-7a24bcf299d0 d4321bbd-3f43-e3f5-4a38-97d4359facd1 d5b87c63-ca6e-20a3-1e72-36fcf8f196f0 e bbfe-501f-fda7a61db10f ec42527d-d328-ad15-a04c-64a39f8fbe99 Note: We have tools to identify the WebPart Name. Assemblies That Require Reinstallation The following Custom Code Assemblies will require reinstallation within the SharePoint 2010 environment. KnowledgeBaseEventHandler, Version= , Culture=neutral, PublicKeyToken=71e9bce111e9429c KWizCom.SharePoint.Features.SLFEFeature, Version= , Culture=Neutral, PublicKeyToken=30fb4ddbec95ff8f KWizCom.SharePoint.FieldControls.DualLookupType,Version= ,Culture=neutral,PublicKeyToken=30fb4ddbec9 Microsoft.SharePointTraining.Features, Version= , Culture=neutral, PublicKeyToken=37f7dd f9 ReservationEventHandler, Version= , Culture=neutral, PublicKeyToken=71e9bce111e9429c ResourceEventHandler, Version= , Culture=neutral, PublicKeyToken=71e9bce111e9429c Web Templates That Require Reinstallation The following Web Templates will require reinstallation within the SharePoint 2010 environment. [STSADM] [SPContentDatabaseSequence] [WARNING] [12/14/2010 3:25:12 PM]: WebTemplate ID (lcid: 1033 [STSADM] [SPContentDatabaseSequence] [WARNING] [12/14/2010 3:25:12 PM]: WebTemplate ID (lcid:

13 [STSADM] [SPContentDatabaseSequence] [WARNING] [12/14/2010 3:25:13 PM]: WebTemplate ID (lcid: 1033 [STSADM] [SPContentDatabaseSequence] [WARNING] [12/14/2010 3:25:13 PM]: WebTemplate ID (lcid: 1033 [STSADM] [SPContentDatabaseSequence] [WARNING] [12/14/2010 3:25:13 PM]: WebTemplate ID (lcid: 1033 [STSADM] [SPContentDatabaseSequence] [WARNING] [12/14/2010 3:25:13 PM]: WebTemplate ID (lcid: 1033 [STSADM] [SPContentDatabaseSequence] [WARNING] [12/14/2010 3:25:13 PM]: WebTemplate ID (lcid: 1033 [STSADM] [SPContentDatabaseSequence] [WARNING] [12/14/2010 3:25:13 PM]: WebTemplate ID (lcid: 1033 Custom Views That Will Require Rebuilding The following views will require manual rebuilding within the SharePoint 2010 environment. **** Too Many To List **** Please refer to Appendix. Custom Fields That Will Require Development The following fields will have to be manually created to support the custom lists they are associated with. Custom Field HoldsField HoldStatusField HTML Image Link SummaryLinks LayoutVariationsField ContentTypeIdFieldType BusinessData TargetTo Field Detail HoldsField(Hold Status) HoldStatusField(Hold Status) HTML(Publishing HTML) Image(Publishing Image) Link(Publishing Hyperlink) SummaryLinks(SummaryLinks) LayoutVariationsField(Variations) ContentTypeIdFieldType(Content Type ID) BusinessData(Business data) TargetTo(Audience Targeting) Large Lists That Will Require Manual Upgrade The following Large Lists will require additional manual upgrade work. Shared Documents Document Workflow History Hi Budget Planning Planning 2010 [11566 Item HelpFold [5804 Items] 13

14 . Proposed Project Phases Time Line of Activity Note that the Test and Production infrastructures are already in place for SharePoint The following phases assume they are ready to go. Phase 1: Migrate to Test - This has been already done once and is ready for additional work detailed above. - Where possible, automate the post migration changes that were determined to be necessary. Phase 2: Department Site Owner / End User Training Phase 3: Migrate to Production - Re-implement the step by step post migration changes that were determined as required during Phase 1. Phase 4: Production Customization - Re-introduce YEC look and feel where possible. - Move Departments to individual Site Collections for better security and scalability Phase 5: End User Training Sessions 14

15 Report Summary We believe this report highlights some of the major challenges that YEC faces going forward with the migration of SharePoint 2007 to SharePoint The report is meant as a stepping stone for further planning and consideration. Above all, we want to emphasize to YEC Management that this project is not a simple slam dunk and that is because of the major amount of customization that has taken place over the past four years that the current SharePoint environment has been in place. End Of Report 15

16 Appendix A:. SharePoint 2010 extended migration db attach report One of the most popular ways to migrate SharePoint from 2007 to 2010 is probably using the Database Attach method. If you have ever tried this kind of approach you will notice that there is a lack of informations in what customizations have been made in the old SharePoint 2007 farm that needs to be migrated. Using SharePoint's Windows PowerShell cmdlet is possible to test a database attach before performing the attach: Test-SPContentDatabase -Name <database name> -WebApplication< URL> This tool display on your screen a report that shows basic informations about all issues that this approach will have. Until you don't solve all the Issues, you should not proceed with the database attach. Unfortunately you won't obtain informations on where certain issues are located: Missing features will be displayed just as a GUID Missing webparts will be displayed just as GUID This means that you won't be able to located them so easly and port them on SharePoint Until now! SharePoint 2010 extended migration db attach report is able to parse this report and generate and extended version for each issue! A MissingFeature Issue will become from Category : MissingFeature Error : True UpgradeBlocking : False Message : Database [xxxx] has reference(s) to a missing feature: Id = [xxxxxx]. Remedy : The feature with Idxxxxxx is referenced in the database [xxxx], but... Will be transformed in Feature definition: < Feature xmlns=" Id="F5DF760A- EAA5-428b-912D-0BC0D361F771" Title="Feature Title" Description="Feature Desc" Version=" " Scope="Site" Hidden="false" ImageUrl="Folder\icon.png"> < ElementManifests> < ElementManifest Location="Location.xml" /> < /ElementManifests> < /Feature> Feature scope: Site Installed Url: 16

17 Feature Id: xxxxxx And a MissingWebPart issue like Category : MissingWebPart Error : True UpgradeBlocking : False Message : WebPart class [xxx] is referenced [3] times in the database xxxx], but is not installed on the current farm... Will be transfomed in: WebPart Details: CustomWebPart WebPart name: CustomWebPart WebPart Type name: CustomWebPart.namespace Assembly Name: CustomWebPartAssembly, Version= , Culture=neutral, PublicKeyToken= dcd8080b491 WebPart Id:: xxx This wep part can be located in the following pages: SubSite/default.aspx SubSite1/subsite/page.aspx One of the most popular ways to migrate SharePoint from2007 to 2010 is probably using the Database Attach method. If you have ever tried this kind of approach you will notice that there is a lack of informations in what customizations have been made in the old SharePoint 2007 farm that needs to be migrated. Using SharePoint's Windows PowerShell cmdlet is possible to test a database attach before performing the attach: Test-SPContentDatabase -Name <database name> -WebApplication <URL> This tool display on your screen a report that shows basic informations about all issues that this approach will have. Until you don't solve all the Issues, you should not proceed with the database attach. Unfortunately you won't obtain informations on where certain issues are located: Missing features will be displayed just as a GUID Missing webparts will be displayed just as GUID This means that you won't be able to located them so easly and port them on SharePoint Until now! SharePoint 2010 extended migration db attach report is able to parse this report and generate and extended version for each issue! 17

18 . A MissingFeature Issue will become from Category : MissingFeature Error : True UpgradeBlocking : False Message : Database [xxxx] has reference(s) to a missing feature: Id = [xxxxxx]. Remedy : The feature with Idxxxxxx is referenced in the database [xxxx],but... Will be transformed in Feature definition: <Feature xmlns=" Id="F5DF760A-EAA5-428b-912D-0BC0D361F771" Title="Feature Title" Description="Feature Desc" Version=" " Scope="Site" Hidden="false" ImageUrl="Folder\icon.png"> <ElementManifests> <ElementManifest Location="Location.xml" /> </ElementManifests> </Feature> Feature scope: Site Installed Url: Feature Id: xxxxxx And a MissingWebPart issue like Category : MissingWebPart Error : True UpgradeBlocking : False Message : WebPart class [xxx] is referenced [3] times in the database xxxx], but is not installed on the current farm... Will be transfomed in: WebPart Details: CustomWebPart WebPart name: CustomWebPart WebPart Type name: CustomWebPart.namespace Assembly Name: CustomWebPartAssembly, Version= , Culture=neutral, PublicKeyToken= dcd8080b491 WebPart Id:: xxx This wep part can be located in the following pages: SubSite/default.aspx SubSite1/subsite/page.aspx 18

19 How to generate the Extended Migration db attach report The most important thing to know about this tool is that it needs to be run in the old SharePoint 2007 farm to be able to retrieve all necessary data using the SharePoint's Object model. This are the required steps to run the tool correctly: Back up and restore the SiteCollection'sdatabase into SharePoint 2010's database server For help: Run the powershell comand Test-SPContentDatabase to generate the input report For help: Copy the c:\report.txt file in the SharePoint 2007 farm Run the executable by passing the c:\report.txt file as an input parameter When executing the last command, the tool will connect to the SharePoint's Database where the site's collection content db is located and perform a simple select to obtain information on where custom web part's are deployed. For this reason the job should run with necessaries privileges. Browse the app.config in the source code if you are wondering what kind of query is used. The following figure should clarify this process (click the image to see it at the actual size). 19

20 . Once the new report has been created, open the report.txt file to get all the informations that you were waiting for :) Here is an example of a generated report: =============================================== Report started at 28/09/2010 9:23:56 PM =============================================== ############################### ### Feature Report ### ############################### [Informations] -> 3 Feature issues have been parsed from imput file. -> 85 Feature have been found into your content db -> 3 Features have been analized Feature definition: <Feature xmlns=" Id="367B94A9-4A15-42BA-B4A E018" Title="Report Server Integration Feature" Description="Enables rich reporting using Microsoft SQL Server Reporting Services." Version=" " Scope="Site" 20

21 ReceiverAssembly="Microsoft.ReportingServices.SharePoint.UI.ServerPages,Versi on= , Culture=neutral,PublicKeyToken=89845dcd8080cc91" ReceiverClass="Microsoft.ReportingServices.SharePoint.UI.ReportServerFeature" > <ElementManifests> <ElementManifest Location="ItemCustomActions\ecbExtension.xml" /> <ElementManifest Location="AdminUI\AdminUIEntryPoints.xml" /> <ElementManifest Location="WebPartsElements.xml" /> <ElementManifest Location="ReportServerContentTypes.xml" /> </ElementManifests> </Feature> Feature scope: Site Installed Url: Feature Id: 367b94a9-4a15-42ba-b4a e018 Feature definition: <Feature Id="bcb59ac1-e1b6-49d0-a91b-9dc99b837c23" Title="My Custom Feature" Description="My Custom Dec!" Version=" " Hidden="FALSE" Scope="Site" DefaultResourceFile="core" xmlns=" <ElementManifests> <ElementManifest Location="elements.xml" /> <ElementFile Location="CustomWebPart.webpart" /> </ElementManifests> </Feature> Feature scope: Site Installed Url: Feature Id: bcb59ac1-e1b6-49d0-a91b-9dc99b837c23 Feature definition: <Feature Id="9b5429f0-b21e-4590-b44d-a a" Title="Super Custom Feature" Description="This is a super Feature" Version=" " Hidden="FALSE" Scope="Site" DefaultResourceFile="core" xmlns=" <ElementManifests> <ElementManifest Location="elements.xml" /> <ElementFile Location="SuperWebPart.webpart" /> </ElementManifests> </Feature> Feature scope: Site Installed Url: Feature Id: 9b5429f0-b21e-4590-b44d-a a ############################### ### WebParts Report ### ############################### [Informations] -> 5 WebParts issues have been parsed from imput file. 21

22 . -> 68 WebParts have been found into your content db -> 3 WebParts have been analized ============================================================== [WebPart : CustomWebPart] ============================================================== WebPart Details: MasterDetailWebPartProps WebPart name: CustomWebPart.webpart WebPart Type name: Dev4Side.Sample.CustomWebPart Assembly Name: Dev4Side.Sample, Version= , Culture=neutral, PublicKeyToken= WebPart Id:: 6b78009e-a658-61f4-9c66-b04fdde52e77 This wep part can be located in the following pages: Site1/SubSite2/deafault.aspx Site2/SubSite2/Hello.aspx Site2/SubSite2/Help.aspx ============================================================== [WebPart : ReportViewer] ============================================================== WebPart Details: ReportViewer WebPart name: ReportViewer WebPart Type name: Microsoft.ReportingServices.SharePoint.UI.WebParts.ReportViewerWebPart Assembly Name: Microsoft.ReportingServices.SharePoint.UI.WebParts, Version= , Culture=neutral, PublicKeyToken= WebPart Id:: 7e287d59-ae e52a-6420e81ddc91 This wep part can be located in the following pages: Site3/SubSite5/Pages/Budget.aspx Site2/Pages/Reports.aspx Site2/Stats/default.aspx ============================================================== [WebPart : SuperWebPart] ============================================================== WebPart Details: SuperWebPart WebPart name: SuperWebPart WebPart Type name: Dev4Side.Sample.SuperWebPart Assembly Name: Dev4Side.Sample, Version= , Culture=neutral, PublicKeyToken=eaf58ff25bb059f9 WebPart Id:: 2c7df9ff-d5ea-f4e5-d3b4-be74bfc883b4 This wep part can be located in the following pages: Pages/super.aspx ############################################################################ ############### the following web parts could not be analized ############## ############################################################################ ============================================================== [WebPart : a20f6f5f-8aa d-05616d2e2777] ============================================================== 22

23 This web part can be located in the follwoing urls: Site/somewhere/default.aspx Site/somewhereElse/default.aspx Site3/somewhere/default.aspx ============================================================== [WebPart : aa bab4-74a6-5ef6-10cc54c1dcb2] ============================================================== This web part can be located in the follwoing urls: Site5/somewhere/default.aspx Site2/SubSite2/somewhere/default.aspx =============================================== Report ended at 28/09/2010 9:24:02 PM =============================================== 23