Step by Step Administration by Step Administration Hussain Shakir LinkedIn: Twitter: Blog: Step by Step SharePoint Manual 1 Table of Contents

Step by Step Administration

Hussain Shakir

LinkedIn: https://www.linkedin.com/in/mrhussain

Twitter: https://twitter.com/hshakir_ms

Blog: http://mstechguru.blogspot.com/

https://www.linkedin.com/in/mrhussain

https://twitter.com/hshakir_ms

http://mstechguru.blogspot.com/

Step by Step SharePoint Manual

1

Table of Contents

About Author .................................................................................................................................... 3

1. Manage Permissions .............................................................................................................. 4

1.1. Create SharePoint Group ................................................................................................ 4

1.2. Permission Levels ........................................................................................................... 5

1.3. Add users to a SharePoint group or directly to the site ................................................... 9

1.4. Remove users from a SharePoint group ........................................................................ 10

1.5. Delete a SharePoint group ............................................................................................ 10

1.6. Edit group Quick Launch list ......................................................................................... 10

1.7. Grant permissions for a site .......................................................................................... 11

1.7.1. Make sure you have the correct permissions. ........................................................... 11

1.7.2 Review the existing permissions settings for your site. .................................................... 12

1.7.3. Add groups with the right people in them................................................................. 15

1.8. Mange List or Document Library Permissions ............................................................... 18

1.8.1. View users and SharePoint groups associated with a list or library ................................. 18

1.8.2. View users and SharePoint groups associated with a folder, document, or list item ....... 18

1.8.3. Edit permission assignments on permission levels on a list or library ........................ 18

1.8.4. Edit permission assignments on permission levels on a folder, document, or list item

19

1.8.5. Break permission inheritance on a list or library ....................................................... 20

1.8.6. Break permission inheritance on a folder, document, or list item ............................. 20

1.8.7. Inherit permissions for a list or library ...................................................................... 21

1.8.8. Inherit permissions for a folder, document, or list item ............................................ 22

1.8.9. Remove user permissions from a list or library ......................................................... 22

1.8.10. Remove user permissions from a folder, document, or list item ............................... 23

2. Site Management 2.1. Create Web application .................................................................... 24

To create a Web application that uses Windows-classic authentication by using Central

Administration ......................................................................................................................... 24

2.2. Create, edit, and delete quota templates ..................................................................... 26

To create a quota template ...................................................................................................... 26

To edit a quota template ......................................................................................................... 26

To delete a quota template ...................................................................................................... 27


2

2.3. Create a site collection ................................................................................................. 27

To create a site collection by using Central Administration ...................................................... 28

2.4. Add or remove site collection administrators ............................................................... 28

To add a site collection administrator by using Central Administration .................................... 28

2.5. Lock or unlock site collections ...................................................................................... 29

To lock or unlock a site collection by using Central Administration ........................................... 29

2.6. How to Recover Data from an Unattached Content Database ....................................... 30


3

About Author

Shakir is IT Consultant with over 13 years of extensive experience working with Microsoft

Technologies AD, Exchange, O365, Windows Azure, PowerShell, Skype for Business, SQL,

SharePoint and Microsoft public clouds, and providing solutions to different local &

international Enterprise customers.

Shakir has been involved in Infrastructure Designing and Implementation, Virtualization, and

Disaster Recovery. Extensive hands-on experience in Core Server Infrastructure, Cloud

Computing, Virtualization/ Management and Information Protection. Analysis and Support of

Microsoft Windows Server based Client / Server network, AD, Messaging, Skype for Business,

SQL Always ON, Virtualization and System Center Infrastructure Products. Shakir has various

industry certifications: MCT, MCTS, MCITP, MCSA, MCSE: Messaging, MCPS, MCSE: Cloud

Platform and Infrastructure and also providing trainings on Microsoft Based Technologies.


4

1. Manage Permissions A fundamental responsibility concerning site security is to manage who can access resources on your

site. SharePoint enables you, as a site owner, to control which users or groups of users have access

to your SharePoint sites.

1.1. Create SharePoint Group

SharePoint installs with several prebuilt groups but in practice you will want to create custom groups for you company.

Adding a group is very simple:

1. In Site Settings > Site Permissions. Click Create Group

Figure 1.1.1

2. As shown in figure 1.1.2. Add the name of the group, brief description. 3. Select group owner, by default the logged on user. 4. Select who can view and edit membership. 5. Choose the permission level group members get on this site: http://sharepointapp:2012

http://sharepointapp:2012/


5

Figure 1.1.2. Create SharePoint Group

1.2. Permission Levels

Although sites that are built on SharePoint often have additional default SharePoint groups,

SharePoint includes five permission levels by default. Each of these permission levels has

specific permissions associated with it. As a site owner, you can choose which permissions

are associated with these permission levels (except for the Limited Access and Full Control

permission levels) or add new permission levels to combine different sets of permissions.

As a site owner, you can associate permissions with permission levels and also associate

permission levels with users and SharePoint groups. Users and SharePoint groups are

associated with securable objects such as sites, lists, list items, libraries, folders within lists

and libraries, and documents.

The following tables list and describe the permission levels that you can assign to users and

SharePoint groups and the permissions you can assign to permission levels. For each

permission, the permission level that it is associated with it, by default, is listed. For each

permission, any permissions dependent on it are listed, as well as any default permission

levels that include the permission.

Default permission levels in SharePoint

Permission Level Description

Full Control This permission level contains all permissions. Assigned to the Site name Owners SharePoint group, by default. This permission level cannot be customized or deleted.

Design Can create lists and document libraries, edit pages and apply themes, borders, and style sheets in the Web site. Not assigned to any SharePoint group, by default.

Contribute Can add, edit, and delete items in existing lists and document libraries. Assigned to the Site name Members SharePoint group, by default.

Read Read-only access to the Web site. Users and SharePoint groups with this permission level can view items and pages, open items, and documents. Assigned to the Site name Visitors SharePoint group, by default.

Limited Access

The Limited Access permission level is designed to be combined with fine-grained permissions to give users access to a specific list, document library, item, or document, without giving them access to the entire site. However, to access a list or library, for example, a user must have permission to open the parent Web site and read shared data such as the theme and navigation bars of the Web site. The Limited Access permission level cannot be customized or deleted.

List, site, and personal permissions

SharePoint includes 33 permissions, which are used in the five default permission levels. You can change which permissions are included in a particular permission level (except for the Limited Access and Full Control permission levels) or create a new permission level to contain a specific set of permissions that you specify.


6

Permissions are categorized as list permissions, site permissions, and personal permissions, depending upon the objects to which they can be applied. For example, site permissions apply to a particular site, list permissions apply only to lists and libraries, and personal permissions apply only to things like personal views, private Web Parts, etc. The following tables show permissions and the permission levels they are assigned to, by default.

List Permissions

Permission Full Control Design Contribute Read Limited Access

Manage Lists X X

Override Check-Out

X X

Add Items X X X

Edit Items X X X

Delete Items X X X

View Items X X X X

Approve Items X X

Open Items X X X X

View Versions X X X X Delete Versions X X X

Create Alerts X X X X

View Application Pages

X X X X X

Site Permissions

Permission Full Control

Design Contribute Read Limited Access

Manage Permissions X

View Usage Data X

Create Subsites X

Manage Web Site X

Add and Customize Pages

X X

Apply Themes and Borders

X X

Apply Style Sheets X X Create Groups X

Browse Directories X X X

Delete Versions X X X

Use Self-Service Site Creation

X X X X

View Pages X X X X

Enumerate Permissions

X

Browse User Information

X X X X X

Manage Alerts X

Use Remote Interfaces

X X X X X

Use Client Integration Features

X X X X X

Open X X X X X


7

Edit Personal User Information

X X X

Personal Permissions

Permission Full Control Design Contribute Read Limited Access

Manage Personal Views

X X X

Add/Remove Private Web Parts

X X X

Update Personal Web Parts

X X X

Dependencies and descriptions

Many permissions are dependent on other permissions. When you select a

permission that is dependent on another, the permission on which it is dependent

is also automatically selected. Likewise, clearing a permission on which other

permissions are dependent also clears the dependent permissions. The following

tables describe what each permission is used for and lists dependent permissions, if

applicable.

List Permissions

Permission Description Dependent permissions

Manage Lists Create and delete lists, add or remove columns in a list, and add or remove public views of a list.

View Items, View Pages, Open, Manage Personal Views

Override Check-Out Discard or check in a document which is checked out to another user.

View Items, View Pages, Open

Add Items Add items to lists, add documents to document libraries, and add Web discussion comments.


Edit Items Edit items in lists, edit documents in document libraries, edit Web discussion comments in documents, and customize Web Part Pages in document libraries.


Delete Items Delete items from a list, documents from a document library, and Web discussion comments in documents.


View Items View items in lists, documents in document libraries, and Web discussion comments.

View Pages, Open

Approve Items Approve a minor version of a list item or document.

Edit Items, View Items, View Pages, Open

Open Items View the source of documents with server-side file handlers.


View Versions View past versions of a list item or document.



8

Delete Versions Delete past versions of a list item or document.

View Items, View Versions, View Pages, Open

Create Alerts Create e-mail alerts. View Items, View Pages, Open

View Application Pages View documents and views in a list or document library.

Open

Site Permissions


Manage Permissions Create and change permission levels on the Web site and assign permissions to users and groups.

Approve Items, Enumerate Permissions, Open

View Usage Data View reports on Web site usage. Approve Items, Open

Create Subsites Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.

View Pages, Open

Manage Web Site Perform all administration tasks for the Web site as well as manage content.

View Pages, Open

Add and Customize Pages

Add, change, or delete HTML pages or Web Part pages, and edit the Web site using a Windows SharePoint Services-compatible editor.

View Items, Browse Directories, View Pages, Open

Apply Themes and Borders

Apply a theme or borders to the entire Web site.

View Pages, Open

Apply Style Sheets Apply a style sheet (.css file) to the Web site. View Pages, Open

Create Groups Create a group of users that can be used anywhere within the site collection.

View Pages, Open

Browse Directories Enumerate files and folders in a Web site using an interface such as SharePoint Designer or Web-based Distributed Authoring and Versioning (Web DAV).

View Pages, Open

Use Self-Service Site Creation

Create a Web site using Self-Service Site Creation.

View Pages, Open

View Pages View pages in a Web site. Open

Enumerate Permissions

Enumerate permissions on the Web site, list, folder, document, or list item.

View Items, Open Items, View Versions, Browse Directories, View Pages, Open

Browse User Information

View information about users of the Web site. Open

Manage Alerts Manage alerts for all users of the Web site View Items, Create Alerts, View Pages, Open

Use Remote Interfaces

Use Simple Object Access Protocol (SOAP), Web DAV, or SharePoint Designer interfaces to access the Web site.

Open

Open Open a Web site, list, or folder to access items inside that container.

No dependent permissions

Edit Personal User Information

Allow a user to change his or her own user information, such as adding a picture.

Browse User Information, Open


9

Personal Permissions


Manage Personal Views

Create, change, and delete personal views of lists. View Items, View Pages, Open

Add/Remove Private Web Parts

Add or remove private Web Parts on a Web Part Page.

View Items, View Pages, Open, Update Personal Web Parts

Update Personal Web Parts

Update Web Parts to display personalized information.


To create a new permission level

1. In Site Settings > Site Permissions. Click Permission Levels

2. Click Add Permission Level

3. Name the new permission level and configure the permissions using the

checkbox listing and then click Create.

4. The new permission you just created should now be visible in the Permissions

listing and you can select it and click OK.

Figure 1.2.1 Create new permission level.

1.3. Add users to a SharePoint group or directly to the site

On the Site Actions menu , click Site Settings.

Note On a site for which the Site Actions menu is customized, point to Site Settings, and then click the settings that you want to view.

1. On the Site Settings page, in the Users and Permissions column, click People and groups. 2. On the People and Groups page, in the Quick Launch, click Groups. 3. On the People and Groups: All Groups page, in the Group column, click the link for the

SharePoint group to which you want to add users. 4. On the People and Groups: GroupName page, on the New menu, click Add Users.


10

5. On the Add Users page, in the Add Users section, use the Browse button to select the users you want to add to this SharePoint group. Alternatively, type the user names, Windows domain group names, or e-mail addresses, separated by semicolons, that you want to add to this SharePoint group.

6. In the Give Permission section, either select a SharePoint group from the Add users to a SharePoint group list or select Give users permission directly, and then select the permission level you want to assign to this group.

Note Adding permission directly adds the users directly to the site, rather than to a SharePoint group.

7. Click OK.

1.4. Remove users from a SharePoint group




SharePoint group from which you want to remove users. 4. Select the check boxes for the users you want to remove from this SharePoint group. 5. On the Actions menu, click Remove Users from Group. 6. Click OK to confirm the action.

1.5. Delete a SharePoint group




SharePoint group that you want to delete. 4. On the Settings menu, click Group Settings. 5. On the Change Group Settings page, scroll to the bottom of the page, and then click Delete. 6. Click OK to confirm the action.

1.6. Edit group Quick Launch list

Use the following steps to specify what SharePoint group names appear in the Quick Launch on the People and Groups page.



11


1. On the Site Settings page, in the Users and Permissions column, click People and groups. 2. On the People and Groups page, in the Quick Launch, click Groups. 3. On the People and Groups: All Groups page, on the Settings menu, click Edit Group Quick

Launch. 4. On the Edit Group Quick Launch page, in the Groups section, add the existing SharePoint

groups that you want to appear in the Quick Launch, and remove those that you do not want to appear.

5. Click OK.

1.7. Grant permissions for a site

The integrity, confidentiality, and privacy of your organization’s mission-critical information rests on how secure you make your site – specifically, who you choose to grant access to your site.

The process of granting and restricting access to your SharePoint sites and content is called managing permissions.

You manage permissions by using SharePoint groups, which control membership, or by using fine-grained permissions, which help you control content at the item or document level. This article focuses on using SharePoint groups to control access to a site.

1.7.1. Make sure you have the correct permissions.

To manage permissions for a site, you must have the Manage Permissions level for the site or content.

To make sure you can manage permissions for a site, click the Site Actions menu and ensure that you can see the Site Permissions link, which looks like this:


12

If you cannot see the Site Permissions link, you’ll need to follow your organization’s process for requesting permissions.

1.7.2 Review the existing permissions settings for your site.

There are two situations in which you’re most likely to be thinking about permissions for a site:

You’ve added a new site to a site collection. If this is the case, your new site inherits the permissions settings from the site above it in the site collection hierarchy.

You’ve taken over ownership for an existing site that was created by someone else. If this is the case, the site might not inherit permissions settings from the site above it – the previous owner might have broken that inheritance to set custom permission settings.

Either way, you can see who has access to your site on the site’s permission page. You can also check this page to see whether the site inherits permissions from the site above it.

To open a site’s permission page:

1. Click Site Permissions on the Site Actions menu.


13

Here’s an example of the permissions page for a new team site, Contoso11/Research, which inherits permissions from a site called Contoso11:

The Name column lists SharePoint groups with permissions to the site. The Permission Levels column lists the permission levels granted to each group. For

example, the Contoso Owners group has Full Control and Limited access permission levels.

Next, see the members of any group by clicking the group name in the Name column:


14

(A) Christa Geller and (B) Diane Prescott are members of the Contoso11 Owners group.

Note You can check the permission levels for anyone in your organization. Click Check Permissions on the permissions page for the site and then type the name of the person you want to check in the User\Group box.


15

1.7.3. Add groups with the right people in them

1. Click Site Permissions on the Site Actions menu to open the site permissions page. 2. Click the Grant Permissions button. 3. In the Grant Permissions dialog box, type the names of the groups (or users) to whom you

want to grant access to your site. If you type the names of users, it’s a good idea to add them to an existing group in the second section of the dialog box, Grant Permissions. (You can grant permissions to individual users directly, but the cost of maintaining a system like that adds up quickly.)

4. Click OK.

To change the permissions assigned to a user or group:

1. Click Site Permissions on the Site Actions menu to open the site permissions page. 2. Click the name of the user or group, and then click the command on the ribbon that you

want to use.


16

Here are a couple examples using the hypothetical site Contoso, which includes a Visitors group and an Approvers group.

To add a new member to the Contoso Visitors group, in the following example, first you would open the site permissions page.

Next, click the Contoso Visitors link under Name to display the members of the group:

On the New menu, click Add Users, and then type the name of the person you want to add, in this case, Sean Chai, and then click OK:


17

Now Sean is a member of the visitors group.

To remove the Approvers group for the Research site, you would click Approvers and then click Remove User Permissions:

You can use the commands on the ribbon to restore inheritance from the parent site, or to grant, modify, check, or manage permissions for the site.


18

1.8. Mange List or Document Library Permissions

SharePoint provides the ability to manage permissions on individual lists and libraries, and on individual folders, documents, and list items within those lists and libraries. If you have sensitive information stored in a particular securable object and you do not want to expose the information to all members of a site, you can add or remove users and SharePoint groups with the permission levels you want them to have on a particular securable object.

Any users with the Manage Permissions permission on a particular securable object, such as a list, library, folder within a list or library, document, or list item can manage permissions on that particular securable object.

By default, Site Owners have the Manage Permissions permission. Any user with the Full Control permission level on a particular securable object can also manage permissions on that securable object.

1.8.1. View users and SharePoint groups associated with a list or library

1. Open the list or library in which you want to view users and SharePoint groups. 2. On the Settings menu, click Document Library Settings or List Settings. 3. On the Customize page, in the Permissions and Management column, click Permissions for

this document library or Permissions for this list.

The Permissions: Securable object name page displays all users and SharePoint groups (and their assigned permission levels) that are applied on this securable object.

Note The page description describes the inheritance status for this securable object. Also, check boxes appear next to the Users/Groups column if unique permissions are being used for this securable object.

1.8.2. View users and SharePoint groups associated with a folder, document, or list item

1. Open the list or library which contains the folders, document, or list item for which you want to view users and SharePoint groups.

2. Rest the pointer on the folder, document, or list item for which you want to view permissions, click the arrow that appears, and then click Manage Permissions.

The Permissions : Securable object name page displays all users and SharePoint groups and their assigned permission levels that are applied on this securable object.

Note The page description describes the inheritance status for this securable object. Also, check boxes appear next to the Users/Groups column if unique permissions are being used for this securable object.

1.8.3. Edit permission assignments on permission levels on a list or library

Use the following steps to edit the permission assignments for permission levels of selected users and SharePoint groups associated with a list or library. Note that if the securable object on which you are editing permission levels is inheriting permissions from a parent securable object, performing the following steps breaks this inheritance.


19

At a later time, you can choose to re-inherit permissions from the parent securable object. Note that inheriting permissions from the parent discards any unique permissions that may have been created for this securable object, such as unique SharePoint groups or permission level assignments that was created at this securable object while using unique permissions.

1. Open the list or library on which you want to edit permission levels. 2. On the Settings menu, click List Settings or Document Library Settings. 3. On the Customize page, in the Permissions and Management column, click Permissions for

this list or Permissions for this document library.

The Permissions page displays all users and SharePoint groups associated with this library and their assigned permission levels.

Note The page description describes the inheritance status for this securable object. Also, check boxes appear next to the Users/Groups column if unique permissions are being used for this securable object. If check boxes do not appear next to the user and group names on the Permissions page, permissions are being inherited from a parent securable object.

4. If your list or library is inheriting permissions, you must first stop inheriting permissions to edit permission levels on this securable object. To do this, on the Actions menu, click Edit Permissions, and then click OK to confirm.

5. Select the check boxes for the users and SharePoint groups on which you want to edit permission levels on this securable object.

6. On the Actions menu, click Edit User Permissions. 7. In the Choose Permissions section, select the permission levels you want, clear those you do

not want, and then click OK.

1.8.4. Edit permission assignments on permission levels on a folder, document, or list item

Use the following steps to edit the permission levels of selected users and SharePoint groups associated with a folder, document, or list item. Note that if the securable object on which you are editing permission levels is inheriting permissions from a parent securable object, performing the following steps breaks this inheritance.

At a later time, you can choose to re-inherit permissions from the parent securable object. Note that inheriting permissions from the parent discards any unique permissions that may have been created for this securable object, such as unique SharePoint groups or permission level assignments that was created at this securable object while using unique permissions.

1. Open the list or library that contains the folder, document, or list item, on which you want to edit permission levels.

2. Click the drop-down menu to the right of the folder, document, or list item on which you want to edit permission levels, and then click Manage Permissions.

The Permissions : Securable object name page displays all users and SharePoint groups at this securable object and their assigned permission levels.



20

3. If your list or library is inheriting permissions, you must first stop inheriting permissions to edit permission levels on this securable object. To do this, on the Actions menu, click Edit Permissions, and then click OK to confirm.

4. Select the check boxes for the users and SharePoint groups on which you want to edit permission levels on this securable object.

5. On the Actions menu, click Edit User Permissions. 6. In the Choose Permissions section, select the permission levels you want, clear those you do

not want, and then click OK.

1.8.5. Break permission inheritance on a list or library

By default, lists and libraries inherit permissions from the parent site. Use the following steps if you want to break this inheritance and create unique permissions on a particular list or library.

At a later time, you can choose to re-inherit permissions from the parent securable object. Note that inheriting permissions from the parent discards any unique permissions that may have been created for this securable object, such as unique SharePoint groups or permission level assignments that was created at this securable object while using unique permissions. Note that all unique permission level assignments are also discarded from folders in lists and libraries, list items, and documents within the list or library when you choose to re-inherit permissions.

1. Open the list or library in which you want to break inheritance from the parent securable object.

2. On the Settings menu, click List Settings or Document Library Settings. 3. In the Permissions and Management column, click Permissions for this list or Permissions for

this document library.

The Permissions : Securable object name page displays all users and SharePoint groups for this securable object and their assigned permission levels.


4. On the Actions menu, click Edit Permissions, and then click OK to confirm the action.

Note The Edit Permissions option is not available on the Actions menu if this securable object has unique permissions that are not being inherited from the parent securable object.

1.8.6. Break permission inheritance on a folder, document, or list item

By default, folders, documents, and list items inherit permissions from their parent securable object. In most cases, this means that they inherit their permissions from the list or library that contains them. In the case where folders, documents, and list items are contained by other folders, they would, by default, inherit permissions from the folder that contains them. Use the following steps if you want to break this inheritance and create unique permissions on a particular folder, document, or list item.

At a later time, you can choose to re-inherit permissions from the parent securable object. Note that inheriting permissions from the parent discards any unique permissions that may have been created


21

for this securable object, such as unique SharePoint groups or permission level assignments that were created at this securable object while using unique permissions.

1. Open the list or library that contains the folder, document, or list item on which you want to break inheritance from the parent securable object.

2. Rest the pointer on the folder, document, or list item on which you want to break inheritance, click the arrow that appears, and then click Manage Permissions.

The Permissions page displays all users and SharePoint groups on this securable object and their assigned permission levels.


3. On the Actions menu, click Edit Permissions, and then click OK to confirm the action.

Note The Edit Permissions option is not available on the Actions menu if this securable object has unique permissions that are not being inherited from the parent securable object.

1.8.7. Inherit permissions for a list or library

By default, lists and libraries inherit permissions from the parent site. However, this inheritance can be broken to create unique permissions on a particular securable object. You can re-inherit permissions at any time. Use the following steps to re-inherit permissions from the parent securable object for a list or library that is currently using unique permissions that are not inherited from the parent.

Inheriting permissions from the parent discards any unique permissions that may have been created for this securable object, such as unique SharePoint groups or permission level assignments that were created at this securable object while using unique permissions.

1. Open the list or library on which you want to re-inherit permissions. 2. On the Settings menu, click List Settings or Document Library Settings. 3. On the Customize page, in the Permissions and Management column, click Permissions for



Note The page description describes the inheritance status for this securable object. Also, check boxes appear next to the Users/Groups column if unique permissions are being used for this securable object. If check boxes do not appear next to the user and group names on the Permissions page, permissions are already being inherited from a parent securable object.

4. On the Actions menu, click Inherit Permissions and then click OK to confirm the action.


22

1.8.8. Inherit permissions for a folder, document, or list item

By default, folders, documents, and list items inherit permissions from their parent securable object. In most cases, this means that they inherit their permissions from the list or library that contains them. In the case where folders, documents, and list items are contained by other folders, they would, by default, inherit permissions from the folder that contains them. Use the following steps to re-inherit permissions from the parent securable object for a folder, document, or list item that is currently using unique permissions that are not inherited from the parent.

Inheriting permissions from the parent discards any unique permissions that may have been created for this securable object, such as unique SharePoint groups or permission level assignments that were created at this securable object while using unique permissions.

1. Open the list or library that contains the folder, document, or list item on which you want to re-inherit permissions.

2. Rest the pointer on the folder, document, or list item on which you want to re-inherit permissions, click the arrow that appears, and then click Manage Permissions.

The Permissions page displays all users and SharePoint groups at this securable object and their assigned permission levels.

Note The page description describes the inheritance status for this securable object. Also, check boxes appear next to the Users/Groups column if unique permissions are being used for this securable object. If check boxes do not appear next to the user and group names on the Permissions page, permissions are already being inherited from a parent securable object.

3. On the Actions menu, click Inherit Permissions and then click OK to confirm the action.

1.8.9. Remove user permissions from a list or library

Use the following steps to remove users or SharePoint groups from a list or library.

1. Open the list or library on which you want to remove user permissions. 2. On the Settings menu, click List Settings or Document Library Settings. 3. On the Customize page, in the Permissions and Management column, click Permissions for



Notes

The page description describes the inheritance status for this securable object. Also, check boxes appear next to the Users/Groups column if unique permissions are being used for this securable object. If check boxes do not appear next to the user and group names on the Permissions page, permissions are being inherited from a parent securable object.

If permissions are being inherited from the parent, you cannot remove users at this securable object. If you want to delete users and SharePoint groups from the parent securable object (which this securable object inherits those permissions from), you must manage the permissions of the parent.


23

4. Perform one of the following: To manage the permissions of the parent, on the Actions menu, click Manage

Permissions of Parent. If you are currently inheriting permissions from the parent and want to break this

inheritance and create unique permissions for this securable object, on the Actions menu, click Edit Permissions, and then click OK to confirm the action.

If the list or library is already using unique permissions that are not inherited from the parent, proceed to the next step.

5. Select the check boxes for the users and SharePoint groups you want to remove from this list or library.

6. On the Actions menu, click Remove User Permissions, and then click OK to confirm the action.

1.8.10. Remove user permissions from a folder, document, or list item

Use the following steps to remove users or SharePoint groups from a folder, document, or list item.

1. Open the list or library that contains the folder, document, or list item on which you want to remove user permissions.

2. Rest the pointer on the folder, document, or list item on which you want to remove user permissions, click the arrow that appears, and then click Manage Permissions.

The Permissions page displays all users and SharePoint groups on this securable object and their assigned permission levels.

Notes

The page description describes the inheritance status for this securable object. Also, check boxes appear next to the Users/Groups column if unique permissions are being used for this securable object. If check boxes do not appear next to the user and group names on the Permissions page, permissions are being inherited from a parent securable object.

If permissions are being inherited from the parent, you cannot remove users on this securable object. If you want to delete users and SharePoint groups from the parent securable object (which this securable object inherits those permissions from), you must manage the permissions of the parent.

3. Perform one of the following: To manage the permissions of the parent, on the Actions menu, click Manage

Permissions of Parent. If you are currently inheriting permissions from the parent and want to break this

inheritance and create unique permissions for this securable object, on the Actions menu, click Edit Permissions, and then click OK to confirm the action.

If this securable object is already using unique permissions that are not inherited from the parent, proceed to the next step.

4. Select the check boxes for the users and SharePoint groups you want to remove from this securable object.

5. On the Actions menu, click Remove User Permissions, and then click OK to confirm the action.


24

2. Site Management

2.1. Create Web application

A Web application is composed of an Internet Information Services (IIS) Web site that acts as a logical unit for the site collections that you create. Before you can create a site collection, you must first create a Web application.

Each Web application is represented by a different IIS Web site with a unique or shared application pool. You can assign each Web application a unique domain name.

You use Web applications to isolate content. When you create a new Web application, you also create a new content database and define the authentication method used to connect to the database. In addition, you define an authentication method to be used by the IIS Web site in SharePoint Server 2010.

SharePoint Server 2010 offers two ways of authenticating users, as follows:

- Classic mode authentication, through which users log on to a Web application by using Windows authentication.

- Claims-based authentication, through which users log on to a Web application by using Windows authentication, forms-based authentication (FBA), or Trusted Identity provider (SAML). If you use FBA or SAML, you must perform additional configuration steps.

Create a Web application that uses Windows-classic authentication

To create a Web application that uses Windows-classic authentication by using Central

Administration

1. Verify that you have the following administrative credentials: o To create a Web application, you must be a member of the Farm Administrators

SharePoint group and member of the local Administrator group on the computer running Central Administration.

2. On the Central Administration Home page, in the Application Management section, click Manage web applications.

3. On the ribbon, click New. 4. On the Create New Web Application page, in the Authentication section, click Classic Mode

Authentication. 5. In the IIS Web Site section, you can configure the settings for your new Web application by

selecting one of the following two options: o Click Use an existing web site, and then select the Web site on which to install your

new Web application.

o Click Create a new IIS web site, and then type the name of the Web site in the Name box.

6. In the IIS Web Site section, in the Port box, type the port number you want to use to access the Web application. If you are creating a new Web site, this field is populated with a


25

random port number. If you are using an existing Web site, this field is populated with the current port number.

7. Optional: In the IIS Web Site section, in the Host Header box, type the host name (for example, www.contoso.com) you want to use to access the Web application.

8. In the IIS Web Site section, in the Path box, type the path to the IIS Web site home directory on the server. If you are creating a new Web site, this field is populated with a suggested path. If you are using an existing Web site, this field is populated with the current path of that Web site.

9. In the Security Configuration section, configure authentication and encryption for your Web application.

a. In the Authentication Provider section, click NTLM.

b. In the Allow Anonymous section, click No.

c. In the Use Secure Sockets Layer (SSL) section, click No. 10. In the Public URL section, type the URL for the domain name for all sites that users will

access in this Web application. This URL will be used as the base URL in links shown on pages within the Web application. The default URL is the current server name and port

11. In the Application Pool section, do one of the following:

a. Click Use existing application pool, and then select the application pool you want to use from the drop-down menu.

b. Click Create a new application pool, and then type the name of the new application pool or keep the default name.

12. Under Select a security account for this application pool, do one of the following:

a. Click Predefined to use a predefined security account, and then select the security account from the drop-down menu.

b. Click Configurable to specify a new security account to be used for an existing application pool.

13. In the Database Name and Authentication section, choose the database server, database name, and authentication method for your new Web application, as described in the following table.

Item Action

Database Server Type the name of the database server and Microsoft SQL Server instance you want to use in the format <SERVERNAME\instance>. You can also use the default entry.

Database Name Type the name of the database, or use the default entry.

Database Authentication

Select the database authentication to use by doing one of the following:

If you want to use Windows authentication, leave this option selected. We recommend this option because Windows authentication automatically encrypts the password when it connects to SQL Server.

If you want to use SQL authentication, click SQL authentication. In the Account box, type the name of the account you want the Web application to use to authenticate to the SQL Server database, and then type the password in the Password box.

Note:

SQL authentication sends the SQL authentication password to the SQL Server unencrypted. We recommend that you only use SQL


26

authentication if you force protocol encryption to the SQL Server of encrypt your network traffic by using IPsec.

14. In the Service Application Connections section, select the service application connections that will be available to the Web application. In the drop-down menu, click default or custom. You use the custom option to choose the services application connections that you want to use for the Web application.

15. In the Customer Experience Improvement Program section, click Yes or No. 16. Click OK to create the new Web application.

2.2. Create, edit, and delete quota templates

A quota template consists of storage limit values that specify the maximum amount of data that can

be stored in a site collection. When the storage limit is reached, a quota template can also trigger an

e-mail alert to the site collection administrator. You can create a quota template that can be applied

to any site collection in the farm.

To create a quota template

1. Verify that you have the following administrative credentials: o You are a member of the Farm Administrators group on the computer that is

running the SharePoint Central Administration Web site.

2. On the Central Administration home page, click Application Management. 3. On the Application Management page, in the Site Collections section, click Specify quota

templates. 4. On the Quota Templates page, in the Template Name section, click Create a new quota

template. 5. In the New template name box, type the name of the new template.

If you want to base your new template on an existing quota template, expand the Template to start from list, and then click the template that you want.

6. In the Storage Limit Values section, set the values that you want to apply to the template. o If you want to restrict how much data that can be stored, click the Limit site storage

to a maximum of check box and type the storage limit in megabytes into the box.

o If you want an e-mail message to be sent to the site collection administrator when a certain storage threshold is reached, click the Send warning E-mail when Site Collection storage reaches check box and type the threshold in megabytes into the box.

7. Click OK.

To edit a quota template



2. On the Central Administration home page, click Application Management.


27

3. On the Application Management page, in the Site Collections section, click Specify quota templates.

4. On the Quota Templates page, in the Template Name section, expand the Template to modify list, and then click the template that you want to edit.

5. Change the settings as necessary, and then click OK.

To delete a quota template



2. On the Central Administration home page, click Application Management. 3. On the Application Management page, in the Site Collections section, click Specify quota

templates. 4. In the Template Name section, expand the Template to modify list, and then click the

template that you want to delete. 5. At the bottom of the Quota Templates page, click Delete, and then click OK.

2.3. Create a site collection

A site collection is a group of Web sites that have the same owner and share administration settings, for example, permissions. When you create a site collection, a top-level site is automatically created in the site collection. You can then create one or more subsites below the top-level site.

A site collection must exist within a Web application. You can create a site collection based on an existing Web application, or you can create a Web application and then create a site collection within that application. For more information, see Create a Web application (SharePoint Server 2010).

If your Web application is for a single project or for use by a single team, you should use a single site collection to avoid the overhead of managing multiple sites. However, complex solutions benefit from multiple site collections because it is easier to organize content and manage permissions for each site collection. For example, because there is no built-in navigation from one site collection to another, having multiple site collections can provide an additional layer of security for site content.

SharePoint provides site templates in the following categories: collaboration, meetings, enterprise, publishing, and custom. When you create a site collection, you select the template that matches what you want the site to do. For example, choose the Publishing Portal template if you want to create a large intranet site that has many more readers than contributors.

Before you create a site collection, ensure that the following prerequisites are available:

A Web application in which to create the site collection.

A quota template, if you plan to define values that specify how much data can be stored in a site collection and the storage size that triggers an e-mail alert to the site collection administrator. For more information, see Create, edit, and delete quota templates.

http://technet.microsoft.com/en-us/library/cc261875.aspx




28

To create a site collection by using Central Administration

1. Verify that you have the following administrative credentials: 2. To create a site collection, you must be a member of the Farm Administrators

SharePoint group on the computer that is running the SharePoint Central Administration Web site.

3. On the Central Administration Web site, in the Application Management section, click Create site collections.

4. On the Create Site Collection page, in the Web Application section, if the Web application in which you want to create the site collection is not selected, on the Web Application menu click Change Web Application, and then click the Web application in which you want to create the site collection.

5. In the Title and Description section, type the title and description for the site collection.

6. In the Web Site Address section, select the path to use for your URL (for example, a wildcard inclusion path such as /sites/, or the root directory (/).

7. If you select a wildcard inclusion path, you must also type the site name to use in your site's URL.

8. In the Template Selection section, in the Select a template list, select the template that you want to use for the top-level site in the site collection, or click the Custom tab to create an empty site and apply a template later.

9. In the Primary Site Collection Administrator section, type the user name (in the form DOMAIN\username) for the user who will be the site collection administrator.

10. In the Secondary Site Collection Administrator section, type the user name for the secondary administrator of the site collection.

Designating a secondary site collection administrator is a best practice to ensure that someone can manage the site collection when a primary site collection administrator is not present.

11. If you are using quotas to manage storage for site collections, in the Quota Template section, click a template in the Select a quota template list.

12. Click OK.

2.4. Add or remove site collection administrators

To add a site collection administrator by using Central Administration

1. Verify that you have the following administrative credentials: o To add a site collection administrator, you must be a member of the Farm

Administrators group on the computer that is running the SharePoint Central Administration Web site.

2. On the home page of the SharePoint Central Administration Web site, select Application Management.

3. On the Application Management page, under Site Collections, select Change site collection administrators.


29

4. On the Site Collection Administrators page, click the arrow next to the site collection name and select Change Site Collection.

5. If the site collection to which you want to add an administrator is listed, select the URL of the site collection and then click OK. If the site collection is not listed, click the arrow next to the Web application name; click Change Web Application; select the name of the Web application that contains the site collection; select the URL of the site collection; and then click OK.

6. In the Secondary Site Collection Administrator area, either type the name of the user whom you want to add by using the format <domain>\<username> or select the user by using the address book.

7. Click OK.

2.5. Lock or unlock site collections

You can apply locks to a site collection to prevent users from updating content or you can temporarily prevent users from accessing the site collection.

The following table describes the locking options that are available in Microsoft SharePoint Server 2010.

Option Description

Not locked Unlocks the site collection and makes it available to users.

Adding content prevented Prevents users from adding new content to the site collection. Updates and deletions are still allowed.

Read-only (prevents additions, updates, and deletions)

Prevents users from adding, updating, or deleting content.

No access Prevents users from accessing the site collection and its content. Users who attempt to access the site receive an error.

To lock or unlock a site collection by using Central Administration

1. Verify that you have the following administrative credentials. o You must be a member of the Site Collection Administrators group for the site

collection.

2. In Central Administration, click Application Management. 3. On the Application Management page, in the Site Collections section, click Configure quotas

and locks. 4. If the site collection you want isn't already selected, in the Site Collection section, on the

Site Collection menu, click Change Site Collection. Use the Select Site Collection page to select a site collection.

5. On the Site Collection Quotas and Locks page, in the Site Lock Information section, select one of the following options:

o Not locked to unlock the site collection and make it available to users.

o Adding content prevented to prevent users from adding new content to the site collection. Updates and deletions are still allowed.


30

o Read-only (blocks additions, updates, and deletions) to prevent users from adding, updating, or deleting content.

o No access to prevent users from accessing the site collection and its content. Users who attempt to access the site receive an error.

6. If you select Adding content prevented, Read-only (blocks additions, updates, and deletions), or No access, type a reason for the lock in the Additional lock information box.

7. Click OK.

2.6. How to Recover Data from an Unattached Content Database

You can restore or copy content, such as sites, site collections, lists, or document libraries, from a

content database without having to attach the content database to the farm. We will use one of the

site backups yielded from our backup daily or monthly scripts and use one of those backups to

restore specific item or list,

How to Restore from Unattached Content Database, Step by Step

1. Find the backup file that contains that document you need. You’ll need to know document original location so that you can match that to the content database. You will also need to find out when the document was corrupted or deleted, so that you grab the backup file from the right date. When you have all this information you can find the reuqired backup file (or probably request it from your SQL DBA or Backup operators).

2. Restore content database to a temporary location. Backup file is not enough, to use the unattached content database recovery you need the database mounted on a SQL server. This can be the same SQL instance used by SharePoint, or a different SQL box. If you restore into the same SQL instance make sure you (or your SQL DBA’s) use a different name for the restored database and don’t override the production content! Note the name of the SQL Server instance and the name of the database copy.

3. Open Microsoft SQL Server Management Studio > Right click on the content database and select Tasks > Back Up...


31

4. Enter the Backup Name, select Destination, and click OK to start.


32

5. Now, let's restore this backup database to the SQL Server with a different name.

Open Microsoft SQL Server Management Studio > Right click on Databases and select Restore Database...


33

Enter the new database name. Make sure you don't overwrite the original

content database. Select the Source and click OK to start.


34

6. Go to SharePoint Central Administration, navigate to Backup and Restore and click the “Recover data from an unattached content database” link under Granular Backup.


35

7. Enter the Database Name and Authentication, and then choose Browse content.

8. In this example, we will recover a Calendar list from the backup set:


36

9. Enter the File path and click on Start Export.

10. Finish export.


37

11. The exported .cmp file can then be imported to SharePoint using the SharePoint 2010 Management Shell (which is also a new feature in SharePoint 2010) command:

Import-SPWeb -identity http://destination_sitecollection -path \\path\exported_file.cmp

Documents

Step by Step Administration by Step Administration Hussain Shakir LinkedIn: Twitter: Blog: Step by Step SharePoint Manual 1 Table of Contents