Outbound HA
When enabling the HA option on the Logger Side A and Side B (note which should both be stopped while doing this) - it checks that the entered username or group is valid. When I did this, the config fails with an unhelpful error of:
“Failed to enable Outbound Option HA because UCCE-LOGGERB-12345678 is not a valid user or security group”
This error was not very helpful - as no details on WHY the web setup application found this user / group was invalid was given.
TAC were able to confirm that the setup application runs a PowerShell script which uses the Get-ADUser command.
You can test this is working or not working by running the following command in PowerShell and replacing ipccadmin with the username you are using.
Get-ADUser -LDAPFilter '(SAMAccountName=ipccadmin)'
The exact script is at the bottom of this section. The Get-ADUser relies on the Active Directory Web Services, which runs on Domain Controllers on TCP 9389. This TCP port happened to be blocked by a Firewall in our environment and when opened up, it was successfully able to connect and verify the users, and successfully config Outbound HA.
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd391908(v=ws.10)?redirectedfrom=MSDN
Java Code |(which then uses PowerShell) to check if the AD user / group name is valid
public static boolean validateADGroup(String groupname) {
String groupCommand = "Get-ADGroup -LDAPFilter '(SAMAccountName=" + groupname + ")'";
return validateADExistence(groupCommand);
}
public static boolean validateADUser(String username) {
String userCommand = "Get-ADUser -LDAPFilter '(SAMAccountName=" + username + ")'";
return validateADExistence(userCommand);
SQL Install Components
Outbound HA needs to have SQL Server Replication is installed. You can confirm if this is available via the following method:
Actually no it doesn't!
The Troubleshooting Guide above (based on 11.6) is NOT valid. SQL Replication is NOT used any more (since 12.0) - a custom Replication by the application is used instead (as the SQL replication was not fast enough apparently). So ignore this doc.