Archive

Archive for the ‘PowerShell’ Category

Preparation materials posted for Exam 70-576: PRO: Designing and Developing Microsoft SharePoint 2010 Applications

March 8, 2010 Leave a comment

On the Microsoft Learning site the prep materials for the 70-576 PRO exam have been published. It appears that the exam is scheduled to be released June 15 and the exam is still in development.

To see full details visit the Microsoft Learning Center exam description for 70-576

About this Exam

This exam is designed to test the candidate’s knowledge and skills on designing developing applications on the Microsoft SharePoint Server 2010 platform.

Audience Profile

The candidate is responsible for designing custom code for projects that are deployed to SharePoint servers. This includes technology selection across the many ways to build code in SharePoint, ensuring the team development environment is configured, creating a strategy for code deployment, versioning, configuration, or structure.
The candidate also leads a team of SharePoint developers, has at least two years of SharePoint development experience, has at least three years of ASP.NET development experience

Credit Toward Certification

When you pass Exam 70-576: PRO: Designing and Developing Microsoft SharePoint 2010 Applications, you complete the requirements for the following certification(s):

PRO: SharePoint Server Developer

 Skills Being Measured

This exam measures your ability to accomplish the technical tasks listed below.The percentages indicate the relative weight of each major topic area on the exam.

Creating an Application Design (19%)

  • Evaluate application data access and storage

    This objective may include but is not limited to: SharePoint List and relationships, Document Library, SQL Database, BCS, web service, file system, remote BLOB storage, and all other external data sources

  • Identify artifacts from application requirements

    This objective may include but is not limited to: web parts, event receivers, list definitions, list templates, workflows, site definitions, custom actions, content types, site columns, mapping artifacts to application requirements

  • Select a deployment model

    This objective may include but is not limited to: identifying artifacts and execution appropriate for sandbox and farm (i.e. GAC vs. BIN) implementation, designing solutions for single server or multi-server environments, dividing artifacts between sandbox and farm

  • Select the appropriate execution method

    This objective may include but is not limited to: in-page, workflow, event receiver (asynchronous vs. synchronous), timer job, and service application, selecting which logic execution model to use for a problem, determining where code or artifact runs

Designing UX (17%)

  • Determine presentation page type

    This objective may include but is not limited to: Web Part page, application Page, publishing page, page layout, static page

  • Determine SharePoint visual components

    This objective may include but is not limited to: web parts, silverlight, AJAX, ribbon, visual web parts, delegate controls, custom field types, dialog

  • Plan branding strategy

    This objective may include but is not limited to: determining usage of themes, templates, enforce consistency via site definitions, master pages and page layouts, determining usage of CSS styles and JavaScript, designing usage and role of Styles Library or Site Collection Library

  • Design application customization strategy

    This objective may include but is not limited to: supportable customizations allowed through SharePoint UI, SharePoint Designer 2010, VS 2010 (site columns, content types, page customization, themes, page layouts, personalization)

  • Design navigation strategy

    This objective may include but is not limited to: identify inclusion of navigational items (global/current/custom), consume an existing site map provider vs. create a custom provider, determine depth and inclusion of pages/sites, dynamic vs. static navigation, consume an existing navigation control vs. create a custom navigation control

Managing Application Development (18%)

  • Design for localization and globalization

    This objective may include but is not limited to: use and implementation of resource files, variations (content creation and workflow, multilingual content), selecting locales, date and time, regional settings, RTL vs. LTR

  • Develop a security approach

    This objective may include but is not limited to: authentication (NTLM, Kerberos, Forms-based Authentication, claims, Single Sign-On, Anonymous), authorization (SharePoint groups, AD groups, claims, permission levels) enterprise-wide security policies

  • Define application configuration approach

    This objective may include but is not limited to: defining "web.config" modifications, Lists as a configuration option, Property bags, declarative vs. programmatic, SP persisted objects

Optimizing SharePoint Application Design (15%)

  • Optimize page performance

    This objective may include but is not limited to: View State, Inline JS, Inline  CSS, HTML output, AJAX, Client side cache, .NET cache, BLOB Cache, Session State, IIS compression

  • Optimize data access

    This objective may include but is not limited to: SPQuery, SPSiteDataQuery, Large lists, Search (managed properties), SharePoint 2010 query throttling, Client object model vs. web service/rest/SOAP/RPC, Linq

  • Design for logging and exception handling

    This objective may include but is not limited to: Determining appropriate level of logging to include in a custom code project, Evaluating SharePoint log data, Instrumenting code to improve the ability to maintain the system, Determining when exceptions are raised, error values returned, and what should be written to the SharePoint ULS log, Debugger, and Event log

  • Identify and Resolve deployment issues

    This objective may include but is not limited to: single server vs. farm vs. multi-farm, infrastructure vs. content database, web applications, application pools, feature activation failures, pushing applications to front end, security context, feature scope, feature dependencies

  • Analyze memory utilization

    This objective may include but is not limited to: Memory profiling, Disposal of SharePoint objects, Load testing, Identifying memory bottlenecks (hierarchy), Analyze ULS logs, Monitoring memory counters, ensure implemention of IDisposable on custom artifacts containing IDisposable members

Designing SharePoint Composite Applications (13%)

  • Design external application integration

    This objective may include but is not limited to: Selecting appropriate BCS connection from Web Service, .NET Type, and SQL Connection, Defining authentication requirements, Defining solutions that include Office client applications

  • Determine data capture approach

    This objective may include but is not limited to: Evaluate when to use different forms technologies (InfoPath vs. ASP.NET), Office client, Silverlight, BCS, Infopath Forms Services

  • Design SharePoint information architecture

    This objective may include but is not limited to: Content types (local, global), Site columns, Site structure, Taxonomy (managed metadata)

  • Design a workflow solution

    This objective may include but is not limited to: workflow tool (Visio, SharePoint Designer, Visual Studio), Sequential vs. State Machine, Item vs. Site, Declarative vs. Code, custom actions

Designing SharePoint Solutions and Features (18%)

  • Plan SharePoint Features

    This objective may include but is not limited to: Feature Sets, Feature Stapling, determine feature scope, Create a new Feature (vs. extending), activation dependencies, feature receivers

  • Plan SharePoint solution packaging

    This objective may include but is not limited to: Create a new Solution (vs. extending), Manage reference assemblies in a SharePoint WSP solution, solution sets,  solution dependencies,  solution targeting

  • Establishing application modification and version upgrade strategy

    This objective may include but is not limited to: Designing an artifact upgrade strategy,  Feature and solution upgrade,  Site upgrade,  Versioning custom assemblies,  Versioning workflows (new feature, new assembly version, new code),  Resolving incompatible changes between dev and production

  • Develop a strategy for delivery of application modifications and existing data transformation

    This objective may include but is not limited to: Formulating a new version of custom code,  Updating Web parts while retaining properties, connections and other user entered settings,  Content maintenance, Developing a content upgrade strategy, Deployment configurations, Deploying modified code safely (data safe), Preparing scripts (PowerShell, EXE), packages (WSP, MSI), or installers

Preparation materials published for Exam 70-573: TS: Microsoft SharePoint 2010, Application Development

March 8, 2010 2 comments

On the Microsoft Learning site the prep materials for the 70-573 MCTS exam have been published. It appears that the exam is scheduled to be released June 15 and the exam is still in development.

To see full details visit the Microsoft Learning Center exam description for 70-573

About this Exam

This exam is designed to test the candidate’s knowledge and skills on developing applications on the Microsoft SharePoint Server 2010 platform.

Audience Profile

A Microsoft Certified Technology Specialist (MCTS) in Microsoft SharePoint 2010, Application Development should be able to perform the following tasks:

  • Write code that extends SharePoint 2010
  • Add and support code to an existing project
  • Write code for and test custom features in a SharePoint solution such as a Visual Web Part or Event Receiver
  • Implement a solution designed by lead SharePoint Developer

The candidate should also have the following experience:

  • 12 months with ASP.NET 3.5 with Visual Studio 2008 (or later)
  • 6 months develop with SharePoint 2007 or later
  • 3 months with SP 2010 and VS2010 (includes beta releases)

Credit Toward Certification:

When you pass Exam 70-573: TS: Microsoft SharePoint 2010, Application Development, you complete the requirements for the following certification(s):

TS: SharePoint 2010 Developer

Exam 70-573: TS: Microsoft SharePoint 2010, Application Development: counts as credit toward the following certification(s):PRO: SharePoint Server 2010 Developer

 

Skills Being MeasuredThis exam measures your ability to accomplish the technical tasks listed below.The percentages indicate the relative weight of each major topic area on the exam.

Working with the SharePoint User Interface (19%)

  • Manage SPSite and SPWeb programmatically by using Visual Studio 2010
    This objective may include but is not limited to: creating sub webs, referencing SPFiles, manipulating property bag, when to call Update, referencing SPContext, SPSite, SPWeb,  SPSite.OpenWeb, SPWeb.Webs, feature activiation and deactivation

    This objective does not include: trivial cases such as setting title and other loose properties of the objects

  • Implement a dialog by using the Dialog Framework

    This objective may include but is not limited to: Create dialogs from JavaScript or from server side, display dialogs

  • Create a custom ribbon object

    This objective may include but is not limited to: adding custom actions to the ribbon, customizing groups, customizing tabs, customizing the existing ribbon

  • Customize navigation programmatically
    This objective may include but is not limited to: TopNav bar, quick launch, custom actions

    This objective does not include: custom menu controls, custom site map providers

  • Create and apply branding to a SharePoint site
    This objective may include but is not limited to: applying custom master pages to content pages and application pages, placeholders, page layouts, programmatically working with themes, deploying CSS, CSSlink, ScriptLink

    This objective does not include: graphic design, creating a CSS

Developing Web Parts and Controls (21%)

  • Create Web Parts
    This objective may include but is not limited to: including properties, controls using Render vs. CreateChildControl, life cycle,  visual, standard Web Parts,  

    This objective does not include: trivial case where developer uses Visual Web Part project template

  • Create connectable Web Parts

    This objective may include but is not limited to: Implement consumer/provider interfaces

  • Debug Web Parts

    This objective may include but is not limited to: ULS log, and event log, debug.log tracing, developer dashboard

  • Create and implement delegate controls

    This objective may include but is not limited to: overriding existing controls with lower sequence, developing and using .ascx files

Developing Business Logic (19%)

  • Implement a custom workflow in Visual Studio 2010
    This objective may include but is not limited to: work with inititation data or association data to create a SharePoint task, extend a workflow imported from SharePoint Designer 2010, use a HandleExternalEvent and CallExternalMethod to interact with a custom local service, work with inititation data or association data in a site workflow, corelation token

    This objective does not include: trivial cases such as workflows with no custom actions, initiation data, association data.

  • Create a custom workflow action

    This objective may include but is not limited to: create a custom SPD action, create and add a custom activity to a Visual Studio workflow, define an action.xml file

  • Create and implement event receivers

    This objective may include but is not limited to: accessing event properties, list, item, site, email, avoiding recursion, cancelling events, choosing synchronization state

  • Customize Enterprise Content Management (ECM)
    This objective may include but is not limited to: creating a content type that inherit from appropriate parent, creating and implementing a custom publishing field control that is page mode aware, activating a master page programmatically including token usage

    This objective does not include: page layouts, formatting

  • Create, implement and debug a Timer Job

    This objective may include but is not limited to: configuration, programmatic scheduling, queueing, attaching debugger to the Timer service

  • Create and modify Business Connectivity Service model in Visual Studio 2010

    This objective may include but is not limited to: create a BDC model in Visual Studio 2010, define insert, update and delete methods, create and read items, make data searchable

  • Manage Users, Groups, Permissions

    This objective may include but is not limited to: SPGroups, SPUser, permission inheritance, all securable objects, SPRoleDefinition, SPRole, SPRoleAssignment

Working With SharePoint Data (22%)

  • Access list data by using the Server object model

    This objective may include but is not limited to: SPQuery, LINQ, SPList, SPSiteDataQuery, schema management, working with a query Governor, create LINQ query that includes a join statement, SPQuery Vs. SPSiteDataQuery

  • Access SharePoint Data by using ADO.NET Data Services

    This objective may include but is not limited to: WCF ListData.svc, RESTFUL URLs conventions, create and use a client service reference

  • Access (CRUD) data by using the Client Object Model

    This objective may include but is not limited to: Javascript, .NET, Silverlight, Build Silverlight User Interface for SharePoint using Client Object Model, Query data by using CAML over the Client Object Model in Silverlight, non data API (site, web, list, access)

  • Work with documents programmatically

    This objective may include but is not limited to: SPFile, SPFolder, SPVersion, upload document and set meta data

  • Work with the meta data

    This objective may include but is not limited to: Access data from user profiles, taxonomy, folksonomy

  • Extending SharePoint Search

    This objective may include but is not limited to: creating a custom query using full text query or keyword query, customize the look and feel of the search result using XSLT

  • Implement and debug code that executes in an alternative security context

    This objective may include but is not limited to: create code that uses the RunWithElevatedPrivileges delegate (including debugging), create code that uses the System Account, create code that impersonate a different user

  • Create and modify a custom content type

    This objective may include but is not limited to: declaratively and programmatically creating and upgrading content type using Visual Studio 2010, modifying an exisiting content type, site columns

Stabilizing and Deploying SharePoint Components (19%)

  • Manage a solution in Visual Studio 2010

    This objective may include but is not limited to: modify the contained features in the solution, add an assembly that is not included in the visual studio solution, manage mapped folders for localization, sandbox and farm solutions, customize manifest.xml 

  • Manage a feature by using Visual Studio 2010
    This objective may include but is not limited to: upgrading, localizing, versioning, developing features, feature receivers (activating and installing) that interact with their parent object, customizing feature.xml

    This objective does not include: features without elements

  • Store and retrieve configuration data

    This objective may include but is not limited to:  App config, web config, persisted object, list, xml, file system, cookies, property bag

  • Create a site definition by using Visual Studio 2010
    This objective may include but is not limited to: feature activation, site provisioning, localization

    This objective does not include: list definitions and modules defined in ONET.xml, SharePoint Designer

  • Manage SharePoint object life cycle by using the Dispose API

    This objective may include but is not limited to: SPWeb, SPContext, IDisposable, Try…Catch…Finally, using blocks

  • Develop, debug, and deploy sandboxed solutions

    This objective may include but is not limited to: APIs that are allowed or not allowed in sandbox, use a full trust proxy

Upgrade and migration cmdlets (SharePoint Server 2010)

February 21, 2010 Leave a comment

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

You can use Windows PowerShell cmdlets to help perform an upgrade from an earlier version of Microsoft SharePoint Server 2010.

The following cmdlets are available for Beta.

Cmdlet name

Test-SPContentDatabase

To download the SharePointProductsCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Visio Graphics Services cmdlets (SharePoint Server 2010)

February 21, 2010 Leave a comment

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

Visio Graphics Service is a service in Microsoft SharePoint Server 2010 that users can use to view published Visio diagrams. The service also refreshes published Visio diagrams that are connected to supported data sources.

All Visio Graphics Service settings will support backup and recovery, regardless of whether there is a UI setting. This means all global settings will support backup and restore operations.

The Visio Graphics Service has Windows PowerShell functionality that you can use to provision a new instance, manage and configure available data sources, manage and configure a list of safe data providers, and configure all the global settings of the service.

The following cmdlets are available for Beta.

Cmdlet Name

Get-SPVisioExternalData

Get-SPVisioPerformance

Set-SPVisioPerformance

Get-SPVisioSafeDataProvider

New-SPVisioSafeDataProvider

Remove-SPVisioSafeDataProvider

Set-SPVisioSafeDataProvider

Get-SPVisioServiceApplication

New-SPVisioServiceApplication

Set-SPVisioServiceApplication

Get-SPVisioServiceApplicationProxy

New-SPVisioServiceApplicationProxy

To download the VisioServicesCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Search cmdlets (SharePoint Server 2010)

February 21, 2010 Leave a comment

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

Search is composed of several components, all of which provide specific functionality that is required for Search to operate. These components can be configured by using Windows PowerShell cmdlets.

The following cmdlets are available for Beta.

Administration

Cmdlet name

Get-SPEnterpriseSearchAdminComponent

Set-SPEnterpriseSearchAdminComponent

Crawling

Cmdlet name

Get-SPEnterpriseSearchCrawlComponent

Get-SPEnterpriseSearchCrawlContentSource

Get-SPEnterpriseSearchCrawlCustomConnector

Get-SPEnterpriseSearchCrawlDatabase

Get-SPEnterpriseSearchCrawlExtension

Get-SPEnterpriseSearchCrawlMapping

Get-SPEnterpriseSearchCrawlRule

Get-SPEnterpriseSearchCrawlTopology

New-SPEnterpriseSearchCrawlComponent

New-SPEnterpriseSearchCrawlContentSource

New-SPEnterpriseSearchCrawlCustomConnector

New-SPEnterpriseSearchCrawlDatabase

New-SPEnterpriseSearchCrawlExtension

New-SPEnterpriseSearchCrawlMapping

New-SPEnterpriseSearchCrawlRule

New-SPEnterpriseSearchCrawlTopology

Remove-SPEnterpriseSearchCrawlComponent

Remove-SPEnterpriseSearchCrawlContentSource

Remove-SPEnterpriseSearchCrawlCustomConnector

Remove-SPEnterpriseSearchCrawlDatabase

Remove-SPEnterpriseSearchCrawlExtension

Remove-SPEnterpriseSearchCrawlMapping

Remove-SPEnterpriseSearchCrawlRule

Remove-SPEnterpriseSearchCrawlTopology

Set-SPEnterpriseSearchCrawlContentSource

Set-SPEnterpriseSearchCrawlDatabase

Set-SPEnterpriseSearchCrawlRule

Set-SPEnterpriseSearchCrawlTopology

Service Application

Cmdlet name

Get-SPEnterpriseSearchService

Get-SPEnterpriseSearchServiceApplication

Get-SPEnterpriseSearchServiceApplicationProxy

Get-SPEnterpriseSearchServiceInstance

New-SPEnterpriseSearchServiceApplication

New-SPEnterpriseSearchServiceApplicationProxy

Remove-SPEnterpriseSearchServiceApplication

Remove-SPEnterpriseSearchServiceApplicationProxy

Restore-SPEnterpriseSearchServiceApplication

Set-SPEnterpriseSearchService

Set-SPEnterpriseSearchServiceApplication

Set-SPEnterpriseSearchServiceApplicationProxy

Set-SPEnterpriseSearchServiceInstance

Start-SPEnterpriseSearchServiceInstance

Stop-SPEnterpriseSearchServiceInstance

Upgrade-SPEnterpriseSearchServiceApplication

Querying

Cmdlet name

Get-SPEnterpriseSearchQueryAuthority

Get-SPEnterpriseSearchQueryComponent

Get-SPEnterpriseSearchQueryDemoted

Get-SPEnterpriseSearchQueryKeyword

Get-SPEnterpriseSearchQueryScope

Get-SPEnterpriseSearchQueryScopeRule

Get-SPEnterpriseSearchQuerySuggestionCandidates

Get-SPEnterpriseSearchQueryTopology

Get-SPEnterpriseSearchRankingModel

Get-SPEnterpriseSearchSecurityTrimmer

New-SPEnterpriseSearchQueryAuthority

New-SPEnterpriseSearchQueryComponent

New-SPEnterpriseSearchQueryDemoted

New-SPEnterpriseSearchQueryKeyword

New-SPEnterpriseSearchQueryScope

New-SPEnterpriseSearchQueryScopeRule

New-SPEnterpriseSearchQueryTopology

New-SPEnterpriseSearchRankingModel

New-SPEnterpriseSearchSecurityTrimmer

Remove-SPEnterpriseSearchQueryAuthority

Remove-SPEnterpriseSearchQueryComponent

Remove-SPEnterpriseSearchQueryDemoted

Remove-SPEnterpriseSearchQueryKeyword

Remove-SPEnterpriseSearchQueryScope

Remove-SPEnterpriseSearchQueryScopeRule

Remove-SPEnterpriseSearchQueryTopology

Remove-SPEnterpriseSearchRankingModel

Remove-SPEnterpriseSearchSecurityTrimmer

Restart-SPEnterpriseSearchQueryComponent

Set-SPEnterpriseSearchQueryAuthority

Set-SPEnterpriseSearchQueryComponent

Set-SPEnterpriseSearchQueryKeyword

Set-SPEnterpriseSearchQueryScope

Set-SPEnterpriseSearchQueryScopeRule

Set-SPEnterpriseSearchQueryTopology

Set-SPEnterpriseSearchRankingModel

Metadata

Cmdlet name

Get-SPEnterpriseSearchMetadataCategory

Get-SPEnterpriseSearchMetadataCrawledProperty

Get-SPEnterpriseSearchMetadataManagedProperty

Get-SPEnterpriseSearchMetadataMapping

New-SPEnterpriseSearchMetadataCategory

New-SPEnterpriseSearchMetadataCrawledProperty

New-SPEnterpriseSearchMetadataManagedProperty

New-SPEnterpriseSearchMetadataMapping

Remove-SPEnterpriseSearchMetadataCategory

Remove-SPEnterpriseSearchMetadataManagedProperty

Remove-SPEnterpriseSearchMetadataMapping

Set-SPEnterpriseSearchMetadataCategory

Set-SPEnterpriseSearchMetadataCrawledProperty

Set-SPEnterpriseSearchMetadataManagedProperty

Set-SPEnterpriseSearchMetadataMapping

Topology

Cmdlet name

Import-SPEnterpriseSearchTopology

Export-SPEnterpriseSearchTopology

General

Cmdlet name

Get-SPEnterpriseSearchIndexPartition

Get-SPEnterpriseSearchLanguageResourcePhrase

Get-SPEnterpriseSearchPropertyDatabase

Get-SPEnterpriseSearchSiteHitRule

New-SPEnterpriseSearchLanguageResourcePhrase

New-SPEnterpriseSearchPropertyDatabase

New-SPEnterpriseSearchSiteHitRule

Remove-SPEnterpriseSearchLanguageResourcePhrase

Remove-SPEnterpriseSearchPropertyDatabase

Remove-SPEnterpriseSearchSiteHitRule

Set-SPEnterpriseSearchIndexPartition

Set-SPEnterpriseSearchPropertyDatabase

Microsoft FAST Search Server 2010 for SharePoint

Microsoft FAST Search Server 2010 for SharePoint can replace SharePoint Server search features in environments where scale and performance requirements exceed the capabilities of SharePoint Server search. FAST Search Server 2010 for SharePoint can be deployed across multiple servers for redundancy and to increase performance and capacity. Deployment and management take place primarily through command-line operations — not the SharePoint Central Administration Web site — and can be scripted by using Windows PowerShell. FAST Search Server 2010 for SharePoint is only available with a SharePoint Server Enterprise Client Access License (CAL).

The following table describes the cmdlets for FAST Search Server 2010 for SharePoint.

Cmdlet name

Get-SPEnterpriseSearchExtendedConnectorProperty

Set-SPEnterpriseSearchExtendedConnectorProperty

Set-SPEnterpriseSearchExtendedQueryProperty

Get-SPEnterpriseSearchExtendedQueryProperty

Get-SPEnterpriseSearchExtendedClickThroughExtractorJobDefinition

To download the SearchCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta(http://go.microsoft.com/fwlink/?LinkId=179124).

User Profile Service cmdlets (SharePoint Server 2010)

February 21, 2010 Leave a comment

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

In Microsoft SharePoint Server 2010, the User Profile Service is used to store and process information about users. This information is stored as a collection of user profile properties per user. The user information must be imported into the user profile store before it can be used by various personalization-related features and people search. These properties can be imported from line-of-business applications and directory services (primarily Active Directory directory service and Lightweight Directory Access Protocol (LDAP)).

In SharePoint Server 2010, the use of social tagging, expertise tagging, and profile synchronization are new features.

SharePoint Server 2010 provides an enterprise-wide repository for storing social and expertise tags and for associating those tags with a user’s profile. Administrators can control who can tag items on a given site, decide which tags can be used, and delete tags prior to a specific date or based on a specific user profile ID. Tagging relies on the Managed Metadata Service and can be enabled by using either the UI or Windows PowerShell cmdlets.

Profile synchronization synchronizes data in the SharePoint profile store with profile information contained in directory services across the enterprise, such as Active Directory or LDAP. After a connection to the appropriate directory service has been set up, profile synchronization can be scheduled to run on a regular basis.

You can use User Profile Service Windows PowerShell cmdlets to create and configure the User Profile Service and profile tags, and to configure permissions and all global settings for the User Profile Service.

The following cmdlets are available for Beta.

Cmdlet name

New-SPProfileServiceApplication

Set-SPProfileServiceApplication

New-SPProfileServiceApplicationProxy

Set-SPProfileServiceApplicationProxy

Add-SPProfileServiceApplicationTenant

Remove-SPProfileServiceApplicationTenant

Set-SPProfileServiceApplicationTenant

To download the UserProfileCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Secure Store Service cmdlets (SharePoint Server 2010)

February 21, 2010 Leave a comment

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

In Microsoft SharePoint Server 2010, the Secure Store service replaces the single sign-on (SSO) service that was used in Microsoft Office SharePoint Server 2007. The Secure Store Service is a claims-aware authentication service that includes a secure database for storing credentials that are associated with application IDs. These application IDs can be used to authorize access to external data sources. The Secure Store Service provides the capability of securely storing credentials and associating them to specific identities or a group of identities. A common scenario for Secure Store Servcie is an application trying to authenticate against a system in which the current user is known by a different name or has a different account for authentication. When used with Microsoft Business Connectivity Services, the Secure Store Service provides a means to authenticate against external data sources.

When you use Windows PowerShell cmdlets, you can create and configure a Secure Store Service instance, configure the settings of a credentials database, and configure all global settings of the Secure Store Service.

The following cmdlets are available for Beta.

Cmdlet name

Clear-SPSecureStoreCredentialMapping

Update-SPSecureStoreCredentialMapping

Disable-SPSingleSignOn

Get-SPSecureStoreApplication

New-SPSecureStoreApplication

Remove-SPSecureStoreApplication

Set-SPSecureStoreApplication

New-SPSecureStoreServiceApplication

Set-SPSecureStoreServiceApplication

New-SPSecureStoreTargetApplication

New-SPSecureStoreTargetApplicationField

Update-SPSecureStoreCredentialMapping

Upgrade-SPSingleSignOnDatabase

Update-SPSecureStoreGroupCredentialMapping

Update-SPSecureStoreMasterKey

Update-SPSecureStoreApplicationServerKey

To download the SecureStoreCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).