1. What are the different Exchange 2003 versions?
Go to your server in Exchange System Manager, right-click your server, choose Properties, and on the General tab make a note of the version number.
Each version of Exchange Server includes a build number so that you can easily identify which version of the product you are running:
6944.4 = Exchange 2003 RTM (including SBS2003)
7226.6 = Exchange 2003 SP1
7638.2 = Exchange 2003 SP2
2. Tell me a bit about the capabilities of Exchange Server?
1) Outlook Anywhere (OWA)
2) Mailbox Can sync with Blackberry Device.
3) Calender Shairing.
4) MAPI & POP3 Client support.
3. What is happening with public folders?
Public folders are similar to mailbox stores, but the information within a public folder store is contained within a dedicated database. Exchange 2007 de-emphasizes public folders. Public folders may not be included in future releases, but support for public folders will be maintained through at least 2016. Current Microsoft Exchange customers should plan to migrate to Outlook 2007 and Exchange 2007. We recommend that you investigate integrating Microsoft Windows SharePoint Services with Exchange Server 2007 if you must have an application that supports sharing documents, calendar items, contacts, and tasks and archiving distribution lists. For other customized applications that are being developed, you should use Microsoft .NET. For more information about public folders
No. All administration of Exchange Server 2007 must be done by using the Exchange Management Console or the Exchange Management Shell. All administration of Exchange 2000 Server or Exchange Server 2003 must be done by using their respective administrative interfaces. The one exception to this rule is that you can use Exchange System Manager found in Exchange Server 2003 to perform most Exchange Server 2007 public folder administrative tasks.
5. What is the Autodiscover service?
The Autodiscover service gathers the required configuration information in Active Directory to enable Outlook 2007, Office Outlook Web Access, and mobile e-mail clients to efficiently locate and connect to the appropriate Exchange 2007 Mailbox server that contains the user's mailbox. The Autodiscover service is also used to make configuring Outlook 2007 clients easier and to provision mobile devices that are used to connect to Exchange 2007. By default, the Autodiscover service is enabled.
Unified Messaging Web services that run on the Client Access server enable full client functionality for UM-enabled users. Additionally, installing and configuring a Client Access server in the same site as the Unified Messaging servers reduces the bandwidth that is required if they are deployed in separate Active Directory sites.
Unified Messaging servers submit voice mail and fax messages to a Hub Transport server by using SMTP. This can occur only if they are deployed in the same Active Directory site.
8. What if the Client Access server role is not available from the Internet?
You can disable redirection for the Client Access server. The Internet-accessible Client Access server will act as an HTTP proxy to the Client Access server that is located in the same site as the user's mailbox.
Installing the Client Access server role in every Active Directory site that contains user mailboxes reduces the use of corporate bandwidth by redirecting the connection to the Client Access server that is in the same Active Directory site in which the user's mailbox is contained.
10. Can the Exchange 2007 server roles be deployed and configured on the same physical hardware?
Because Exchange 2007 is role-based, you can deploy all Exchange Server 2007 server roles, except the Edge Transport server role on a single physical server. If you are clustering, you cannot deploy the Mailbox server role on the same server as the Client Access, Unified Messaging, Hub Transport, or Edge Transport server roles. When the server roles are installed on the same or shared hardware, they function as separate entities.
