1598 Mailserver i Windows organisation Agenda
Contents
1598 Mailserver i Windows organisation Agenda
Målepind
- Eleven opnår et fagligt niveau minimum svarende til MCP Implementing and Managing Exchange Server 2003 eller nyere
- Eleven kan installere en eller flere mailservere i et Windows Domæne
- Eleven kan installere en mailserver i et cluster
- Eleven kan installere en mailserver i et front-end/back-end system
- Eleven kan administrere brugerkonti for mailserveren
- Eleven kan konfigurere sikkerhed for mailserveren
- Eleven kan lave backup og restore af dele af mailserveren
- Eleven kan lave en disaster recovery af hele mailserveren
- Eleven kan oprette delte mapper på mailserveren
Materiale
Agenda
- Introduktion
- Installation af Exchange 2013
- Mailbox rollen
- Client Access rollen
- Client Connectivity
- Message Transport
- Afslutning
Dag1
- Introduktion
- Exchange server infrastructure
- Læs om systemkrav og installation
- Installation af Exchange 2013
Review Question(s)
Question: Which server role in Exchange Server 2013 handles the message transport?
Question: How do Outlook clients from an internal network connect to Exchange Server 2013?
Question: On what is the EAC built?
Tools
EAC
Exchange Management Shell
Dag2
- Mailbox rollen
- Læs om Mailbox rollen
Tools
Exchange Mailbox Server Role Calculator
Exchange Administration Center
Exchange Management Shell (EMS)
Useful EMS cmdlets include:
- New-MailboxDatabase<math></math>
- Get-MailboxDatabase
- Set-MailboxDatabase
- Move-DatabasePath
Review Question(s)
Question: Why would you choose to use SATA drives instead of a SAN or small computer system interface (SCSI) drives for your Mailbox servers?
Question: Your organization needs to determine which storage solution to deploy for the new Exchange Server 2013 messaging environment. What information should you consider when selecting the hardware?
Dag3
- Client Access rollen
- Læs om Client Access rollen.
To enable access to the Client Access server from the Internet, you need to complete the following steps:
*Configure the external URLs for each of the required client options. You can configure all of the Client Access server web server-based features with an external URL. This URL is used to access the website from external locations.
By default, the external URL is blank. For Internet-facing Client Access servers, the external URL should be configured to use the name published in DNS for that Active Directory site. The external URL also should use the same name that is used for the server certificate. For Client Access servers that will not have an Internet presence, the setting should remain blank.
*Configure external DNS name resolution. For each Client Access server that you are exposing to the Internet, you must verify that the host name can be resolved on the Internet. To do this, add a host record for the Client Access server to the DNS zone on the DNS server that hosts the Internet DNS zone for your organization. If you are using different host names for each Client Access server, then you must configure a host record for each host. *Configure access to the Client Access server virtual directories. Each of the client access methods uses a different virtual directory. If you are using a standard firewall or application-layer firewall that filters client requests based on the virtual directory, you need to ensure that all virtual directories are accessible through the firewall. *Implement SSL certificates with multiple subject alternative names. If you are using multiple host names for the Client Access services, or if you are publishing Autodiscover to the Internet, then ensure that the SSL certificates that you deploy on each Client Access server have the required server names listed in the subject alternative name extension. *Plan for Client Access server access with multiple sites. If your organization has multiple locations and Active Directory sites, and you are deploying Exchange Servers in each site, your first decision is whether you will make the Client Access servers in each site accessible from the Internet. If you choose not to make the Exchange Servers in specific sites accessible from the Internet, you should not configure an external URL. All client requests to that server can be used as a proxy from an Internet-accessible Client Access server. If you do decide to make a site’s Client Access server accessible from the Internet, you need to complete the steps listed below for each site.
Configure a unique external URL for the Client Access servers that are accessible from the Internet. Ensure that the host records for each site are added to the appropriate DNS zone. Configure the firewalls and SSL certificates for each site.
Configuring POP3 and IMAP4 Client Access
You can use the services console to do this, or you can use Exchange Management Shell. To use Exchange Management Shell, on the computer running the Client Access server role, you should run the following cmdlets:
Set-service msExchangePOP3 -startuptype automatic Start-service msExchangePOP3 On the computer running the Mailbox server role, you should run the following cmdlets Set-service msExchangePOP34BE -startuptype automatic Start-service msExchangePOP3BE
Dag4
- Client Connectivity
- Læs om High Availability.
- Message Transport
- Læs om Backup og restore.
Dag5
- Evaluering af projektarbejde
- Teoretisk prøve
- Afslutning