Wednesday, December 17, 2014

different types errors in websites

different types errors in websites
Here they are, listed and explained in reverse order, the five most common HTTP errors. Drumroll, please…

5. HTTP error 401 (unauthorized)
This error happens when a website visitor tries to access a restricted web page but isn’t authorized to do so, usually because of a failed login attempt.

4. HTTP error 400 (bad request)
This is basically an error message from the web server telling you that the application you are using (e.g. your web browser) accessed it incorrectly or that the request was somehow corrupted on the way.

3. HTTP error 403 (forbidden)
This error is similar to the 401 error, but note the difference between unauthorized and forbidden. In this case no login opportunity was available. This can for example happen if you try to access a (forbidden) directory on a website.

2. HTTP error 404 (not found)
Most people are bound to recognize this one. A 404 error happens when you try to access a resource on a web server (usually a web page) that doesn’t exist. Some reasons for this happening can for example be a broken link, a mistyped URL, or that the webmaster has moved the requested page somewhere else (or deleted it). To counter the ill effect of broken links, some websites set up custom pages for them (and some of those are really cool).
And the most common HTTP error of all is……….

1. HTTP error 500 (internal server error)

The description of this error pretty much says it all. It’s a general-purpose error message for when a web server encounters some form of internal error. For example, the web server could be overloaded and therefore unable to handle requests properly.

Wednesday, December 10, 2014

SharePoint site suddenly Read Only even for Administrators!

So at some point in time something had happened to our SharePoint 2010 server to cause what appeared to be a total lock down on the SharePoint sites.
It must have been something strange, something weird, who knows what but it resulted in is ALL users, even site administrators and users with full administrative rights unable to do anything!  Nobody could add new documents or edit documents; nearly every single Document or Library option is greyed out!
The fix it would seem is performed via the central administration website for your server.
  1. Central Administration -> Site Collection Quotas and Locks.
  2. Select your site collection
  3. Change the Site Lock Information radio button from “Read-only” to “Not locked”
  4. OK the changes
 SharePoint 2010 Central Administration Site Collection Quotas and Locks Read-only
You don’t even need to reboot or issue an iisreset command.

SharePoint 2010 Service Account Password Change

My SharePoint Farm has multiple application pools including SharePoint Services running.
And each Application Pool is running on different service account.

To check which application pool is running using which service account.

Go to Run >> Type inetmgr. This will open Internet Information Services Manager.

Click on Application Pool and you can see Identity of Application pool which is Service account.
Add caption

When we create Application Pool or Application Service and choose new service application pool account, this account

get registered to Manage Accounts under Security.

Path will be Central Administration >  Security > Manage Accounts

We can see here are all service accounts are registered.

If you want to Check password of service account you can check using PowerShell command.

Open Windows PowerShell Module from All Application Program.

type below PowerShell Command.

Get-WmiObject –Namespace root/MicrosoftIIsV2 –Class IIsApplicationPoolSetting –Property Name, WAMUserName, WAMUserPass | Select Name, WAMUserName, WAMUserPass

and it will show all passwords of particular service account name.


This will help you in case you forget your AppPool Service Account password.

Now, we will change password of service account which is running a web application name Tesst – 

And you can see
the service account name is spdev\testpass and password is P@ssw0rd3

For changing password of spdev\testpass  go to Central Administration > Security > Manage Accounts
look for spdev\testpass and edit.

Now check box named Change Password Now and select Set account password to new value.
enter new password and click on ok.

To confirm password is changed or not you can run above PowerShell script.


Install and Configure SharePoint Server 2013 step by step

Install and Configure SharePoint Server 2013 step by step
In this blog post I am covering all basic required steps of
SharePoint 13 installation. And have divided this in 4 parts.

1) Install Windows Server 2012 and Active Directory configuration.

2) Install SQL Server 2012.

3) Install and configure SharePoint Server 2013 .

4) Configure SharePoint Server Service Applications

Managed Metadata Service Application
Search Service Application
User Profile Service Application
5) Create your first web application on SharePoint Server 2013.

Installation and configuration of Windows Server and SQL server
have done more specific to build SharePoint Server farm prospective.

For example, Permissions given to Service accounts during
installation of windows server. Installation of SQL server and SharePoint Server have done by

specific service account.
If you have any query, please post comment.


Tuesday, December 9, 2014

Hands-On-Lab: Configuration Managed Metadata Service Application

Applies to: SharePoint Server 2013

Summary: Metadata actually plays a very critical role across the organization.
When we want to identify any specific information, we tag the information. We always begin with a Term. Term is any phrase or a word given to identify
specific content or information on a site. Metadata plays very critical role in defining a strict policy of tagging items
based on specific terms only which will internally help people to find and locate the information easily when they search any content specific to their area
of interest. When any items tagged properly, then the search becomes very easy.

• Logged in as a Farm Administrator account on the SharePoint Server
• Have a “Service Application Pool” Service account

Here we start configuration of metadata server.
1) Open Central Administration,

Go to Application Management >> Manage Service Application >> Click on New >> Select Managed Metadata Service.

You can give name to service whatever you want, I’ve given “Managed Metadata Service” for more clarity.
and Database name as Managed_Metadata.

Give AppPool name “SharePoint – Managed Metadata Service”

I’ve used svcMetadata service account for Application Pool Identity.

Click on OK.

---------------Start Metadata Service from SharePoint Services-------------------

Once the service is created you can see it listed on Managed Service Application Page.

Now we need to start Metadata Service from SharePoint Services on Server page.
for that go to Central Panel >> Under System Settings >> Manage Services on the server.
Start “Managed Metadata Web Service”

Go back to Manage Application Service and Open Metadata Service Application

This will launch the below screen which is referred to as the Term Management Tool.
-----------------------Open the Term Store Management Tool---------------------
1. Open the Term Store Management Tool to define the Term sets and Terms by
clicking on the Managed Metadata Service Application instance in Central Admin
2. Define the Taxonomy for Navigation - Groups, Termsets and
Terms for the Managed Metadata Service as mentioned in below Picture.

3. Create Publishing Web Application; you will have default
“Structured Navigation” applicable for the Global and Current Navigation for the web application
4. Click on the Settings link and Go To “Site Settings” link
5. Click on the “Navigation” link from the “Look and Feel” section .
6. Check the Navigation Settings available for the Global Navigation be default:
7. Change the Global Navigation and Current Navigation to “Managed Navigation” instead of “Structured Navigation”
7. Change the Global Navigation and
Current Navigation to “Managed Navigation” instead of “Structured Navigation”
7. Select the “Countries” Term Set for Managed Navigation as shown below and Click on Ok button
8. Navigate to Home Page and observe the changes in Navigations both Global and Current,
you should be able to see the Countries as Navigational nodes.
9. Click on the “Edit Links” link in Global Navigation and Click on
Add Link button to add a new City in United States “New York”
11. Drag and Drop the new link into “USA” menu properly and save it
12. Refresh the Page and you should be able to see newly added link in both the Navigations –
13. Go to Term Store Manager Tool from Site Settings and
Observe the changes in the Termsets (look for the one that you have added new) 14. Repeat the same steps for Current Navigation and Add
new link node for the “UK”15. Hide the Cities for Mumbai from Global Navigation 16. Edit the Master Page and Allow Current Navigation’s for more
than 2 levels so that you can View cities from Mumbai in Current Navigation Navigation using Managed Metadata
Summary: SharePoint 2013 introduces managed metadata based navigation.
It provides the ability to apply friendly URLs to pages. The Navigation items can be managed using the term store or Managed Metadata.
It allows you to create and update navigation for all sites in the farm using the Managed Metadata Service Application
There are two different locations to manage your Managed Metadata Navigation:
Site Settings and Central Administration. Architecture
Managed Metadata Service will be used for creating Termsets
which can be applied to navigation of Site Collection.
Steps for Configuring Metadata based Navigation
1.Enable the Publishing Feature by navigating to the site Settings  Manage Site Features
2.Click on Site Settings from the top right navigation as shown in the below figure
3). Next, click on Navigation under “Look and Feel” usually on the top right
4. Click on the Managed Navigation option.
5) Using the little drop down arrow on the Term Set,
Create Terms to reflect your desired navigation
8. Use the tabs at the top to manage “Navigation” and “Term-Driven Pages”.
9. Use the tabs at the top to manage “Navigation” and “Term-Driven Pages”.
Choose between two Navigation Node Types:
• Simple Link or Header
• Term-Driven Page with Friendly URLThe Simple Link or Header
is the more traditional hyperlink to an item or create a heading to group links.
10. Next we will set the Friendly URL by moving to the next tab for the term,
Term-Driven Pages. There you will find options to change the friendly
url as well as setting the target page for the hyperlink. (Can even set SEO properties! – cool)
Click on Save when you are done
11) Time to see the results, notice my url
12. Don’t forget that we are using the Managed Metadata Service (Term Store) which means you can have more than 1 level in the navigation
Conclusion: With this, we are done with how to activate the
Content Type Hub, Configured the Managed Metadata Service Application, Navigation using Managed Metadata.

Configure/ Setting up User Profile Service Application on SharePoint Server 2013

Hands-On-Lab: Setting up User Profile Service Application in SharePoint 2013

Applies to: SharePoint Server 2013
Summary: Learn how to Configure User profile Service Application
information by using the SharePoint Server method. The User Profile service application stores information about users
in a central location. Social computing features use this information to enable productive interactions so that users can collaborate efficiently.
In order to provision My Sites, enable social computing features such as social tagging and newsfeeds, and create and distribute profiles across multiple
sites and farms, you must enable the User Profile service application. Date Description
Dec 10, 2014 Initial version

Configure User Profile Service Application on SharePoint Server 2013

Note: User Profile Service required Managed Metadata Service.
So first we will configure Managed Metadata Service Application. The user profile service provides out SharePoint farm with
all the social networking features plus more. It forms the basis of My Site support, User Profile Pages, Audiences and Social tagging.
Let’s start configuration. navigate to User Profile Server.
Central Administration >> Application Management >> Manage Service Manage Application >> Click on New >> Select User Profile Service Application.

Enter Name : User Profile Service Application
Application Pool Name : SharePoint – User Profile Service
I’ve used svcUPS account for Application Pool Identity.

I will keep User Profile database name as it is. It’s good practice to
change or add database name when you have two user profiles running in your SharePoint farm.

You can change User Profile Synchronization database name or keep as it is.

Click on Create.
Now we need to start User profile service from Manage Services on the server.
For that go to Central Admin >>Under System Service >> Manage Services on the server
first start User Profile Service then start User Profile Synchronization Service
It will ask you about your farm administrator accounts password.

User profile service will take 15-20 minutes to start.
This in turn, will correctly configure and start our ForeFront Identity Manager Windows Services (FIM).

Now we have to Reset IIS server.
Go to Run >> Type IISReset

Let’s Configure Synchronization Connection, for that navigate to
Central Administration >> Application Management >>
Manage Service Application >> User Profile Service >> Configure Synchronization Connection

Click on Create New Connection

Connection Name : AdSync
Forest Name : (Put name of your forest)
I’ve used svcAdSync service account. and enter password of that account.
Click on Populate Containers. and selected OU of your users you want to synchronize with User Profile Service.

Click OK.
Go back to User Profile Service and User Profile Synchronization under Synchronization Option.
Select “Start Full Synchronization

Once synchronization complete. You can go to User Profile Service Application >> People >> Manage User Profiles and can find users in Active Directory.

Conclusion: In this way, we have learned configuration of User Profile service application
on SP 2013. Configuring profile synchronization (or profile sync) is a process that involves many steps. This article divides the process into shorter phases,
both so that you can see progress and to reduce the number of steps through which you have to backtrack if you make an error.

Tuesday, December 2, 2014

Free Sharepoint 2013 Apps


Newsfeed notifier

NapaDevelopment tool

Video carousel

News Sticker

Mini Calendar

Export to CSV

Image Carousel

Importatnt Message

Site usage

Carousel slider

Project Management

List Carousel

Contact form


Prayer time


Location finder

SharePoint Object Explorer

Analogue World clock

What is Central Administration in SharePoint?

What is Central Administration in SharePoint?
After doing the installation of SharePoint 2010, a separate site collection is created for performing different administrative functions that might needed on a daily basis. This site collection is known as Central Administration site. This site collection is different than the site collections which you have created and is run on its own web application in IIS.It is the main point for all the administration related activities for all the SharePoint sites. All farm server administrators is having an permission to access to this site much like the regular site they can edit and customize Central Administration site.

Central Administration site can be divided into the following eight areas,

Application management
General application settings
System settings
Backup and restore
Upgrade and migration
Configuration wizards

1.Application Management: In application management user can perform the following tasks,

Creation of New Web applications
Creation of New Site collections
Manage services that are installed on SharePoint site (Excel Services, User profile service, BCS)
Manage content database (Content database stores SharePoint data)

2.Monitoring: It is used to manage monitoring, reporting and to check the status of SharePoint site. The monitoring can be divided into following three areas,

Health Status: It is used to manage the services on the SharePoint Server (Visio services, farm level services).Administrator also see the report of the services like which service is failing etc. It is also used to define rules or scheduling of application pool recycles.

3.Security : It covers some important areas as mentioned below,

Management of administrator accounts
Configuration and management of service accounts
Management of password change settings and policies
Specification of authentication providers, trusted identity provides
Antivirus settings
Blocked file types
Web part security
Self –service security
Security token services

4.General Application Settings: It is used to configure some general options for SharePoint site collections and sites like configuration of sending mails to the users. Also in Web Content Management (WCM) context that user want to manage deployment and approval of the content, this can also be done in the general application settings.

5.System Settings :

Managing servers in the farm
Managing farm features
Configuring alternate access mappings

6.Backup and Restore :

Perform regular scheduled backups of SharePoint Sites
Perform ad hos backups
Restored from previously backed up SharePoint site

7.Upgrade and Migration: Many times it happens that you need to install a patch on the SharePoint server or you need to upgrade your SharePoint product from standard to enterprise. Administrator can perform this type of action from within the “Upgrade and Migration” part of the Central Administration site

8. Configuration Wizards: It is simply step-by-step wizard that configures your SharePoint server for administrator. When administrator first installed SharePoint, he can see this wizard or even this wizard can be run manually after installation of any patch on the SharePoint server.

SharePoint 2013 Central Admin

SharePoint 2010 Administration Interview Questions

SharePoint 2010 Administration Interview Questions What is Microsoft SharePoint Portal Server?

MS SharePoint Portal Server is an integrated suite from server side, to help improve organizational effectiveness with the help of providing


What are zones?

Different logical paths (URLs meaning) of gaining access to the same SharePoint Web application.

Five Zones :

Internet Zone

What are Web Application Policies?

Enables security policy for users at the Web application level, rather than at the site collection or site level. Importantly, they override all other security settings.

What is a site collection?

A site collection contains a top-level website and can contain one or more sub-sites web sites that have the same owner and share administration settings.

What are content databases?

A content database can hold all the content for one or more site collections.

What is a site?

A site in SharePoint contains Web pages and related assets such as lists, all hosted within a site collection.

How is SharePoint Portal Server different from the Site Server?

SharePoint Portal Server:

- SharePoint server services are key information worker infrastructure that provides additional functionality to the MS Office system applications. Site Server:

How is security managed in SharePoint?

Share point uses digital dashboard technology that provides an interface for the purpose of creating web parts and making them appear them on dash boards. The security is applicable throughout the organization.

What is Windows SharePoint Services?

Creation of websites for information sharing and document collaboration will be enabled by Windows SharePoint Services. It provides additional functionality for MS Office system and other desktop applications. It also supports like a platform for the development of applications.

What are the Hardware and Software requirements for SharePoint 2010 ?

Hardware requirements :
# Processor 64-bit, four-core, 2.5 GHz minimum per core.
# RAM 4 GB for developer or evaluation use, 8 GB for single server and multiple server farm installation for production use.
# Hard disk 80 GB for installation
For production use, you need additional free disk space for day-to-day operations. Add twice as much free space as you have
RAM for production environments.

Software requirements :
# The 64-bit edition of Windows Server 2008 Standard with SP2. If you are running Windows Server 2008 without SP2, the
Microsoft SharePoint Products and Technologies 2010 Preparation Tool installs Windows Server 2008 SP2 automatically.

What Has Changed with SSP in SharePoint 2010.?
In SharePoint 2010 Shared Service Providers (SSP's) are replaced by Service Applications. Services are no longer combined into a SSP. They are running independent as a service application. The service application architecture is now also built into Microsoft SharePoint Foundation 2010, in contrast to the Shared Services Provider (SSP) architecture that was only part of Office SharePoint Server 2007.
A key benefit here is that all services are installed by default and there is no SSP setup.
Additional improvements for the service application model include:

• The services architecture is extensible, allowing third-party companies to build and add services to the platform.
• Services are managed directly in Central Administration (rather than a separate administration site).
• Services can be monitored and managed remotely.
• Services can be managed and scripted by Windows PowerShell™.
• Shared services communications take place over HTTP(S). Shared services do not directly access databases across farms.
• Most new services are built on the Windows Communications Framework. They have optimization built into their protocol,
using binary streams instead of XML for data transfer. Test results show improvements in network throughput with this change.

Can we create a Single set of Services that will be shared across the farm?

Similar to the SSP model in Office SharePoint Server 2007, a single set of services can be shared by all sites in a farm. By publishing a service application (from the sharing group, under Service application tab), you can share it across server farms. This capability does not apply to all service applications, and some services can be shared only within a single server farm.

What are Managed Accounts?

To reduce the load of managing various service accounts in Microsoft SharePoint Server 2010, the concept of managed accounts has been introduced. Much like managed accounts in Windows Server 2008, they allow SharePoint Server to take control of all the service accounts you use. After SharePoint Server has control of these accounts, it can either manage their passwords — automatically changing them as necessary — or it can notify you when an accounts password is about to expire,
allowing you to make the change yourself.

What is LINQ. How is it used in Sharepoint ?

LINQ is a feature of the programming languages C# 3.0 and Visual Basic .NET. LINQ allows you to query in an object-oriented way, supports compile-time check, gives you intellisense support in Visual Studio and defines a unified, SQL like syntax to query any data source. But unlike other languages and query syntaxes which vary from one type of data source to another, LINQ can be used to query, in principle, any data source whatsoever. Hence, developers may find that it is the only query syntax that they ever need to know. It is commonly used to query objects collections, XML and SQL server data sources.
LINQ to SharePoint is officially being supported with the 2010 release.It works similar to LINQ to SQL or LINQ to Entity.
The LINQ to SharePoint Provider is defined in the Microsoft.SharePoint.Linq namespace. It translates LINQ queries into Collaborative Application Markup Language (CAML) queries.The gateway class for the LINQ to SharePoint provider is Microsoft.SharePoint.Linq.DataContext which represents the data of a SharePoint Foundation Web site.

How to Move content Databases using PowerShell ?

To attach\detach an existing content database
use Mount-SPContentDatabase "" –DatabaseServer "" –WebApplication http://webapplicationname/

is the content database to be attached.

is the name of the database server.

http://WebapplicationName is the name of the Web application to which the content database is being attached.

To detach a content database:

Dismount-SPContentDatabase ""

How to Export a Site or List in SharePoint 2010?

SharePoint Server 2010 provides several new features that provide a granular level of backup for various components of site content. This includes content at the site, subsite, and list level.

Through Central Administration(Granular level Back-up) a SharePoint Administrator can configure a backup of a subsite or list. An Administrator can choose a site and a specific list to be exported.The administrators can also choose to export security and select the different versions that will be exported with the list.

Changes in Themes in SharePoint 2010. Can we re-deploy and use the Old Cutsom themes in SharePoint 2010?
SharePoint Server 2010 has changed the way themes work, making them easier to customize. You can now, change colors, fonts, links etc from themes interface itself. Also, you can import PowerPoint themes directly into SharePoint Server.

What is Enterprise Metadata Management?

Enterprise metadata management (EMM) is a set of features introduced in Microsoft SharePoint Server 2010 that enable taxonomists, librarians, and administrators to create and manage terms and sets of terms across the enterprise.
The managed metadata service: is a service application that enables the use of managed metadata and
allows you to share content types across site collections and across Web applications. The service publishes a term store and content types, and the metadata is consumed via the managed metadata connection. A managed metadata service and connection are created when the metadata service application is created.

What are Web Applications in SharePoint?

An IIS Web site created and used by SharePoint 2010. Saying an IIS virtual server is also an acceptable answer.

What is an application pool?

A group of one or more URLs that are served by a particular worker process or set of worker processes.

Why are application pools important?

They provide a way for multiple sites to run on the same server but still have their own worker processes and identity.

What are My Sites?
Specialized SharePoint sites personalized and targeted for each user.

What is the difference between Classic mode authentication and Claims-based authentication?

As the name implies, classic authentication supports NT authentication types like Kerberos, NTLM, Basic, Digest, and anonymous. Claims based authentication uses claims identities against a against a trusted identity provider.

When would you use claims, and when would you use classic?

Classic is more commonly seen in upgraded 2007 environments whereas claims are the recommended path for new deployments.

What is Business Connectivity Services in SharePoint ?

SharePoint 2010 provides a new set of technologies known as Business Connectivity Services for retrieving, editing,updating, and deleting data from external systems(for e.g. data from ERP or CRM database). BCS enhances the SharePoint platform’s capabilities with out-of-box features, services and tools that streamline development of solutions with deep integration of external data and services.

How is BCS Different from BDC in SharePoint ?

Even though the BDC made it relatively easy to create read-only solutions that display data in the Business Data List Web Part, it was not so simple to create a solution that enabled users to make changes and write that data back to the external store.BCS, on the other hand, provides you with Read-Write capable connectivity from Client and Server to Database, WCF/Web Services and .Net Sources. A Developer can now use SharePoint Designer 2010 and VS 2010 rapid development tools to access
external data.

How would you create an Information Site in SharePoint 2010?

In SharePoint 2010 You can create a Read-Only Farm/site or site-collection by setting the Content database as Read-only.In SharePoint 2010 You can create a Read-Only Farm/site or site-collection by setting the Content database as Read-only.In a read-only farm, only content databases are read-only. All other databases, including the configuration database, Central Administration content database, and search database, are read/write.
The site collection that is associated with a read-only content database is automatically set to be read-only.

The user experience of a read-only site is characterized by the following:

* Common tasks that do not require writing to the content database are fully available.

* Most of the common tasks that require writing to the content database are not available, either because they have been
disabled in the user interface or because the user is no longer allowed to apply changes.

* Some common tasks that require writing to the content database appear to be available, but return errors.

What would you clean up before upgrading to SharePoint 2010?

Before you begin upgrading from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, you should make sure that your environment is functioning in a healthy state and that you clean up any content that you do not have to upgrade.Before you begin upgrading from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, you should make sure that your environment is functioning in a healthy state and that you clean up any content that you do not have to upgrade.

Clean Up - Before Upgrading to SharePoint 2010

Look for some things before you start upgrading stuff

* Delete unused or underused site collections and sites.
You do not want to upgrade content that you do not have to keep. If it has been unused for a long time and will not be needed in the future, back it up, and then delete it to free storage and administrative resources, improve upgrade performance, and reduce upgrade risk.

* Remove extraneous document versions

Large numbers of document versions can slow down an upgrade significantly. If you do not have to keep multiple versions, you can have users delete them manually or use the object model to find and remove them.

* Remove unused templates, features, and Web Parts

Firstly,verify that no sites are using any template, feature, or Web Part. You can use the pre-upgrade checker (Stsadm -o preupgradecheck) and the Stsadm -o EnumAllWebs operation to identify these customizations in your environment. If you are not using any customization, then you should delete it.

* Address large lists

By default, large list query throttling is appliedafter an upgrade to SharePoint Server 2010. If a list is very large, and users use a view or perform a query that exceeds the limit or throttling threshold, the view or query will not be permitted.Check any large lists in your environment and have the site owner or list owner address the issue before upgrade. For example, they can create indexed columns by using filtered views, organize items into folders, set an item limit on the page for a large view, or use an external list.

Describe the potential components for both a single server, and multiple servers, potentially several tiered farms :

A single-server SharePoint Server 2010 environment leverages a built-in SQL Server 2008 Express database. The problems with this environment is scalability, not being able to install the with built-in database on a domain controller, the database cannot be larger than 4 GB, and you cannot use User Profile Synchronization in a single server with built-in database installation.
An example of a multiple tier farm would be a three-tier topology, considered one of the more efficient physical and logical layouts to supports scaling out or scaling up and provides better distribution of services across the member servers of the farm. This is considered a good architecture since one can add Web servers to the Web tier, add app servers to the application tier, and add database servers to the database tier.

What is SharePoint 2010?
SharePoint 2010 is the business collaboration platform for the Enterprise & the Web that enables you to connect & empower people through an integrated set of rich features. Whether deployed on-premises or as hosted services, SharePoint 2010 helps you cut costs with a unified infrastructure while allowing you to rapidly respond to your business needs.

What Has Changed with 12 hive in SharePoint?

Three New Folders have been added in 12 hive structure.
• UserCode – files used to support sandboxed solutions .
• WebClients – used for the client Object Model.
• WebServices – .svc files .

How would you re-deploy the old custom solutions in SharePoint 2010.What Changes are needed to the old Solution files.

SharePoint 2010 object model contains many changes and enhancements, but our custom code will still compile and, will run as expected. You should however, rewrite and recompile any code that refers to files and resources in "12 hive".

Whats New with SharePoint WebParts?

A developer can create two types of webparts using Visual Studio 2010.
1. Visual Webparts - Allows you to Drag and Drop the controls from the Toolbox to WebPart Design surface. You can of course write your custom code in the code file. You can also package and deploy your webparts directly to Sharepoint from VS by pressing Clt+F5. Visual studio 2010 also provides you with three different views for developing webparts. The views are split view, design view and Source view(as we have in designer 2007).
Note : The Visual Webpart project Item basically loads a User Control as a WebPart.
2. ASP.Net WebParts - Where a developer can build up User Interface and logic in a class file. You do not have designer for drag and drop of controls. This webpart inherits from standard ASP.Net webpart. For Deployment we can again use ctrl+f5 to deploy this webpart.

What are the Visual Studio 2010 Tools for SharePoint.Ans. Visual Studio 2010 includes SharePoint-specific project types and project item types, and includes powerful packaging, deployment, and debugging features that help increase your efficiency as a SharePoint 2010 developer.
Some of the Templates avaiable are :
1.Visual Web Part project template.
2. List defination template.
3. Content Type template.
4. Empty Project template.
5. Event Receiver template.
6. some workflow template.
7. the Site Definition template
and many more....

What are SharePoint Sandboxed soultions ?
Ans. SharePoint 2010 provides a new sandboxed environment that enables you to run user solutions without affecting the rest of the SharePoint farm. This environment means that users can upload their own custom solutions without requiring intervention from administrators, and without putting the rest of the farm at risk. This means that the existing sites\pages or components will not be effected by the newly added soultion.
Users can deploy the below four things as sandboxed soultions :
1. WebParts.
2. Event Receivers.
3. List Definations.
4. Workflows.

What are Requirenments for SharePoint 2010.?

SharePoint Server 2010 will support only 64 - bit. It will require 64 bit Windows Server 2008 or 64 bit Windows Server 2008 R2. In addition to this, it will require 64 bit version of SQL Server 2008 or 64-bit version of SQL Server 2005.

What are the Methods of Backup and Recovery in SharePoint 2010?

Microsoft SharePoint Server 2010 provides a broad range of levels for performing backups, including the entire farm, farm configuration information, site collections, subsites, or lists.
SharePoint Server 2010 uses two different tools to configure backup and recovery.
1. Central Administration : Central Administration provides a user interface where SharePoint Administrators will be prompted
via menu structures to select the information that needs to be backed up. (see the Image below)
2. Windows PowerShell : Windows PowerShell is a command line tool that provides SharePoint administrators a way to perform backup and recovery with additional options such as file compression or working with SQL snapshots.
Listed below are a few of the benefits available when working with Windows PowerShell:
• Windows PowerShell scripts can be developed and scheduled (with Windows Task Scheduler), whereas Central Administration is used for single-use backups and restores.

• Windows PowerShell has the advantage of running against SQL snapshots instead of the production database. One of the parameters of the Windows PowerShell command will cause a SQL snapshot to be generated, and then Windows PowerShell will run the action against the snapshot instead of the production database. This will reduce the resource impact of the backup operation on the production environment.

• With Windows PowerShell, SharePoint administrators will have more granular control of options for the backup or restore.

Google+ Followers