Studying for Exam 70-332: Advanced Solutions of Microsoft SharePoint Server 2013

This is the third post in a quest for my SharePoint 2013 certification. My first and second posts focused on exam 70-331: Core Solutions of Microsoft SharePoint 2013. This is the second SharePoint exam, 70-332: Advanced Solutions of Microsoft SharePoint Server 2013.

The two critical things to concentrate on are breadth of knowledge on SharePoint 2013 and integrated systems, as well as the order that installation and configuration must be run in. The exam tests the exact steps and the correct order is vital to pass the exam.

Plan Business Continuity Management (21 percent)

Plan for SQL high availability and disaster recovery

This objective may include but is not limited to: plan for SQL Server mirroring, plan for SQL Server clustering, plan for SQL Server AlwaysOn, plan for SQL Server Log Shipping, plan for storage redundancy, plan for login replication

plan for SQL Server mirroring:

Database Mirroring (SQL Server)

  • Database mirroring is a solution for increasing the availability of a SQL Server database
  • Mirroring is implemented on a per-database basis and works only with databases that use the full recovery model
  • Mirroring requires at least two fully licensed SQL Servers, with a maximum of four participating in the mirror
  • Security and permissions must be manually configured on each SQL Server instance to ensure failover works

Creating a  mirror involves these main steps:

  1. Back up the principal database and transaction log
  2. Restore the backed-up database on the mirror server
  3. Create the mirror connection

plan for SQL Server clustering:

Before Installing Failover Clustering

  • SQL Server clustering relies on Windows Server Failover Clustering (WSFC) to be configured and available
  • a network name for the cluster instance is required
  • one or more ip addresses for the cluster instance is required
  • one or more disks in a Windows Cluster Service group are required
  • At least one SQL Server instance with SQL Server Agent, Full-text Search, Replication, and the SQL Server service

plan for SQL Server AlwaysOn:

SQL Server AlwaysOn Availability Groups

  • AlwaysOn High Availability Groups replaces database mirroring
  • it can fail over a group of databases instead of just one at a time
  • Multiple secondary servers supported (max four)
  • Asynchronous active log sync available
  • Built-in encryption and compression
  • Automatic page repair
  • Uses two synchronous secondary servers

plan for SQL Server Log Shipping:

About Log Shipping (SQL Server)

SQL Server Log shipping allows you to automatically send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. The transaction log backups are applied to each of the secondary databases individually. An optional third server instance, known as the monitor server, records the history and status of backup and restore operations and, optionally, raises alerts if these operations fail to occur as scheduled.

  • Failover is always manual
  • An infinite number of servers can receive log shipments
  • Failover is slow compared to other failover solutions
  • Transaction logs are backed up and applied to secondary servers
  • Changing primary to secondary server role is manual
  • Log shipping uses committed and uncommitted transactions

Requirements for log shipping:

  1. Full or Bulk Logged recovery model for primary database
  2. An existing backup shared folder available to all participating servers

Steps:

  1. Open SQL Server Management Studio
  2. In Properties, select Transaction Log Shipping
  3. Enable the primary database
  4. Configure the transaction log backup settings
  5. Enter a network path for the transaction logs
  6. Configure the schedule
  7. Add the secondary instance and configure
  8. Select a Monitor for the server configuration

Failover steps:

  1. All backup files must be available for the secondary server
  2. Apply all transaction logs in order
  3. Back up the transaction tail WITH NORECOVERY (if available)
  4. Apply the transaction tail
  5. Recovery the secondary server and make it available
  6. Change applications as required to point to the new server

plan for storage redundancy:

Create a high availability architecture and strategy for SharePoint 2013

Design storage architecture based on capacity and I/O requirements

plan for login replication:

Configure SQL Server 2012 AlwaysOn Availability Groups for SharePoint 2013

SQL Server 2012 introduces the concept of Users with Passwords for Contained Databases. The database itself stores all the database metadata and user information, and a user who is defined in this database does not have to have a corresponding login. The information in this database is replicated by the availability group and is available after a failover.

Important: If you create a new SharePoint login to use for an existing availability group, make sure to add the login to the contained database so it is replicated to each server that is hosting a SQL Server instance for the availability group. For example, if you create another application pool for a Web App and give it a new identity (an application pool account that you have not used), then you need to add that account as a login.

  • Logins aren’t replicated with data unless the instance is replicated
  • Scripting the logins is an effective method of ensuring they are consistently applied

Plan SharePoint high availability

This objective may include but is not limited to: plan for service distribution, plan for service instance configuration, plan for physical server distribution, plan for network redundancy, plan for server load balancing, plan for SQL Server aliases

plan for service distribution:

Capacity management and sizing overview for SharePoint Server 2013

  • Web Front End (WFE)
  • Search server
  • Application server

Search server:

  • Crawl component
  • Content processing component
  • Indexing component
  • Query processing component
  • Analytics processing component
  • Search administration component

plan for service instance configuration:

Plan service deployment in SharePoint 2013

Streamlined topologies — The distribution of services and other components in a farm is intended to maximize system resources of server hardware. Streamlined architectures include front-end servers, batch-processing servers, and database servers.

Traditional topologies — Topologies are based on traditional approaches to building architectures with Web servers, application servers, and database servers.

plan for physical server distribution:

High availability and disaster recovery concepts in SharePoint 2013

  • RAID 0: Provides performance improvement, no redundancy (disk striping)
  • RAID 1: Provides redundancy (disk mirroring)
  • RAID 5: Data written over minimum three disks with parity information
  • RAID 10: Provides performance and redundancy (RAID 1+0)

plan for network redundancy:

Understand network topology requirements

Plan the network connections within and between farms. We recommend that you use a network that has low latency.

The following list provides some best practices and recommendations:

  • All servers in the farm should have LAN bandwidth and latency to the server that is running SQL Server. Latency should be no greater than 1 millisecond.
  • We do not recommend a wide area network (WAN) topology in which a server that is running SQL Server is deployed remotely from other components of the farm over a network that has latency greater than 1 ms., because this topology has not been tested.
  • Plan for an adequate WAN network if you plan to use SQL Server the AlwaysOn implementation suite, mirroring, log shipping, or Failover Clustering to keep a remote site up-to-date.
  • We recommend that web servers and application servers have two network adapters: one network adapter to handle user traffic and the other to handle communication with the servers that are running SQL Server.

To enable Network Load Balancing:

  1. Install Network Load Balancing on each server
  2. Configure NLB using the NLB Manager
  3. Create a new NLB Cluster
  4. ‘Select servers and IP addresses
  5. Select Unicast or Multicast
  6. Edit and add port rules (not required)
  7. Add additional servers as required
  • An NLB Cluster can have 32 nodes (servers)
  • Adding hosts doesn’t bring down the cluster
  • A host can be brought down for maintenance
  • NLB allows for multiple IP addresses

plan for SQL Server load balancing:

  • Linked servers can be used to distribute load across content databases
  • Federated database servers can use horizontal partitioning (very advanced)

plan for SQL Server aliases:

SQL Server aliases

Create or Delete a Server Alias for Use by a Client (SQL Server Configuration Manager)

To create a SQL alias:

  1. Use SQL Server Config Manager (cliconfg.exe)
  2. Create a New Alias
  3. Enter alias name, port, protocol and server

Plan backup and restore

This objective may include but is not limited to: establish a SharePoint backup schedule, establish a SQL Server backup schedule, plan a non-production environment content refresh, plan for farm configuration recovery, plan for service application recovery, plan for content recovery

establish a SharePoint backup schedule:

Overview of backup and recovery in SharePoint 2013

The SharePoint 2013 backup architecture and recovery processes include:

  • farm backup and recovery;
  • granular backup and recovery; and
  • recovery from an unattached content database

Plan for backup and recovery in SharePoint 2013

establish a SQL Server backup schedule:

  • Review available backup technologies
  • Size of content databases
  • Differing importance of data
  • How long to maintain backups
  • How often to perform backups (full or incremental)

plan a non-production environment content refresh:

Options for content refresh:

  • Content database backup/restore
  • Content deployment using Web Content Management

plan for farm configuration recovery:

Back up farm configurations in SharePoint 2013

Backup-SPConfigurationDatabase -Directory <BackupFolder> -DatabaseServer <DatabaseServerName> -DatabaseName <DatabaseName> -DatabaseCredentials <WindowsPowerShellCredentialObject> [-Verbose]

plan for service application recovery:

Back up service applications in SharePoint 2013

Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <ServiceApplicationName> [-Verbose]

plan for content recovery:

Content recovery options:

  1. Recovery via Restore-SPSite
  2. Content database recovery via SQL Server
  3. Recovery via Central Administration

Back up content databases in SharePoint 2013

Using the Mount-SPContentDatabase to the same farm requires the use of AssignNewDatabaseId parameter if the database is being restore as a new database to the same farm.

Steps to restore a content database:

  1. Use Mount-SPContentDatabase (with the optional AssignNewDatabaseId parameter if required)
  2. Use Get-SPContentDatabase with ConnectAsUnattachedDatabase
  3. Use Central Admin, Backup and Restore, Recover Data from an Unattached Content Database in the Granular Backup section
  4. Enter the database and SQL instance information
  5. Select the Browse Content option
  6. Select the site collection, site, or list that needs to be restore and click Restore

Plan a SharePoint Environment (20 percent)

Plan a social workload.

This objective may include but is not limited to: plan communities, plan My Sites, plan social permissions, plan user profiles, plan activity feeds, plan connections

plan communities:

Plan for communities in SharePoint Server 2013

Community Sites provide a computing solution for users to collaborate around questions, problems, interests, suggestions, opinions, and so on. Through feedback, in the form of replies, members gain access to valuable information from which they can further narrow the most useful responses via the number of members who like a reply and which reply is marked as the best reply. These actions provide incentives for members of the community to participate and build a reputation within the community. Over time, users who have provided the most positive contributions to the community become top contributors and earn trust from other members.

Members can receive Badges from moderators (gifts – only one allowed at a time) as well as earn badges for achieving points answering questions, writing posts, etc.

Steps to enable community site on an existing web:

  1. Enable the SharePoint Server Standard Collection feature
  2. Enable the Community Site feature

Steps to support full Community Site features (@ and #):

  1. Create a Metadata service application (for hash tags)
  2. Create a User Profile service application (for @ mentions)
  3. Create a Search service application
  4. Enable email sending (for moderation of content)

To enable monitoring of offensive content:

  1. On the community site home page, click Community Settings in the Community Tools search
  2. Select “Enable Reporting of Offensive Content”
  3. Click OK

plan My Sites:

Plan for My Sites in SharePoint Server 2013

A My Site is a personal site for a user in an organization. Although a My Site appears as a single site to a user, the My Sites architecture in SharePoint Server consists of a web application, a My Site host site collection, an individual site collection, and several SharePoint service applications and features. Except for the individual site collection, all other parts of this infrastructure are configured once and shared among all the users who are part of the My Sites deployment.

Configure My Sites in SharePoint Server 2013

  1. Create a My Sites web application (highly recommended)
  2. Create a User Profile Service Application
  3. Start the User Profile Service Application
  4. Create a My Sites site collection
  5. Create a Permission Policy to Create Subsites
  6. Create a User Policy for all users with the Create Subsites permission policy
  7. Configure the User Profile Service Application

Exchange Auto Discovery enables the SkyDrive option in Office 2013 and on mobile devices. The PowerShell script must be run on an exchange server.

Personal Sites (SkyDrive) are created asynchronously by SharePoint 2013 to reduce server load. There are two queues:

  1. Interactive queue – filled by requests from a user click a link in the browser
  2. Non-interactive queue – filled if a user tries to access SkyDrive via Office 2013 or if code is used to create/populate My Sites

Configure Personal site collections (SkyDrive):

  1. in Central Admin, select Manage Web Applications in Application Management
  2. Click the My Site web application
  3. Select a quota to apply
  4. Check “Be Hidden From Users” option
  5. Click OK

plan social permissions:

Plan for social computing and collaboration in SharePoint Server 2013

Audiences can be used to group people by profile attributes, such as job classification, office, etc. To create an audience:

  1. In Central Admin, click Manage Service Applications under Application Management
  2. Select the User Profile service application
  3. Click Manage Audiences under the People section
  4. Click New Audience
  5. Enter the details for the Audience and click OK

Social permissions are set using the following:

  1. In Central Admin, click Manage Service Applications under Application Management
  2. Select the User Profile service application
  3. Click Manage User Permissions
  4. Add the relevant user group (NT AUTHORITY\Authenticated Users is added by default)
  5. Select the Create Personal Site, Follow People and Edit Profile, and/or Use Tag and Notes (as required)
  6. Click OK

plan user profiles:

Plan user profiles in SharePoint Server 2013

A user profile is a collection of properties that describes a single user, and also the policies and other settings associated with each property. The user who is described by a profile is represented by a unique identifier in the profile, and the remaining properties provide information about that user, such as the user’s phone numbers, manager, office number, job title, and so on. The set of user profiles for a SharePoint Server 2013 farm are stored in the profiles database associated with a User Profile service application.

User profiles are also used in server-to-server authentication which allows for servers to access and request resources from one another on behalf of users.

Plan profile synchronization for SharePoint Server 2013

Synchronize user and group profiles in SharePoint Server 2013

The User Profile service application consists of the following three databases:

  1. Profile database
  2. Synchronization database
  3. Social tagging database

To configure the User Profile Synchronization service (FIM):

  1. The Farm service account must be a member of the local admin group on all servers that the user profile sync will run on
  2. Use Central Admin to start the User Profile service
  3. Use Central Admin to start the User Profile Sync service
  4. Create a User Synchronization account with Replicating Directory Changes permission on the Active Directory domain you want to synchronise with
  5. If you are exporting changes to AD, the User Sync account also needs Grant Create Child Objects and Write permissions to the OU being synced (such as thumbnailPhoto)

plan activity feeds:

Overview of microblog features, feeds, and the Distributed Cache service in SharePoint Server 2013

Plan for feeds and the Distributed Cache service in SharePoint Server 2013

The Distributed Cache service runs in two modes: Dedicated and Collocated. The Distributed Cache caches login information, which means NLB doesn’t require server affinity.

Users can follow three main items:

  1. People: maximum 1,000
  2. Documents: maximum 500
  3. Sites: maximum 500

plan connections:

Plan for feeds and the Distributed Cache service in SharePoint Server 2013

Plan and configure a search workload.

This objective may include but is not limited to: plan and configure search result relevancy, plan and configure index freshness, plan and configure result sources, plan and configure the end-user experience, plan and configure a search schema, analyze search analytics reports

plan and configure search result relevancy:

Manage search relevance in SharePoint Server 2013

Create and deploy a thesaurus in SharePoint Server 2013

<br /><br />$searchApp = Get-SPEnterpriseSearchServiceApplication Import-SPEnterpriseSearchThesaurus -SearchApplication $searchApp -Filename &lt;Path&gt;<br /><br />

Create and deploy custom entity extractors in SharePoint Server 2013

Manage company name extraction in SharePoint Server 2013

Manage query rules in SharePoint Server 2013

Query rules can change the format, display, and ordering of search results.

To create a query rule:

Manage query suggestions in SharePoint Server 2013

Manage query spelling correction in SharePoint Server 2013

Configure authoritative pages in SharePoint 2013

Building a thesaurus:

  1. Create a CSV file with Key, Synonym and Language
  2. Start a SharePoint management shell
  3. Use the powershell commands:
<br /><br />$searchApp = Get-SPEnterpriseSearchServiceApplication<br /><br />Import-SPEnterpriseSearchThesaurus -SearchApplication $searchApp -filename &lt;path&gt;<br /><br />

Building a custom entity extraction:

  1. Create a CSV file with Key, Display form
  2. Start a SharePoint management shell
  3. Use the powershell commands:
<br /><br />$searchApp = Get-SPEnterpriseSearchServiceApplication<br /><br />Import-SPEnterpriseSearchExtractionDictionary -SearchApplication $searchApp -filename &lt;path&gt; -DictionaryName &lt;dictionary name&gt;<br /><br />

plan and configure index freshness:

Manage crawling in SharePoint 2013

Manage continuous crawls in SharePoint Server 2013

Continuous Crawl setting is available in the Crawl Schedules section of the Content Source.

plan and configure result sources:

Understanding result sources for search in SharePoint Server 2013

The result source is a definition that specifies each of the following:

  • A search provider or source URL to get search results from — for example, the search index of the local SharePoint Search service
  • A protocol to use to get search results — for example, the OpenSearch protocol
  • A query transform, which can narrow results from the given search provider or URL to a specified subset — for example, a subset that has a particular content type

A result source can also specify other settings, such as an authentication method to use when requesting results from a provider.

Configure result sources for search in SharePoint Server 2013

plan and configure the end-user experience:

plan and configure a search schema:

Overview of the search schema in SharePoint Server 2013

The search schema contains crawled properties, crawled property categories, the crawled to managed property mapping and the managed property settings. Managed property settings define what you can search for and how, for example if you can refine or query on a property.

The search schema is stored in the Search Administration database. The search schema contains:

  • The mapping between crawled properties and managed properties. This can be a mapping from one crawled property to one managed property, from one to many, many to one or even a many to many mapping.
  • How the managed properties should be written to the search index. For example, to which full-text index the values of the managed properties should be written and to which weight group (context).
  • The settings for the different managed properties. For example, if you can search on, query on, or refine search results by particular managed properties.
  • Crawled property categories that group properties according to their IFilter or protocol handler. If you edit a crawled property category, your changes apply to all of the crawled properties within the category. This can influence performance and how items are saved in the search index.

Search schema updates are propagated through the search system every minute.

Manage the search schema in SharePoint Server 2013

analyze search analytics reports:

Plan and configure a Web Content Management (WCM) workload.

This objective may include but is not limited to: plan and configure channels, plan and configure product catalog and topic pages, plan and configure Design Manager, plan and configure content deployment, plan and configure display templates, plan and configure variations

plan and configure channels:

Overview of mobile devices and SharePoint Server 2013

With device channels in SharePoint Server 2013, you can render a single publishing site in multiple ways by using different designs that target different devices based on their user agent string. You create a single site and author the content in it a single time. Then, that site and content can be mapped to use different master pages and style sheets for a specific device or group of devices. Also, you can easily show different content to different device channels using same page and page layout.

plan and configure product catalog and topic pages:

What’s new in web content management for SharePoint 2013 publishing sites

SharePoint Server 2013 has added the ability to designate any library or list as a catalog. After the Cross-Site Collection Publishing feature is enabled for a site collection, you can designate any library or list within that site collection as a catalog so that content can be reused on publishing site collections. You can use catalog-enabled libraries or lists for scenarios such as an article library, knowledge base library, or product catalog.

To create a product catalog:

  1. Create site columns (or use existing ones)
  2. Modify the Product content type and add the site columns
  3. Create the product hierarchy in the Term Store
  4. Add the product items, and approve them if necessary
  5. Add the new site columns to the managed properties within the search schema

Configure cross-site publishing in SharePoint Server 2013

  1. Create site collections for cross-site publishing
  2. Activate the Cross-Site Collection Publishing feature
  3. Create and manage term sets for tagging content on authoring sites
  4. Create catalog content by using SharePoint lists
  5. Share a library or list as a catalog
  6. Make a term set available to other site collections
  7. Configure search for cross-site publishing

plan and configure Design Manager:

Overview of themes in SharePoint 2013

Overview of Design Manager in SharePoint 2013

Design Manager is a feature in SharePoint 2013 that makes it easier to create a fully customized, pixel-perfect design while using the web-design tools that you’re already familiar with. Design Manager is a publishing feature that is available in publishing sites in both SharePoint Server 2013 and Office 365. You can also use Design Manager to brand the public-facing website in Office 365.

With Design Manager, you can create a visual design for your website by using whatever web design tool or HTML editor you prefer, using only HTML and CSS, and then upload that design into SharePoint. Design Manager is the central hub and interface where you manage all aspects of a custom design.

plan and configure content deployment:

Enterprise content management cmdlets in SharePoint Server 2013

Content deployment copies content from a source SharePoint Server 2013 site collection to a destination site collection. You can copy the entire source site collection or a subset of sites.

Note: Make sure that you run the initial content deployment as a full deployment. After you complete a full deployment, you can run an incremental deployment, which deploys only changed pages and related assets.

New-SPContentDeploymentJob

New-SPContentDeploymentPath

plan and configure display templates:

Customize search result types in SharePoint 2013

A search result type is a rule that causes distinct kinds of search results to be displayed in different ways. It consists of the following:

  • One or more characteristics or conditions to compare each search result against, such as the result source or content type of the search result
  • A display template to use for search results that meet the conditions. The display template controls the way in which all results that meet the conditions appear and behave on a search results page.

Display templates for search results are in the Search folder in the master page gallery for the site collection

plan and configure variations:

Variations overview in SharePoint Server 2013

The variations feature in SharePoint Server 2013 and SharePoint Online makes content available to specific audiences on different sites by syncing content from a source variation site to each target variation site. When users visit the root site, they are redirected to the appropriate variation site, based on the language setting of their web browser. Content on a target variation site can be translated into other languages before it is published. Variations can be used only on sites that are created by using one of the Publishing site templates, or on sites for which the SharePoint Server Publishing Infrastructure feature was activated.

Plan for variations in SharePoint Server 2013

Job name Default schedule
Variations Create Hierarchies Job Definition Hourly
Variations Propagate List Items Job Definition Every 15 minutes
Variations Propagate Page Job Definition Every 15 minutes
Variations Propagate Sites and Lists Job Definition Every 30 minutes

Plan an Enterprise Content Management (ECM) workload.

This objective may include but is not limited to: plan and configure E-Discovery, plan and configure document routing, plan and configure co-authoring, plan and configure record disposition and retention, plan large document repositories, plan and configure software boundaries

plan and configure E-Discovery:

What’s new in eDiscovery in SharePoint Server 2013

Plan for eDiscovery in SharePoint Server 2013

  1. determine how many eDiscovery Centers you need and where to put the eDiscovery Centers
  2. identify the locations that contain content that can be discovered
  3. consider the permissions that you have to grant to eDiscovery users.

Configure eDiscovery in SharePoint Server 2013

  1. Configure communication between SharePoint Server 2013 and Exchange Server 2013.
  2. Configure Search to crawl all discoverable content.
  3. Grant permissions.
  4. Create an eDiscovery Center

plan and configure document routing:

Plan document sets in SharePoint Server 2013

plan and configure co-authoring:

Overview of co-authoring in SharePoint 2013

Planning considerations:

  1. Permissions
  2. Versioning – minor versioning may interfere with the synchronisation and versioning capabilities of OneNote
  3. Number of versions
  4. Versioning period – how often SharePoint products will create a new version

plan and configure record disposition and retention:

To configure site closure:

  1. In the Site Collection Site Settings, click Site Policies in the Site Collection Administrator section
  2. On the Site Policies page, click Create
  3. Enter metadata for the site policy
  4. Choose how to handle site deletion and closure
  5. Choose whether to make the site collection and all subsites read-only
  6. Click OK to create the policy

 

plan large document repositories:

plan and configure software boundaries:

Upgrade and Migrate a SharePoint Environment (20 percent)

Evaluate content and customizations.

This objective may include but is not limited to: perform migration pre-check tasks, analyze content database test results, configure web application authentication for upgrade, resolve orphan objects, resolve missing file system components, resolve configuration conflict issues

perform migration pre-check tasks:

Clean up an environment before an upgrade to SharePoint 2013

Use the Stsadm –o enumallwebs operation on all content databases in your SharePoint 2010 Products environment to identify specific customizations in subsites

</p><p>stsadm -enumallwebs -databasename &lt;name&gt; -includefeatures -includewebparts</p><p>

analyze content database test results:

Upgrade databases from SharePoint 2010 to SharePoint 2013

Test-SPContentDatabase

Use the Test-SPContentDatabase cmdlet to test a content database against a Web application to verify all customizations referenced within the content database are also installed in the web application. This cmdlet can be issued against a content database currently attached to the farm, or a content database that is not connected to the farm. It can be used to test content databases from SharePoint 2010 Products and from SharePoint Products and Technologies.

</p><p>Test-SPContentDatabase [-Identity] &lt;SPContentDatabasePipeBind&gt; [-AssignmentCollection <br />&lt;SPAssignmentCollection&gt;] [-DatabaseCredentials &lt;PSCredential&gt;] [-ExtendedCheck <br />&lt;SwitchParameter&gt;] [-ServerInstance &lt;SPDatabaseServiceInstancePipeBind&gt;] [-ShowLocation <br />&lt;SwitchParameter&gt;] [-ShowRowCounts &lt;SwitchParameter&gt;]</p><p>

configure web application authentication for upgrade:

Web applications must use the same authentication schema as the SharePoint 2010 content database i.e. Claims-based or classic Windows-based authentication. Test-SPContentDatabase reports when the web application in the SharePoint 2013 farm has a different authentication to the SharePoint 2010 content database.

resolve orphan objects:

Clean up an environment before an upgrade to SharePoint 2013

Before you upgrade, use the Enumallwebs operation in stsadm command-line tool to discover which sites are in which content databases and compare the results. Also, examine each site collection in the results and check whether it is listed as missing in the site map. Being listed as missing indicates that it is an orphaned site.

Enumallwebs: Stsadm operation

Remove-SPSite

resolve missing file system components:

Use the WinDiff tool to compare differences between file system components

resolve configuration conflict issues:

Plan an upgrade process.

This objective may include but is not limited to: plan removal of servers in rotation, configure a parallel upgrade, configure read-only access for content, configure upgrade farms, measure upgrade performance, plan an installation sequence

plan removal of servers in rotation:

configure a parallel upgrade:

configure read-only access for content:

Set databases to Read-Only in SharePoint before backup up content databases and restoring them.

Once successfully restored, set the content database to Read and Write

configure upgrade farms:

measure upgrade performance:

plan an installation sequence:

Upgrade site collection.

This objective may include but is not limited to: perform a health check, analyze and resolve health check results, plan and configure available site collection modes, plan and configure site collection upgrade availability, plan and configure EVAL mode, plan and configure site collection upgrade throttling

perform a health check:

Run site collection health checks in SharePoint 2013

Rule name Description Rule ID
Conflicting Content Types This rule checks for conflicts between existing content types and content types that are created when you upgrade the site to SharePoint 2013. A conflict occurs when both content types have the same name. befe203b-a8c0-48c2-b5f0-27c10f9e1622
Customized Files This rule checks for any files that were customized (or unghosted) in the site collection or subsites. When run in repair mode, it can reset the page to the default (reghost the file). cd839b0d-9707-4950-8fac-f306cb920f6c
Missing Galleries This rule checks for all default galleries and reports if any are missing from the site collection or subsites. ee967197-ccbe-4c00-88e4-e6fab81145e1
Missing Parent Content Types This rule checks for missing parent content types. If a missing parent content type is found, you can either delete the orphaned content type or associate the orphaned content type with a different parent content type.ge a9a6769f-7289-4b9f-ae7f-5db4b997d284
Missing Site Templates This rule checks to make sure that the template the site is based on is available and reports if any elements are missing. 5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd
Unsupported Language Pack References This rule checks to make sure that the language packs that are used by the site collection exist and are referenced correctly by the site collection. 99c946f7-5751-417c-89d3-b9c8bb2d1f66
Unsupported MUI References This rule checks to make sure that the multi-user interface elements that are used by the site collection exist and are referenced correctly by the site collection. 6da06aab-c539-4e0d-b111-b1da4408859a

Test-SPSite -Identity <SiteURL> [-Rule <RuleID>]

analyze and resolve health check results:

Repair-SPSite -Identity <SiteURL> [-Rule <RuleID>]

plan and configure available site collection modes:

plan and configure site collection upgrade availability:

plan and configure EVAL mode:

Manage site collection upgrades to SharePoint 2013

Request-SPUpgradeEvaluationSiteCollection -identity URL to site

plan and configure site collection upgrade throttling:

Control site throttle settings for upgrade to SharePoint 2013

$wa = Get-SPWebApplication <URL>

$wa.SiteUpgradeThrottleSettings

Create and Configure Service Applications (21 percent)

Create and configure App Management.

This objective may include but is not limited to: create and configure the App Store, create and configure subscriptions, configure marketplace connections, configure DNS entries, configure wildcard certificates

create and configure the App Store:

Overview of apps for SharePoint 2013

An app for SharePoint is a small, easy-to-use, stand-alone app that solves a specific end-user or business need. Site owners can discover and download apps for SharePoint from a public SharePoint Store or from their organization’s internal App Catalog and install them on their SharePoint sites.

The following are examples of apps for SharePoint that site owners could add to their sites:

  • An app that provides event planning tools.
  • An app that provides a shopping cart experience for a site.
  • An app that sends a note of recognition for good work (kudos) to someone in the organization.

Plan for apps for SharePoint 2013

Configure an environment for apps for SharePoint (SharePoint 2013)

create and configure subscriptions:

Configure an environment for apps for SharePoint (SharePoint 2013)

Apps rely on the App Management and Microsoft SharePoint Foundation Subscription Settings service applications. These service applications use the multi-tenancy features to provide app permissions and create the subdomains for apps.

The following two SharePoint Services must be started to enable subscriptions:

  1. App Management Service
  2. Microsoft SharePoint Foundation Subscription Settings Service

configure marketplace connections:

Manage the App Catalog in SharePoint 2013

The App Catalog site is a special site collection on a web application. Because each web application can have an App Catalog site, a farm can have more than one App Catalog site.

When you create an App Catalog site, you get two libraries for apps:

  • Apps for SharePoint
  • Apps for Office

Because an App Catalog is scoped to a web application, all apps that you want to make available for a web application have to be in the App Catalog site collection for that web application. You create the App Catalog site collection from SharePoint Central Administration.

Farm administrators can determine whether users can purchase apps from the SharePoint Store. This setting is at the web application scope. If users cannot purchase apps, they can still browse the SharePoint Store, and request an app. Farm administrators and the App Catalog site owner can view and respond to app requests.

configure DNS entries:

Configure an environment for apps for SharePoint (SharePoint 2013)

  1. Create a forward lookup zone for apps (eg. ContosoApps.com)
  2. Create a CNAME alias from the app domain to the sharepoint domain (eg. *.ContosoApps.com -> SharePoint.Contoso.com)

Forward lookup zones can be created via DNS Manager in Windows Server 2008 R2.

configure wildcard certificates:

Configure an environment for apps for SharePoint (SharePoint 2013)

  1. Create a Wildcard SSL certificate for the new app domain (eg. https://*.ContosoApps.com)

Create and configure productivity services.

This objective may include but is not limited to: create and configure Microsoft Excel Services, Microsoft Access services, Microsoft Visio services, Microsoft Word Automation services, Microsoft PowerPoint Conversion services, and Translation Services

create and configure Microsoft Excel Services:

Overview of Excel Services in SharePoint Server 2013

Excel Services consists of Excel Calculation Services, the Excel Web Access Web Part, and Excel Web Services for programmatic access. It supports sharing, securing, managing, and using Excel 2013 workbooks in a browse.

create and configure Microsoft Access services:

create and configure Microsoft Visio services:

create and configure Microsoft Word Automation services:

create and configure Microsoft PowerPoint Conversion services and Translation Services:

Configure service application federation.

This objective may include but is not limited to: plan services to federate, perform a certificate exchange, manage trusts, manage service application permissions, publish service applications, consume service applications

plan services to federate:

perform a certificate exchange:

manage trusts:

manage service application permissions:

publish service applications:

consume service applications:

Create and configure a Business Connectivity Service (BCS) and Secure Store application.

This objective may include but is not limited to: import and configure BCS models, configure BCS model security, configure BCS for search, generate a Secure Store master key, manage Secure Store target application permissions, create Secure Store target applications

import and configure BCS models:

configure BCS model security:

Set permissions on the BCS Metadata Store for a Business Connectivity Services on-premises solution in SharePoint 2013

configure BCS for search:

generate a Secure Store master key:

manage Secure Store target application permissions:

create Secure Store target applications:

Manage SharePoint Solutions, BI, and Systems Integration (18 percent)

Manage SharePoint solutions and applications.

This objective may include but is not limited to: manage sandbox solution quotas, configure sandbox solution management, deploy farm solutions, upgrade farm solutions, deploy Apps, upgrade Apps

manage sandbox solution quotas:

configure sandbox solution management:

deploy farm solutions:

upgrade farm solutions:

deploy Apps:

upgrade Apps:

Plan and configure a BI infrastructure.

This objective may include but is not limited to: plan and configure Performance Point, plan and configure reporting services, plan and configure PowerPivot, plan and configure Excel Services, plan and configure PowerView, plan and configure BI security

Deployment Topologies for SQL Server BI Features

plan and configure Performance Point:

PerformancePoint Services in SharePoint Server 2013 overview

PerformancePoint Services in SharePoint Server 2013 is a performance management service that you can use to monitor and analyze your business. By providing flexible, easy-to-use tools for building dashboards, scorecards, and key performance indicators (KPIs), PerformancePoint Services can help individuals across an organization make informed business decisions that align with companywide objectives and strategy.

Configure PerformancePoint Services (SharePoint Server 2013)

plan and configure reporting services:

Install Reporting Services SharePoint Mode for SharePoint 2013

Reporting Services in SharePoint mode does not install a separate instance as per previous versions. It is configured and operated within SharePoint and has it’s own Service Application and Service Proxy within SharePoint.

  1. Set up accounts
  2. Install Reports Services Report Server in SharePoint Mode
  3. Register and start the Reporting Services SharePoint Service
  4. Create a Reporting Services Service Application
  5. Activate the Power View Site Collection Feature

plan and configure PowerPivot:

Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1)

plan and configure Excel Services:

plan and configure PowerView:

Activate the Report Server and Power View Integration Features in SharePoint

plan and configure BI security:

Create and configure work management.

This objective may include but is not limited to: configure a connection to Exchange, configure a connection to Microsoft Project Server, manage trusts, plan Exchange configuration for E-Discovery

configure a connection to Exchange:

Configure site mailboxes in SharePoint Server 2013

  1. Install Exchange Web Services API on SharePoint Server
  2. Establish OAuth Trust and Service Permissions on SharePoint Server 2013
  3. Establish OAuth Trust and Service Permission on Exchange Server 2013

configure a connection to Microsoft Project Server:

Install and configure Project Server 2013

  1. Install Project Server on every SharePoint server in the farm
  2. Run the SharePoint Config Wizard for each server in the farm
  3. Start the Project Server Application service
  4. Create a Project Server service application
  5. Create a Project Server web app (recommended)
  6. Create the root Project Server site collection and give all users Read access to it

manage trusts:

Exchange trust certificates between farms in SharePoint 2013

  1. Export the root certificate from the consuming farm
  2. Export the STS certificate from the consuming farm
  3. Export the root certificate from the publishing farm
  4. Copy the certificates
  5. Import the root certificate and create a trusted root authority on the consuming farm
  6. Import the root certificate and create a trusted root authority on the publishing farm
  7. Import the STS certificate and create a trusted service token issuer on the publishing farm

plan Exchange configuration for E-Discovery:

Plan for eDiscovery in SharePoint Server 2013

  1. Decide how man eDiscovery centers are required, based on the number of search service applications
  2. Identify discoverable content
  3. Determine permission requirements by granting eDiscovery user access via a web application policy, or adding eDiscovery users as site collection administrators for every site collection that contains discoverable content
Advertisements

One Response to “Studying for Exam 70-332: Advanced Solutions of Microsoft SharePoint Server 2013”

  1. lammy82 Says:

    Page is a bit broken from about halfway down! But thanks for putting this up – still very useful!

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s


%d bloggers like this: