Posts

Showing posts from March 7, 2010

E14 - Configure Outlook Anywhere in an Environment with Earlier Versions of Exchange

Image
    When you deploy the Outlook Anywhere feature (formerly known as RPC over HTTP) on a Microsoft Exchange Server 2010 Client Access server that will provide access to Microsoft Exchange Server 2007 or Exchange Server 2003, you must configure Outlook Anywhere for the earlier versions. Looking for other management tasks related to Exchange 2010 Outlook Anywhere? Check out Managing Outlook Anywhere .   Configure Outlook Anywhere for Exchange Server 2003 You can configure Outlook Anywhere for the original release version of Exchange 2003 and for Exchange 2003 with Service Pack 1 (SP1) or SP2 by following the configuration steps for RPC over HTTP for these versions of Microsoft Exchange. For detailed steps, see How to Configure Outlook Anywhere with Exchange 2003 .    Configure Outlook Anywhere for Exchange Server 2007 Use the EMC or the Shell in Exchange Server 2007 to enable Outlook Anywhere for your organization. For detailed steps, see How to Enable Outlook Anywhere .

E14 - Proxying for Outlook Web App

Image
  The following scenario shows how incoming requests are handled for a user who connects to an Exchange 2010 Client Access server named CAS-01 using Outlook Web App. The Client Access server queries Active Directory to determine the location of the user's mailbox and the version of Microsoft Exchange installed on the Mailbox server. If the user's mailbox is on an Exchange 2010 Mailbox server, go to step 3. E2K3 user 無法使用 https://exchangeFQDN/OWA 存取E2010 CAS   Outlook Web Access could not find a mailbox for MSFT\bqt.msv12. If the problem continues, contact technical support for your organization and tell them the following: The mailbox may be stored on a Microsoft Exchange 2000 or Microsoft Exchange 2003 server, or the Active Directory user account was created recently and has not yet replicated to the Active Directory site where this Client Access server is hosted. Request Url: https://oaw.MSFT.com:443/owa/auth/error.aspx User host a

E14 Proxying for Exchange ActiveSync

Image
  If User 1 tries to access Client Access server 02 using Exchange ActiveSync, they'll receive an error because Client Access server 01 is the appropriate Client Access server for their mailbox. 1. The following scenario shows how incoming requests are handled for a user who connects to an Exchange 2010 Client Access server named CAS-01 using a mobile device. 2. The Client Access server queries the Active Directory to determine the location of the user's mailbox and the version of Microsoft Exchange installed on the Mailbox server . If the user's mailbox is on an Exchange 2010 computer that has the Mailbox server role installed, go to step 3 3. Exchange ActiveSync 都透過proxy 運作至相同或不同AD site 上的Exchange 2003 B-E ActiveSync IIS virtual directory. E2010 CAS 可直接proxy 至E2K3 B-E. If the user's mailbox is on an Exchange 2003 server , the incoming request is proxied to the Exchange 2003 server that hosts the user's mailbox and the Exchange Act

E14 Overview CAS Proxy AND Redirection

Image
  1. A Client Access server can also perform redirection for Microsoft Office Outlook Web 應用程式 URLs . Redirection is useful when a user is connecting to a Client Access server that isn't in their local Active Directory site. 2. If you don't have multiple Active Directory sites in your organization, you don't have to configure Exchange 2010 for proxying or redirection. 3. in Microsoft Exchange Server 2003, the front-end server communicates with the back-end server over HTTP. In Exchange 2010, the Client Access server communicates with the Mailbox server over RPC . You must have an Exchange 2010 Client Access server in every Active Directory site that contains a Mailbox server. Proxying occurs when one Client Access server sends traffic to another Client Access server . An Exchange 2010 Client Access server can proxy requests in the following two situations: Between Exchange 2010 Client Access servers    Proxying requests between two Exchange 2010 Client Acces

Ticket: Exchange 2003 - Deleting this mailbox store may result in the loss of system messages used by Exchange

Image
    When does the System Attendant mailbox get created? Can it be moved or re-created? The System Attendant mailbox is created when the system attendant is created on a server. It is associated with the first mailbox store created on a server. If an attempt is made to delete the mailbox store containing the System Attendant mailbox, the following warning will appear: Deleting this mailbox store may result in the loss of system messages used by Exchange, such as Free/Busy or Key Management Security. If you choose to continue, you need to restart the system attendant service after the store is deleted. If the store is then deleted, the System Attendant mailbox will be moved automatically into another mailbox store on the server, that is, the HomeMDB value on the directory object will be updated. The system attendant service must be restarted to reconfigure MSExchangeFBPublish to use the new mailbox location, and the mailbox object may not rea