Description Alexander Kläser 2015-02-25 13:08:35 CET

In the following scenario, joining into an AD domain can confusing:

* An old DC master service record (e.g., from previous test) exists on the AD DNS server side.

* When setting up a new UCS system to join the AD domain, the old DC master service record is detected and one needs to choose a server role (backup, slave, or member).

* The consecutive join fails, as the presumed master does not exist anymore (from setup.log):

**************************************************************************
* Join failed!                                                           *
* Contact your system administrator                                      *
**************************************************************************
__JOINERR__:ping to ucs-7235.mydomain.intranet failed
* Message:  ping to ucs-7235.mydomain.intranet failed
**************************************************************************

We were first a bit puzzled what exactly happened. I can imagine that a tester will have a much harder understanding what exactly has happened.

It would be good at least to prompt a hint in case the presumed DC master cannot be reached. Then, it would be nice to be able to force a join as a DC master and to overwrite existing service records (and maybe other things).