©2012 Microsoft Corporation. All rights reserved. ©2012 Microsoft Corporation. All rights reserved.

Transcript ©2012 Microsoft Corporation. All rights reserved. ©2012 Microsoft Corporation. All rights reserved.

Service Applications with their own DBs:

           App Management Service Business Data Connectivity Managed Metadata Service Search Secure Store Service Machine Translation Service State Service Usage and Health Data Collection User Profile Word Automation Service Access Services App databases

Remote farms don’t need perms to parent farm DBs* Any farm can publish SAs One web application can use both local and remote SAs Enables centralized “enterprise” SAs Support only in specific service applications       Business Data Connectivity Managed Metadata Service Search Secure Store Service Machine Translation Services User Profile

Service application

Search Managed Metadata Machine Translation Service Business Data Connectivity User Profile Secure Store Service

Allowed for WAN environments?

Hybrid with Office365

Application pool Service accounts Databases Service application settings Deploying service applications by using the Initial Configuration Wizard

All service applications are deployed to the same application pool.

The same account is used for all services. You can edit service accounts later.

Database names are automatically generated, including GUIDs that are long and difficult to remember.

Default settings are applied to service applications. You can change these later.

Deploying service applications manually or by using Windows PowerShell

You can deploy service applications to dedicated application pools, if desired.

You can apply different service accounts to service applications.

You can assign database names and implement a naming convention.

You can implement custom settings when the service application is deployed.