Managing exchange server 2013
- 1. Microsoft® Official Course Module 1 Deploying and Managing Microsoft® Exchange Server 2013
- 2. Module Overview • Exchange Server 2013 Prerequisites and Requirements • Exchange Server 2013 Deployment • Managing Exchange Server 2013
- 3. Managing Exchange Server 2013
- 4. Lesson 3: Managing Exchange Server 2013 • Managing Exchange Server 2013 • What Is EAC? • Managing User Mailbox Properties with Outlook Web App • What Is Windows PowerShell? • Windows PowerShell Syntax • Accessing Help in Windows PowerShell • What Is Exchange Management Shell? • Exchange Management Shell Administration Examples • Demonstration: Using Exchange Administration Tools to Manage Exchange
- 5. Managing Exchange Server 2013 Methods for Exchange Server 2013 management: • Exchange Administration Center • Outlook Web App options • Exchange Management Shell
- 6. What Is EAC?
- 7. Managing User Mailbox Properties with Outlook Web App • Users can manage the following features by using Outlook Web App: • Outlook Web App settings • Manage inbox rules • Message tracking • Manage site mailboxes • Manage mobile devices • Manage text messaging • Group memberships • Recover deleted messages • Block and allow lists • Change their password • Manage apps
- 9. What Is Windows PowerShell? • PowerShell is an object-based management environment • PowerShell is an engine that enables administrators to: • Create automation scripts • Perform batch modifications • Access unavailable settings • PowerShell provides a foundation upon which the GUI-based administrative tools of Microsoft can rest: • Actions can be accomplished in its command-line console • Actions can be invoked within GUIs by running PowerShell commands in the background
- 10. Windows PowerShell Syntax • Cmdlet names are a pairing of verbs and nouns, such as: • Use cmdlet parameters to modify actions and provide configuration information. Parameters include: • Named. -EventLog System, -UserName John • Switch. -Verbose, -Debug, -Confirm • Positional. • Get-EventLog System • Get-EventLog –LogName System • Common parameters: -WhatIf, -Debug, -Verbose, -Confirm Verb Noun Cmdlet Get EventLog Get-EventLog Set ExecutionPolicy Set-ExecutionPolicy New VM New-VM
- 11. Accessing Help in Windows PowerShell • To access the Help documentation, run Get-Help, followed by the cmdlet name, or run the cmdlet name, followed by the –help parameter: • Get-Help has parameters to adjust the amount of help displayed. These parameters include: • -detailed • -examples • -full • -online • Other cmdlets that you can use for accessing help include Update-Help, Show-Command, Get-Command, and tab completion Get-Help Get-EventLog Get-EventLog -help
- 13. What Is Exchange Management Shell? • Exchange Management Shell is a command-line interface for administering Exchange Server 2013 • Exchange Management Shell includes the following features: • Provides more than several hundred cmdlets for Exchange Server 2013 administration • Offers an extensible scripting engine • Applies RBAC permissions
- 14. Exchange Management Shell Administration Examples • Enable-Mailbox -Identity adatumBart • New-MailboxExportRequest -Mailbox Bart –FilePath LON-EX1 PSTFileShareBart_Mailbox.pst • Get-MailboxStatistics -Database MailboxDatabase • New-MailboxDatabase -Name MailboxDatabase -Server LON-Ex1 • Get-ExchangeServer -Status | Format-List • New-DynamicDistributionGroup -Name DDG -Alias DDGAlias - OrganizationalUnit OU -IncludedRecipients MailboxUsers • New-MoveRequest -Identity 'user1'-TargetDatabase Executives
- 15. Demonstration: Using Exchange Administration Tools to Manage Exchange In this demonstration, you will see how Exchange Administration Tools are used to manage Exchange Server 2013
- 16. Lab: Deploying and Managing Exchange Server 2013 • Exercise 1: Evaluating Requirements and Prerequisites for an Exchange Server 2013 Installation • Exercise 2: Deploying Exchange Server 2013 • Exercise 3: Managing Exchange Server 2013 Logon Information Estimated time: 60 minutes Virtual Machines: 20341B-LON-DC1-B 20341B-LON-EX1-B User Name: AdatumAdministrator Password: Pa$$w0rd
Editor's Notes
- #2: Presentation: 120 minutes Lab: 60 minutes After completing this module, students will be able to: Understand Microsoft® Exchange Server 2013 prerequisites and requirements. Understand Exchange Server 2013 deployment. Manage Exchange Server 2013. Required materials To teach this module, you need the Microsoft® Office PowerPoint® file 20341B_01.pptx. Important: We recommend that you use Microsoft Office PowerPoint 2007 or a newer version to display the slides for this course. If you use PowerPoint Viewer or an earlier version of Office PowerPoint, all the features of the slides might not display correctly. Preparation tasks To prepare for this module: Read all of the materials for this module. Practice performing the demonstrations. Practice performing the labs. Work through the Module Review and Takeaways section, and determine how you will use this section to reinforce student learning and promote knowledge transfer to on-the-job performance. As you prepare for this class, it is imperative that you complete the labs yourself so that you understand how they work and the concepts that are covered in each. This will allow you to provide meaningful hints to students who may get stuck in a lab, and it also will help guide your lecture to ensure that you cover the concepts that the labs cover.
- #6: Introduce management techniques for Exchange Server 2013. Do not go into much detail at this point, as these topics are discussed later.
- #7: Describe the Exchange Administration Center (EAC). Explain that the EAC replaces both the EMC and ECP in Exchange Server 2010. Discuss the purpose of each node in the left pane, but do not go into technical details, as these nodes will be used for Exchange administration throughout the remainder of this course.
- #8: Discuss what users can do by using Outlook Web App interface.
- #10: Discuss Windows PowerShell with the students. If some of the students are familiar with other scripting technologies, such as VBScript, you can discuss with the class what kinds of scripts or tasks they are currently using or have used in the past. It is important to emphasize that Windows PowerShell is more than just a command line to perform specific tasks. Remind the students that Windows PowerShell can manage Windows Server roles and features, and it can be used to provision, manage, and report on various objects, directories, and components.
- #11: Discuss that cmdlets are named with a verb-noun combination. Discuss some common verbs, such as Get, Set, New, Add, and Remove. Explain that Windows PowerShell standards ensure that many of the cmdlets have intuitive names. Provide students with examples of tasks to complete, and determine whether they are able to identify the appropriate cmdlet. Make sure that the students understand what parameters are and how to use them. The students should understand the differences between the parameters to be able to complete the lab and to improve their Windows PowerShell skills after the course. Make sure that you emphasize the correct syntax for typing cmdlets with their parameters and values. Most command-line languages require that the correct syntax be typed, and Windows PowerShell is not an exception. Discuss what each kind of parameter is and when you might use them.
- #12: Whether the students are new to Windows PowerShell or are very experienced with it, at some point they must review the documentation for a cmdlet. Stress to the students that reading the Help information is important because it explains the detailed usage of each cmdlet. Explain how to obtain help by using Get-Help or by using the –help parameter. Remind students that they can even run the cmdlet with the –help parameter to get help. Discuss use of the Get-Help parameters, ‑full, ‑example, ‑detailed, and –online, to obtain varying levels of detail. In Windows PowerShell 3.0, a new cmdlet of Update-Help also downloads the latest help information to the local server.
- #14: Lead a class discussion about Exchange Management Shell. Discuss how Exchange Management Shell and Exchange Management Console run on top of Windows PowerShell 3.0, and how Exchange Management Shell uses the Windows PowerShell Remoting feature. Discuss the fact that cmdlets are typically designed around a repetitive administrative task, and that Exchange Management Shell provides more than 700 cmdlets for Exchange Server-specific management tasks. These cmdlets are in addition to the non-Exchange Server system cmdlets included in the basic Windows PowerShell shell design. Make sure that the students understand that Windows PowerShell is more than just a command-line interface; it also provides a comprehensive scripting engine that you can automate with programs.
- #15: Provide some tips and tricks that show the students how they can more efficiently use Exchange Management Shell. Then discuss each provided example.
- #16: Revert all virtual machines at the conclusion of the demonstration. Preparation Steps To perform this demonstration, you need to start the 20341B-LON-DC1-B and 20341B-LON-EX1-B virtual machines. Sign in to both virtual machines as Adatum\Administrator with the password Pa$$w0rd. You must also have performed all other demonstrations in this module. Note: If previous demonstration is not completed, and Exchange Server 2013 is not installed on LON-EX1-B, you can choose to perform this demo with LON-DC1, LON-CAS1, and LON-MBX1 machines. Demonstration Steps On LON-EX1, from the Start screen, open Internet Explorer. In the Address bar, type https://lon-ex1.adatum.com/ecp, and then press Enter. On the Exchange Admin Center page, sign in as Adatum\Administrator with the password Pa$$w0rd. On the subsequent Exchange Admin Center page, click save. Review the options in the EAC. In the EAC console, click recipients in the left pane, and then click mailboxes in the central pane. Click the + sign and then click User mailbox. In the new user mailbox window, select Existing user and then click browse. In the Select User – Entire Forest window, select Aidan Delaney, and click ok. In the Alias text box, type AidanD, and click save. Make sure that Aidan Delaney appears in the list of mailboxes. In the top right corner of the EAC console, click Administrator and then click Sign out. In Internet Explorer, in the address bar, type https://lon-ex1.adatum.com/owa and then press Enter.
- #17: Make sure that the students start B version of LON-DC1 and LON-EX1 machines, as other VMs already have Exchange Server 2013 installed. In some cases, students may not be able to send messages after installing Exchange Server 2013. Students may notice that when they send messages, the messages stay in the Drafts folder in Outlook Web App. Provide the following troubleshooting steps if students experience this issue: On LON-EX1, open the Exchange Management Shell. Type Test-ServiceHealth, and press Enter. Verify that all required services are running. If the services are not running, start them. Type Restart-Service MSExchangeSubmission, and press Enter. Type Restart-Service MSExchangeDelivery, and press Enter. Check to see if the message has been delivered. If not, type Restart-Service MSExchangeTransport, and press Enter. Check to see if the message has been delivered. If the messages are still not being delivered, restart the Microsoft Exchange Active Directory Topology service from the Services console. Restart all dependent services. Verify that all services set to Automatic start are started. Check to see if the message has been delivered. Exercise 1: Evaluating Requirements and Prerequisites for an Exchange Server 2013 Installation The Active Directory administrators at A. Datum have prepared a test AD DS environment for the Exchange Server 2013 deployment. The server administration team has deployed a Windows Server 2012 server that you can use to deploy the first Exchange Server 2013 server in the test organization. You must verify that the Active Directory environment and the server meet all prerequisites for installing Exchange Server 2013. Exercise 2: Deploying Exchange Server 2013 After evaluating the Exchange Server 2013 requirements, you are ready to begin the deployment process. You must first prepare AD DS, and then perform a single server Exchange installation. For evaluation purposes, all roles will be installed on a single server. At the end, you will verify whether the core Exchange services and components are installed correctly.