What is a SharePoint?

Microsoft SharePoint Server 2010 is a platform, installed on a server and

accessed with an Internet connection, which has many capabilities, including
website design, collaboration, content management, and sharing and
aggregation of business intelligence data

Hardware requirements [For all servers database and SharePoint]:

64-bit processor
For front-end servers, RAM 4GB for development, 8GB for production.
For Database servers, RAM 8GB for small deployment, 16GB for
medium deployments.
80GB of hard disk

Software requirements:

OS:

64-bit Windows Server 2008 R2 or 64-bit Windows Server 2008 SP2.

For development environments, we can use either Windows 7 or
Windows Vista. But, it is highly recommended that we should not use these OS
for production environments.

Database:

64-bit SQL Server 2008 R2 or 64-bit SQL Server 2008 with SP1 and CU2
only or 64-bit SQL Server 2005 SP3.

Remember, to install SharePoint 2010, it checks for all prerequisites required and
if it didnt find any then it starts downloading them from Microsoft site and install
them in your server. Below are the listed modules which installs by the
preparation tool.

Web Server (IIS) role

Application Server role
 Microsoft .NET Framework version 3.5 SP1
SQL Server 2008 Express with SP1
Microsoft Sync Framework Runtime v1.0 (x64)
Microsoft Filter Pack 2.0
Microsoft Chart Controls for the Microsoft .NET Framework 3.5
Windows PowerShell 2.0
SQL Server 2008 Native Client
Microsoft SQL Server 2008 Analysis Services ADOMD.NET
ADO.NET Data Services Update for .NET Framework 3.5 SP1
A hotfix for the .NET Framework 3.5 SP1 that provides a method to
support token authentication without transport security or message encryption in
WCF.
Windows Identity Foundation (WIF)

SharePoint farm environments or deployment?

Single Server Deployment

The simplest topology install everything onto a single server. Single server
installations are only suitable for three scenarios:

Evaluation

Testing and development

Small office deployments

Whilst a single server installation is fine for evaluation and testing purposes, it
will only be suitable for low key small production environments. It will need at
least 8Gb of RAM, preferably more for performance to be acceptable. Obviously,
being a single server, it has very low fault-tolerance. If the server suffers a
hardware failure, no SharePoint til its fixed.

Farm Deployment
For most production environments, some level of farm will be implemented. Even
small deployments will see a performance benefit from deploying at least two
servers, separating the databases from the web and application servers.

The classic scenario is the three-tier architecture web front end(s), application
server(s) and database server(s). SharePoint services enable each tier to be
scaled up and out to meet specific requirements:

But this is the first check-point if you are following Microsoft guidelines. The
topology diagram provided by Microsoft (see references) suggests web servers
should also be used for querying in small farm deployments (3 to 5 servers). A
good strategy for load balancing performance but be aware that you will require
additional RAM and storage on those web servers. If your web front-ends barely
make the minimum hardware spec, performance may be impacted instead of
improved. In that case, a better approach would be to keep the query component
on the application server and control your indexing schedule to share resources
limit the amount of indexing during working hours when query performance is
more important.

Two web front-ends are always better than one for load-balancing performance
(and resilience) regardless of user numbers. Beyond that, Microsofts rule of
thumb is to have one web front-end per 10,000 users. Many small farms will start
with a single application server but it does risk a single point of failure impacting
availability of SharePoint.
Search is without doubt the first reason for needing to add application and
database servers to your farm. The indexing process is a resource hog that
impacts both the application server running the service and the database holding
the search databases. Querying is also resource heavy compared to standard
page rendering requests. If you are planning on deploying enterprise search
covering lots of content (millions of items), consider the following:

If you can have a large enough hardware specification for your web servers to
take the load, do run the query component on them for load balancing. Have a
dedicated application server for the indexing service and a dedicated database
server for the search databases. The additional application server also adds
resilience to your farm. Should the indexing server fail, it just means no fresh
updates to the query servers until the indexing server is fixed. If the other
application server should fail, you could temporarily stop indexing and use the
indexing server to run all other services until the failed server is recovered.

As you scale up into larger search requirements, the next layer of separation is to
have dedicated query servers. This introduces a fourth tier to your farm: web
server query server application server database server. By the time you are
this big, you may also want to introduce a third database server dedicated to
content databases:
In large farm deployments, you will start to scale components to multiple servers.
For example you may have two or more dedicated indexing servers (the index in
SharePoint 2010 can be partitioned, enabling parallel indexing of multiple
sources a huge improvement over previous versions but watch out for network
bandwidth issues) If you are developing applications on top of SharePoint, you
will probably want a dedicated application server for running the sandboxed code
(smaller deployments will make do with a dedicated web application on their
single application server).

There are also other topologies to consider such as extranets, public-facing web
sites and hosted deployments. This post was just intended to help get you
started in the right direction. One final point to consider. Summary guidelines are
often based on user numbers. When it comes to your production environment,
dont forget to consider the type of activities you have planned. A small number
of users managing legal documents and records will use a lot more resources
than occasional web surfers. Indexing needs are determined by the volume of
content (type and size as well as quantity of items) to be indexed regardless of
user numbers.

What is Farm in sharepoint 2010?

A Farm or Server Farm is a group of servers that share the same administrative
tools and are part of the same organization or group.

It can be done (web/datababase/index etc) on a single server in Simple

Installation mode in which case you dont need a NLB. For many small
businesses this is plenty enough.

Medium sized businesses usually start with at least 2 Web Front Ends (WFEs) and
a database server.

Multinationals can have some very complex setups involving dozens of

components.

What is webserver in sharepoint 2010?

SharePoint : Web Front End server (WFE)

A web server that handles web page requests from users, processes the request
and returns the data.

They process HTTP/S traffic and rely on Internet Information Server (IIS) to
provide much of the web server 'stack'
In a farm there can be multiple Web Front End (WFE) servers and a Network
Load Balancer (NLB) will distribute requests between them.

This is the primary method of scaling in SharePoint - as the number of users

grows you add more WFE servers.

Is also used to add redundancy - If a WFE fails the NLB can distribute requests to
other WFE's.

A typical SharePoint farm

What is application server in sharepoint 2010?

SharePoint : Application Server

An Application Server is a computer that provides key infrastructure and services
for applications that are hosted on a farm.

Typically - in SharePoint this means that a server that has been assigned to run
duties such as Excel, Visio or Access Services or Index/Search services - as
opposed to general web server duties of a web front end server.
What is application management in sharepoint central administration?

lets begin by navigating to SharePoint 2010 Central Administration / Application

Management. You will notice that the redesigned interface organises and
categorises items in an orderly fashion, with a lot of familiarity with SharePoint
2007.

The first step in the process is creating your first Web Application to host our Site
Collections.

Under the section Web Applications, click on Manage web applications.

On the new fluent ribbon UI, click on New. (By the way, I think the ribbon UI is a
welcome addition to the 2010 interface making it easier for administrators and
end users to make decisions and change details within a couple of clicks).
The all so familiar Create New Web Application window appears albeit as a pop
up window which does make navigation a lot nicer.
There are a couple of enhancements and improvements worth noting, with the
first being the two types of authentication that you are provided with when
creating your new web application, being Claims Based Authentication vs. Classic
Mode Authentication. In summary, SharePoint 2010 is now claims aware
making SharePoint a lot easier to work with systems such as Active Directory and
providing single sign on for on-premises and cloud based applications across
organisations. The following link provides a great overview on Claims Based
Authentication and the role it will play within SharePoint 2010.

http://blogs.technet.com/ritaylor/archive/2009/06/03/claims-based-
authentication-an-overview.aspx

Proceed and fill out the Create New Web Application Form. As a guide, I have
provided sample answers below .

Authentication: Claims Based Authentication

IIS Web Site:

Create a new IIS web site

Name: SharePoint Intranet Portal (Always best practice to create a new IIS
website for each new SharePoint Web Application.)

Port: 80

Host Header: Leave Blank or specify a preferred host header. (If you specify a
host header, the alternate access mapping will be created for you automatically.
Please ensure that you also create the relevant A record in DNS.

Path: Leave default C:\inetpub\wwwroot\wss\VirtualDirectories\80 (This is usually

determined by Port number and or Host Header Input)

Security Configuration

Allow Anonymous: No

Use Secure Sockets Layer (SSL): No

Identity Providers

Enable Windows Authentication: Negotiate (Kerberos or NTLM)

Sign in Page URL

Default Sign In Page

Public URL

Keep default Entry against your Default Zone.

Application Pool

Create new Application pool: SharePoint Intranet Portal (I have matched the
pool name against my IIS website name for consistency, again its best practice
to create a new application pool for each SharePoint Web Application that you
create.

Database Name and Authentication

Specify your Database Server, Database Name and keep Windows authentication
which is recommended.

Failover Server

This is a new feature in SharePoint 2010 providing you with the ability to specify
a second SQL server that is participating in database mirroring, allowing you to
easily failover if the primary SQL server fails. This is a welcome addition
providing a means of high availability.

Service Application Connections:

Edit the following group of connections: default

Note, SharePoint 2010 allows you to connect a web application to all service
applications available in a farm or a subset that you define. This can be changed
at any time.

Customer Experience Improvement Program

Enable Customer Experience Improvement Program: Yes or No

Click OK to initiate the creation process.

Click OK

Our new Web Application will now be listed along side our SharePoint Central
Administration v4 Web Application under Central Administration/ Application
Management / Manage web applications
We are now ready to create our first site collection. Navigate to Central
Administration / Application Management / Create Site collections.

As you can see, the interface hasnt changed at all from SharePoint 2007.

Ensure that the newly created Web Application is selected.

Enter a Title and Description. Under Template Selection I will click on the
Collaboration Tab and select the trusty Team Site as this will be my starter site
hierarchy for my development Intranet Portal.

Enter the Primary and Secondary Site collection administrators and then click OK.
Thats it. Our first site collection is up and running.

This is only the beginning of our journey. In upcoming posts I will delve into the
nitty gritty and get my hands dirty discussing the new features of SharePoint
2010.

This concludes our series on getting the basics of SharePoint 2010 up and
running and will serve as a base for all future posts on introducing SharePoint
2010.

What is a SharePoint site template?

SharePoint site templates are pre-built definitions designed around a particular

business need. You can use these templates as they are to create your own
SharePoint site and then customize the site as much as you like. SharePoint 2010
comes bundled with a lot of default site templates, like Team Site, Blog site, and
Group Work Site as shown here.

In addition to the default templates, you can create your own site template based
on a site youve created and customized in SharePoint. When you save your site
as a template, you create a Web Solution Package, or WSP. A WSP is a CAB file
with the solution manifest. The solution you create gets stored in the Solution
Gallery for the SharePoint site collection. From there, you can download a copy of
the solution or activate it on the server. When you save your SharePoint site as a
template, youre saving the overall framework of the site its lists and libraries,
views and forms, and workflows. In addition to these components, you can
include the contents of the site in the template, for example, the documents
stored in the document libraries. This could be useful to provide sample content
for users to get started with. Keep in mind that this could also increase the size of
your template beyond the default 50 MB site template limit.

Out-of-the-box (OOB) Site Templates in SharePoint Server 2010

You can retrieve the list of site templates using the following PowerShell methods:

Option 1.

Add-PSSnapinMicrosoft.SharePoint.PowerShell -easilentlycontinue | Out-Null

Get-SPWebTemplate | ft ID, name, Title, Description -autosize -wrap

Option 2.

Add-PSSnapinMicrosoft.SharePoint.PowerShell -easilentlycontinue | Out-Null

$globalAdmin = New-Object
-TypeName"Microsoft.SharePoint.Administration.SPGlobalAdmin";
$globalAdmin.VirtualServers[0].GetWebTemplates("1033") | ft Id, Name, Title,
Description -AutoSize -Wrap;

Powershell script to get all the list templates in sharepoint 2010?

$web = Get-SPweb http://SiteUrl
Write-host Web Template: $web.WebTemplate | Web Template ID: $web.WebTemplateId
$web.Dispose()

# To get a list of all web templates, use the following PowerShell code

function Get-SPWebTemplateWithId
{
$templates = Get-SPWebTemplate | Sort-Object "Name"
$templates | ForEach-Object {
$templateValues = @{
"Title" = $_.Title
"Name" = $_.Name
"ID" = $_.ID
"Custom" = $_.Custom
"LocaleId" = $_.LocaleId
}
 New-Object PSObject -Property $templateValues | Select @("Name","Title","LocaleId","Custom","ID")
}
}

Creating the Alternate Access Mapping

To create the alternate access mapping for the new URL,
1. Open the SharePoint Central Administration page. Click
the Configure alternate access mappings link under Application
Management.

2. In the Alternate Access Mappings page, click on the Edit Public

URLs link.

3. On the Edit Public Zone URLs page, make sure that you select the correct web
application that you want to configure for alternate access mappings. In this
example, my http://sharepoint1 site is mapped to theSharePoint - 80 web
application in IIS. Under the Public URLs, section, enter the new URL that you
want mapped to the existing web application. I used the Intranet field and
entered the URLhttp://corporateportal.testdomain.com. This is how I want
my internal end-users to access my existing SharePoint web application instead
of using the server hostname. Click the Save button.

You
you can
looknowthe
access
links the existing SharePoint web now
application using
newthe new URL. If
of the oldatone. in the SharePoint site, they point the URL instead

Alternate
correct access
web mappings
applications tell
and SharePoint
sites soURLs how to mapcan
that properly
SharePoint web requests
serve to the
theAscorrect
content back
mentioned in to
theyou, translating
earlier part of the
this tip, we are in the process.
preparing our I've site for a
SharePoint
scale-out
(NLB). As SharePoint
NLB uses a farm deployment
virtual server nameusing Windows
instead of theNetwork
server Load Balancing
hostnames
access
alreadyapplications,
in place prioritto
is configuring
important tothe make sure that
SharePoint thistoURL
farm runtranslation isto
on a NLB cluster.
Difference between Claim Based Authentication and Classic mode
Authentication?

Claims Based Authentication: This is a new feature in SharePoint Server 2010

that is built on the Windows Identity Foundation (WIF). It uses the identity of
the user as well as other details, which can originate within the users
organization, other organizations, or the Internet. It enables authentication
across Windows-based systems and systems that are not Windows based. Claims
Based Authentication is a flexible framework based on standard Security
Assertion Markup Language (SAML) tokens, but it is not the actual means of
authentication. TIP If you are upgrading from SharePoint Server 2007 and used
Forms-based authentication or Web single sign-on (SSO) authentication, you
must convert to Claims Based authentication before SharePoint Server 2007 Web
applications can be used in SharePoint Server 2010.

Classic Mode Authentication: This mode essentially uses IIS authentication

for SharePoint Server 2010 Web applications. If you simply want to use Kerberos
or NTLM, select Classic Mode Authentication. Note that Basic authentication can
be configured after the creation of a Web application, but not during the creation.
Always use Secure Sockets Layer (SSL) when leveraging Basic
authentication.

Classic mode authentication Claims based authentication

You cannot configure the FormsIt enables authentication from windows

based authentication if your web
as well as non-windows based systems.
application is using Classic Mode
This also provides the capability to
Authentication. You can convert
have
a multiple authentications in a
web application from Classic single URL.
Mode Authentication to Claims
Based Authentication. However,
that can only be done using
PowerShell commands and its an
irreversible process.

Classic mode authentication

Claims based authentication supports
supports Kerberos, NTLM, Digest,
Kerberos, NTLM, Digest, Basic, AD DS, A
Basic, anonymous authentications.
database such as a SQL Server
database, An Lightweight Directory
Access Protocol (LDAP) data store such
as Novell eDirectory, Novell Directory
Services (NDS), or Sun ONE.
 Claims are the recommended path for
new deployments in SharePoint 2010.

Classic is more commonly seen in

2007 environments.

Step 1: The user logs on to the workstation and requests service on the host.
The workstation sends a message to the Authorization Server requesting a ticket
granting ticket (TGT).

Step 2: The Authorization Server verifies the users access rights in the user
database and creates a TGT and session key. The Authorization Sever encrypts
the results using a key derived from the users password and sends a message
back to the user workstation.

The workstation prompts the user for a password and uses the password to
decrypt the incoming message. When decryption succeeds, the user will be able
to use the TGT to request a service ticket.

Step 3: When the user wants access to a service, the workstation client
application sends a request to the Ticket Granting Service containing the client
name, realm name and a timestamp. The user proves his identity by sending an
authenticator encrypted with the session key received in Step 2.

Step 4: The TGS decrypts the ticket and authenticator, verifies the request,
and creates a ticket for the requested server. The ticket contains the client name
and optionally the client IP address. It also contains the realm name and ticket
lifespan. The TGS returns the ticket to the user workstation. The returned
message contains two copies of a server session key one encrypted with the
client password, and one encrypted by the service password.

Step 5: The client application now sends a service request to the server
containing the ticket received in Step 4 and an authenticator. The service
authenticates the request by decrypting the session key. The server verifies that
the ticket and authenticator match, and then grants access to the service. This
step as described does not include the authorization performed by the Intel AMT
device, as described later.

Step 6: If mutual authentication is required, then the server will reply with a
server authentication message.

The Kerberos server knows "secrets" (encrypted passwords) for all clients and
servers under its control, or it is in contact with other secure servers that have
this information. These "secrets" are used to encrypt all of the messages shown
in the figure above.

To prevent "replay attacks," Kerberos uses timestamps as part of its protocol

definition. For timestamps to work properly, the clocks of the client and the
server need to be in synch as much as possible. In other words, both computers
need to be set to the same time and date. Since the clocks of two computers are
often out of synch, administrators can establish a policy to establish the
maximum acceptable difference to Kerberos between a client's clock and server's
clock. If the difference between a client's clock and the server's clock is less than
the maximum time difference specified in this policy, any timestamp used in a
session between the two computers will be considered authentic. The maximum
difference is usually set to five minutes.

NTLM Authentication: Challenge- Response mechanism?

In the NTLM protocol, the client sends the user name to the server; the server
generates and sends a challenge to the client; the client encrypts that challenge
using the users password; and the client sends a response to the server.If it is a
local user account, server validate users response by looking into the Security
Account Manager; if domain user account, server forward the response to domain
controller for validating and retrive group policy of the user account, then
construct an access token and establish a session for the use.

List of the service applications in SharePoint 2010

1. Access Services

2. Application Registry

3. Business Data Connectivity

4. Excel
5. Lotus Notes Connector

6. Managed Metadata

7. PerformancePoint

8. Search

9. Secure Store

10. State

11. Usage and Health

12. User Profile

13. Visio Graphics

14. Web Analytics

15. Word Automation

How to configure search service application in sharepoint 2010.

1. We need to first start the search service application in Central Admin.

2. Go to Application Management -> Manage service application.

3. Then start a new Search Service Application.

4. Provide the application name, in this case Service Search Application.

5. Provide a search service account.

6. Configure application pools for both the Search Admin Web Service and
the Search Query and Site Settings Web Service.
7. Click OK and wait for SharePoint to process the request. This may take
several minutes.

8. A message will then appear if the search service application was successfully
created.
9. OK, the search service application has been created, now we need to do some
configuration work.

10. Once again, go to Application Management -> Manage service

applications.

11. Select Search Service Application, then click the

Administrators ribbon button to configure the search service for
administrators.

12. Select SearchAdmin. This is the service account we previously created in

the search service application.
13. Now to assign the permissions.

14. Almost done, go to Search Service Application -> Content Sources and
select Start all crawls.
15. Once the crawl has completed, the search box is now ready to use.

How to configure userprofile service application in sharepoint 2010.

Click above to view at full size.

The key components are briefly described below.

User Profile Service Application

Note: A SharePoint Service Application is a logical / conceptual object
which is currently very badly articulated. I will be covering service
applications in more detail in a future article. The relevant physical
assets are described in this article.
An IIS Application which sits in the SharePoint Web Services IIS Web Site. The
IIS Web Site is on every machine in the farm. When we start the Service Machine
Instance later, the IIS Application will be created. It will be named with a GUID
and is hosted by an Application Pool (which is also named with a GUID!). It hosts
a couple of WCF services (profileproperty and profiledbcache). This is known as a
Service Application Endpoint.

The Service Application Endpoint has three associated back end databases and
other configuration. Pages for managing the Service Application are hosted in
Central Administration and are called using a GUID in the query string. The WCFs
dont actually do any work themselves but provide an interface to calling clients
and calls other elements of the system.

There can be more than one instance of the User Profile Service Application, but
there is a one to one mapping between a Service Application and the User
Profile Synchronization Service Service Machine Instance or SharePoint
Service.
Note: The concept of a Service Machine Instance or SharePoint Service (i.e.
the items in Services on Server) is very badly articulated in general and the
name of course is deeply confusing.

There is also a Service Connection (aka Proxy). This lives within the SharePoint
Foundation Web Application Service and allows Service Consumers (Web
Applications) to call the Service Application.

User Profile Service

A SharePoint
some .NET Service that
assemblies in Services
do some onwork
Server.
withThis is notand
profiles a Windows Service,which
but
are not
options.to do
This with Synchronising
should run on the of properties.
machine in the There
farm you noother
are wish to
elements
configuration
use to host the
User Profiles
Machine Role. When its running that machine is known as the Service
Instance.

User Profile Synchronization Service

A SharePointofService
provisioning the in Services onManager
Server. This is bits.
a wrapper responsible fortothe
associate
will run. with,
This andForefront
need Identity
to the
specify (FIM)
the credentials under You select
which the aFIM
UPS SA
Services
User Profiles
Machine Role. When its running that machine is known as the Servicethe
should
Instance.
run on machine in the farm you wish to use to host
 Forefront Identity Manager
A bundled version
configuration of FIMItthat
and data. includes
is not two to
supported Windows
use theServices, and
FIM client associated
tool but thisare
can
be useful for
configured byviewing
the progress
User Profile and identifying
Synchronization errors.
Service The two FIM
SharePoint services
Service (rolls
off the tongue doesnt it!).
The FIM Client is located at C:\Program Files\Microsoft Office
Servers\14.0\Synchronization Service\UIShell\miisclient.exe

strongly recommend that you deploy the June or August Cumulative Updates
(CU). Preferably the August CU, which offers a much easier installation. These
contain numerous fixes related to User Profile Synchronization. Install these
preferably before creating your Farm using PSConfig. The August CUs are
available at:

KB 2352346 - SharePoint Foundation 2010

KB 2352342 - SharePoint Server 2010

Please follow
Services the
to use ansteps below to
Application IDcorrectly
from theconfigure SharePoint
Secure Store 2010 Excel
Services.
How to configure excel service application in sharepoint 2010
 Configure the following in SharePoint Central Administration

1. Under Application Management, click on Manage Service Applications

2. Click on Secure Store Service (the first one in the list, application, not
the proxy)

3. In the Edit tab on the ribbon bar, click New.

4. In the "Create New Secure Store Target application" page, enter the
following:

o Target Application ID: ExcelServices

o Display Name: ExcelServices

o Contact Email: whatever@whatever.com (Use a real address)

o Target Application Type: Group

o Target Application URL: None

5. Click Next.

6. On the next screen, use the field defaults (Windows UserName,

Windows Password) and click Next

7. On the next screen, enter the following values:

o Target Application Administrators: (Domain\Administrator)

o Members: (Domain\Domain Users)

8. Click OK

9. After the Target Application ID is created, select the checkbox next to

ExcelServices, and click Generate New Key in the ribbon.
10. On the next screen, enter your Pass Phrase in the Pass Phrase and
Conform Pass Phrase boxes

11. Again on the screen listing the Target Application IDs, select the
checkbox next to ExcelService, and click Set Credentials in the ribbon.

12. On the next screen, enter the Username and password into the fields:
(this user must have access to the data that needs to be queried)

Configure Excel Services

In SharePoint Central Administration
1. Click Application Management

2. Click on Manage Service Applications

3. Click on Excel Services Applications

4. Click Global Settings.

5. Scroll to the bottom and in the Application ID field, enter ExcelServices

6. Click OK.

You
theirwill now find Excel
authentication spreadsheets with data connections in them which have
retrieve their data! set to None will use the Unattended Service Account to
Managed Metadata service application:

Managed Metadata is a hierarchical collection of terms that can be associated

with items in SharePoint 2010. We can use Central Administration website to
manage these terms.

This is a new feature in SharePoint 2010.

Example: You have a document library to upload articles. For each item you can
specify a column metadata of category like C#, ASP.NET etc.

The Purpose

So you might be wondering that there exist list columns for the same purpose.

Following are some advantages provided by Managed Metadata:

1. Term Sets can be shared across a site collection or globally

2. Searching using Metadata gives more relevant result

Some Concepts inside Managed Metadata

 Term: A term is keyword that can be associated with a SharePoint
item.
Term Set: A term set is a group of terms. You can restrict that a
particular item should contain a term from a particular term set. For example:
setting the category of an article item from term set [C#, ASP.NET].
Local Term Sets: Site collection scoped term set. Only site user can
see it.
Global Term Sets: Global Term Set created outside the site
collection. They are visible to all users.

Managed Metadata Service

The metadata is managed through Central Administration and using the Service
Application named Managed Metadata Service.

Practical

So now we can proceed to see how to setup Managed Metadata and use it along
with a Document Library. Following are the activities involved:

1. Setup Term Store Administrator

2. Setup Term Set and Terms
3. Set Managed Metadata Column
4. Perform a Search using the Metadata

Step 1: Setup Term Store Administrator

Open the Central Administration website and click the Manage Service
Applications link.
From the appearing list click on the Managed Metadata Service as shown below.

You will get the following screen. Now set the Term Store Administrator(s).
These users are allowed to add/remove Term Sets. So please go ahead and
assign a user for your site. You will see some strange characters after resolving
the user name. They specify they type of Authentication for the user. Eg: i
#.w|hp\admin
After assigning the user, select the Working Languages and click the Save
button. Now we are ready to proceed with Term Set creation.

Step 2: Setup Term Set and Terms

Click over Managed Metadata Service tree item from the left hand side panel.

Note: This is little tricky. You should click on the right hand side corner of the
item.
You will get the New Group option as shown above. Click the option and enter a
name for the Group. From the right hand side set the users who are going to
manage the group.

Click the Save button. Now you are ready to create the Term Sets.

Click the mouse over the right hand side corner of Group and from the listed
options click New Term Set as shown below.

Enter a name for the new Term Set as shown below.

Now click on the right side of Term Set and from the options select Create Term.

Enter the Terms as shown below:

So now you are ready with the Term Sets and Terms. We can proceed to the next
step.

Step 3: Set Managed Metadata Column

Back to the SharePoint site, create a document library and name it as Articles.

After the library is created, from the Library tab click the Create Column option.

In the appearing dialog enter the name and select the column type as Managed
Metadata
Now drag the right scrollbar and set the Term Set properties.

Now click the OK button to save the changes.

Back in the library try adding a document.

Click the OK button and you will be prompted with the following dialog. Here you
can select the Category by clicking the right side Browse button.

On clicking the Browse button you will get the following dialog.
Select an appropriate category (double click) and click the OK button. In the next
dialog click the OK button. Now the Category Metadata is set to the library item.

Note: Please note that you can select multiple category items.

So this concludes the article on Managed Metadata and its use along with a
Library. In the Advanced Search Page we can use the Managed Terms for filtering
more relevant results.

SP2010 Ramp up: Setting up the Content Type Hub

The following steps will set up your Content Type Hub for your SP2010 Farm:
1. Create new web app & site collection
1. Title: Content Type Hub
2. Central Admin > Manage Service Applications
1. Click once on Managed Metadata Service
1. In Ribbon > Properties
2. Set Content Type Hub to the url of the site collection you just
created
3. Check "Report syndication "
4. OK
2. Click once on Managed Metadata Service Connection
1. Ribbon > Properties
2. Check all boxes
3. OK
3. Go to Content Type Hub site
1. Activate Site Collection Feature: Content Type Syndication Hub
2. Settings > Galleries > Site Content Types
3. Create content type
4. Go to other site collection/web app
1. Site Settings > Site Collection Admin > Content Type Publishing
1. Check "Refresh all published content type
5. Go to Central Admin > Monitoring > Check Job Status
1. Find the "Content Type Subscriber" job for your other site
collection
2. Click on Content Type Subscriber
3. Click "Run Now
6. Once that job completes, go back to other site collection
1. Site Settings > Site Collection Admin > Content Type Publishing
2. You should now see the new content types from the hub appear
3. They will also show up in Galleries > Site Content Types

Backup and restor in sharepoint 2010.

we can explore the backup and restore operations inside SharePoint. For Administration tasks we need to
use the SharePoint Central Administration web site which is accessible from the Start menu, as shown below.
 Following are the most common administrative tasks:

Backup and Restore

Site Usage Analysis
Cleaning up Unused Sites
Managing the Search Service
Managing Quotas and Locks

Backup
We can perform different levels of backup inside SharePoint 2010. The levels include:

Farm Backup
Site Collection Backup
Site Backup
Web Application Backup
List Backup
Library Backup
Solution Package Backup
 Configuration Backup
Content Database Backup

The types of Backup are:

1. Full Backup
2. Differential Backup
3. Incremental Backup

We can have automated backup strategies to backup the required contents on intervals.

The Backup and Restore settings can be accessed from SharePoint Central Administration.

For performing a manual backup, use the Perform a backup link shown above. In the appearing page,
select the items you need to backup and click the Next button. Depending on the item the backup size will
increase.
In the next page of the backup wizard, enter the backup type and location as shown below.
Click the Start Backup button to perform the backup. Make sure you set the location shared access to
Everyone.

The above screen shows that your backup operation is running. Wait for a few while to complete the
operation. After the operation, you will get a report as shown below.

Note
If the Backup page says the Administrative service is not running, you need to start it manually from
Windows Services.

Use the Run window to execute the command services.msc. In the appearing applet, right click and start
theSharePoint 2010 Administration service.
Restore
We can restore a farm, site, or the backed up item using the Restore from a backup option.

In the appearing page select the radio button of the appropriate backup and click the Next button.

You can see that the backup location is remembered automatically. In real world scenarios we have to
choose different backup locations.

In the next page select the components to restore.

 Click the Next button and the restore operation gets started.

How to take the backup using powershell command?

Backup and Restore SharePoint 2010 Site Collection with PowerShell
One of the most annoying processes with SharePoint is backing up a site
collection. There is a build in tool that you can use but it is kinda clunky and can
take a while to perform the backup. I used it once and was not impressed.
PowerShell provides a quick and easy way to do site collection backups. My
favorite part is that you can do the entire backup with one, uno, un, 1 (thats all I
know for the number one so yeah) line of code. Just a little something to be
careful of, you need to use the Windows SharePoint 2010 Management Shell, not
the regular Windows PowerShell. I spent about 15 minutes trying to figure out
why it (Windows PowerShell) didnt think that Backup-SPSite was a valid
command. Here are the steps you should take. Note that doing the backup will
put your site into a read only mode.

1. Click Start
2. Go to All Programs
3. Go to Microsoft SharePoint 2010 Products
4. Open SharePoint 2010 Management Shell
A PowerShell command prompt will appear and you need to format the following
to fit the backup for your site.
Backup-SPSite -Identity SiteCollectionURLHere -Path
BackupFilePathHere [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-
Verbose]
 I recommend creating a folder where you can place these backups before starting
the backup process so they arent just chillin on the C:\ drive of your SharePoint
server; just a thought. Here is a little explanation of those additional parameters
that are inside the braces [ ]
Force Include this if you want to override a backup with the same
name
NoSiteLock Will prevent the site from going to Read Only mode while
the backup is being taken. A small warning, if someone changes content on the
site while the backup is being created and according to Microsoft might lead to
possible data corruption
UseSQLSnapshot A database snapshot will be taken before the
backup begins and the backup will be done off the snapshot. The advantage is
that changes can be made to the site while the backup process is running
without fear of corruption. The snapshot will be deleted automatically when the
backup is completed. You dont need to specify the -NoSiteLock parameter when
using this method
Here is a simple example of what the script may look like if you want to just do a
backup:
Backup-SPSite -Identity http://servername/sites/BISite -Path
D:\SharePointBackups\BISite\07-13-2011.bak
To do site restores the syntax is almost just as easy. You will need to use the
same SharePoint 2010 Management Shell as doing the backup.
Restore-SPSite -Identity SiteCollectionURLHere
-Path BackupFilePathHere [-DatabaseServer DatabaseServerNameHere]
[-DatabaseName ContentDatabaseNameHere] [-
HostHeader HostHeaderHere] [-Force] [-GradualDelete] [-Verbose]
DatabaseServer Specify the server for the content database
DatabaseName Specify the name of the content database
HostHeader URL of the Web application that will hold the host-named
site collection
Force Overwrite the site collection if it exists
GradualDelete Recommended for site collections over 1 Gig in size,
existing data is marked as deleted and gradually removed over time by a job
rather than all at once to reduce the performance hit of deleting large amounts of
data
how
usingtoPower
perform Import/Export
Shell ? operation of a particular SharePoint site
1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell.
4. At the Windows Power Shell command prompt type the following command:

5. You will get a Power shell command prompt like below

6. In SharePoint 2010, Power Shell command Export-SPWeb is used to export the

site
7. Please see the screen shot for the Power Shell command
8. Export-SPWeb -Identity http:\\ServerName:port\Site -Path
c:\\backup\Exportback.dat

9. The NoFileCompression
performed parameter lets you specify that no filelower
compression is
usage
backup up toduring
30%
folder being
the export
during
created
process.
the export
instead of
Using
process.
a
this parameter
Using
compressedthisfile. can
parameter
If you
resource
willthe
use result in a
NoFileCompression
it when you import theparameter
contentinbythe Export-SPWeb
using command,
the Import-SPWeb you must also use
command.
10. To import to a site you have to use Import-SPWeb command
11. The complete command is
12. Import-SPWeb -Identity-Force
c:\\backup\Exportback.dat http:\\ServerName:port\Site -Path
13. I have used -force to over write the existing site in my destination
How to configure bcs in sharepoint 2010 using sharepoint designer?
how to create a Business Data Connectivity using external Content type through
SharePoint Designer. Business Data Connectivity can be used to integrate with
SQL database and SharePoint in your working scenario to manage datas using
SQL Server.

Step 1:

Open SQL Server and create a database named Employee. Then create a
table named EmpInfo and create a column as show in a figure below

Step 2:

Go to Central Administration and click Manage Service application

Step 3:

Click the New button from menu, list of services will be listed. Then click
the Business Data Connectivity servicesand configure them.

Step 4:
After connecting the Business Data Connectivity services. Open SharePoint
Designer and click Central Administration

Step 5:

Click the External Content Types from the left menu

Step 6:

Click New External Content Types from the file menu

Step 7:

Click here to discover external data sources and define operations for
connecting the external data source shown below
Step 8:

Add Connection button to connect the SQL Server

Step 9:
Choose the Data Source Type as SQL Server

Step 10:

Configure SQL Server as below and click ok

Step 11:

Now the SQL Server is connected and you will get the Employee
Database connection Source

Step 12:

Click Table name Emp -> Tables ->EmpInfo then right click the EmpInfo and
click the Create All operations
Step 13:

Then All operation will popped up. Click Next button

Step 14:
Parameter Configuration popped up and click Finish Button

Step 15:

Click Create Lists & Form Icon from Ribbon

Step 16:

Then Conformation Will be popped up and give Yes to save the changes

Step 17:

Enter List Name as Employee information and click ok button

Step 18:

Go to Central Administration

Click Site Actions->View All Site Content and EmployeeInformation will be

listed there.
Step 19:

Click the New button from the menu

Step 20:

Add New item and Save it

Step 21:

Open SQL Server ->Choose the Database Employee and Check the
Emplnfo table using Query analyser. Your data will be saved.
How to configure secure store service application in sharepoint 2010?
The Secure Store Service provides a more flexible solution to the problems
partially addressed Single Sign-On (SSO) in MOSS 2007. It allows for the secure
storage of usernames and passwords for shared resources and the mapping of
users to specific access identities. It is commonly used for access to data for
Business Connectivity Services, Excel Service Applications and Visio Service
Applications.
Microsoft have some really good documentation on this topic. Their planning
guide ishttp://technet.microsoft.com/en-us/library/ee806889.aspx and their own
more detailed configuration guide is http://technet.microsoft.com/en-
us/library/ee806889.aspx.
However, for many (especially for dev and piloting) this provides a quick guide to
getting it up and running.
You should check that you are a Service Application Administrator for the
instance of the Secure Store Service you will be configuring.
The first step is to initialize the Secure Store Service:
1. From Central Administration, choose Manage service
applications from theApplication Management group:

2. Click on the Secure Store Service link (either is OK they both link to
the same place):

3. If this is the first time the Secure Store Service has been accessed, you
will need to Generate New Key (from the ribbon):

4. To generate a new key you must provide a passphrase. This is used for
encrypting information stored in the secure store so it is wise to choose a strong
passphrase. There is no way (at least that I know) of recovering the passphrase,
so do not forget it!
At this point the Secure Store Service is ready for you to start adding the target
applications that you want to store credentials for. For each application you want
to access, do the following:
1. Click on the New target application ribbon button:
2. Complete the Target Application Settings using the notes below:

3. The target application id is the unique name of the application (and

cannot be changed), although the display name can.
4. Contact e-mail is pretty self explanatory.
5. Then we get to the Target Application Type. The first choice to make
is either:
1. Individual meaning that each user connecting to SharePoint will
be mapped to a unique set of credentials to connect to this target applications; or
2. Group meaning that all users connecting to SharePoint in a
specific group will be mapped to a shared set of credentials to connect to this
target application.
6. Now we need to decide whether the type should be normal, Ticket,
or Restricted. Maybe its just me, but I found the on-screen help not very useful
and online help took a few seconds longer than usual to find. Essentially, these
options have the following meaning:
1. Ticket this applies to target applications who support ticket (or
claim) based authentication. Claims based identity management is a big theme
in Microsoft.NET 3.0 and if you want a primer in this topic please
see http://msdn.microsoft.com/en-us/magazine/cc163366.aspx;
2. Restricted allows you to provide implementation specific
additional authentication in the target application;
3. Normal this is the more traditional method of providing
authentication credentials (username, password and maybe other information)
with each connection.
7. I am interested at this point in a connection to SQL Server, and a single
set of Windows logon credentials for all users is what Im after, so I
choose Group, and click Next.
8. Next Im prompted to specify the authentication field names and type.
The default of Windows User Name and Windows Password is exactly what I
need, but if you are connecting to a target application that needs more
information you can add fields of various types to this target application:

9. Ive chosen to have a single set of credentials for a group of SharePoint

users, so next I need to specify who can administer this target application and
who are the members of the group of users that will use these credentials:

Note that in Administrators and Members I can use the new People and
 Groups picker dialog, which is a big improvement on the 2007 version:

10. Finally, click OK and youre done: target application created.

Thats it youre done. Using this target application is for another post, but to
give you an idea, the screen shot below shows specifying this target application
from Excel
What is managed account in sharepoint?
Managed accounts is a brand new concept of SharePoint 2010. They are
designed to give administrators more control over the domain accounts that are
used in different section of SharePoint.

When you register a account with SharePoint, administrators can maintain the
account from SharePoint itself:

1) Free from worries of password change how & where in SharePoint

If a password left unchanged in any part of SharePoint it can do lot of hell J

When a domain account is registered with SharePoint as a managed account. It

can be used as:

1) To run application pools

2) To run service applications.

The account which install SharePoint2010 is automatically/already registered as a
managed account. More accounts can be added later by clicking Security
category in Central Administration home page and select Configure managed
accounts under the subcategory General Security. While registering a managed
account, you simply need to provide the

username with domain and password.

You have many option there like i.e. to have SharePoint automatically handle the
password changes for you. This option is the most useful option as it
removes from burden to change password everywhere in the SharePoint :

If you decide to use the automatic password change option, SharePoint will take
over setting the password for the account in Active Directory for as long as the
account is registered as a managed account.
 If dont allow SharePoint to change the passwords automatically; It can still be
easy to manage password from within Central Administration now from the
Managed Accounts page, you can edit the account whose password you like to
change. There you can change the password by checking the box next to Change
password now.

Imp Note: If someone change the password for the account directly in AD without
the knowledge of SharePoint, your managed accounts will not work. SharePoint
needs the accounts password to use it. For any password change it is
recommended to change the password from SharePoint and not with AD.

How to configure incoming and outgoing email in sharepoint 2010?

There are certain benefits you can get from configuring your SharePoint system
for incoming and outgoing emails.

For instance, with Incoming Email enabled in SharePoint, your teams members
can automatically store the messages and attachments they send to other team
members into lists and libraries without having to open your SharePoint site and
doing a manual upload. This will help your organization move away from Public
Folders.

On the other hand, with Outgoing Email enabled, users can set alerts and use
them to track various items such as lists, library items, and documents and be
notified whenever changes to these items occur. It will also allow email
administrators to receive messages regarding important system issues.

(Instructional video below provides a walkthrough of the steps contained in this

article.)

Important Reminders Before Configuring Email

Before you set out to configure your SharePoint for incoming and outgoing email,
there are some things you need to know.

SharePoint 2010, which is the version well be referring to throughout

this tutorial, relies on the SMTP service in Windows 2008 or Windows 2008 R2 for
 incoming email. Thus, that service will have to be enabled in SharePoint before
anything else.
SharePoint 2010 supports configurations from any SMTP service for
sending outgoing email. However, for this tutorial, well be using Exchange 2010
and well be assuming it has already been set up as its own member server in
your organization and ready for use.
Finally, to work with Exchange 2010, you will have to configure send
and receive connectors.
Lets start the ball rolling.

Enabling SMTP in SharePoint

Go to your SharePoint server and open the Server Manager. Next, click
the Features node and then click the Add Features link.

This will launch the Add Features Wizard. In the Features list, scroll down until
you find the item named SMTP Server. Click that.
A dialog box will then pop-up, asking you whether you want to add role services
and features required for the installation of the SMTP Server. Click the Add
Required Role Services button.

In the succeeding screens, just click the Next buttons until you reach the one
that says Confirm Installation Selections, at which youre supposed to
click Install.
Barring any unforeseen hitches, you should reach the Installation
Results screen with all items marked as Installation succeeded. If you did,
click the Close button.

Configuring SMTP using the IIS 6.0 Manager

For you to be able to configure that SMTP service, the Internet Information
Services (IIS) 6.0 Management Tools (a.k.a. IIS 6.0 Manager) should be installed
on your Windows 2008 R2 Server. To see if theyre already there, navigate
to Start > All Programs > Administrative Tools.
If it hasnt been installed yet, then just go to the Server Manager, click
the Roles node, scroll down that large Roles pane on the right until you see the
link called Add Role Services, and click that link.

In the Add Role Services window, scroll down the list of Role services until
you reach the IIS 6 Management Compatibility items. Check the relevant
items as shown on the screenshot below and proceed with the installation. Notice
that the items are grayed. Thats because, in our system, the IIS 6.0
Management tools have already been installed. We just wanted to show you
where to go should you discover that those tools havent been installed yet.
With the IIS 6.0 Manager already installed, you can already configure the SMTP
service. Launch the IIS 6.0 Manager (we showed you where to find it earlier) and
navigate to SMTP Virtual Server #1.

Right-click on SMPT Virtual Server #1 and, in the context menu that appears,
select Properties. This should bring up the SMTP Virtual Server #1
Properties window.
Most of the settings here may be left to their default values. However, you may
click those tabs and change the property settings you find there to suit the needs
of your organization. For instance, in theGeneral tab, you may want to
check Enable logging if you want to perform some troubleshooting.
After closing the SMTP Virtual Server #1 Properties window, select
the Domains item that you see under SMTP Virtual Server #1. Next, right-
click on the domain name of the SMTP virtual server found in the right panel and
select Properties.

Select your desired location for the Drop directory. Of course, you may accept
the default location if you want. Click OK when done.
Youre done with configuring the SMTP service. The next part is to ensure that the
service will start automatically. To do that, go to Start > All
Programs > Administrative Tools > Services.

Once the Services window is up, scroll down until you see the item
named Simple Male Transfer Protocol (SMTP). Normally, its Startup
Type will be set to Manual.
To change that to Automatic, double-click on the item in question to bring up its
correspondingProperties window. Expand the drop-down list box beside
the Startup type property and selectAutomatic. Click Apply, then OK.

That practically covers what you have to do as with regards to SMTP

configurations on your SharePoint server. The next step is to configure SMTP
settings on the Exchange Server side.

Configuring SMTP on Exchange Server

Go to your Exchange Server and open up your Exchange Management
Console. In the screenshot below, youll notice that, in our set up, we already
created mailboxes for all our users. Were going to assume youve also done that
at your end.

The first thing to do here is to create a Send Connector. Navigate to

the Organization Configurationon the left panel, select Hub Transport, and
click the Send Connectors tab. Next, go to the Actionspanel on the right and
click New Send Connector.

This will bring up the New Send Connector Introduction screen. Give the send
connector a name, e.g. SharePoint 2010 Incoming, and specify its intended use,
e.g. Internal. When done, click Next.
In the Address Space window, youll then be asked to specify the address space
to which the connector will route mail. First, click the Add button.

Next, enter the address of the server thats handling your SMTP service into
the Address field. In this case, that server is your SharePoint server, so enter its
address there. Click OK.
That will add the address space to the list in the Address Space window.
Click Next.

When youre in the Network Settings window, youll notice the Use domain
name system option is grayed out. Thats because weve set the email to be
sent internally. Hence, mail will be routed through a set of smart hosts. If
instead we had set the emails to be sent out over the Internet, then the first
option would not have been grayed out.
To add a smart host, click the Add button.
When you start adding a smart host, youll be required to enter the IP address of
the server thats hosting your SMTP service. Again, this server is no other than
your SharePoint server. But instead of entering the FQDN like you did earlier,
which is given as the second option, its recommended that you enter the
numeric IP address. This will give you a better chance of connecting in case
certain connectivity problems occur in the future.

After clicking OK, youll see the IP address added to the list of smart hosts.
Click Next.
In the succeeding window named Configure smart host authentication
settings, just leave the option to None and click Next.

When youre in the Source Server window, make sure your Hub Transport server
is on that list. In a typical Exchange installation, which is what we have, a single
Exchange server is set to handle all three roles (i.e., Mailbox, Client Access, and
Hub Transport). So if you find your Exchange server there, chances are, youre
good to go. Click Next.
Finally, youll be shown a summary of your new Send Connector configurations.
Click New.

This will create the new send connector. Once creation is complete, click Finish.
Configuring Active Directory to allow contacts to show up in the Outlook
Address book
At this point, you will need to go to your Domain Controller and make some
changes to Active Directory to allow contacts to be created within an
organizational unit so that they show up in the Outlook Address Book after they
are created.

Go to your Domain Controller and open the Active Directory Users and
Computers.
First, create an Organizational Unit as shown.

Give the Organizational Unit a name (e.g. Sp Contacts), then click OK.
Next, change the permissions of that Organizational Unit by right-clicking it and
selecting Delegate Control.

When the welcome screen of the Delegation of Control Wizard appears,

click Next.
You will want to delegate control to the account that controls the SharePoint
Central administration application pool, which, in this case, is the SP Admin
account. Click the Add button.

Enter spadmin in the text field labeled Enter the object names to select,
then click OK.
In the next screen, select its corresponding item and click Next.

Youll then be asked whether you want to delegate a set of common tasks or
create a custom task to delegate. Select the second option and click Next.
When asked to indicate the scope of the task you want to delegate, select This
folder, existing objects in this folder, and creation of new objects in this
folder. Click Next.

In selecting the permissions you want to delegate, first

check General and Creation/deletion of specific child objects. Then, in
the Permissions list, check Create All Child Objects and Delete All Child
Objects. Click Next.
If all goes well, you will have reached the end of the Delegation of Control wizard.
If so, click Finish.

One last thing you need to do within Active Directory is to enable the SP Admin
account with the Delete Subtree permission. To do that, go to the View menu
and select Advanced Features.
This will show more items on the right-hand panel. Right-click on the SharePoint
contacts organizational unit you created earlier and select Properties.

In the properties window, navigate to the Security tab and click

the Advanced button.
In the Advanced Security Settings window, select the SPADMIN account.

This is where you will then find the Delete subtree permission. Check
its Allow checkbox.
Click OK to close that window, then click the OK button of each window you
encounter until youre back to the Active Directory Users and
Computers window.

With that, youre done setting what needs to be set in Active Directory so that
your contacts will show up in your Outlook address book. The final step is to do
an IIS reset on your SharePoint server.
Go back now to the SharePoint server. Right-click on the PowerShell quick-launch
icon then click Run as Administrator.

When the dialog window appears, click Yes.

In the PowerShell, type in iisreset to start the reset process. Wait until the reset
completes, then close the window.

Although youre already done with this phase, the next few steps will still be
performed in the SharePoint server environment, so keep it open.

Configuring Incoming Email Settings in Central Administration

Youre now ready to configure incoming email settings from inside Central
Administration. To begin, launch the SharePoint Central Administration.
Once inside the Central Administration, go to the left side of the screen and
click System Settings.

Under E-Mail and Text Messages (SMS), click Configure incoming e-mail
settings.
 On the right-hand side of the screen, youll see a bunch of option buttons, text
fields, and checkboxes that will allow you to specify certain configuration
settings. Apply the following settings:

Enable sites on this server to receive e-mail?

Select Yes
Settings mode:
Select Automatic
Use the SharePoint Directory Management Service to create
distribution groups and contacts?
Select Yes

Active Directory container where new distribution groups and

contacts will be created:
Enter the name of the container using this format:
OU=[ContainerName], DC=[domain], DC=[com] ,
wherein ContainerName is the name of the Organizational Unit you created
earlier, domain is the second-level domain, and com is the top-level domain.
For example: OU=SP Contacts, DC=carvedrockfitness, DC=com
SMTP mail server for incoming mail:
This is usually filled in automatically, so just check if it is correct.

Accept messages from authenticated users only?

Select No
Allow creation of distribution groups from SharePoint sites?
 Select No. One offshoot of selecting this option is that you wont need the
approval settings that follow. This is why youll then see the check boxes being
grayed out.

E-mail server display address:

Leave as is.

Select Accept mail from all e-mail servers

When youre done with all these, click OK.

With the configurations you just did, certain changes are expected to
automatically take effect on the Drop folder. Thus, you can verify whether the
configuration process all went well by checking the Drop folder to see whether
those changes did in fact take effect.

To do that, navigate to Start > Computer > C: > inetpub > mailroot. There
youll find the drop folder.
Right-click on the Drop folder and select Properties.

When the Drop Properties window appears, navigate to the Security tab.
Scroll down the list ofGroup or user names and see if the items
WSS_ADMIN_WPG and WSS_WPG are present. If they are, then youre
good to go.
Configurations to add a library as a contact under your organizational
unit
Before you can go to the main process of checking whether your SharePoint
incoming email feature is working, youll need to perform just a few more
configuration steps. Go now to a client system, open a Web browser and navigate
to your SharePoint site.

Next, go to the Libraries section and click a link to a library (we assume you
already have some in there). In our example, the library were about to open is
called Recipes.
To change the settings of that library, go to the Library tab and click Library
Settings.

Go to the Communications section and click the link named Incoming e-mail
settings.
 On the right-hand side of the screen, youll see another bunch of option buttons
and text fields that will allow you to specify configuration settings for this library.
Apply the following settings:

Allow this document library to receive e-mail?

Select Yes.
E-mail address:
Assign a name for the e-mail address.

Group attachments in folders?

Select an option thats best suited for you.

Overwrite files with the same name?

Select No.

Save original e-mail?

Select Yes.
Save meeting invitations?
Select No.
E-mail security policy:
At this point, just select Accept e-mail messages from any sender. However,
in a real-world scenario, you might want to choose the first option.
 When youre done with all those settings, click OK. After that, the library whose
settings you just configured will automatically be added as a contact under the
Organizational Unit created earlier. This is now a result of all those numerous
steps you went through.

Manage site quotas and lock?

Manage site quotas and locks
Microsoft
that Windows
youcalled
can manage SharePoint
site and Services
server allows you
resources. Youtocan
specify quotas
create for sites,
multiple so
sets of
quotas,
farm, or to suitquota templates,
different users. and
You use them
can all
useusersin different
locksfrom
to stop areas of
sites from the server
exceeding
your storage
necessary. quota limits, and to block accessing a site if
Create a quota template
1. Click Start, point to All Programs, point to Administrative Tools,
and then click SharePoint Central Administration.

2. On the Central Administration page, under Component

Configuration, click Manage quotas and locks.

3. On the Manage Quotas and Locks page, click Manage Quota

Templates.

4. On the Manage Quota Templates page, in the Template name area,

click Create a new quota template.

5. In the Template to start from box, select a template to base your

new template on.

6. In the New template name box, type the name to use for your new
quota template.

7. Select the Limit site storage to a maximum of: ___ MB check box,
and then type the amount of storage to allow at a maximum.

8. In the Storage Limit Values section, select the Send warning e-

mail when site storage reaches ___ MB check box, and then type the amount
of storage to allow before sending a warning e-mail message.
9. In the Invited User Limits section, select the Limit invited users to
a maximum of: ___ users, and then type the number of users to allow.

Note The user limit option is available only in Active Directory account mode.
10. Click OK.

When you
and the click
page is OK, the new template is added to the list of available templates,
refreshed.
Delete a quota template
You can delete
remember that adeleting
quota template
a quota if you change
template does your quota quota
not delete structures. However,
values from sites
that
using were
a created
particular using the
quota quota
template, template.
you must To remove
use the quotas
object from
model andallperform
sites a
SQL Server query.
1. Click Start, point to All Programs, point to Administrative Tools,
and then click SharePoint Central Administration.

2. On the Central Administration page, under Component

Configuration, click Manage quotas and locks.

3. On the Manage Quotas and Locks page, click Manage Quota

Templates.

4. On the Manage Quota Templates page, in the Template name area,

click Edit an existing template.

5. In the Template to modify box, select the quota template you want
to delete.

6. Click Delete.

When youlist
from the click OK, Windows
of available SharePoint
templates, Services
and the removes
page is the quota template
refreshed.
Change an existing quota template
You can change individual quota values in a template. The new values apply only
to new top-level Web sites created by using the quota template. Windows
SharePoint Services does not apply the changed values to existing sites unless
you use the object model to update the values in the database.

1. Click Start, point to All Programs, point to Administrative Tools,

and then click SharePoint Central Administration.
2. On the Central Administration page, under Component
Configuration, click Manage quotas and locks.

3. On the Manage Quotas and Locks page, click Manage Quota

Templates.

4. On the Manage Quota Templates page, in the Template name area,

click Edit an existing template.

5. In the Template to modify box, select the quota template to change.

6. Update the options you want to change, and then click OK.
When you click OK, Windows SharePoint Services updates the template, and
refreshes the page.

View current quota values and data for a site

1. Click Start, point to All Programs, point to Administrative Tools,
and then click SharePoint Central Administration.

2. On the Central Administration page, under Component

Configuration, click Manage quotas and locks.

3. On the Manage Quotas and Locks page, click Manage Site Collection
Quotas and Locks.

4. In the Select a top-level Web site section, type the URL in the Enter
the top level Web site URL box, and then click View Data.

5. In the Site Quota Information section, view the settings listed to see
the quota settings and current values.

To view the
Statistics current data
Summary pagefor
forathe
site, you canWeb
top-level alsosite.
use the Site Collection Usage
View quota data for a site
1. On the site you want to view data for, click Site Settings.

2. In the Administration section, click Go to Site Administration.

3. In the Site Collection Administration section, click View site
collection usage summary.

Change quota values for a site

After
Note you check
that this the site quota data, you can change the quota
and values for a does
site.
not affect any action does
site except not site
the change
you the quota
specify. template, the change
1. Click Start, point to All Programs, point to Administrative Tools,
and then click SharePoint Central Administration.

2. On the Central Administration page, under Component

Configuration, click Manage quotas and locks.

3. On the Manage Quotas and Locks page, click Manage Site Collection
Quotas and Locks.

4. In the URL of top-level Web site section, type the URL in the Enter
the top-level Web site URL box, and then click View Data.

5. In the Site Quota Information section, change the Limit storage to

a maximum of __ MB amount, Send warning e-mail when site storage
reaches __MB amount, or Maximum users allowed amount setting.

Note Theservice.
directory user limit option is available only in account mode for Active Directory
6. Click OK.

Lock a site manually

1. Click Start, point to All Programs, point to Administrative Tools,
and then click SharePoint Central Administration.

2. On the Central Administration page, under Component

Configuration, click Manage quotas and locks.

3. On the Manage Quotas and Locks page, click Manage Site Collection
Quotas and Locks.

4. In the URL of top-level Web site section, type the URL in the Enter
the top-level Web site URL box, and then click View Data.

5. In the Site Lock Information section, select Adding content

prevented or No access. Choosing No access blocks all access to the site
 including viewing pages. Choosing Adding content prevented blocks adding
new subsites or content, but does not block reading or deleting content.

6. the Additional
To addlock
details about the reason
information: box. for the lock, type an explanation in
7. Click OK.

Unlock a site
When a site
Settings andisLocks
locked manually, you can unlock it by using the Site Quota
page.
1. Click Start, point to All Programs, point to Administrative Tools,
and then click SharePoint Central Administration.

2. On the Central Administration page, under Component

Configuration, click Manage quotas and locks.

3. On the Manage Quotas and Locks page, click Manage Site Collection
Quotas and Locks.

4. In the URL of top-level Web site section, type the URL in the Enter
the top-level Web site URL box, and then click View Data.

5. In the Site Lock Information section, select Not locked, and then
click OK.

Quotas in sharepoint 2010?

Quotas
Inside
A QuotaSharePoint
specifies 2010,
the the administratorofcan control the be
storage limits ofausers.
collection.
sites. The We can
Quota alsomaximum
make
Settings allows
amount
a Quota
Email
data
Template thatcan
that
Notifications in
can stored
be the
case used inside
across
quota
site
other
limit
exceeded a particular level.
Please follow the steps mentioned to change the Quota Settings.
Open the Central
Site Collections > Administration website and navigate to Application Settings >
Specify Quota Templates.

In the appearing
Personal page as
Site template. shown
You may below
wish toyou can a
create edit the maximum
separate size
template as for the
well.
The Quota Settings will be sending Email Notification in case of the warning limit
exceeded.
The above
affect settings
all the sites are for
using the
this Quota Template.
template. Any change in the template will
site collection
steps. Quota without changing If
theyou wanted
Quota to change
template only
use the a particular
following
Click onshown
link as the Application
below. Settings > Site Collections > Configure Quotas and Locks

In the appearing page you can set the Quota check box. By default it is
unchecked.
Locks
Locks allow
deleting the administrator
contents in a site to disallow
collection. users from viewing / adding / migrating
editing /
or doing
in the backup/restore
Administrators activities.
group. ForThis option
performing could be useful
this action the while
user should be
Following are the locking options available in SharePoint 2010.
Not Locked: This is the default scenario where users can view / edit site
contents
Adding Content Prevented: Adding new contents are blocked but edit / delete
are allowed.
Read Only: Users can only view the contents. Add / Edit / Delete are not allowed
No Access: Users are not allowed to access the site.
For
web locking a particular
site open site, use
the Application the following
Management > steps. From Central
Site Collections Administration
> Configure quotas
and locks option.

In the appearing page as shown below, change the Lock status as shown below.

Click the OKdefault

SharePoint buttonweb
to save
site.the
Youchanges. Now
will get the you canerror
following try accessing
message.your

After testing please ensure you change the lock status back to Not locked.
Sharepoint service accounts?
Account Purpose
sp13_dev_sql The SQL Server service accounts are used to run
 SQL Server. It is the service account for the
following SQL Server services:
MSSQLSERVER
sp13_dev_sqlAgent SQLSERVERAGENT
If you do not use the default SQL Server
sp13_dev_sqlAnalysis
instance, in the Windows Services console, these
services will be shown as the following:

MSSQL<InstanceName>
SQLAgent<InstanceName>
The Setup user account is used to run the
following:
sp13_dev_setup Setup
SharePoint Products Configuration
Wizard
The server farm account is used to perform the
following tasks:
sp13_dev_farm Configure and manage the server
(Server farm account
farm.
or database access
account) Act as the application pool identity for
the SharePoint Central Administration Web site.
Run the Microsoft SharePoint
Foundation Workflow Timer Service.
This a domain account used for application pool
identity. For e.g. When you create a Web
sp13_dev_pool
Application, and you create a pool for it, you
select this account!
This a domain account used for the Service
Applications Pools. For e.g. When you create a
sp13_dev_Services
Managed Metadata Service application and
create a pool for it, you select this account!
sp13_dev_Crawl This used within the Search Service Application
 to crawl content. The Search Service Application
will automatically grant this account read access
on all Web Applications.
This is used to run the SharePoint Windows
sp13_dev_Search
Search Service.
This the account used for the User Profile
Synchronization between your Service
Application and your Active Directory. This
sp13_dev_UserProfile
account does not need any local rights; however
you need to give it Replicate Directory
Changes rights on the Active Directory in order
to allow the synchronization.
Note : Number of Service accounts depends upon your organizations
requirements. Go ahead and add\remove accounts as per your convenience

Understanding sharepoint central Administration

Application Mangement:
Understanding System Settings in SharePoint Central Administration
The System
settings. Settings
shows sectionSettings
the System containssection.
a lot of configuration options for farmwide

System Settings
As youdiscussed
parts, can see the various
in the configuration
following sections.options are divided into three major
Servers
The Servers
Servers in section
This Farm allows
screenyou
liststothe
configure
servers the servers
in screen
the farm in the farms. The
toManage
remove them.
saw in the The Manage
Understanding Services
Application on Server
Management is and allows
the same
section
you
... as the one you

Understanding Monitoring in SharePoint Central Administration

The Monitoring
logging, section shows
and reporting. allows the
youMonitoring
to configuresection.
various options related to timer jobs,
The configuration settings in the Monitoring section are discussed in the following
sections.
Understanding Backup and Restore in SharePoint Central Administration
The
to Backup and
performing andRestore section
restoring allows
backups onyou
yourtoSharePoint
perform various operations
farm.Backup.
This related
is divided into
mainly two sectionsFarm Backup and Restore and Granular
Farm Backup and Restore
This sectionfarm.
SharePoint allows you to perform
Following are the backup and
important restoreinoperations
screens on the entire
this section:
Perform
farm. a BackupThis
This includes screen allows
the configuration you to
database, back up
solution the entire
store, SharePoint
SharePoint web
applications, and shared
specific components services.
within In in
the farm addition this
case you ...screen allows you to back up

Understanding Security in SharePoint Central Administration

The Security
SharePoint section
farm. Theallows yousections
following to configure thethe
discuss security settings
important for the
Security screens.
Exploring Users Settings
The Users section
administrators contains
group and tovarious
manage settings tothe
users in manage users
Approve in the farm
orapplication
Reject distribution
groups.
through In addition
the Specifyyou
Webcan provide
Applicationusers
User access at the web
Policy screen. level
General Security
This section
following list:allows you to configure various security settings as described in the
Configure
delete Managed
managed AccountsThis
accounts. screen...
A managed account allows you to add, edit, and

Specify user policy for web application

These screens allow an administrator to set permissions per web application.
They are like site collection permissions, but permission here apply to all sites in
a web application.
The "permission policies" define groups of permission rights (similar to
permissions levels of a site collection).

Full Read - good for search/caching

Full Control - good for global admins
Deny Write - good for public facing
Deny All - good for restricted sites
The "user policy" area, then allows you to assign those permission polices to
certain users/groups.

The default users policies for example, allow the search account to read all sites
in a web application, without having to set permissions individually on each site
collection. Another policy you should add is for the caching account.

An example of a custom policy, would be denying deleting items/version on a

whole web application for certain users, maybe for an public facing extended
web application

Understanding Upgrade and Migration in SharePoint Central Administration

This
patchscreen allows you
management. Theto important
manage the various settings
screens related
section to
areupgrade and
and Patch
installed inInstallation Status,
your SharePoint which
farm lists thewithin
as shown variousthis
components the patches
and Product

How to convert farm licence:

Go to CAclickonugrade and migration click on converfarmlicence

How to convert standard to enterprise version:

 How to check patch status

How to check the database status

How to install service pack 1 in sharepoint 2010

1. Download SharePoint Foundation 2010 SP1

2. The installation process will ask you to reboot. Reboot the server.

3. Once the server has rebooted, start the SharePoint Configuration

Wizard and complete the process.

4. Upon completion you should be able to open Central Administration

Window.

For your SharePoint 2010 Standard / Enterprise Server, complete the following
steps

1. Download SharePoint Foundation 2010 SP1

2. Download SharePoint Server SP1

3. Install SharePoint Foundation 2010 SP1

4. The installation will ask you to reboot. There is no need for it, so you
can cancel the same.

5. Install SharePoint Server SP1.

6. The installation will ask you to reboot. Reboot the server at this stage.

7. Once the server has rebooted, start SharePoint Configuration Wizard

and complete the process.

8. Upon completion you should be able to open Central Administration

window.

Tada, your SharePoint will now SP1d

Before a SharePoint server is upgraded and being a vanilla install it will have the
following version number
Once the upgrade is completed, SharePoint server will contain the following
version number
Understanding General Application Settings in SharePoint Central Administration
As
andthe name suggests
features, this
which can besection
dividedallows you to configure
as discussed many sections.
in the following general settings