SPHOL3220: Overview of IT Professional Features in SharePoint Server 2013

Transcription

1 2013 SPHOL3220: Overview of IT Professional Features in SharePoint Server 2013 Hands-On Lab Lab Manual

2 This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes Microsoft. All rights reserved.

3 Contents HOL021: OVERVIEW OF IT PROFESSIONAL FEATURES IN SHAREPOINT SERVER Lab Objectives... 2 Audience... 2 Scenario... 2 Getting Started... 2 Connect to the Lab Environment... 2 Exercise 1 Explore the Central Administration Web Site... 3 Scenario... 3 Task 1 Browsing the Central Administration Web Site... 3 Task 2 Exploring Farm Management... 4 Exercise 2 Create and Configure a SharePoint Site... 6 Scenario... 6 Task 1 Creating a New Site Collection... 6 Task 2 Adding Users and Setting Permissions... 8 Exercise 3 Apply Resource Throttling Scenario Task 1 Configuring Resource Throttling Exercise 4 Health Monitoring Overview Scenario Task 1 Reviewing Health Rule Definitions Task 2 Running Health Checks Task 3 Using the Developer Dashboard Exercise 5 Manage Service Applications Task 1 Exploring SharePoint Service Applications Task 2 Publishing and Consuming SharePoint Services Task 3 Managing Service Application Associations Exercise 6 Use the SharePoint Management Console Scenario Task 1 Exploring the SharePoint 2013 Management Shell Task 2 Using Windows PowerShell to Create a Site Task 3 Using Windows PowerShell to Add Users Summary Page 1

4 Overview of IT Professional Features in SharePoint Server 2013 Estimated time to complete this lab: 60 minutes Lab Objectives The goal for this HOL is to give you an overview of some of the IT Pro features in SharePoint Server After completing this lab, you will be able to: Find your way around the Microsoft SharePoint Server 2013 Central Administration Web site. Use the basic site management tools in SharePoint Server Describe the health monitoring capabilities of SharePoint Server Provide and consume SharePoint Server 2013 service applications. Use commands from the Windows PowerShell command-line interface in the SharePoint Management Console. Audience Scenario SharePoint Site Collection Administrators and SharePoint IT Professionals The objective of this hands-on lab is to introduce you to some of the key features for IT Pros in SharePoint Server SharePoint Server 2013 includes many features that are designed to assist server farm administrators. These include a powerful Central Administration interface, tools to help you manage availability and monitor performance, a flexible service model, and full support for scripting in Windows PowerShell. This lab provides an introduction to these features. Getting Started Connect to the Lab Environment This lab is completed using virtual machines that run on Windows Server 2012 Hyper-V technology. To log on to the virtual machines, press CTRL+ALT+END and enter your logon credentials. Formatted: Font: Bold If necessary, Llog on to the SharePoint (SP) virtual machine (VM) as Administrator, with the credentials CONTOSO\Administrator, pass@word1. After you have logged on to the VM, start Internet Explorer, navigate to the demo home page at and When the VM first starts, there is some indexing and compiling that must complete before the page will load. You may need to try again to load the site. In the lab environment you will already be logged on using the System Account.log on to SharePoint as Administrator with the following credentials: Username: CONTOSO\Administrator Password: pass@word1 Microsoft Confidential Page 2

5 Exercise 1 Explore the Central Administration Web Site Estimated time to complete this exercise: 10 minutes Scenario As with previous versions of SharePoint products and technologies, the Central Administration Web site provides the starting point for all of your day-to-day SharePoint configuration and administration tasks. In this exercise, you will familiarize yourself with the Central Administration interface and the site navigation model, including the Office- style ribbon control. Task 1 Browsing the Central Administration Web Site In this task, you will familiarize yourself with the Central Administration Web site. 1. Launch the Central Administration Web site. To do this, click Start and then click SharePoint 2013 Central Administration. 2. Take a moment to examine the contents and layout of the Central Administration home page. Notice the logical grouping of administrative tasks by functional area. 3. Observe one difference from SharePoint 2010 is that, by default, the ribbon is hidden. Click the PAGE tab. The ribbon appears. Click the BROWSE tab. The ribbon disappears. Microsoft Confidential Page 3

6 4. Click the Application Management heading. Notice how administrative tasks that relate to application management are grouped into logical subheadings. 5. Under Web Applications, click Manage web applications. 6. On the Web Applications Management page, click the intranet.contoso.com row. Notice how the SharePoint ribbon displays a Web Applications tab that contains all of the available administrative tasks for an intranet Web application. 7. Go back to the Central Administration home page. Task 2 Exploring Farm Management In this task, you will explore some of the farm and database management features in SharePoint Server On the Central Administration home page, under click Application Management, and in the Databases section, click Manage content databases. 2. In the Database Name column, click one of the databases listed in the Database Name column. The Manage Content Database Settings page appears 3. Scroll down to the Failover Server section. Microsoft Confidential Page 4

7 For high-availability scenarios, you can use SharePoint Server 2013 with Microsoft SQL Server database mirroring. If you use database mirroring to replicate your content database onto a mirror server, you can specify the name of the mirror server here. In the event that the primary server becomes unresponsive, SharePoint Server 2013 can automatically switch to using the mirror server. 4. Return to the Central Administration home page, and then click the Upgrade and Migration heading. 5. On the Upgrade and Migration page, click Check product and patch installation status. The Manage Patch Status page provides a central location where you can monitor the build version and status of each component in your server farm. 6. Go back to the Upgrade and Migration page, and then click Review database status. Microsoft Confidential Page 5

8 The Manage Databases Upgrade Status page displays status information for each database in the server farm. The status column advises you when a database requires attention. If time permits, explore the other categories on the Central Administration home page. In this exercise, you explored SharePoint s Central Administration Web site, which allows you to configure your environment. You: Learned how to make the SharePoint ribbon appear. Learned the ways you can manage Web applications. Learned ways that you can learn about and manage the farm. Learned how to configure a database for failover. Learned how to determine the status of products and patches. Learned how to determine the status of databases. Exercise 2 Create and Configure a SharePoint Site Estimated time to complete this exercise: 10 minutes Scenario Creating and configuring sites and workspaces lies at the heart of every SharePoint administrator's dayto-day responsibilities. In this exercise, you will create and configure a new top-level SharePoint team site. Task 1 Creating a New Site Collection In this task, you will use the Central Administration interface to create a new SharePoint team site. 1. On the Central Administration home page, under Application Management, Site Collections, click Create site collections. Microsoft Confidential Page 6

9 2. Ensure that the Web Application field is set to If not, click the Web Application drop-down menu, click Change Web Application and click 3. In the Title and Description section, specify a title of My Team Site and type a brief description for the new site. 4. In the Web Site Address section, verify that sites is selected from the drop-down box. In the text box, type team. 5. In the Template Selection section, select 2013 from the Select experience version drop-down box. 6. Select English as the language. 7. In the Template Selection section, on the Collaboration tab, ensure Team Site is selected. 8. In the Primary Site Collection Administrator section, in the User name text box, type CONTOSO\Administrator and then click the Check Names button. The name Administrator should be underlined. 9. Scroll to the bottom of the page, and then click OK. Note that creating the site may take a few minutes. 10. On the Top-Level Site Successfully Created page, click the new site URL to view the Web site. You may want to make a note of the URL. 11. Take a few minutes to explore the new team site layout. 12. Leave the team site browser window open; you will use it in the next task. Microsoft Confidential Page 7

10 Task 2 Adding Users and Setting Permissions In the SharePoint delegated administration model, adding users and configuring permissions on a SharePoint site is the responsibility of the site collection administrator, rather than the farm administrator. As such, you must configure users and groups from the site itself, rather than from the Central Administration Web site. In this task, you will add users and configure permissions on the team site that you created in the previous task. 1. In the upper right corner of the My Team Site page, click the Gear icon. Select Site Settings. 2. In the Users and Permissions section, click Site permissions. The first thing that you should notice is that the SharePoint ribbon displays all of the commands that you need to create and manipulate permissions for users and groups. The second thing that you should notice is that SharePoint has automatically created three groups for your site and assigned default permission levels. The My Team Site Members group is granted the Edit permission level. The My Team Site Owners group is granted the Full Control permission level. The My Team Site Visitors group is granted the Read permission level. 3. On the SharePoint Ribbon, click Permission Levels. The Permission Levels page shows the default permission levels that are available for your site and explains them. Microsoft Confidential Page 8

11 Permission levels are actually groupings of more granular individual permissions. If you require finer control over permissions, you can create your own custom permission levels. You can assign permission levels to SharePoint groups, groups in the Active Directory directory service, or individual users. 4. Go back to the Permissions page by clicking Permissions in the title and then click the My Team Site Members group. 5. On the My Team Site Members page, click the New drop-down menu. In the drop-down box, click Add users to this group. The Share My Team Site dialog box appears. 6. In the Share My Team Site dialog box, in the Share My Team Site text box, add the following users: Katie Jordan Alex Darrow 7. Click Share. 8. The My Team Site Members page appears and shows the new team members. 9. In the upper right corner of the page, click the Gear icon. Click Site settings. The Site Settings page appears. 10. Click Site permissions. A page with the Permissions tab selected appears. Notice that the ribbon is visible. 11. Use the check box to select My Team Site Members. On the SharePoint ribbon, click Edit user permissions. Notice how you can assign any of the permission levels that you saw earlier to the My Team Site Members group. Currently, the Edit checkbox is selected. If you had created custom permission levels, they would also be available for selection here. Microsoft Confidential Page 9

12 12. Click Cancel and you will return to the Permissions page. In this exercise, you created and configured a SharePoint site. You: Created a site collection named team. Reviewed the groups that were created and their permissions. Added users to the site. Reviewed their permissions. Exercise 3 Apply Resource Throttling Estimated time to complete this exercise: 5 minutes Scenario SharePoint Server 2013 includes resource throttling tools that can help you to manage the load on your server farms. By limiting resource-intensive activities, such as database queries against very large lists, you can help to mitigate the resource contention that can cause performance issues during peak times. In this exercise, you will configure and test resource throttling for large lists. Task 1 Configuring Resource Throttling In this task, you will use the Central Administration Web page to configure resource throttling for large lists. Microsoft Confidential Page 10

13 1. Open the browser window that shows the Central Administration Web site. 2. Click the Application Management heading. 3. On the Application Management page, under Web Applications, click Manage web applications. 4. On the Web Applications page, click the intranet.contoso.com row. 5. On the SharePoint Ribbon, on the General Settings drop-down menu, click Resource Throttling. 6. The Resource Throttling page appears. Microsoft Confidential Page 11

14 Database queries against lists that contain over two thousand items become increasingly resource intensive as the number of items in the list rises. You can use these settings to prevent queries that include too many items, and to warn site administrators when the number of items in Microsoft Confidential Page 12

15 a list approaches this threshold. You can also permit larger database queries at certain times of day, such as during off-peak hours. 7. Scroll down to the Daily Time Window for Large Queries section. Select Enable a daily time window for large queries. 8. Set the Start time to 7 P.M. and the Duration to 12 hours. 9. Scroll down to the HTTP Request Monitoring and Throttling section. Formatted: Font: Bold The HTTP request throttling job is enabled by default. When front-end Web servers experience high load, low-priority requests such as requests from the search indexing service are rejected until the server load falls back to manageable levels. 10. Review the other sections on the Resource Throttling page, and then click OK. 11. Close all open browserthe Resource Throttling windows. In this exercise you learned how to configure resource throttling, which helps you to manage workloads. You learned where the resource throttling tools are located, and how to select a time frame when it is acceptable to handle large queries. Exercise 4 Health Monitoring Overview Estimated time to complete this exercise: 10 minutes Scenario SharePoint Server 2013 includes some powerful new features to help you monitor performance and identify problems in your SharePoint server farms. In this exercise, you will review health rule definitions, run a health check on your site collection, and enable the developer dashboard. Microsoft Confidential Page 13

16 Task 1 Reviewing Health Rule Definitions SharePoint Server 2013 uses a rule-based health analyzer to identify performance, security, configuration, and availability issues in your SharePoint environment. In this task, you will study the rule definitions and learn how to review problems that the health analyzer has identified. 1. Launch Switch to the Central Administration Web site. 2. On the Central Administration home page, click the Monitoring heading. The Monitoring page appears. 3. Under Health Analyzer, click Review rule definitions. The Health Analyzer Rule Definitions page appears. The Health Rule Definitions list shows the rules that the SharePoint Server 2013 health analyzer uses to identify potential issues in your server farm. The health analyzer checks each rule on an hourly, daily, weekly, monthly, or on-demand basis according to the Schedule field. Notice that some rules are set to repair automatically. For example, if the health analyzer detects that databases that SharePoint uses have fragmented indices, it will automatically attempt to defragment the database index. 4. In the Security category, select the fourth rule: The server farm account should not be used for other services. 5. On the SharePoint ribbon, click the Items Tab, then Click Edit Item. 6. Notice that you can change various rule settings. For example, you can clear the Enabled check box to prevent the health analyzer from checking against this rule. Microsoft Confidential Page 14

17 7. On the SharePoint Ribbon, cclick Cancel to return to the Health Analyzer Rule Definitions page. 8. Go back to the Monitoring page, and under Health Analyzer, click Review problems and solutions. The Review problems and solutions page reports on issues that the health analyzer has identified, according to the health rule definitions that you reviewed previously. 9. In the Configuration category, click one of the list items. Notice how you are presented with a page that provides a detailed explanation of the problem, together with a description of the action that is required to remedy it. 10. Return to the Monitoring page. Task 2 Running Health Checks The Site Collection Health Checks tool uses a set of rules to see if there are any issues with the sites in a site collection. For example, it checks for missing site templates. You run the health checks manually Microsoft Confidential Page 15

18 to prepare for an upgrade. In addition, the health checks are run automatically in repair mode when you start to upgrade a site collection. You can also run the health checks at any time to verify that a site is working as expected. In this task, you will learn how to run a health check. 1. Open the My Team Site home page at Click the Gear icon in the upper right corner and click Site settings. 2. In the Site Collection Administration section, click Site collection health checks. The Site Collection Heath Checks page appears. 3. Click the Start checks button. 4. You will see a screen that says Clean bill of health and that lists the checks that were run. Task 3 Using the Developer Dashboard The Developer Dashboard enables IT Pros and developers to troubleshoot problems with individual pages. Here are some of its capabilities: A breakdown of the request/response cycle with timings for each operation. Microsoft Confidential Page 16

19 A breakdown of the response times for each database query that the rendering process triggers. A breakdown of the load times for each Web Part on the page. Detailed request information per page with chart views. A dedicated tab for ULS log entries for particular request. Additional detailed information included for request analyzing, such as being able to see how individual queries to a SQL Server database perform. You enable the Developer Dashboard with four PowerShell commands. 5. You must launch the SharePoint 2013 Management Shell with Administrative privileges. Click Start, point to SharePoint 2013 Management Shell, and then click Run as Administrator. 6. In the SharePoint 2013 Management Shell, at the PS C:\Users\Administrator.CONTOSO> prompt, type the following command, and then press ENTER. $content = ([Microsoft.SharePoint.Administration.SPWebService]::ContentService) This command creates an instance of the content service object. 7. At the PS C:\Users\Administrator.CONTOSO> prompt, type the following command, and then press ENTER. $appsetting =$content.developerdashboardsettings This command retrieves an instance of the Developer Dashboard settings. 8. At the PS C:\Users\Administrator.CONTOSO> prompt, type the following command, and then press ENTER. $appsetting.displaylevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::On This command sets the display level to ON, which means that the Developer Dashboard is enabled and its icon will be displayed in the top-right corner of the browser. 9. At the PS C:\Users\Administrator.CONTOSO> prompt, type the following command, and then press ENTER. $appsetting.update() This command updates and saves the settings so that they are available to the content service object. 10. Refresh the My Team Site browser page at You should see the Developer Dashboard icon in the upper right corner of the browser. Microsoft Confidential Page 17

20 11. Click the icon. The Developer Dashboard should open as a new window in the browser. 12. Take some time to explore the Developer Dashboard. 13. Close the Developer Dashboard. In this exercise, you learned how to determine the health of your site and how to enable and display the Developer Dashboard. You did this by: Microsoft Confidential Page 18

21 Learning how to view the rules that are used to determine the health of your site. Learning how to edit existing rules. Learning how to review any problems and get detailed information about them. Learning how to run health checks. Learning the PowerShell commands to enable the Developer Dashboard. Learning how to open the Developer Dashboard. Exercise 5 Manage Service Applications Estimated time to complete this exercise: 10 minutes Scenario SharePoint Server 2013 provides a powerful and flexible services model. You can configure, share, and consume services at a granular level. Task 1 Exploring SharePoint Service Applications In this task, you will gain an overview of how to view and manage service applications. 1. Switch to the Central Administration website On the Central Administration home page, click the Application Management heading On the Application Management page, under Service Applications, click Manage service applications. Formatted: Not Expanded by / Condensed by The Manage Service Applications page lists the SharePoint service applications that are configured in the farm. All services are started by default. Note that, for most services, there is a corresponding proxy service that enables you to consume services that are provided either locally or remotely Select the Access Services row (not the hyperlink). On the SharePoint ribbon, make sure the Service Applications tab is selected. The SharePoint ribbon displays all of the commands that you need to manage the selected service instance: The Manage button opens the settings page for the selected service. The Administrators button enables you to grant management permissions for the selected service to specific accounts, groups, or claims. Microsoft Confidential Page 19

22 The Publish button enables you to make the selected service available to other SharePoint server farms. The Connect button enables you to consume a service application that an external server farm provides On the SharePoint Ribbon, click New. The New drop-down menu displays all of the service types for which you can create new instances. The services model is extensible, so third-party solution developers can create additional services that you can make available in your server farms. You can create more than one instance of each service type if required, for example, if you want to provide differently configured service instances to different Web applications. Task 2 Publishing and Consuming SharePoint Services In SharePoint Server 2013, you can make individual services available to other server farms, and you can consume individual services from external server farms. 1. On the Manage Service Applications page, ensure that the Business Data Connectivity Service row is selected. 2. On the SharePoint ribbon, on the Service Applications tab, click Publish. 3. In the Publish Service Application dialog box, make sure that the Publish this Service Application to other farms check box is selected, and then click OK. This makes the Business Data Connectivity Service instance available to other SharePoint server farms on your network. This page also displays the URL at which the service is published. Note that you can also provide a description of the service and a help page URL to assist farm administrators who want to consume this service. To connect to a published service from another SharePoint server farm, you must use the Connect tool on the SharePoint Ribbon. 4. On the SharePoint Ribbon, on the Service Applications tab, on the drop-down menu below the Connect button, select Business Data Connectivity Service. 5. In the Connect to a Remote Service Application dialog box, in the Farm or Service Application address box, type the following URL: sp:32844/topology/topology.svc. Click OK. The connection wizard searches for Business Data Connectivity instances that are published on the URL that you specified. 6. The Connect to a Remote Service Application dialog box appears. Business Data Connectivity Service should appear in the name column. Click on that row. 7. Make sure that the Add this service application s proxy to the farm s default proxy list is selected. 8. Click OK. 9. In the Connect to a Remote Service Application dialog box, give the service proxy a unique name, and then click OK. Formatted: Font: Bold Microsoft Confidential Page 20

23 10. At this point, you should receive a message informing you that SharePoint Server 2013 has successfully connected to a remote service application (although in this case the service is not actually remote). Click OK. When you make a service application available to Web applications, you must assign the required permissions to the service accounts of each Web application. You can do this by selecting the service, such as the Business Data Connectivity Service, and using the Permissions button on the SharePoint ribbon. Task 3 Managing Service Application Associations As an administrator, it is important that you can control which service applications are available to each Web application in your server farm. In SharePoint Server 2013, you can select whether each individual service application is available to sites within a specific Web application. 1. On the Central Administration home page, click the Application Management heading. 2. On the Application Management page, under Web Applications, click Manage web applications. 3. On the Web Applications Management page, select the intranet.contoso.com row. 4. On the SharePoint ribbon, click Service Connections. 5. In the Configure Service Application Associations dialog box, in the Edit the following group of associations list, click [custom]. 6. Note that you can select which service proxies the Web application is permitted to consume. 7. Scroll down and Cclick Cancel to close the window. In this exercise, you learned about SharePoint service applications. You did this by: Using Central Administration to learn the different ways to create and manage a service application. Using Central Administration to publish a service. Using Central Administration to connect to a service. Using Central Administration to select the service proxy a Web application can use. Exercise 6 Use the SharePoint Management Console Estimated time to complete this exercise: 15 minutes Scenario Windows PowerShell is a powerful interactive scripting environment, and SharePoint Server 2013 takes full advantage of this. The SharePoint Management Console is a Windows PowerShell environment that you can use to script time-consuming administrative tasks. In this exercise, you will experiment with some simple Windows PowerShell commands (known as cmdlets) for SharePoint Server Microsoft Confidential Page 21

24 Task 1 Exploring the SharePoint 2013 Management Shell In this task, you will familiarize yourself with the SharePoint 2010 Management Shell and learn how to get help on Windows PowerShell commands. 1. On the Start menu, point to All Programs, Microsoft SharePoint 2013 Products, click SharePoint 2013 Management Shell, and then click Run as Administrator. 2. Wait for the PS> C:\Users\Administrator.CONTOSO> prompt to appear, type the following command, and then press ENTER. get-command pssnapin "Microsoft.SharePoint.PowerShell" more This command displays all of the available cmdlets in the Microsoft.SharePoint.PowerShell namespace. Press the SPACEBAR to page down the list. Notice that there are hundreds of cmdlets that relate to a broad range of administrative tasks. To get detailed help and information on a particular cmdlet, you can use the get-help <cmdletname> -detailed command. 3. Type the following command, and then press ENTER. get-help Get-SPSite detailed The console window displays detailed information about how to use the Get-SPSite cmdlet. As you might have guessed, cmdlets that include the Get prefix return information. You can use these cmdlets to write information to the console, or to provide information to other cmdlets. 4. Type the following command, and then press ENTER. Get-SPSite The console window displays the URL of each site collection in the server farm (excluding the Central Administration site collection) and each site collection s compatibility level. Microsoft Confidential Page 22

25 Task 2 Using Windows PowerShell to Create a Site In this task, you will use the SharePoint 2013 Management Shell to create a new top-level team site. 5. Type the following command, and then press ENTER. get-help New-SPSite -detailed The console window displays detailed information about the various parameters of the New- SPSite cmdlet. In this task, you will specify: The URL at which the site should be created. The owner of the site. The name of the site. The site template on which the site should be based. To specify the site template, you need to provide the internal name of the template. You can use the Get-SPWebTemplate cmdlet to retrieve the internal names of all of the available site templates. 6. Type the following command and then press ENTER. Get-SPWebTemplate The console window displays a list of all of the available site templates. For this task, you will create a team site. The internal name for the team site template is STS#0. 7. Type the following command, and then press ENTER. New-SPSite Url " OwnerAlias "CONTOSO\Administrator" Name "PowerShell Site" -Template "STS#0" 8. This command may take a few moments. When it returns, it displays the URL of the new site and its compatibility level. Microsoft Confidential Page 23

26 9. Open a browser window and browse to Verify that the new team site was created successfully. Task 3 Using Windows PowerShell to Add Users In this task, you will use the SharePoint 2013 Management Shell to add users to your new top-level team site. 1. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER. get-help New-SPUser -detailed The console window displays detailed information about the various parameters of the New- SPUser cmdlet. In this task, you will specify: The alias of the users. Microsoft Confidential Page 24

27 The URL of the site to which the users will be added. The permission level that will be granted to users. 2. Type the following command, and then press ENTER. New-SPUser UserAlias "CONTOSO\garthf" Web " PermissionLevel "Contribute" The prompt returns with the user login and the display name. 3. Type the following command, and then press ENTER. New-SPUser UserAlias "CONTOSO\alexd" Web " PermissionLevel "Read" The prompt again returns with the user login and the display name. 4. Open a browser window and browse to 5. Click the Gear icon in the top right corner. Select Site Settings. In the Users and Permissions section, click Site permissions. 6. Verify that Garth Forth and Alex Darrow have been given appropriate permissions on the site. Microsoft Confidential Page 25

28 If you would like to learn more about Windows PowerShell, see HOL023 Introduction to Windows PowerShell with SharePoint Server In this exercise, you learned how to use the SharePoint Management Console to enter PowerShell cmdlets. You learned how to: Get information about which commands are available. Get information about a specific command. Get information about existing sites. Use commands to create sites. Use commands to add users to sites. Summary This lab provided a brief tour of some of the features for IT Professionals in SharePoint Server In particular, the lab explored: The new Central Administration Web site layout. The site creation and management processes. Resource throttling. The health monitoring tools and features. The service model. The SharePoint 2013 Management Shell and the use of Windows PowerShell to perform administrative tasks. Microsoft Confidential Page 26