Johnny Yao WorkSpace

  Client Access O utlook 2003 is not supported 若要將 Microsoft Outlook 連接至 Exchange 2013，需使用自動探索服務。不過，Microsoft Outlook 2003 不支援使用自動探索服務。 To connect Microsoft Outlook to Exchange 2013, the use of the Autodiscover service is required. However, Microsoft Outlook 2003 doesn’t support the use of the Autodiscover service. RPC/TCP access for Outlook clients 在 Exchange 2013 中，Microsoft Outlook 用戶端可使用 Exchange 2013 Service Pack 1 或 Outlook 2013 Service Pack 1 和更新版本中的 Outlook 無所不在 (RPC/HTTP) 或 MAPI over HTTP 來連線。 如果組織中有 Outlook 用戶端，則需要使用 Outlook 無所不在及/或 HTTP over MAPI。 In Exchange 2013, Microsoft Outlook clients can connect using Outlook Anywhere (RPC/HTTP) or MAPI over HTTP in Exchange 2013 Service Pack 1 and Outlook 2013 Service Pack 1 and later. If you have Outlook clients in your organization, using Outlook Anywhere and/or MAPI over HTTP is required.

  http://blogs.technet.com/b/aljackie/archive/2013/11/14/outlook-rpc-end-point-and-pf-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook.aspx   http://www.msexchangegeek.com/the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook/   Exchange Team no longer recommend Windows NLB for Client Access Server Load Balancing http://www.stevieg.org/2010/11/exchange-team-no-longer-recommend-windows-nlb-for-client-access-server-load-balancing/   Outlook Intermittent Disconnections – Exchange 2010 http://exchangeserverinfo.net/2013/06/outlook-intermittent-disconnections-exchange-2010/ Troubleshooting Outlook RPC dialog boxes - revisited http://blogs.technet.com/b/exchange/archive/2008/05/02/3405434.aspx

  Update-FileDistributionService –Identity CAS_server –Type OAB

    rpcping -t ncacn_http -o Rpcproxy=qy-cas03.msft.corp.com -P "qy.user3,MSFT,MSFT8899" -H 1 -F 3 -a connect -u 9 -v 3 -s qy-mbx01.MSFT.corp.com -I "qy.user3,MSFT,MSFT8899" -e 6001

Default Client Access server IIS authentication and SSL settings http://technet.microsoft.com/en-us/library/gg247612(v=exchg.141).aspx

    Exchange Server 2013 Outlook Anywhere 內外部 URL http://exchange.msmvp.net/2013/05/exchange-server-2013-outlook-anywhere.html     Outlook Exchange Proxy Settings dialog box always displays the internal host name as the Proxy server in an Exchange Server 2013 environment http://support.microsoft.com/kb/2754898/en-us

  Exchange 2013 Post-Installation Tasks http://technet.microsoft.com/en-us/library/bb124397(EXCHG.150).aspx

    http://blogs.technet.com/b/messaging_with_communications/archive/2012/06/06/outlook-anywhere-timeout-issue-and-recommendation.aspx http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/15-tips-optimize-exchange-2010-infrastructure-part2.html Messages stuck in Outbox with Outlook Anywhere - Newer network devices have more aggressive timeouts. These timeouts can manifest as problems when using Outlook Anywhere; specifically, messages stuck in the Outbox. To resolve this issue, change the timeout for the RPC Proxy component to 120 seconds: HKLM\Software\Policies\Microsoft\Windows NT\Rpc\MinimumConnectionTimeout http://whited0gg.blogspot.tw/2012/08/new-best-practice-for-rpc-timeouts-in.html http://www.expta.com/2012/06/new-best-practice-for-rpc-timeouts-in.html http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/3c776c4f-d74d-4dd2-8661-17b2059aad94 [PS] C:\>get-mailbox -database "BQT-...

    http://technet.microsoft.com/en-us/library/ee332317.aspx

    http://www.howexchangeworks.com/2012/04/redirecting-owa-urls-in-exchange-2010.html   http://www.n2networksolutions.com/2011/01/13/redirect-port-80-on-exchange-2010-to-ssl-or-443-for-owa-or-outlook-web-access/

 

  New on Exchange 2003 ORG with 2003 AD forest & function level. One Server 2008 AD exist Server 2008 R2 ENT with SP1 on VMPlayer Configured NLB Forest and Domain function level upgrade    

    http://blog.morecoffeeany1.com/2010/03/19/building-nlb-exchange-2010-rtm-cas-ht-servers-hyper-v-%E2%80%93-part-1/ http://blogs.kraftkennedy.com/index.php/2009/11/25/configuring-nlb-for-exchange-2010-cas-load-balancing/ (***) Quote from  http://blogs.kraftkennedy.com       1. Create IP and A record for CAS Array VIP: 192.168.1.70  (CASArray.lab2.local)   2. LAN Preparation Node1: Public LAN: 192.168.1.71 (LAB2-CAS01.lab2.local) 255.255.255.0 1921.68.1.1 NLB LAN: 192.168.1.73 255.255.255.0   Node2: Public LAN: 192.168.1.72 (LAB2-CAS02.lab2.local) 255.255.255.0 1921.68.1.1 NLB LAN: 192.168.1.74 255.255.255.0 3. NIC Advanced Settings   4. Create NLB   5. NLB LAN enable forwarding on both nodes That is: netsh interface ipv4 set int “NLB LAN” forwarding=enabled For me the following c...

  Customize the Outlook Web App Sign-In and Sign-Out Pages http://technet.microsoft.com/en-us/library/ee633483.aspx   1. Logon.css C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\14.1.323.0\themes\resources   2. logntopl.gif   3. http redirect to https Simplify the Outlook Web App URL http://technet.microsoft.com/en-us/library/aa998359.aspx   http://linux-sf.blogspot.com/2010/11/exchange-2010-how-to-redirect-non-ssl.html

  http://technet.microsoft.com/zh-tw/magazine/ff626260.aspx Client Creation Q: Do you have any best practices to share for creating an Exchange 2010 CAS array in an Active Directory site? A: I’d advise you to create the CAS array before you make any Mailbox databases or move any mailboxes to an Exchange 2010 Mailbox server in a site. Exchange 2010 Mailbox databases have an attribute called RpcClientAccessServer. If there’s no CAS array in the Active Directory site when the database is created, this will be populated with the server FQDN of an Exchange 2010 CAS server in the Active Directory site. If you create the CAS array before any Mailbox databases, this attribute will instead be given the FQDN of the CAS array as shown in Figure 2. Figure 2 RpcClientAccessServer attribute on a Mailbox database. Why is this a good idea? The Outlook client (whether Outlook 2003, 2007 or 2010) won’t pick up the change automatically. If you use Outlook 2007 or 2010, you can have ...

        [PS] Get-OwaVirtualDirectory  -Identity "bqt-ca07\owa (Default Web Site)" | fl externalurl ExternalUrl : https://oaw.msft.com

    “RPCClinetAccessServer “ not “RPCClientAccess” Get-RpcClientAccess but no Get-RpcClientAccserver Where to find “RPCClientAccessServer” ? Get-MailboxDatabase | ft name, RpcClientAccessServer Get-MailboxDatabase | ft identity,Server, RpcClientAccessServer Set-MailboxDatabase -Identity "DataBase Identity" –RpcClientAccessServer “CAS Server FQDN” Current outlook profile is set to CAS Array: bqtmail.msft.com But when change RPCClientAccessServer, outlook profile will not automatic update new server. I need to create new profile will get new RPCClientAccessServer.

      [PS] C:\Users\Exchadm\Desktop> Get-WebServicesVirtualDirectory -Server bqt-cas01 | fl RunspaceId                    : 3030d5fc-c28d-49f0-bb8c-447a0d92492b CertificateAuthentication     : InternalNLBBypassUrl          : https://bqt-cas01.msft.corp.com/ews/exchange.asmx GzipLevel                     : High Name                          : EWS (Default Web Site) InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity} ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity} LiveIdSpNegoAuthentication    : False WSS...

    Set-OutlookProvider expr -CertPrincipalName "msstd:bqtmail.msft.com" Set-OutlookProvider expr -CertPrincipalName "msstd:*.msft.com"

    Balancing Act: Dual-NIC Configuration with Windows Server 2008 NLB Clusters Configuring NLB for Exchange 2010 CAS Load Balancing Next Steps Before you start using your new NLB cluster for CAS functionality, you should complete two final tasks.  First, IP forwarding should be enabled on each cluster member’s NLB LAN NIC.  By default, Windows 2008 disables IP forwarding, which causes problems with NLB.  IP forwarding enabled allows, from an NLB perspective, requests sent from one NIC to be sent out the other.  IP forwarding can be enabled on your NLB LAN NIC by running netsh interface ipv4 set int “NLB LAN” forwarding=enabled from a command prompt.     netsh interface show int That will show you the interfaces in the server.  Find the name of the cluster NIC and put it in quotes in the following command: ne tsh interface ipv4 set interface "Cluster NIC" forw...