We have made the following updates to the installation guides:
We have finally released an Windows Server 2008 Cluster Continuous Replication Installation Guide (yeah we know it was a way overd...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Ross,
Great Guide! I found 2 things that might help others and can be added to guidance perhaps:
1. Server hardening: SCW template to load for Exchange should be "Exchange2007_WinSrv2008.xml" and Exchange2007Edge_WinSrv2008.xml". This doesn't come clear from the online documentation (linked through from the main guide)
2. So, if you want to keep your Advanced Firewall running and apply SCW, there is a manual change you have to make for the "..BinMicrosoft.Exchange.ClusterReplayService.exe" program, because inbound connections are blocked! You have to add it as an Inbound Rule and add it as a Program and allow connections on Domain,Private and Public network profiles. Symptoms and problems that you get when you don't:
- Get-StorageGroupCopyStatus reports ServiceDown or other errors.
- Test-ReplicationHealth takes a really long time to complete and reports an error on SGCopyStatus.
- So Continuous Replication is is failed state.
- Cluster nodes get slumpy.
Cheers,
Nik
Great Guide! I found 2 things that might help others and can be added to guidance perhaps:
1. Server hardening: SCW template to load for Exchange should be "Exchange2007_WinSrv2008.xml" and Exchange2007Edge_WinSrv2008.xml". This doesn't come clear from the online documentation (linked through from the main guide)
2. So, if you want to keep your Advanced Firewall running and apply SCW, there is a manual change you have to make for the "..BinMicrosoft.Exchange.ClusterReplayService.exe" program, because inbound connections are blocked! You have to add it as an Inbound Rule and add it as a Program and allow connections on Domain,Private and Public network profiles. Symptoms and problems that you get when you don't:
- Get-StorageGroupCopyStatus reports ServiceDown or other errors.
- Test-ReplicationHealth takes a really long time to complete and reports an error on SGCopyStatus.
- So Continuous Replication is is failed state.
- Cluster nodes get slumpy.
Cheers,
Nik