Showing posts with label SharePoint 2010 Governance. Show all posts
Showing posts with label SharePoint 2010 Governance. Show all posts

Sunday, August 26, 2012

Lock or unlock site collections

To lock or unlock a site collection by using Central Administration

1. Verify that you have the following administrative credentials.

· 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:

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

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

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

· 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.

To lock or unlock a site collection by using Windows PowerShell

1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.

2. On the Start menu, click All Programs.

3. Click Microsoft SharePoint 2010 Products.

4. Click SharePoint 2010 Management Shell.

5. At the Windows PowerShell command prompt, type the following command:

6.  Set-SPSite -Identity "<SiteCollection>" -LockState "<State>"

Where:

· <SiteCollection> is the URL of the site collection that you want to lock or unlock.

· <State> is one of the following values:

· Unlock to unlock the site collection and make it available to users.

· NoAdditions to prevent users from adding new content to the site collection. Updates and deletions are still allowed.

· ReadOnly to prevent users from adding, updating, or deleting content.

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

 


Tags van Technorati: ,,

Manage Unused Web Sites

 
To manage unused Web sites

1. Verify that you meet the following minimum requirements:

· You must be a member of the Farm Administrators group.

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

3. On the Application Management page, in the Site Collections section, click Confirm site use and deletion.

4. On the Site Use Confirmation and Deletion page, in the Web Application section, if the Web application that you want to configure is not listed, expand the Web Application list, and then click Change Web Application.

On the Select Web Application dialog box, click the Web application that you want to configure.

5. In the Confirmation and Automatic Deletion Settings section:

· Select or clear the Send e-mail notification to owners of unused site collections check box.
If you select this check box, type the number of days, after the site creation or after the site usage is confirmed, to start to send notifications. The minimum number of days is 30, and the maximum is 365.

· Specify a daily, weekly, or monthly schedule for e-mail notifications. The default schedule is daily. You can also specify the exact time to run the check for the site usage. The default, time is midnight.

· Select or clear the Automatically delete the site collection if use is not confirmed check box.
If you select this check box, type the number of notifications to send before the site collection is deleted. By default, it is 28 notifications.

6. Click OK.

 

Tags van Technorati: ,

Configure Recycle Bin settings

Recycle Bins are used to help users protect and recover data. Microsoft SharePoint Server 2010 supports two stages of Recycle Bins: the first-stage Recycle Bin and second-stage Recycle Bin.

When a user deletes an item, the item is automatically sent to the first-stage Recycle Bin. By default, when an item is deleted from the first-stage Recycle Bin, the item is sent to the second-stage Recycle Bin. A site collection administrator can restore items from the second-stage Recycle Bin.

You turn on and configure Recycle Bins at the Web application level. By default, Recycle Bins are turned on in all the site collections in a Web application

To configure Recycle Bin settings by using Central Administration
  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.

  2. On the SharePoint Central Administration Web site, click Application Management.

  3. On the Application Management page, click Manage Web Applications.

  4. Click the Web application for which you want to configure Recycle Bin settings. The ribbon becomes active.

  5. On the ribbon, click the General Settings drop-down menu, and then click General Settings.

  6. On the Web Application General Settings page, in the Recycle Bin section, you can configure the following settings:

    • You can set the Recycle Bins for the Web application to be On or Off. By default, Recycle Bins are turned on.

      noteNote:

      If you turn off the Recycle Bins, any existing items in both the first and second-stage Recycle Bins are deleted. Depending on how much data is contained in the Recycle Bins, deleting these items can take a long time.

    • You can specify a time after which items in the Recycle Bins are deleted, or you can specify that these items should never be deleted. By default, items are deleted after 30 days.
    • You can specify a percentage of live site quota for second-stage deleted items. The default setting is 50 percent. You can also turn off second-stage Recycle Bins. If you selectOff, site collection administrators cannot recover items deleted from end-user Recycle Bins.The second-stage Recycle Bin quota percentage must be a value from 1 through 500.
  7. After you have finished configuring the Recycle Bins, click OK.

Plan Quota Management

 

A quota specifies storage limit values for the maximum amount of data that can be stored in a site collection. Quotas also specify the storage size that, when reached, triggers an e-mail alert to the site collection administrator. Quota templates apply these settings to any site collection in a SharePoint farm.

By default, a quota contains 300 points. A point is a relative measurement of resource usage, for example, CPU cycles, memory, or page faults. Points enable comparisons between measurements of resource usage that could not be compared otherwise. For example, it takes millions of CPU cycles to make up one point, but each time a sandboxed solution stops working is counted as one point. For more information about sandboxed solutions, see Sandboxed solutions overview (SharePoint Server 2010).

Quotas are particularly useful when you are using Microsoft SharePoint Server 2010 in enterprise environments, such as a company-wide intranet or an Internet Service Provider (ISP). You should use quotas in these environments to ensure that one site collection cannot use so many resources that other site collections can no longer function. You can assign a quota template to a site collection when you create the site collection, or you can assign a quota template at a later time. You can also reverse a decision to use quotas at any place in the site collection hierarchy.

 

About planning quota management

The basic steps to plan quota management are the following:

  1. Determine quota template settings
  2. Determine recycle bin settings
  3. Delete unused Web sites

Determine quota template settings

There is no default quota template for site collections in a SharePoint Server 2010 environment. For example, a quota for a site collection might use the following settings as a starting point:

  1. Automated e-mail is sent to a site collection administrator when the size of the site reaches 450 megabytes (MB).
  2. Users are prevented from uploading additional documents when the size of a site collection reaches 500 MB.

You must evaluate the size and number of items that you expect users to store in their sites. You must also adjust these settings appropriately to ensure that the sites are used in accordance with an organization's best practices. For example, if a specific team or group in an organization has a business need to store a greater volume of content on its team site, you can adjust the quota limits for that site collection.

The size of the data reported by quotas does not necessarily match the size of the storage in the database. This is because the quota feature estimates storage figures for empty sites (that is, sites that contain no user content) and includes those figures in the quota, in addition to the actual storage from the database. The estimated size of an empty site includes the real size of the template pages for SharePoint Server 2010, for example, the forms pages and the pages in the _layouts directory.

If you change the values for a quota template, those changes apply only to new site collections to which you apply the template. SharePoint Server 2010 does not apply the changed quota values to existing sites collections unless you use the object model to update the quota values in the database.

Determine recycle bin settings

The recycle bin can help to prevent the permanent deletion of content. The recycle bin enables site owners to retrieve items that users have deleted, without requiring administrator intervention such as restoring files from backup tapes. Key planning considerations include whether to use the second-stage recycle bin and how much space to allocate.

The recycle bin is turned on and off at the Web application level. By default, the recycle bin is turned on in all the site collections in a Web application.

The recycle bin has two stages. When a user deletes an item, the item is automatically sent to the first-stage recycle bin. By default, when an item is deleted from the first-stage recycle bin, the item is sent to the second-stage recycle bin. The second-stage recycle bin stores items that users have deleted from their recycle bins. Only site collection administrators can restore items from the second-stage recycle bin. The size that is specified for the second-stage recycle bin increases the total size of the site. You must plan data capacity accordingly.

Consider allocating at least a small amount of space, for example, 10 percent, to the second-stage recycle bin to accommodate cases in which a user mistakenly deletes an important document, a folder in a document library, or a column in a list.

Items in both the first-stage and the second-stage recycle bins are automatically deleted when the time period specified for the deleted items expires (by default, 30 days). However, when the size limit of the second-stage recycle bin is reached, items are automatically deleted starting with the oldest items. Site collection administrators can also empty the second-stage recycle bin manually. For more information, see Configure Recycle Bin settings (SharePoint Server 2010).

Delete unused Web sites

You can delete a quota template if you change your quota structures. However deleting a quota template does not delete quota values from site collections to which a quota template has been applied. If you want to remove quotas from all site collections that use a specific quota template, you must use the object model or perform a SQL Server query.

Automatic deletion of unused Web sites can help you lessen the risk of deleting data that is critical to business operations. You should include the following tasks in your planning process:

· Require a secondary contact for all sites. If the site owner is not available or leaves the organization, the secondary contact can confirm the usage of the site. If you do not have a secondary contact and you shorten the number of days or number of notices that are given before you delete an unused site, you might accidentally delete a site that is still required.

· Archive sites before they are deleted automatically. You will be able to restore the sites that contain business-critical information or plan to store the content databases for a longer duration, so that a deleted site can be restored.