Monday, July 25, 2011

Upgradation/migration steps for SharePoint 2010

Here in this article, I am going to explain steps for migrating contents from MOSS 2007 to SharePoint 2010 with "Database attach" method. You can find more detail information from below reference links.

1. Select any MOSS 2007 site for migration
2. Go to SQL Server Management studio and take backup of MOSS 2007 site database.
3. Move database backup file to SharePoint 2010 server manually.
4. Create blank Database from SQL Server Management studio into SharePoint 2010 server.
5. Restore MOSS 2007 backup file (step # 3) to newly created database into SharePoint 2010 server (make sure to select 'overwrite the existing database' option)

Some time if we are getting below error in SQL Server while restoring database then we need to try to perform same steps again and again for some more time. {Detach database, attach database, restore database}

Restore failed for Server “database server name”.  (Microsoft.SqlServer.SmoExtended)
The backup set holds a backup of a database other than the existing 'database” database.
RESTORE DATABASE is terminating abnormally. (Microsoft SQL Server, Error: 3154)

6. Create new web application and site collection into SharePoint 2010 server.
7. Delete content database of newly created web application from going to SQL Server Management studio.
8. Add/Attach step # 5 database to new web application by below command

stsadm -o addcontentdb -url yourWebApplicationUrl -databasename yourDatabasename -databaseserver yourdatabaseServerName

9. After successful upgrade, it will generate upgrade log file which contains missing features, web parts names and other information which failed during upgrade.
10. Check migrated SharePoint 2010 site about data and pages.
11. Open web application settings from central admin to change site collection admin name (if source and destination web application have different user names)
12. If we want to see SharePoint 2010 look and feel in migrated site then we need to change visual upgrade from site settings (update all sites which make interface same like SharePoint 2010) – actually when we migrated site from MOSS 2007 to SharePoint 2010, at that time we have different master page in MOSS. In SharePoint 2010 system is using v4.master page.

Some points about how to verify migrated SharePoint 2010 site
1. Navigation links are coming correctly or not
2. Custom Image are not coming properly or not
3. Documents are migrated with its Meta data or not like uploaded and modified date/time stamp
4. Sub-site data are migrated with as it is navigation option or not (suppose if we have tree structure enable in source MOSS 2007 site then after migration it suppose to come with tree structure navigation only)

Perform pre-upgrade steps for SharePoint 2010:

Different Upgrade Methods in SharePoint 2010:

MSDN SharePoint 2010 upgrade reference Links:

Very good link which describes about migrating to SharePoint 2010:

Other reference links:

Microsoft Visio 2010 – SharePoint 2010

Here I have tried to give some basic explanation about Visio 2010 and how it’s being use in new SharePoint 2010 world.

  • Visio 2010 has its own template called “Microsoft Sharepoint Workflow”
  • Visio 2010 has its own SharePoint workflow activities i.e. Actions, conditions, terminators
  • We can check Visio diagram for validation errors.
  • After completing Visio workflow, we can export workflow to “Visio workflow interchange” format to import the same workflow into Sharepoint Designer 2010.
  • We can import Visio workflow to designer, than we need to assign/attach workflow to any of the content types in site like document, item.
  • For workflow activities, we need to change/modify from designer like collect data activity.
  • We can publish workflow to globally or list level.
  • From workflow settings page, we can have option to see workflow visualization on status page, this is new feature added in SharePoint 2010 from which we can actually see and visual workflow current stage.
  • After publishing workflow, system will generate association, initialization and data collection InfoPath forms which used by workflow
  • From SharePoint site, we can go into any list and select content type to attach workflow to list level. (we can have workflow at content type level too)
  • We can see workflow status in workflow visualization section and also able to open same Visio diagram and changed into it.
  • We can save workflow as "template" and use same template into visual studio projects.
  • In Visio we can only make the actual design of the workflow, not the configuration which is done in SharePoint Designer 2010

Reference Link:

Part 1:

Part 2:

PowerPoint Broadcast site – SharePoint 2010

Some basic concept related to new feature - PowerPoint broadcast site

  • Its new service in SharePoint 2010 which will allow user to broadcast presentation online (it is same like if we are giving webex/NetMeeting session) in which we have presenter and attends for each online meeting.
  • We can see “broadcast this PowerPoint” as one of the option in PowerPoint 2010.
  • For broadcasting any PowerPoint we need to have PowerPoint broadcast service enabled into any site.
  • We can create PowerPoint broadcast site from central admin site collection and that site URL we can use in PowerPoint 2010 for broadcasting any PowerPoint file.
  • We need to add presenter and attends users into sharepoint group for them to see broadcast.

Friday, July 22, 2011

How to install Office web app for SharePoint 2010

  • Office Web Apps is an online version of Microsoft Word, Excel, PowerPoint and OneNote application, which allowing users to access these all Microsoft applications and their respective documents from any Internet connection and any web browsers.
  • It is same like Google documents; in which we don’t require to have Microsoft application installed on our local desktop to browse/access any Google documents from internet.
  • Once we successfully deploy Office Web Apps on SharePoint farm, it will add the following service applications into farm.

    • Word Viewing Service Application
    • Excel Calculation Service
    • PowerPoint Service Application

How to configure PDF search in SharePoint 2010

By default SharePoint won’t search PDF contents in any SharePoint site (same like MOSS 2007)

So we need to install Adobe iFilter on server and follow configuration steps as per below link to able to successfully crawl and search PDF documents and contents.

Installation of SharePoint 2010 on stand alone machine

Overall steps:
1) Run SharePoint.exe for SharePoint 2010
2) Install pre-requisite from menu option
3) Restart the computer
4) Enter the product key for SharePoint 2010
5) Select standalone or server farm for installation and follow the Microsoft pattern installation wizard.
6) After successful installation, system will ask to create default web site at port 80 (central admin site is created automatically based on the setting we choose during installation)

How to Install PowerPivot for SharePoint on an Existing SharePoint Server

I have followed this Microsoft MSDN Link for PowerPivot installation. Believe me its very good link, it has good amount of information, I have followed same steps and able to successfully installed PowerPivot on server.

Here are brief points which needed for PowerPivot installation.

Prerequisites: we need to have server farm installation on SharePoint 2010 server to install Powerpivot.

Overall Steps:

1) Run SQL Server 2008 R2 setup to add “PowerPivot for SharePoint” to Sharepoint farm.
  • During installation, select “new installation/add features” option.
  • Select “SQL Server Powerpivot for SharePoint” option.
  • As per the requirement, select “Add Powerpivot for SharePoint - existing farm”.
  • Complete the Powerpivot installation from SQL Server install file by following installation wizard.

2) Deploy the PowerPivot Solution Package from central admin to respective web application
  • There are two separate solution packages: powerpivotfarm.wsp and powerpivotwebapp.wsp. The first solution (powerpivotfarm.wsp) is deployed when we install the first PowerPivot for SharePoint instance and never needs to be deployed again. The second solution (powerpivotwebapp.wsp) is deployed for Central Administration, but we must need to deploy this solution manually for each SharePoint web application that will support PowerPivot data access

3) Start Services on the Server:
  • Start the Claims to Windows Token Service.
  • Start Excel Calculation Services.
  • Start Secure Store Service.

4) Verify that both SQL Server Analysis Services and SQL Server PowerPivot System Service are started.

5) Create a PowerPivot Service Application (SQL Server PowerPivot Service Application) from Manage service applications option.

6) Enable Excel Services

7) Enable Secure Store Service and Configure Data Refresh

8) Configure the Unattended PowerPivot Data Refresh Account

9) Configure Usage Data Collection

10) Activate PowerPivot Feature Integration for Site Collections

How to verify Installation:
1) In Libraries, we can see new options called “Data Feed Library” and “PowerPivot Gallery”. These library templates are provided by the PowerPivot feature and will be visible in the Libraries list if the feature is integrated correctly.

2) We can create sample excel book which has PowerPivot data and upload same excel into "PowerPivot gallery" library to check about PowerPivot features working fine or not.

NOTE: Once we create/upload any PowerPivot excel book into "PowerPivot gallery" library, behind the scene system is creating separate database for uploaded excel book (we can check this thing by going to SQL Server Management studio and select Analysis Services and in Server Name, need to enter <server-name>\powerpivot to see created database)

We can create PowerPivot data from Excel 2010, if we are not able to see "PowerPivot" as one of the option in excel 2010 ribbon, and then we need to install Add-ins PowerPivot for Excel 

Enjoy in installation!