Exchange what to look for
1) Storage Group
2)MailBox Store /Storage Group
3)Dismonted Mailstore
4) Transaction Log Files and Database files
5) eseutil /r (run in recovery mode to recover data)
eseutil /r /database_name (run to repear the data)
A hard repair occurs when 20120b120u you run an eseutil /p or edbutil /d /r command against an Exchange Server database file, such as the Priv.edb, Pub.edb, or Dir.edb database.
6) Routing Group /Routing Group Master
Routing Group cost; Messages are sent over routing group connectors with the lowest cost.
7)Routing Group Connector (Exchange servers must be Able to send mail directly to each other. We can achieve this by using routing groups.)
8) Bridgehead Server
9) schedule + free busy connector
10) Public Folders
1. Inetinfo.exe Process that handles Internet protocols
2. Emsmta.exe Microsoft Exchange Message Transfer Agent (MTA) Stacks service
3. Mad.exe Microsoft Exchange System Attendant
Microsoft Exchange MTA Stacks (MSExchangeMTA) maintain the link state table between SMTP and the routing engine that is used to communicate link state information between routing groups and throughout the organization. The message transfer agent (MTA) in Exchange now uses Gwart.dll to make a legacy compatible gateway address routing table (GWART). MTA uses Mtaroute.dll as the connection between the legacy MTA and the Microsoft Exchange Routing Engine
The Exchange Information Store service supports data storage (mailboxes and public folders data) on the server. Since a front end OWA server queries backend server for data, this service can be disabled during regular operations.
Microsoft Exchange MTA Stacks service supports message routing to foreign messaging system using X.400 and gateway connectors. It is not a required service on a front end OWA server.
12) Global Catalog Server
13) Site Replication Service (SRS)
14) Active Directory Connector (ADC)
15) Domain controller Roles
TESTKING1 Schema master, Domain naming master, Global catalog
TESTKING2 Infrastructure master, PDC emulator, RID master
16) MSExchangeDSAccess is used for Exchange 2000 and Exchange 2003 to query to a domain controller who is also the global catalog
17) full-text indexing allows to search
open up the IMAP4 SSL port since we need to SECURELY DOWNLOAD
19) RPC over HTTPS only works if you have Outlook 2003 running on Windows XP with SP1 (or higher) connected to a windows 2003 Server with Exchange 2003.
Default system access control list (SACL)
Recipient Update Service for each domain in your organization, (Run the setup /domainprep command in the child domain. Create a Recipient Update Service for the child domain.)
22) SMTP command ETRN (Enhanced TURN), which allows an SMTP client to connect to an SMTP server that has been queuing mail for the client and issue the ETRN command.
Windows 98 does not use DNS natively for name resolution. It uses WINS for NetBIOS name lookups. Adding a WINS address for the Exchange server should resolve the problem.
24) DSaccess Exchange use Dsaccess service to find a set of available directory service servers. For each available directory service server, DSAccess opens LDAP connections dedicated solely on behalf of each process that is using DSAccess. DSAccess updates these LDAP connections with directory service state information (Up, Slow, or Down) that it detects, and channels requests based on this state information. The set of LDAP connections to those available domain controllers and global catalogs and their associated states forms the profile of the process. For reliability and scalability, DSAccess supports a load-balancing mechanism to distribute user context directory service requests in a round-robin fashion among these LDAP connections.
A round-robin DNS is a mechanism that directs incoming requests to servers on a rotating basis. This is done by looping through a list of IP addresses belonging to the servers in the configuration. When an e-mail client attempts to access a mailbox on an Exchange server, the client is given the first IP address on the list. The second client request is given the second IP address in the list, and so on. If there are four servers on the round-robin list, all four IP addresses are used before the first IP address is used again, and the loop starts over. In addition, Exchange 2003 offers improvements over the Exchange 5.5 Site Connector if one of the source bridgehead servers is down
|
