Johnny Yao WorkSpace

    •Default – CAS Server •Each MailboxDatabase has a RpcClientAccessServer field . •This is the end point that mailboxes in those mailbox databases use to connect to the database. When a database fails over, that value doesn't change. The clients are still connecting through that endpoint. •If you can you want that endpoint to be an NLB Cas Array. There's no DNS record changing in your standard database failover. •The attribute gets set when you create mailbox database. •The attribute does not seem to get updated when a database is moved. •The attribute also does not get updated when the CAS server defined in that attribute is down or removed from the organization.           Blog Extended Reading More Information & Reference 1. Exchange Server 2010 and RPCClientAccessServer Madness 2.

  “ In simple terms a CAS Array is a set of Exchange 2010 CAS servers that are load balanced using either Windows Network Load Balancing, Microsoft ISA Server or a third party load balancing appliance. Without configuring a CAS Array the Outlook client will connect to a single CAS server within the Active Directory Site and the connection would fail should that CAS server go offline. •So the array configuration takes two steps which are: 1. Configure the CAS servers in a Windows Network Load Balancing cluster. 2. Configure the CAS Array in Exchange. " There can be only one CAS array configured per Active Directory Site. Also while creating a new Mailbox database in the AD site, the value for the CAS Array was automatically picked up. New-ClientAccessArray –name “BQT CAS Array” –FQDN BQT-CAS.MSFT.corp.com   [PS] C:\Windows\system32> New-ClientAccessArray -name "MSFT CAS Array" -Fqdn "mail.MSFT.com" -Site "BQT" ...

  如何設定檔案共用見證   < ShareUNCPath > 是指檔案共用的 UNC 路徑 (例如 \\E2K7HUB1\MNS_FSW_E2K7CCR)。 <CMSName> 是指叢集信箱伺服器的名稱 (例如 E2K7CCR)。 <Directory> 是指共用目錄的完整路徑 (例如 C:\MNS_FSW_DIR_E2K7CCR)。 <CSA> 是叢集服務帳戶。 <ClusterName> 是叢集本身的名稱 (例如 EXCLUS1)。     建立並保護檔案共用見證的檔案共用 在命令提示字元中執行下列命令，以建立將用於共用的目錄： mkdir <Directory> 建議對目錄名稱使用下列命名慣例："MNS_FSW_DIR_< CMSName >" 執行下列命令來建立共用： net share <shareName>=<Directory> /GRANT:<CSA>,FULL 我們建議對共用名稱使用下列命名慣例："MNS_FSW_< CMSName >" 執行下列命令來指派權限給共用： cacls <Directory> /G BUILTIN\Administrators:F <CSA>:F 使用叢集服務帳戶登入時，請確認可從第一個叢集節點存取共用。使用 Windows 檔案總管或另一個應用程式，驗證是否藉由開啟檔案共用來使用共用。若使用叢集服務帳戶以外的帳戶，則會收到「拒絕存取」的訊息。   設定 MNS 仲裁來使用檔案共用見證 若要設定內容，請在命令提示字元中執行下列命令： Cluster <ClusterName> res "Majority Node Set" /priv MNSF...

    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 En...

  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 ...

  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...

  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 Acc...