Bra

Building Blocks of Design

Author Note This research is being submitted on August 24, 2013, for N234/CET2810C Section 01 Microsoft Exchange Server course.

Building Blocks of Design Exchange Server 2010 has various roles that can be installed on the server to perform specific functions. There are five major server roles, most of which are modular and can reside on a single server (for small environments) or be distributed to multiple servers throughout an organization. First you have the Edge Transport Server Role which establishes perimeter security by providing antivirus and antispam message protection. Then you have the Client Access Server Role which provides user connectivity and also manages MAPI (like outlook) and makes it so the client never has to connect directly to the mailbox server. Also we have the Hub Transport Servers which routs mail, this server has to be deployed at each active directory site that contains a mailbox server. Then we have the Unified Messaging Servers and the Mailbox Servers, the Unified Messaging Server role acts as a gateway for combining email, voice, and fax data into one mailbox that can be accessed by either email or phone. Lastly the Mailbox Server role is everything it’s the core role within in Exchange, it host mailboxes and mail enabled objects such as contacts and distribution lists. These roles among other things such as an active directory infrastructure, Windows Server 2008, Microsoft .NET Framework, Windows Remote Management, Windows Power Shell, and Microsoft Management Console are the building blocks of a fully functional Exchange environment. The difference between a good Microsoft Exchange administrator and a great one is the attention he or she pays to mailbox administration. Mailboxes are private storage places for messages you’ve sent and received, 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. Exchange Server 2010 makes it easy to create several special purpose mailbox types in this paper I will be discussing a plan of the installation of Exchange as well as integrating some of the four major mailbox types that include the linked, room, user, and equipment mailboxes. For a small company I would first install a server that houses the Domain Controller and Active Directory, Also Windows Server 2008 R2 for the Exchange server itself. Then I would add the Exchange Server to the Domain. Next I will begin adding my Roles such as Client Access, Hub Transport and my Mailbox Roles. The two mailbox types I will be adding to my exchange server environment are user mailboxes and room mailboxes. Mailboxes are the most common recipient type used by information workers in an Exchange organization. Each mailbox is associated with an Active Directory user account. Within the Exchange Management Console I will be able to create these mailboxes and types.
The first mailboxes I will create are User Mailboxes, the purpose these mailboxes will serve is so the user can use the mailbox to send and receive messages, and to store messages, appointments, tasks, notes, and documents. And the next mailboxes and type I will create are room mailboxes, Room Mailboxes are fundamentally the same as regular User Mailboxes. They consist of a user account in Active Directory and an associated mailbox in Exchange Server 2010. Its purpose for me will be to assign meeting locations, such as a conference room, class room, or training room. That will allow staff members to use outlook to reserve or schedule a meeting in a specific room at a specific time.
In my exchange environment public folders will also be supported but yes the will eventually be phased out by SharePoint because SharePoint is amazing it can include everything from documents to calendars to lists to pictures to discussion boards and more. All of it can be a part of a SharePoint site, and any user you designate within your organization's network -- and in some cases, even users outside of your network such as partners or vendors -- can then access those pieces and collaborate with you.
The purpose behind mail-enabled groups is to speed up the distribution of messages to multiple e-mail addresses. The purpose behind mail enabled contacts is that it provides a means for adding frequently-used external email addresses into your organization's global address list. By doing this, you ensure members of your organization can easily email external parties such as vendors and business partners.

References Bass, R. (2010, April 20). Installing Exchange 2010. Retrieved August 24, 2013, from http://www.enterprisenetworkingplanet.com/windows/article.php/52231_3877601_2/Installing-Exchange-2010-StepbyStep.htm
Hassel, J. (2012, December 11). SharePoint 2010. Retrieved August 24, 2013, from http://www.computerworld.com/s/article/9234198
Stanek, W. (n.d.). Understand the Exchange Server Roles in Exchange Server 2010. Retrieved August 24, 2013, from http://technet.microsoft.com/en-us/magazine/ff381422.aspx
TechNet (2012, July 23). Create a Room or Equipment Mailbox: Exchange 2010 Help. Retrieved August 24, 2013, from http://technet.microsoft.com/en-us/library/bb124952(v=exchg.141).aspx
Terakedis, R. (2010, November 17). How to Create a Mail Enabled Contact | eHow. Retrieved August 24, 2013, from http://www.ehow.com/how_6554076_create-mail-enabled-contact.html