Local, Domain, Global and Universal Group

Local, Domain, Global and Universal Group

Universal Group accessibility will not be over the external Domain Trust link. To use Universal Group, domains should be in same forest.

We can change Group scope from one to another. But sometime it will not allow you to do that.
Example : Universal group can contain users, computers, global groups, or universal groups from any domain in the same forest, but if you want to change domain local group which contains users\group from another forest or domains over the external Trust link.

Hub Transport Role Server

• Routing email inside the Active directory forest.

 * Hub-to-hub routing within an active directory forest uses Active directory sites, computing routes by using site link cost. Connections are created implicitly between Hub transport servers.

• Send connectors

 * creates a logical connection to a remote email system for the purpose of outbound transmission of email messages.

• Receiver Connectors

 * Server as a logical gateway through which all inbound messages are received. Receive connectors listen for inbound connections from other Hub and edge transport servers.

* Two are created by default: client, for SMTP connections from non-MAPI clients such as POP and IMAP, and default, for connections from other Hub and edge transport servers.

• Edge Subscriptions

 * Identifies the edge transport servers that will be managed through replicated configuration data from the Exchange Organization.

• Accepted Domains

 * Used to define which SMTP domains Exchange will accept for inbound email routing. These can be authoritative or relay domains.

• Remote Domains

 * SMTP domains which are external to your Exchange organization. They are used to define the settings for message transfer between your Exchange organization and domains outside your AD forest. 

DataBase Availability group (DAG)

Exchange server 2010 mailbox databases can only be replicated to other Exchange Server 2010 servers within a DAG. you cannot replicate a database outside of the DAG, or to an Exchange Server 2007.

Active Directory Role in Exchange 2010

Active Directory works in conjunction with Active Directory Application Mode, or ADAM, using a tool called EdgeSync on an Exchange Server 2010 Edge Transport server to move a portion of Active Directory to the edge in an encrypted, secure manner. In addition, Active Directory is leveraged on the Hub Transport server to process rules for compliance and regulatory content assessment. Using Active Directory user, group, organizational unit, site, domain, and forest level rules, content can be assessed and filtered at the Hub
Transport server level.

Client Access Server Role

Exchange Server 2010 now has replicated mailbox technology where a user’s mailbox can be active on a different server in the event of a primary mailbox server failure. By allowing the CAS server to redirect the user to the appropriate destination, there is more flexibility in providing redundancy and recoverability of mailbox access in the event of a system failure.

Unified Messaging Server Role

Unified messaging is the capability for Exchange Server 2010 to be the voice mail server for an organization. Rather than having a separate voice mail system connected to the organization’s phone system, an Exchange Server 2010 unified messaging server can be integrated into the phone system to be able to take messages on incoming calls, and the messages are stored in the users’ Exchange Server mailboxes for playback from the phone or by accessing the message from within Outlook, OWA, or Windows Mobile.

MailBox Server Role

The Mailbox server role is merely a server that holds users’ mailbox information. It is the server that has the Exchange Server EDB databases. However, rather than just being a database server, the Exchange Server 2010 Mailbox server role can be configured to perform several functions that keep the mailbox data online and replicated.