Even with the lates patch the driver still stopps in failing situations, this should be avoided.

There should be an startup option: The driver starts in all cases, where at least one of the domain servers is running and reachable.

Example: No domain controllers for an entire domain are available (due to a wan link outage for example): Then the driver should still initialize and synchronize with the remanining domains.

Minimum general desired start options in case of manually configuration (each domain controller is configured in the Dirver Configuration Tab / Driver Parameters Section)

- Start, if at least one of the domain servers is reachable, write logs/warnings, stop only, if no server at all reachable
- When no domain controllers for an entire domain are available (due to a wan link outage for example) the driver should still initialize and synchronize with the remaining domains, write logs/warnings, stop only if no server at all reachable
- Start only, if all selected DC are available, otherwise stop and write logs/warnings

Start Options in case of Autodiscover used:
- Start only, if all DC are available, otherwise stop and write logs/warnings

Even better would be individual start options in case of manually configuration :
** Above three start options for each domain controller which is configured in the Driver Configuration Tab / Driver Parameters Section **

by: Karl P. | over a year ago | iManager