Exchange 2010 CAS NLB Part1 – Add First NLB Node

-

 

1. Exchange Queue & A: CAS Arrays - Server Roles, Client Creation, Load Balancing and More
2. Configuring NLB for Exchange 2010 CAS Load Balancing
3. Unable to connect to Windows Server 2008 NLB Virtual IP Address from hosts in different subnets when NLB is in Multicast Mode
4. Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1 (***)
5. 網路負載平衡 (NLB)：單點傳播 (Unicast) 與 多點傳送 (Multicast) 的差異
6. 安裝手冊範本 - Client Access Server (Windows Server 2008)
7. Uncovering the new RPC Client Access Service in Exchange 2010 (Part 3)
8. Unicast or Multicast Mode?
9. Quick Tip: Configuring Network Load Balancing (NLB) on Windows 2008 for Exchange CAS Servers…

10. 分享exchange 2007系列之四:Windows 2008 & Exchange CAS NLB

11. Windows Server 2008怎麼設定網路負載(Network LoadBalance)




1.

ServerManagerCmd -i NLB

 image

2.

image

 

Internal CAS array name: BQT-CASArray.MSFT.corp.com
CAS server: BQT-CAS01.MSFT.corp.com  - 10.82.246.91, NIC2 – 192.168.0.91
CAS server: BQT-CAS02.MSFT.corp.com – 10.82.246.92, NIC2 – 192.168.0.92
Internal NLB Cluster name: BQT-CASNLB.MSFT.corp.com

10.1.240.100 and EXCHCASArray.client.local.  Please note that the IP address should be on the same subnet as the two CAS servers that will become members of the NLB cluster.
(Configuring NLB for Exchange 2010 CAS Load Balancing)


3. CAS Array & WNLB 的名稱是可以共用一個, 也可以分開, 只是不知道分開的使用理由為何….
目前就先設定共用一個, 同時也就不需要額外的IP, FYI

WNLB & CAS array name: BQT-CASArray.MSFT.corp.com
DMZ Vitrual IP: 10.82.246.x

When using WNLB to load balance Client access server traffic, does the FQDN of the WNLB need to match the FQDN of the CAS array?
This is not a requirement at all. Personally when using WNLB to load balance CAS server traffic, I call the FQDN of the WNLB something like casarray01.domain.com and the FQDN of the CAS array outlook.domain.com and this works just fine for me, as well as being fully supported. As long as the internal DNS record for the CAS array points to the VIP of the WNLB things should super-duper.


Q: When using Windows Network Load Balancing (WNLB) to load-balance traffic to an Exchange 2010 CAS array, does the FQDN of the WNLB need to match that of the CAS array?
A: This isn’t a requirement at all. For instance, when using Windows NLB to load-balance traffic going to the CAS array, you could specify an FQDN for the Windows NLB of, say, casarray01.contoso.com and assign the CAS array outlook.contoso.com. This would work just fine and is fully supported. As long as the internal DNS record for the CAS array points to the virtual IP of the WNLB, things should be fine.

4.
image

5.
image

6.
image

7.
image

8.

image

9.
image

10.
image

11.
image

12.
In this case this would be port TCP 135 endpoint mapper port which is required for the CAS array.

Update: Please note that, for internally facing CAS servers front-ending MAPI traffic, you will also need to create port rules for TCP port 135 (RPC Endpoint Mapper) and TCP ports 1024-65535 (the dynamic port range for Outlook RPC access).

image

13.
image

14.
image

15.
image

16.

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more