Ref: Exchange 2010 set-RpcClientAccessServer

 

 

“RPCClinetAccessServer “ not “RPCClientAccess”

Get-RpcClientAccess but no Get-RpcClientAccserver

image

Where to find “RPCClientAccessServer” ?

Get-MailboxDatabase | ft name, RpcClientAccessServer

image

image

Get-MailboxDatabase | ft identity,Server, RpcClientAccessServer

image

image

Set-MailboxDatabase -Identity "DataBase Identity" –RpcClientAccessServer “CAS Server FQDN”

image

Current outlook profile is set to CAS Array: bqtmail.msft.com

image

But when change RPCClientAccessServer, outlook profile will not automatic update new server.

I need to create new profile will get new RPCClientAccessServer.

image

Ticket: Exchange 2010 on server 2008 – Event ID 10009 — COM Remote Service Availability

 

網路負載平衡 (NLB):單點傳播 (Unicast) 與 多點傳送 (Multicast) 的差異

 

image

on node1 BQT-CAS01 NLB monitoring status

image

on Node1 BQT-CAS01 ping testing

image

but on Node2 BQT-CAS02 NLB manager seems fine

image

on Node2 BQT-CAS02 ping testing

image

 

Event ID 10009 — COM Remote Service Availability

Check the firewall settings and enable the firewall exception rule

To check the firewall settings and enable the firewall exception rule:

  1. Click Start, and then click Run.
  2. Type wf.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the console tree, click Inbound rules.
  4. In the list of firewall exception rules, look for COM+ Network Access (DCOM In).
  5. If the firewall exception rule is not enabled, in the details pane click Enable rule, and then scroll horizontally to confirm that the protocol is TCP and the LocalPort is 135. Close Windows Firewall with Advanced Security.

 

image

on Node1  “COM+ Network Access (DCOM In)” is disabled

image 

But on Node2 has enabled.

image

Verify

You can verify that the COM service is available remotely by running the Component Services administrative tool and ensuring that the required properties for remote access are configured.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To open Component Services and verify that the required properties for remote access are configured:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. To locate your computer, click Component Services, click Computers, and then click My Computer.
  4. Right-click My Computer, and then click Properties.
  5. Click the Default Protocols tab, and confirm that the appropriate communication protocols are listed.
  6. Click each protocol, and then click Properties to verify that the settings for the protocol are correct.

Node1 BQT-CAS01
image

Node2 BQT-CAS02
image

REF: Exchange 2010 Get-WebServicesVirtualDirectory

 

 

 

[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
WSSecurityAuthentication      : True
LiveIdBasicAuthentication     : False
BasicAuthentication           : False
DigestAuthentication          : False
WindowsAuthentication         : True
MetabasePath                  : IIS://BQT-CAS01.msft.corp.com/W3SVC/1/ROOT/EWS
Path                          : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
Server                        : BQT-CAS01
InternalUrl                   : https://bqtmail.msft.com/EWS/Exchange.asmx
ExternalUrl                   : https://bqtmail.msft.com/ews/exchange.asmx
AdminDisplayName              :
ExchangeVersion               : 0.10 (14.0.100.0)
DistinguishedName             : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=BQT-CAS01,CN=Servers,CN=Exchange Admi
                                nistrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=msft,CN=Microsoft Exchan
                                ge,CN=Services,CN=Configuration,DC=corp,DC=com
Identity                      : BQT-CAS01\EWS (Default Web Site)
Guid                          : 64c3803a-c272-47d4-a3f1-c1396fad684c
ObjectCategory                : corp.com/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass                   : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged                   : 8/25/2010 8:45:51 AM
WhenCreated                   : 5/17/2010 9:26:54 AM
WhenChangedUTC                : 8/25/2010 12:45:51 AM
WhenCreatedUTC                : 5/17/2010 1:26:54 AM
OrganizationId                :
OriginatingServer             : dc13.msft.corp.com
IsValid                       : True

REF: Exchange 2010 upgrade custom address list

 

在收件者命令中建立篩選器

Exchange 2007 SP1 與 SP2 中 -RecipientFilter 參數可篩選的內容

 

-RecipientFilter 參數的許多屬性會接受萬用字元。如果您使用萬用字元,請使用 -like 運算子,而不要使用 -eq 運算子。-like 運算子是用來尋找符合各種類型 (例如字串) 的模式比對,而 -eq 運算子則是用來尋找完全的相符。

其他 OPATH 語法資訊

若要建立自己的自訂篩選,請注意下列事項:

  • 使用大括號 { } 括住具有 FilterRecipientFilter 參數的整個 OPATH 語法字串。
  • 在所有的運算子之前加上連字號。以下為最常見的運算:
    • -and
    • -or
    • -not
    • -eq (等於)
    • -ne (不等於)
    • -lt (小於)
    • -gt (大於)
    • -like (字串比較)
    • -notlike (字串比較)
  • RecipientFilterFilter 參數的許多內容都接受萬用字元。如果您使用萬用字元,請使用 like 運算子,而非 eq 運算子。like 運算子是用來尋找符合各種類型 (例如字串) 的模式比對,而 eq 運算子則是用來尋找完全相符的項目。

 

image

image

image

image

Issue: Exchange 2010 CAS NLB configuration – netsh

 

 

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.

image

image 

image

image

 

netsh interface show int

image

  • 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:
    • netsh interface ipv4 set interface "Cluster NIC" forwarding=enabled

      image

  • You can confirm that it is changed by running the command:
    • netsh interface ipv4 show interface l=verbose

      image