Blogger Templates


Main Difference of SharePoint Migration( 2007 to 2010 and 2010 to 2013)

Instead, you attach a 2010 content database to the 2013 farm. You have the option of retaining the content database as a 2010 content database and to perform what is called a “deferred site collection upgrade.” In essence, this means that the 2010 site collection continues to be a 2010 site collection, just running on a 2013 farm. This is very different than the “visual upgrade” from 2007 to 2010. When you upgraded from 2007 to 2010, the site was upgraded, which meant you had to ensure compatibility. But a master page and other trickery made the site retain the appearance of a 2007 site. In 2013, that option no longer exists. Instead, the 2013 farm retains the 2010 “14 Hive”—with all of its features, site definitions, etc.
So, in theory, all of your 2010 sites will work perfectly well, customization included, in 2013. When you perform a deferred site collection upgrade, you are conceptually “flipping the switch” so that the site collection now runs against the “15 hive”. That is when compatibility might matter.
So, keeping this very high level, the theory is that you could upgrade your farm this weekend to 2013, and your users would be none the wiser. That’s certainly the type of platform upgrade path that Microsoft wants and needs in the cloud (Office 365).
We will see, shortly, just how well it works in the real world. But my guess is we will be much closer to a happy story than to an unhappy story. And, obviously, you will want to test the upgrade process before you actually perform it. But the bottom line is that we’re close to a point where upgrading the platform will become a non-issue, a very minor issue, or at least not a multi-month, insane project.
Because you are likely going to find that you can upgrade smoothly, you can move collaboration workloads from 2010 to 2013 quickly, or implement plans for 2010 in 2013 instead, as 2013 still supports 2010-style customization, workflows, etc.
You can learn more about upgrading to SharePoint 2013 in the Reference Link. As with all other upgrades, there’s no direct upgrade path from 2007 or earlier versions of SharePoint to 2013. You either have to go through 2010 on the way, or use a third party tool. And—knowing that you probably did things in 2007 that you would not choose to do the same way in 2013—I’d strongly recommend a good third party migration tool.
This should give you plenty to chew on for the next few days. Next week, we’ll look at some of the reasons people give me for not moving to SharePoint 2013, including the infamous “we always wait for Service Pack 1” argument. So this discussion is definitely not finished. See you next week!

SharePoint 2010 to 2013 Upgrade Overview

To upgrade from SharePoint 2010 Products to SharePoint 2013, you use the database-attach method to upgrade. In the database-attach method, you first create and configure a SharePoint 2013 farm. Then you copy the content and service application databases from the SharePoint 2010 Products farm, and then attach and upgrade the databases. This upgrades the data to the new version. Site owners can then upgrade individual site collections.
Figure: The sequence of upgrade stages
Stages in upgrade process for SharePoint 2013
Note: This article applies to both SharePoint Foundation 2013 and SharePoint Server 2013, except for information about how to upgrade My Sites and specific service applications that are only in SharePoint Server 2013.
Create the SharePoint 2013 farm
The first stage in the upgrade process creates the new SharePoint 2013 farm:
  1. A server farm administrator installs SharePoint 2013 to a new farm. The administrator configures farm settings and tests the environment.
  2. A server farm administrator sets the SharePoint 2010 Products farm to read-only so that users can continue to access the old farm while upgrade is in progress on the new farm.
    Figure: Create new farm, set old farm to read-only
    Create new farm, set old farm to read-only

Copy the SharePoint 2010 Products databases

The second stage in the upgrade process copies the databases to the new environment. You use SQL Server Management Studio for these tasks.
  1. With the farm and databases in read-only mode, a server farm administrator backs up the content and service application databases from the SQL Server instance on the SharePoint 2010 Products farm.
  2. The server farm administrator restores a copy of the databases to the SQL Server instance on the SharePoint 2013 farm and sets the databases to read-write on the new farm.
    Figure: Use SQL Server tools to copy databases
    Use SQL Server tools to copy databases

Upgrade SharePoint 2010 Products databases and service applications

The third stage in the upgrade process upgrades the databases and service applications.
  1. A server farm administrator configures the service applications for the new farm. The following service applications have databases that you can upgrade during this process:
    • SharePoint Server 2010 and SharePoint Foundation 2010
      • Business Data Connectivity service application
    • SharePoint Server 2010 only
      • Managed Metadata service application
      • PerformancePoint Services service application
      • Search service application
      • Secure Store Service application
      • User Profile service application
  2. A server farm administrator creates a web application on the SharePoint 2013 farm for each web application on the SharePoint 2010 Products farm.
    Figure: Create web applications for upgrade
    Create Web applications for upgrade
  3. A server farm administrator installs all server-side customizations.
    Figure: Copy customizations to the new farm
    Copy customizations to new farm
  4. A server farm administrator then attaches the content databases to the new farm and upgrades the content databases for those web applications.
    Figure: Upgrade the databases by using Windows PowerShell
    Upgrade the databases with Windows PowerShell
  5. A server farm administrator confirms that the upgrade is successful.

Upgrade SharePoint 2010 Products site collections

The final stage in the upgrade process is to upgrade the site collections. In SharePoint 2013, site owners are in charge of upgrading their sites. The upgrade process for My Sites is slightly different from for other types of site collections.

Upgrade My Sites

Note: This section applies to SharePoint Server 2013 only.

A server farm administrator upgrades the My Site host and then individual users can upgrade their My Sites or the farm administrator can upgrade them by using Windows PowerShell. The following illustration shows four stages for the My Site host and My Sites during the upgrade process.
Figure: Stages in upgrading My Sites
Stages in upgrading My Sites
  1. The My Site host has not been upgraded. My Sites cannot be upgraded yet.
  2. A server farm administrator has upgraded the My Site host. No My Sites have been upgraded.
  3. Some users have upgraded their My Sites.
  4. All My Sites have been upgraded.

Note: A server farm administrator can choose to force an upgrade of My Sites without waiting for users to upgrade them.

Upgrade other SharePoint 2010 Products site collections

Owners of all other site collections can start to upgrade their sites as soon as they see a notification on their site's home page that the new version is available. The following illustration shows four stages for a site collection during the upgrade process.
Stages in upgrading site collections
Stages in upgrading site collections
  1. The site owner runs the site collection health checks to determine readiness for upgrade. The site owner addresses issues before they continue with the next step.
  2. Optionally, the site owner requests an upgrade evaluation site collection. A timer job runs to create the site collection and the site owner receives an email message when the evaluation site collection is ready. The site owner previews the new user interface. After several days or weeks, the evaluation site collection expires and is deleted by a timer job.
    A server farm administrator can determine the length of time before expiration.
  3. When the site owner is ready, the site owner starts the upgrade process. The site collection health checks are run again automatically. The site owner must address issues before upgrading. If health checks return no issues, the upgrade starts.
  4. When upgrade is complete, the site owner sees the Upgrade Status page that contains the status and a link to the upgrade logs. The site owner reviews the site to make sure that everything works correctly.

Java Script For Page Referesh

You can also use JavaScript to refresh the page automatically after a given time period. Following is the example which would refresh this page after every 5 seconds. You can change this time as per your requirement.

<script type="text/JavaScript">
function AutoRefresh( t ) {
 setTimeout("location.reload(true);", t);
//   -->
<body onload="JavaScript:AutoRefresh(5000);">
<p>This page will refresh every 5 seconds.</p>

Here setTimeout() is a built-in JavaScript function which can be used to execute another function after a given time interval.

To understand it in better way you can Try it yourself.

Sharepoint - The search request was unable to connect to the Search Service.

Follow the below methods:

Central Admin -> Service Applications ->Manage service applications make sure your search service application is running with a proxy just below it. If not, likely because you did a backup and the proxy requires a second backup, from the ribbon select New -> Search Service Application.

Once created successfully go to CA -> Web Applications -> Manage web applications. Highlight the sharepoint port 80 site and select Service Connections. Make sure your new proxy is selected.

Then under CA -> Application Mgmt -> Manage services on server select Sharepoint Server Search select the new service you setup and make sure the topology looks ok. Then schedule and start a new Full crawl. All set.


Don't forget to add the pdf file type if you've set that up under the old search app before.

Central Admin > Application Management > Office SharePoint Server Shared Services > Create or Configure this farm’s shared services
Shared Services Provider (drop down) > Edit Properties
Edit Shared Services Provider > Index Server: Verify the index server is set

Single Server Farm

On the MOSS 2007 server:

Start > Run > CMD > stsadm.exe -o osearch -action stop
Start > Run > CMD > stsadm.exe -o osearch -action start -role query index

Multiple Server Farm

On the MOSS 2007 Front End Web/Query server:

Start > Run > CMD > stsadm.exe -o osearch -action stop

On the MOSS 2007 Index server:

Start > Run > CMD > stsadm.exe -o osearch -action stop

On the MOSS 2007 Index server:

Start > Run > CMD > stsadm.exe -o osearch -action start -role index

On the MOSS 2007 Front End Web/Query server:

Start > Run > CMD > stsadm.exe -o osearch -action start -role query

Go to Central Admin ->Operations ->Topologies and services ->Services on server
Click “Office SharePoint Server Search”
Make sure the user has sufficient permission to access database.
Note: If your Search query and indexing server are same then set both options “Use this server for indexing content” and “Use this server for serving search queries” to true.

What is page redirection ?

When you click a URL to reach to a page X but internally you are directed to another page Y that simply happens because of page re-direction. This concept is different from JavaScript Page Refresh.
There could be various reasons why you would like to redirect from original page. I'm listing down few of the reasons:
  • You did not like the name of your domain and you are moving to a new one. Same time you want to direct your all visitors to new site. In such case you can maintain your old domain but put a single page with a page re-direction so that your all old domain visitors can come to your new domain.
  • You have build-up various pages based on browser versions or their names or may be based on different countries, then instead of using your server side page redirection you can use client side page redirection to land your users on appropriate page.
  • The Search Engines may have already indexed your pages. But while moving to another domain then you would not like to lose your visitors coming through search engines. So you can use client side page redirection. But keep in mind this should not be done to make search engine a fool otherwise this could get your web site banned.

How Page Re-direction works ?

Example 1:

This is very simple to do a page redirect using JavaScript at client side. To redirect your site visitors to a new page, you just need to add a line in your head section as follows:
<script type="text/javascript">
To understand it in better way you can Try it yourself.

Example 2:

You can show an appropriate message to your site visitors before redirecting them to a new page. This would need a bit time delay to load a new page. Following is the simple example to implement the same:
<script type="text/javascript">
function Redirect()

document.write("You will be redirected to main page in 10 sec.");
setTimeout('Redirect()', 10000);
Here setTimeout() is a built-in JavaScript function which can be used to execute another function after a given time interval.
To understand it in better way you can Try it yourself.

Example 3:

Following is the example to redirect site visitors on different pages based on their browsers :
<script type="text/javascript">
var browsername=navigator.appName; 
if( browsername == "Netscape" )
else if ( browsername =="Microsoft Internet Explorer")

Keep on prompting for credential

  To save your SharePoint password:
  1. Add the SharePoint site to the Local Intranet Zone in Internet Explorer. To do this, go to Tools > Internet Options > Security. In Local Intranet, click the Sites button and then Advanced.
  2. Add your SharePoint URL. Click Ok.
  3. Go to Start > Run and type in "control keymgr.dll’" to open the Windows key manager.
  4. Add <your_sharepoint_site_address> with your SharePoint site login credentials. If this entry already exists, edit it to have your login credentials. 
    • For Vista users, when using the key manager, make sure you select "A Web site or Program credentials" for the type of password, and if prompted to change your password, say "no" (unless you want to change your password).
  5. Enter your password and click OK.
  6. Reboot the computer.
If you are missing the Add button, you may want to modify Windows Registry to be able to save the password. Note that for editing Windows Registry, administrator rights are required. Editing Windows Registry is not safe and you will perform it at your own risk.
  1. In Windows, go to Start > Run and enter "regedit".
  2. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\.
  3. Find the DisableDomainCreds entry. A value of 1 (enabled) will prevent you from saving new credentials.
    Change the value to 0 and reboot. Now you should have the Add button available. Note that 0 is the default value.
  4. Also check the LmCompatibilityLevel entry. It should be set to 3, which is the default value. If you have another value, change it to 3. If it does not work with 3, then also try it with 2.
  5. Reboot the computer to apply changes.