You need to configure SQL Server connectivity
###BeginCaseStudy###
Case Study: 4
Proseware, Inc
Background
General Background
You are a SharePoint administrator for a media distribution company named
Proseware, Inc. Proseware is in the process of upgrading from SharePoint 2010 to
SharePoint 2013. The IT group has deployed a new SharePoint 2013 farm. The farm
is not yet fully configured. You are supporting the product development group during
the planning and configuration of the new SharePoint farm. The product
development group includes the research, development, and marketing teams. The
product development group has multiple team sites and project collaborations sites
in the current SharePoint 2010 farm.
Business Background
Stakeholders have identified the following initiatives:
ProseWeb, a public website that will allow anonymous visitors to browse the
company’s product catalog.
PartnerWeb, a public website that will allow authenticated users from partner
companies to collaborate on product materials.
ProductsKB, a centralized repository where teams can publish product-related
documents, images, videos, and other information related to the company’s product
catalog. Information in this site will be consumed by the ProseWeb site.
Technical Background
The company has an Active Directory Domain Services (AD DS) domain named
proseware.com. All servers and user accounts are members of the domain. The
company has purchased the proseware-apps.com domain to support SharePoint
apps.
The SharePoint 2013 farm currently has the following configuration:
The farm includes seven SharePoint servers named SPWEB1, SPWEB2,
SPWEB3, SPWEB4, SPADM1, SPAPP1, and SPAPP2.
SPWEB1, SPWEB2, SPWEB3, SPWEB4 and SPADM1 are configured as frontend
web servers.
SPADM1
is dedicated for administration purposes.
Windows
Network Load Balancing has been configured to load balance all host names across
the front-end web servers.
Central Administration has been provisioned on SPWEB4 and SPADM1.
The farm includes two database servers named SQL1 and SQL2 that run Microsoft
SQL Server 2012 Enterprise.
Wildcard
certificates for *.proseware.com and *.proseware-apps.com have been installed on
all SharePoint servers.
Five web applications have been created:
ProseWeb
– https://www.proseware.com
PartnerWeb
– https://partners.proseware.com
ProductsKB
– https://kb.proseware.com
Teams
– https://teams.proseware.com
Apps
– https://proseware-apps.com
The
SharePoint development team has created a custom web template solution package
named ProseWebTemplate.WSP for provisioning the ProseWeb site collection.
The package includes a custom template named ProseWeb.
An instance of a managed metadata service application has been configured with a
content type hub. Two enterprise content types named Product Document and
Product Image have been published in the content type hub and are available across
all web applications and sites.
All team collaboration site collections for the product development group are
contained in a single content database named sp_content_teams_productdev. The
database has been restored on SQL1, and upgraded by using the database attach
method on the Teams web application. The site collections have not been ungraded.
All team collaboration site collections for the product development group are
referenced under a wildcard managed path at
https://teams.proseware.com/productdev.
The product development marketing team collaboration site is located at
https://teams.proseware.com/productdev/marketing.
The marketing team has made significant customizations to their team collaboration
site by using Microsoft SharePoint Designer.
Business Requirements
The SharePoint 2013 environment must meet the following business requirements:
Due to export and copyright restrictions, SharePoint sites may be accessed only
from within North America.
The ProseWeb site must display a fixed-width page design for desktop browsers,
and a single responsive web design for all mobile devices. The company’s web
designers have prepared two site templates that meet these requirements.
To support the website design layouts, images on the website must be rendered in
one of three standard sizes, specified in pixels: Thumbnail (150 x 150), Catalog (300
x 300), and Detail (500 x 500).
Users must be able to easily copy product-related documents, images, and other
files from any team collaboration site to the ProductsKB site. Metadata on content
must be preserved when moving or copying content between sites.
The product development group’s team collaboration site collections must be
upgraded.
Technical Requirements
You have the following technical requirements:
SQL Server connections must use TCP and port 1488.
Site collection upgrades must be throttled for no more than 20 concurrent upgrades
within any content database, and throttled at 10 concurrent upgrades for any web
application instance.
If a site collection has been customized by using SharePoint Designer:
The site collection upgrade must be performed by a farm administrator.
All customizations must be evaluated and verified before performing the upgrade.
All sandboxed solution code must run on the same server as the original request.
Requests originating from outside the company network must not be routed to any
server running Central Administration.
SPAPP1 and SPAPP2 must not process user requests for site content and pages.
You must deploy the custom web template solution as a full-trust farm solution and
use the ProseWeb template when creating the root site collection for the ProseWeb
web application.
The ProductsKB site must be provisioned by using a Records Center site template.
###EndCaseStudy###
You are preparing to migrate to the new SharePoint environment. You need to configure
SQL Server connectivity. What should you do?
Which URL should you specify?
###BeginCaseStudy###
Case Study: 4
Proseware, Inc
Background
General Background
You are a SharePoint administrator for a media distribution company named
Proseware, Inc. Proseware is in the process of upgrading from SharePoint 2010 to
SharePoint 2013. The IT group has deployed a new SharePoint 2013 farm. The farm
is not yet fully configured. You are supporting the product development group during
the planning and configuration of the new SharePoint farm. The product
development group includes the research, development, and marketing teams. The
product development group has multiple team sites and project collaborations sites
in the current SharePoint 2010 farm.
Business Background
Stakeholders have identified the following initiatives:
ProseWeb, a public website that will allow anonymous visitors to browse the
company’s product catalog.
PartnerWeb, a public website that will allow authenticated users from partner
companies to collaborate on product materials.
ProductsKB, a centralized repository where teams can publish product-related
documents, images, videos, and other information related to the company’s product
catalog. Information in this site will be consumed by the ProseWeb site.
Technical Background
The company has an Active Directory Domain Services (AD DS) domain named
proseware.com. All servers and user accounts are members of the domain. The
company has purchased the proseware-apps.com domain to support SharePoint apps.
The SharePoint 2013 farm currently has the following configuration:
The farm includes seven SharePoint servers named SPWEB1, SPWEB2,
SPWEB3, SPWEB4, SPADM1, SPAPP1, and SPAPP2.
SPWEB1, SPWEB2, SPWEB3, SPWEB4 and SPADM1 are configured as frontend web servers.
SPADM1 is dedicated for administration purposes.
Windows Network Load Balancing has been configured to load balance all host names across
the front-end web servers.
Central Administration has been provisioned on SPWEB4 and SPADM1.
The farm includes two database servers named SQL1 and SQL2 that run Microsoft
SQL Server 2012 Enterprise.
Wildcard certificates for *.proseware.com and *.proseware-apps.com have been installed on
all SharePoint servers.
Five web applications have been created:
ProseWeb
– https://www.proseware.com
PartnerWeb
– https://partners.proseware.com
ProductsKB
– https://kb.proseware.com
Teams
– https://teams.proseware.com
Apps
– https://proseware-apps.com
The SharePoint development team has created a custom web template solution package
named ProseWebTemplate.WSP for provisioning the ProseWeb site collection.
The package includes a custom template named ProseWeb.
An instance of a managed metadata service application has been configured with a
content type hub. Two enterprise content types named Product Document and
Product Image have been published in the content type hub and are available across
all web applications and sites.
All team collaboration site collections for the product development group are
contained in a single content database named sp_content_teams_productdev. The
database has been restored on SQL1, and upgraded by using the database attach
method on the Teams web application. The site collections have not been ungraded.
All team collaboration site collections for the product development group are
referenced under a wildcard managed path at
https://teams.proseware.com/productdev.
The product development marketing team collaboration site is located at
https://teams.proseware.com/productdev/marketing.
The marketing team has made significant customizations to their team collaboration
site by using Microsoft SharePoint Designer.
Business Requirements
The SharePoint 2013 environment must meet the following business requirements:
Due to export and copyright restrictions, SharePoint sites may be accessed only
from within North America.
The ProseWeb site must display a fixed-width page design for desktop browsers,
and a single responsive web design for all mobile devices. The company’s web
designers have prepared two site templates that meet these requirements.
To support the website design layouts, images on the website must be rendered in
one of three standard sizes, specified in pixels: Thumbnail (150 x 150), Catalog (300
x 300), and Detail (500 x 500).
Users must be able to easily copy product-related documents, images, and other
files from any team collaboration site to the ProductsKB site. Metadata on content
must be preserved when moving or copying content between sites.
The product development group’s team collaboration site collections must be
upgraded.
Technical Requirements
You have the following technical requirements:
SQL Server connections must use TCP and port 1488.
Site collection upgrades must be throttled for no more than 20 concurrent upgrades
within any content database, and throttled at 10 concurrent upgrades for any web
application instance.
If a site collection has been customized by using SharePoint Designer:
The site collection upgrade must be performed by a farm administrator.
All customizations must be evaluated and verified before performing the upgrade.
All sandboxed solution code must run on the same server as the original request.
Requests originating from outside the company network must not be routed to any
server running Central Administration.
SPAPP1 and SPAPP2 must not process user requests for site content and pages.
You must deploy the custom web template solution as a full-trust farm solution and
use the ProseWeb template when creating the root site collection for the ProseWeb
web application.
The ProductsKB site must be provisioned by using a Records Center site template.
###EndCaseStudy###
You need to configure the Send To connection.
Which URL should you specify?
Which cache should you configure?
###BeginCaseStudy###
Case Study: 4
Proseware, Inc
Background
General Background
You are a SharePoint administrator for a media distribution company named
Proseware, Inc. Proseware is in the process of upgrading from SharePoint 2010 to
SharePoint 2013. The IT group has deployed a new SharePoint 2013 farm. The farm
is not yet fully configured. You are supporting the product development group during
the planning and configuration of the new SharePoint farm. The product
development group includes the research, development, and marketing teams. The
product development group has multiple team sites and project collaborations sites
in the current SharePoint 2010 farm.
Business Background
Stakeholders have identified the following initiatives:
ProseWeb, a public website that will allow anonymous visitors to browse the
company’s product catalog.
PartnerWeb, a public website that will allow authenticated users from partner
companies to collaborate on product materials.
ProductsKB, a centralized repository where teams can publish product-related
documents, images, videos, and other information related to the company’s product
catalog. Information in this site will be consumed by the ProseWeb site.
Technical Background
The company has an Active Directory Domain Services (AD DS) domain named
proseware.com. All servers and user accounts are members of the domain. The
company has purchased the proseware-apps.com domain to support SharePoint apps.
The SharePoint 2013 farm currently has the following configuration:
The farm includes seven SharePoint servers named SPWEB1, SPWEB2,
SPWEB3, SPWEB4, SPADM1, SPAPP1, and SPAPP2.
SPWEB1, SPWEB2, SPWEB3, SPWEB4 and SPADM1 are configured as frontend
web servers.
SPADM1
is dedicated for administration purposes.
Windows
Network Load Balancing has been configured to load balance all host names across
the front-end web servers.
Central Administration has been provisioned on SPWEB4 and SPADM1.
The farm includes two database servers named SQL1 and SQL2 that run Microsoft
SQL Server 2012 Enterprise.
Wildcard
certificates for *.proseware.com and *.proseware-apps.com have been installed on
all SharePoint servers.
Five web applications have been created:
ProseWeb
– https://www.proseware.com
PartnerWeb
– https://partners.proseware.com
ProductsKB
– https://kb.proseware.com
Teams
– https://teams.proseware.com
Apps
– https://proseware-apps.com
The
SharePoint development team has created a custom web template solution package
named ProseWebTemplate.WSP for provisioning the ProseWeb site collection.
The package includes a custom template named ProseWeb.
An instance of a managed metadata service application has been configured with a
content type hub. Two enterprise content types named Product Document and
Product Image have been published in the content type hub and are available across
all web applications and sites.
All team collaboration site collections for the product development group are
contained in a single content database named sp_content_teams_productdev. The
database has been restored on SQL1, and upgraded by using the database attach
method on the Teams web application. The site collections have not been ungraded.
All team collaboration site collections for the product development group are
referenced under a wildcard managed path at
https://teams.proseware.com/productdev.
The product development marketing team collaboration site is located at
https://teams.proseware.com/productdev/marketing.
The marketing team has made significant customizations to their team collaboration
site by using Microsoft SharePoint Designer.
Business Requirements
The SharePoint 2013 environment must meet the following business requirements:
Due to export and copyright restrictions, SharePoint sites may be accessed only
from within North America.
The ProseWeb site must display a fixed-width page design for desktop browsers,
and a single responsive web design for all mobile devices. The company’s web
designers have prepared two site templates that meet these requirements.
To support the website design layouts, images on the website must be rendered in
one of three standard sizes, specified in pixels: Thumbnail (150 x 150), Catalog (300
x 300), and Detail (500 x 500).
Users must be able to easily copy product-related documents, images, and other
files from any team collaboration site to the ProductsKB site. Metadata on content
must be preserved when moving or copying content between sites.
The product development group’s team collaboration site collections must be
upgraded.
Technical Requirements
You have the following technical requirements:
SQL Server connections must use TCP and port 1488.
Site collection upgrades must be throttled for no more than 20 concurrent upgrades
within any content database, and throttled at 10 concurrent upgrades for any web
application instance.
If a site collection has been customized by using SharePoint Designer:
The site collection upgrade must be performed by a farm administrator.
All customizations must be evaluated and verified before performing the upgrade.
All sandboxed solution code must run on the same server as the original request.
Requests originating from outside the company network must not be routed to any
server running Central Administration.
SPAPP1 and SPAPP2 must not process user requests for site content and pages.
You must deploy the custom web template solution as a full-trust farm solution and
use the ProseWeb template when creating the root site collection for the ProseWeb
web application.
The ProductsKB site must be provisioned by using a Records Center site template.
###EndCaseStudy###
You need to configure caching to support the ProseWeb site design elements.
Which cache should you configure?
Which Windows PowerShell cmdlets should you run?
###BeginCaseStudy###
Case Study: 4
Proseware, Inc
Background
General Background
You are a SharePoint administrator for a media distribution company named
Proseware, Inc. Proseware is in the process of upgrading from SharePoint 2010 to
SharePoint 2013. The IT group has deployed a new SharePoint 2013 farm. The farm
is not yet fully configured. You are supporting the product development group during
the planning and configuration of the new SharePoint farm. The product
development group includes the research, development, and marketing teams. The
product development group has multiple team sites and project collaborations sites
in the current SharePoint 2010 farm.
Business Background
Stakeholders have identified the following initiatives:
ProseWeb, a public website that will allow anonymous visitors to browse the
company’s product catalog.
PartnerWeb, a public website that will allow authenticated users from partner
companies to collaborate on product materials.
ProductsKB, a centralized repository where teams can publish product-related
documents, images, videos, and other information related to the company’s product
catalog. Information in this site will be consumed by the ProseWeb site.
Technical Background
The company has an Active Directory Domain Services (AD DS) domain named
proseware.com. All servers and user accounts are members of the domain. The
company has purchased the proseware-apps.com domain to support SharePoint
apps.
The SharePoint 2013 farm currently has the following configuration:
The farm includes seven SharePoint servers named SPWEB1, SPWEB2,
SPWEB3, SPWEB4, SPADM1, SPAPP1, and SPAPP2.
SPWEB1, SPWEB2, SPWEB3, SPWEB4 and SPADM1 are configured as frontend
web servers.
SPADM1
is dedicated for administration purposes.
Windows
Network Load Balancing has been configured to load balance all host names across
the front-end web servers.
Central Administration has been provisioned on SPWEB4 and SPADM1.
The farm includes two database servers named SQL1 and SQL2 that run Microsoft
SQL Server 2012 Enterprise.
Wildcard
certificates for *.proseware.com and *.proseware-apps.com have been installed on
all SharePoint servers.
Five web applications have been created:
ProseWeb
– https://www.proseware.com
PartnerWeb
– https://partners.proseware.com
ProductsKB
– https://kb.proseware.com
Teams
– https://teams.proseware.com
Apps
– https://proseware-apps.com
The
SharePoint development team has created a custom web template solution package
named ProseWebTemplate.WSP for provisioning the ProseWeb site collection.
The package includes a custom template named ProseWeb.
An instance of a managed metadata service application has been configured with a
content type hub. Two enterprise content types named Product Document and
Product Image have been published in the content type hub and are available across
all web applications and sites.
All team collaboration site collections for the product development group are
contained in a single content database named sp_content_teams_productdev. The
database has been restored on SQL1, and upgraded by using the database attach
method on the Teams web application. The site collections have not been ungraded.
All team collaboration site collections for the product development group are
referenced under a wildcard managed path at
https://teams.proseware.com/productdev.
The product development marketing team collaboration site is located at
https://teams.proseware.com/productdev/marketing.
The marketing team has made significant customizations to their team collaboration
site by using Microsoft SharePoint Designer.
Business Requirements
The SharePoint 2013 environment must meet the following business requirements:
Due to export and copyright restrictions, SharePoint sites may be accessed only
from within North America.
The ProseWeb site must display a fixed-width page design for desktop browsers,
and a single responsive web design for all mobile devices. The company’s web
designers have prepared two site templates that meet these requirements.
To support the website design layouts, images on the website must be rendered in
one of three standard sizes, specified in pixels: Thumbnail (150 x 150), Catalog (300
x 300), and Detail (500 x 500).
Users must be able to easily copy product-related documents, images, and other
files from any team collaboration site to the ProductsKB site. Metadata on content
must be preserved when moving or copying content between sites.
The product development group’s team collaboration site collections must be
upgraded.
Technical Requirements
You have the following technical requirements:
SQL Server connections must use TCP and port 1488.
Site collection upgrades must be throttled for no more than 20 concurrent upgrades
within any content database, and throttled at 10 concurrent upgrades for any web
application instance.
If a site collection has been customized by using SharePoint Designer:
The site collection upgrade must be performed by a farm administrator.
All customizations must be evaluated and verified before performing the upgrade.
All sandboxed solution code must run on the same server as the original request.
Requests originating from outside the company network must not be routed to any
server running Central Administration.
SPAPP1 and SPAPP2 must not process user requests for site content and pages.
You must deploy the custom web template solution as a full-trust farm solution and
use the ProseWeb template when creating the root site collection for the ProseWeb
web application.
The ProductsKB site must be provisioned by using a Records Center site template.
###EndCaseStudy###
You need to configure the site collection upgrade settings.
Which Windows PowerShell cmdlets should you run?
Which Windows PowerShell cmdlet should you run?
###BeginCaseStudy###
Case Study: 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 Farm
The 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###
Before you upgrade the web application, you need to validate that customizations will
continue to function. Which Windows PowerShell cmdlet should you run?
Which two Windows PowerShell cmdlets should you run?
###BeginCaseStudy###
Case Study: 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 Farm
The 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 comply with the requirements of the legal department. Which two Windows
PowerShell cmdlets should you run? (Each correct answer presents part of the solution.
Choose two.)
Which Windows PowerShell cmdlet should you run?
###BeginCaseStudy###
Case Study: 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 Farm
The 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 ensure that users can edit the appropriate documents by using Office Web
Apps. Which Windows PowerShell cmdlet should you run?
You need to configure authentication for the WebApp1 application pool account
###BeginCaseStudy###
Case Study: 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 Farm
The 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 configure authentication for the WebApp1 application pool account.
What should you do?
Which two service applications should you configure?
HOTSPOT
###BeginCaseStudy###
Case Study: 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 Farm
The 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 are configuring service applications to support access to the company data warehouse.
You need to assign permissions. Which two service applications should you configure? (To
answer, select the appropriate service applications in the answer area.)
You need to configure the required level of access to the SharePoint 2010 farm prior to the migration
###BeginCaseStudy###
Case Study: 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 Farm
The 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 configure the required level of access to the SharePoint 2010 farm prior to the
migration. What should you do?