Probe did not fetch latest information from AD

Symptom:

- Domain user not able to log-in into Kaseya console even after full-sync

- Synced machine/policy/agent not appeared/installed in Kaseya console

- Full-sync does not reflect information between AD and Kaseya console even after harvest is completed

Assumption:

- You have installed multiple probe on the past

- You decommissioned a machine from becoming probe and promote another machine to become a new probe

Things you can do:

1- Check the domain watch logs to find any lead on the issue

2- Ensure the account verification is successful   

3- Run full-sync for the current probe and identify the behaviour

4- Identify the AgentGUID that promoted as probe machine by hovering to green icon and find the AgentGUID

5- Identify the domain name from the Kaseya console Domain Watch

6- Run SQL query below in ksubscriber to confirm the domain and machine promoted as probe:

Select top 10 * from KdsManagedDomainCollectors where ref like '%[input domain-name]%'

7- compare the output from query below with the AgentGUID in step 4

8- Remove the old / unused probe by checking the statusCode column. NULL = not in used. Show number = in used.

9- To remove, run below query in ksubscriber:

delete from KdsManagedDomainCollectors where ref like '%[input domain-name]%' and agentGuid=[input-AgentGUID]