A guide to Microsoft Exchange server provides information on such topics as configuring Exchange clients, setting up mailboxes, using public folders, and performing backups and recovery.
Provides information about such topics as how to manage workstations and servers, how to control access to files and shared network resources, how to configure DNS, and how to protect data.
Portable and precise, this pocket-sized guide delivers ready answers for administering your Server Core installation. This eBook includes the following formats, accessible from your Account page after purchase:. EPUB The open industry format known for its reflowable content and usability on supported mobile devices. PDF The popular standard, which reproduces the look and layout of the printed page.
This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours. A reporting infrastructure produces reports for us and usually lets us design new reports. You might decide to broaden this scope in various ways—such as to include matters relating to the database s But with options flooding the market and updates and add-ons coming at a rapid pace, determining what you require now, and in the future, can be a tall task.
As these database icons begin to proliferate, they can be organized logically via the userdefined tabs that run across the top of the interface. It's entirely up to the user which database icons reside on the desktop and how they are When you change the product key on an Edge Transport server, you must resubscribe the server in the Exchange organization to apply the change.
Additionally, you cannot use product keys to downgrade editions. To downgrade editions, you must uninstall Exchange Server and then reinstall Exchange Server. Microsoft offers on-premise and online implementations of Exchange Server.
An on- premises Exchange Server is one that you install in your organization. An online Exchange Server is delivered as a subscription service from Microsoft. Note The full installation option of Windows Server is required for all Exchange servers. Exchange Server requires Microsoft Management Console 3. NET Framework version 3.
Other prerequisites are role-specific and discussed in Chapter 2. As WinRM 2. You can verify the availability of WinRM 2. The WinRM service is configured for manual startup by default. You must change the startup type to Automatic and start the service on each computer you want to work with.
To configure Windows PowerShell for remoting, enter the following command: Enable-PSRemoting —force In many cases, you will be able to work with remote computers in other domains. However, if the remote computer is not in a trusted domain, the remote computer might not be able to authenticate your credentials.
To enable authentication, you need to add the remote computer to the list of trusted hosts for the local computer in WinRM. If you cannot connect to a remote host, verify that the service on the remote host is running and is accepting requests by running the following command on the remote host: winrm quickconfig This command analyzes and configures the WinRM service.
When this process completes, WinRM should be set up correctly. When starting PowerShell from another program, such as the command prompt cmd. Exchange Server uses the Windows Installer and has a fully integrated installation process. This means you can configure Exchange Server much like you can any other application you install on the operating system. The installation can be performed remotely from a command shell as well as locally.
Chapter 2 provides detailed instructions for installing Exchange Server With an initial installation, Windows Installer will first check the system configuration to determine the status of required services and components, which include checking the Active Directory configuration and the availability of components, such as IIS Internet Information Server , as well as operating system service packs, installation permissions for the default install path, memory, and hardware.
After checking the system configuration, the installer allows you to select the roles to install. Whether you use the Standard or Enterprise Edition, you have similar options. Generally, you will not want an internal Exchange server to also be configured as a domain controller with a global catalog.
Note For details on how the various server roles are used, see Chapter 2, which also provides guidelines for sizing and positioning the various server roles. Edge Transport servers are not members of the Active Directory forest and are not configured on domain controllers. Spam can be automatically deleted, quarantined, or filed as junk e-mail. Tip Using the Exchange Server management tools, administrators can manage messages sent to the quarantine mailbox and take appropriate actions, such as deleting messages, flagging them as false positives, or allowing them to be delivered as junk e-mail.
Messages delivered as junk e-mail are converted to plain text to strip out any potential viruses they might contain. This server can then perform recipient lookups on incoming messages and block messages that are for nonexistent users.
A sender can then be added temporarily to the Blocked Senders list. Although these antivirus and antispam features are fairly extensive, they are not comprehensive in scope. Forefront Security for Exchange Server helps protect Exchange servers from viruses, worms, and other malware using multiple antivirus scan engines and file filtering capabilities.
Forefront Security provides distributed protection for Exchange servers with the Mailbox server, Hub Transport server, and Edge Transport server roles. Although you can install Forefront Security on Exchange servers with these roles to gain substantial antivirus protection, you do not need to install Forefront Security on Exchange servers with only the Client Access Server or Unified Messaging Server role.
You can use the Forefront Security Setup program to install the server and management components. These modifications include new system services, integrated authentication, and new security groups.
Table provides a summary of key services, how they are used, and with which server components they are associated. If this Transport, Directory service is stopped, most Exchange servers Mailbox, Topology will not be able to start. This includes mailbox Information stores and public folder stores. Submission Microsoft Manages assistants that are responsible for Mailbox Exchange calendar updates and booking resources.
Mailbox Assistants Microsoft Provides support for monitoring and Exchange diagnostics. Microsoft Provides secure host for Exchange Server Exchange services.
Indexer Microsoft Provides a host for essential Exchange Exchange services. If this service is Messaging Speech Engine stopped, speech recognition services will not be available to Unified Messaging clients.
Ensures that Forefront Controller initializes properly with the information store. Controller starts and stops scan jobs and applies engine updates. Microsoft Processes incidents and manages Forefront Forefront Server quarantine logging, performance logging Security Security and notifications.
Web Enables remote and delegated Client Access Management management for the web server, sites and Service applications.
Services Exchange Server Authentication and Security In Exchange Server , e-mail addresses, distribution groups, and other directory resources are stored in the directory database provided by Active Directory. Active Directory is a directory service running on Windows domain controllers.
When there are multiple domain controllers, the controllers automatically replicate directory data with each other using a multimaster replication model. This model allows any domain controller to process directory changes and then replicate those changes to other domain controllers. The first time you install Exchange Server in a Windows domain, the installation process updates and extends Active Directory to include objects and attributes used by Exchange Server You perform these tasks in the Exchange Management Console only.
Exchange Server fully supports the Windows Server security model and relies on this security mechanism to control access to directory resources. For example, to add a user to a distribution group, you simply make the user a member of the distribution group in Active Directory Users And Computers.
Every Exchange mailbox must be associated with a domain account—even those used by Exchange for general messaging tasks. In the Exchange Management Console, you can create a new user account as part of the process of creating a new mailbox.
Note To support coexistence with Exchange Server and Exchange Server , all Exchange Server servers are automatically added to a single administrative group when you install Exchange Server Instead, you manage Exchange servers according to their roles and the type of information you want to manage using the Exchange Management Console.
When you add an administrator to one of these security groups, the administrator inherits the permissions permitted by that role.
As a result of these changes, all storage group functionality has been moved to the database level. This group is used to apply Password Setting objects to all hosted mailboxes. This group is used to apply RBAC self-service permissions to mailboxes. This group allows Exchange servers to work together.
Members of this group have permission to read and modify all Exchange configuration settings as well as user accounts and groups. Members of this group have permission to read and modify user accounts and groups. Exchange Server and Exchange Server bridgehead servers must be made members of this group to allow proper mail flow in the organization. For more information on interoperability, see Chapter 2.
Not only does Exchange Server store information in Active Directory, but it also uses the Active Directory routing topology to determine how to route messages within the organization. Routing to and from the organization is handled using transport servers. Understanding How Exchange Stores Information Exchange stores four types of data in Active Directory: schema data stored in the Schema partition , configuration data stored in the Configuration partition , domain data stored in the Domain partition , and application data stored in application- specific partitions.
In Active Directory, schema rules determine what types of objects are available and what attributes those objects have. When you install the first Exchange server in the forest, the Active Directory preparation process adds many Exchange-specific object classes and attributes to the schema partition in Active Directory.
This allows Exchange-specific objects, such as agents and connectors, to be created. It also allows you to extend existing objects, such as users and groups, with new attributes, such as those attributes that allow user objects to be used for sending and receiving e-mail. Every domain controller and global catalog server in the organization has a complete copy of the Schema partition. During the installation of the first Exchange server in the forest, Exchange configuration information is generated and stored in Active Directory.
Exchange configuration information, like other configuration information, is also stored in the Configuration partition. For Active Directory, the configuration information describes the structure of the directory, and the Configuration container includes all of the domains, trees, and forests, as well as the locations of domain controllers and global catalogs.
For Exchange, the configuration information is used to describe the structure of the Exchange organization. The Configuration container includes lists of templates, policies, and other global organization-level details. Every domain controller and global catalog server in the organization has a complete copy of the Configuration partition.
In Active Directory, the Domain partition stores domain-specific objects, such as users and groups, and the stored values of attributes associated with those objects. As you create, modify, or delete objects, Exchange stores the details about those objects in the Domain partition. During the installation of the first Exchange server in the forest, Exchange objects are created in the current domain.
Whenever you create new recipients or modify Exchange details, the related changes are reflected in the Domain partition as well. Every domain controller has a complete copy of the Domain partition for the domain for which it is authoritative. Understanding How Exchange Routes Messages Within the organization, Hub Transport servers use the information about sites stored in Active Directory to determine how to route messages, and can also route messages across site links.
The Hub Transport server does this by querying Active Directory about its site membership and the site membership of other servers, and then uses the information it discovers to route messages appropriately. Because of this, when you are deploying an Exchange Server organization, no additional configuration is required to establish routing in the Active Directory forest. You must also suppress link state updates for the same.
The trust allows users to see address and availability data across the forests. You deploy Hub Transport servers within the organization. With Hub Transport servers, no other special configuration is needed for message routing to external destinations. You must configure only the standard mail setup, which includes identifying DNS servers to use for lookups.
Beyond this, no other special configuration is required for mail routing and delivery. Exchange Server and Forefront Security for Exchange have separate management consoles. Exchange Server has several graphical tools that replace or combine features of the graphical tools in Exchange Server and earlier editions.
Because best practices are periodically updated, the tool includes an update facility to ensure that the most current best practices are in place. You can use this tool to customize the presentation of contacts, users, groups, public folders, and more in the client interface.
Also allows administrators to manage message queuing and remove messages. Also allows administrators to create performance logs and alerts. Wide arrays of Exchange performance objects are available for tracking performance. Other administration tools that you might want to use with Exchange Server are summarized in Table Windows Server only.
Event Viewer Manage events and logs. Microsoft Network Monitor network traffic and troubleshoot networking Monitor problems. Server Manager Add, remove, and configure roles, role services, and features. You access most of the tools listed in Table from the Administrative Tools program group. Still, there are many times when you might want to work from the command line, especially if you want to automate installation, administration, or maintenance with scripts. The Exchange Management Shell is an extension shell for Windows PowerShell that includes a wide array of built-in commands for working with Exchange Server.
PowerShell commands are referred to as cmdlets pronounced commandlets to differentiate these commands from less powerful commands built into the command prompt and from more full-featured utility programs that can be invoked at the command prompt. Figure The Exchange Management Shell. Like Exchange Server, Forefront Security for Exchange has a management console and a management shell.
You use the Forefront Server Security Administration console to manage Forefront Security using a graphical interface. Forefront Management Shell loads extensions that allow you to manage the configuration of Forefront Security for Exchange.
As Forefront Management Shell does not load the Exchange Server cmdlets, you cannot access the Exchange-specific cmdlets from this shell by default. As the Exchange Management Shell does not load the Forefront-specific cmdlets either, you cannot access the Forefront-specific cmdlets from the Exchange Management Shell by default. Mailboxes are private storage places for sending and receiving mail, and they are created as part of private mailbox databases in Exchange.
Mailboxes have many properties that control mail delivery, permissions, and storage limits. You can configure most mailbox settings on a per- mailbox basis. However, you cannot change some settings without moving mailboxes to a different mailbox database or changing the settings of the mailbox database itself. For example, you set the storage location on the file system, the default public folder database for the mailbox, and the default offline address book on a per- mailbox-database basis.
0コメント