###BeginCaseStudy###
Topic 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 front-end 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:
o ProseWeb – https://www.proseware.com
o PartnerWeb – https://partners.proseware.com
o ProductsKB – https://kb.proseware.com
o Teams – https://teams.proseware.com
o 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:
o The site collection upgrade must be performed by a farm administrator.
o 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 SendTo connection.
Which URL should you specify?
A.
https://kb.proseware.com/dropofflibrary
B.
https://kb.proseware.com/_vti_bin/officialfile.asmx
C.
https://teams.proseware.com/_vti_bin/copy.asmx
D.
https://teams.proseware.com/_vti_bin/officialfile.asmx
Explanation:
Scenario:
The ProductsKB site must be provisioned by using a Records Center site template.
ProductsKB – https://kb.proseware.com
We should append _vti_bin/officialfile.asmx as a default to the URL.Reference: SharePoint 2010 Document Center Send To Connection Setup Walkthrough