###BeginCaseStudy###
Topic 5, Contoso Ltd
Background
A company named Contoso, Ltd. has offices in Seattle and Toronto. Each office has a data center and a
region-specific site in a single Active Directory Domain Services (AD DS) domain named contoso.com.
The database servers run Microsoft SQL Server 2008 R2. Database servers are installed in each data
center and are members of the region-specific sites. The WAN connection between the data centers is a
dedicated T3 connection.
Existing Corporate Farm
Contoso has a SharePoint farm named HQ-SP10. The SharePoint servers in the farm run SharePoint
Server 2010 on Windows Server 2008 R2.
HQ-SP10 hosts many web applications that require unique service accounts. A SharePoint 2010 web
application named WebApp1 is located at https://webapp1.contoso.com. WebApp1 references a
custom knowledge base module in HQ-SP10 and the content is stored in the SharePoint database HQDB.
Employees authenticate to WebApp1 by using classic mode authentication.
Users in both offices make frequent updates to SharePoint content. Administrators make only minimal
changes to the SharePoint farm settings and web applications.
Existing Product Support FarmThe product support department hosts a SharePoint farm named DEPT-SP13. The SharePoint servers in
the farm run SharePoint Server 2013 and are members of a domain named PrdSupport.contoso.com.
DEPT-SP13 hosts two service applications:
A built-in service application provides access to a business data
model connected to the company’s data warehouse.
A custom service application named SvcApp1 provides access to
data in a legacy system.
Users in the product support department access the service applications by using a local web application
named WebApp2. WebApp2 is located at webapp2.contoso.com and is stored in the SharePoint
database DEPTDB. Users in other departments access the service applications by using WebApp1.
Technical Challenges
You are upgrading HQ-SP10 and the web applications hosted in the farm to a new SharePoint Server
2013 farm named HQ-SP13.
When upgrading the content database to SharePoint Server 2013, you receive the following error
message:
Business Requirements
The SharePoint 2010 environment must meet the following business requirements:
HQ-SP10 must provide read-only access to users during the
migration.
All customizations in HQ-SP10 must be migrated to HQ-SP13.
The SharePoint 2013 environment must meet the following business requirements:
HQ-SP13 and the web applications must remain available if one
of the SharePoint servers or database servers is offline.
Users’ documents stored in HQ-SP13 must be available if all the
servers in a region are offline.
Shared resources in SvcApp1 must be available to other
SharePoint farms in the company.
All customizations in HQ-SP13 must be verified after the farm
upgrade.
Periodically, you must provide an offline copy of site content
from HQ-SP13 to the legal department.Technical Requirements
You have the following technical requirements:
All users must be able to access the business data model for the company data warehouse.
Backup administrators must be able to restore HQ-SP13, WebApp1, and SvcApp1 separately.
The SharePoint 2013 environment for HQ-SP13 must meet the following technical requirements:
The database servers must run Microsoft SQL Server 2012.
The databases must belong to a SQL Server AlwaysOn
Availability Group and use the WAN connection for database replication
between the sites.
The database servers must be configured with the Enable
Contained Databases property.
Application pools for the web applications require unique
service accounts.
After the upgrade, users in the accounting department who
connect to WebApp1 must be able to access shared resources in
SvcApp1.
###EndCaseStudy###
You need to resolve the SharePoint database error.
What should you do?
A.
Add a new request URL mapping to the web application.
B.
Remove the orphaned objects from the database.
C.
Set the databases to read-write.
D.
Add the managed path for the site collection to the web application.
Explanation:
ERROR Template Template Id: SPSite Id=Site Id could not be accessed due to exception. Skipping
SPWeb Id=Web Id for template upgrade. Exception: System.IO.FileNotFoundException: The site
with the id Site Id could not be found.
This error indicates that a managed path is missing. Add the managed path for the site collection
into the web application and restart upgrade for the content database that contains this site collection.
Ref: http://technet.microsoft.com/en-us/library/cc262967(v=office.15).aspx