Chapter 1 – What’s New in SP 2010

Wrox SP 2010 Admin

Installation —

SP 2010 Requirements:
OS : 64-bit
Windows: Windows server 2008 or 2008 R2.
.NET: at least 3.5 with SP1
Database: SQL 2005 R2 or later, or SQL 2008. Must be 64 bit.

Scripted installation – pass the setup settings via Config.XML.

The installation needs a farmpassphrase. You need the passphrase to add or remove a server from a farm. The passphrase is used as a basis for encryption between farm members.

Upgrade and patching Options —

A new command in SP 2007 SP2: preupgradecheck, which checks any roadblock to upgrade to SP 2010. It checks lots of configurations in SP 2007 and save the results in an XML file and an .HTM file. IN SP 2010, a similar command is available: Test-SPContentDatabase.

Two methods for upgrade:

(1) in-place upgrade – upgrades SP 2007 to SP2010 on your existing hardware.
(2) database attach – attach Sp 2007 content database to SP 2010 and upgrade automatically.

Downtime mitigation features:

(1) support for read-only content database, while actual database is being upgraded. (SP will remove all UI elements that’s allow user add/edit) SP also supports upgrading multiple databases simultanously, to reduce down time.

(2) SP 2010 supports redirecting traffic during upgrade. User can continue to use the same URL, but is given a client redirect (302) until content is ready in SP 2010.

(3) Virtual upgrade – allow sites upgraded to SP 2010 to use SP2007’s master page and CSS, so the upgraded site can maintain the same look & feel.

Patching –

A new feature in SP 2010 – Health Rules – will alert you about the new patches available.

Central Admin –

SP 2010 Service Applications = SP 2007 Shared service Provider. (SSP)

In SP 2010, all Service Applications are separate, such as Search, profile Import, BDC and managed matadata. Each can be turn on/off as needed, and can be given a different permission. Each service Application admin can only see the service Applications that they have access to. Service Applications are available to all versions of Sharepoint 2010.

Windows Identity Foundation and Claims

SP 2010 supports claimed based authentication. Works with AD, LDAP and LiveID. The product that holds them together is Windows Identity Foundation, which enables users to have identities in different repositories and use them simultanously to access different resources in Sharepoint.

Each user gets a token from each repository that contains claims about the user. Compare it with a driver who has a NC driver’s license and travels to Alaska. An Alaskan policeman will accept the NC driver’s driver’s license becase he trusts the NC state government.

Health and Monitoring –

Health Analyzer: Out of the box SP 2010 has 52 definitions of behaviors that it knows that can go wrong, such as C running out of space. New rules/definitions can be added as a service patch, or writeen by a developer.

Time jobs –

Reporting –

Powershell –

STSADM – deprecated in SP 2010. New friend: Powershell.

Managed Accounts –

Receovering from Disaster –

new and Improved user experience (UX) –

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: