Event 1017 and a Domain Controller that no longer exists

[cco2]

Hello.

A customer running Unity 4.0.4 is seeing Event 1017 every two minutes, as well as related Events 1090 and 1092 every 30 minutes or so. Event 1017 complains that AvDSAD cannot connect to a particular Domain Controller (one that was removed several months ago) and that it will try again in two minutes.

Then, after 15 such entries at two-minute intervals, the Unity throws an Event 1090 saying it will try to contact another Domain Controller, then Event 1092 saying it can't find another and will go back to polling the one that was shut down.

How can we tell the Unity that the old DC doesn't exist, and perhaps point it at another one?

[Hin Lee]

Unity should have found the next available domain controller. One reason for this failure may be due to dns config - collect the GUSI log and post it here for review.

If you REALLY want to set it manually, open Tools Depot, and under Administration, double-click on DC/GC Reconnect Settings Tool

Select the Domain Controllers tab.

Uncheck Enable automatic server search functionality on reconnects for this domain

Enter the fully qualified domain name of the DC that you want Cisco Unity to monitor for directory changes in the field for Manual primary domain controller

Click Force Reconnect.

[cco2]

Thanks for that.

I have clarified the situation with the customer, and in fact the problem isn't just that the domain controller has gone away; it is that an entire domain has been deleted from the AD forest. We need to make the Unity aware that a domain it used to monitor no longer exists.

What do you think?