- Recovery Storage Group can only be used with mailbox stores not public folder stores
- Recovery server must have the same server name as original server. Can use legacyDN to change name
- Need to click checkbox 'This database can be overwritten' when restoring database to original server. Need to do this for each restore
- To enable EVS to be moved between the nodes (failover), each node must be specified as a possible owner of all EVS resources. To ensure that the EVS is automatically moved back to the first node as soon as that node is brought back online, you should enable failback for the EVS
- When a node that hosts a cluster group fails, the group fails over to another node automatically, as long as another node is listed as a possible owner of all the resources in the group exists. You cannot directly enable/disable failover
- The Global Address list (GAL) is stored in the global catalog. To resolve usernames to email addresses, Exchange uses the GAL. Therefore exchange requires access to the global catalog. To minimize the amount of time it takes to resolve usernames, all Exchange servers that host user mailboxes should be well connected to a global catalog sever. Therefore you should enable at least one domain controller in each site as a global catalog server.
- When full-text indexing is enabled, users can perform searches more quickly. In exchange 2003, full-text indexing indexes each word in a database. You cannot create an index for a subset of mailboxes in a store
- You can install exchange system manager before installing the first exchange server 2003, so you can create administrative groups that can be selected during installation
- Public folders that are created on one server can be replicated to other servers. To provide faster access
- You cannot move public folders between different trees.
- Generally SMTP connectors are not required to deliver internet e-mail. If there are no SMTP connectors, then an SMTP virtual server can use DNS or a smart host to route messages to the appropriate SMTP servers. However, it is recommended that one or more SMTP connectors be used to send outbound email because SMTP connectors have more configurable options. SMTP connector can also be configured to use DNS or a smart host. The settings that are configured on an SMTP connector override those set on its bridgehead SMTP virtual server.
- When configuring a connector to use an external smart host, you should specify the IP address and NOT the FQDN.
- The account that is used to perform a migration must be assigned the appropriate level of access to both the original and destination messaging systems. To import the data into the exchange mailboxes, the migration account should be granted the 'Send As' permission for the destination mailbox stores
- In exchange 2003, SMTP protocol is used to deliver all internal and internet email messages. SMTP virtual servers are responsible for routing all messages that are transferred by using SMTP. All relevant delivery options can be configured on the 'Delivery' tab of the SMTP virtual server 'Properties' sheet. There are two groups of settings on this tab: 'Outbound' and 'Local'
- Outlook express supports the following protocols: POP3, IMAP4, NNTP and LDAP
- A POP3 client does not support viewing the contents of a user's mailbox online. It can only download messages from the Inbox folder. Additionally POP3 clients use SMTP to send email.
- IMAP4 clients provide the same functionality as POP3 clients; however users with IMAP4 clients are able to view online and manipulate items that are located in any personal folders in their respective mailboxes, as well as items that are located in the public folders in the default public folder tree, including newsgroup public folders. However IMAP4 clients cannot view newsgroups or any public folders outside of the default public tree
- NNTP clients can view any newsgroups, they can view newsgroups that are hosted in NTFS folders or in any public folders
- You need to configure the routing group connector costs and IP routing to ensure the packets of data are routed in the most efficient manner possible
- It is recommended that each of the following be placed on a separate physical disk: the OS and program files, the paging file, each exchange store, each set of transaction logs, each full-text index and full-text temporary directory
- Typically, a full-text index on a store should require disk space that equals approximately 20-25% of the amount of data in the store.
- You cannot change the location of a full-text index after it has been created. In order to move an index, you must delete it and create a new one.
SSL encryption and decryption mostly affects CPU and memory usage

No comments:
Post a Comment