Chapter 6 – Managing Sharepoint 2010 – Using Central Administration – Part 2

MS Sharepoint 2010 – Admin’s Companion – P. 315

Backup and Restore —

Perform a backup, you either perform a farm backup (back up all components, or just back up one single component; you can’t select multiple components)

(1) Not allowed backup to be scheduled (bad!)
(2) Not allowed backup directly to tape.
(3) Not allowed more than one Sharepoint Component to be backup. Unless it’s entire farm.

Granular backup – back up site collections, sites, lists and libraries.

Recover Data from an Unattached Content Database — Accessing unattached content database directly in Sharepoint allows you to restore site collections, sites, libraries and lists from these SQL server databases.

Security —

By default, the builtin\Administrators has FARM ADMIN access; it is recommended to remove it; instead, use AD group to the Farm Administrator.

Approve or Reject Distribution Group — To allow Sharepoint Groups to have email addreaaes so that new distribution groups can be created in AD. By default, when new distribution groups are created or deleted, these operations require farm administrator approval before the actual create or delete operations is performed in AD.

General Security —

Configuring managed Accounts – Define an AD account and configure it to automatically change the password. (Sharepoint manages AD account password change for you.)
Configure service accounts – Allows you to manage service accounts that are being used by a Sharepoint service, such as an application pool or service application.
Configure password change settings – set up email notification, number of days before expiry that an email should be sent,. – Best practice – use a farm admin group as email address.
Manage Trust
– trusts are created when two farms are communicating with each other by allowing one of the farms to consume services from the other. The consuming farm must trust the root certificate authority (CA) for SSL on the farm that is hosting the shared service applications.
Manage Anti-virus settings – Before you can manage this, you need to install a Sharepoint-2010 compatible anti-virus software such as Microsoft Forefront.
Define blocked file type —
Manage web part security —

Information Policy —

Configure Information Rights Management (IRM) – don’t use, or use the default one in AD, or provide a IRM Server address
(difference between security and IRM:
Security: who can see what content;
IRM: what can be done with the content after it is accessed by the user (like Mp3))

Configure Information Management Policy (IMP) – Labels, Auditing, Retention and Barcodes.

Upgrade and Migration —

Convert farm license type (enter 25 chars key), enable enterprise features, enable currently available features on all sites.

General Application Settings —

External Service Applications – Configure Send to Connections – (target site has to have Content Organizer feature enabled)
More info:
Send or copy or move to a Content Organizer address so that target Content Organizer can accept and file the file.

Once you send it, the target (Judy)’s Drop Off Library, you will see the file. Target site’s Content Organizer will fle the file automatically based on the rules.

Configure Document Conversions – to configure this feature, you must start these two services (“service in server”)

InfoPath Forms Services —

Site Directory – not officially supported in Sharepoint 2010; for backward compability only. TO actiate this feature in Sharepoint 2010, go to:

You will have to create a Site Directory using stsadm

Search —

Farm Search Administration – define search proxy server (used for external crawl), timeout, ignore SSL warning, and access the Search Service Application

Crawler Impact Rules – create one or more than one rules, to craw site with how many simultaneous crawling requests; or only one request at a time, and interval.

Content Deployment —

Content deployment is a feature of Web Content Management (WCM) that allows multiform topologies for deploying content from sites or site collections to remote sites or site collections. You can use this to create a staging environment (authoring environment), and then finally move to a production environment. This feature can be used on the same server (between site collections), or different farms.

First, you must enable remote farm to accept incoming jobs.

The source and target site/site collections must be in different content databases, or you get this error:

Once you define the path, you can create new job and associate with the path.

Create a job: Name/Description, select Path, use SQL Snapshot, Scope (entire site collection, or selected sites), frequency, deploy all content or just changes since last ran; email notification.

Check deployment of Specific Content – provide a source URL to check the status.

Configuration Wizard – solved a mystery today. I was never able to see anything on the Farm Administration Wizard, and after some search today, found the answer.

I got tis error message:

So Farm Configuration Wizard
is not supported
in Standalone Installation!!!

End of a very long Chapter 6 – Jan 11, 2011.

Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: