Forum Discussion
ATA showing a user as an member of Domain Admin who has been deleted for 40 days?
EliOfek
Thanks again. :)
OK, we done that wrong and have now change it so ATA has readonly access to Deleted Objects.
Next question is, how do we get ATA back in sync? Should we just sit back and wait? ;)
ThomasFriisPoulsen , I think this will fix the issue only going forward, as we already "missed" the update.
Which ATA version are you running?
- ThomasFriisPoulsenJul 04, 2019Iron Contributor
1.9.7412.9649EliOfek
- EliOfekJul 07, 2019Microsoft
Try to upgrade to 1.9 Update 2 (1.9.7478.57683).
If the issue is still not resolved, on top of this version, you can induce a forced resync of AD to ATA.
Giving that now we have read access on deleted items, the resync should resolve the issue.
You can do this by opening an elevated command prompt on the Center machine, navigating to the mongo bin folder, and from there issuing the commands:
net stop ATACenter mongo.exe ATA --eval "db.SystemProfile.remove({_t:'DirectoryServicesSystemProfile'})" net start ATACenter
This will force a resync, which can take from a few hours to a few days, depending on your AD size... for most customers it will complete within a few hours.
There is no UI indication on completion because it is actually an ongoing process, we just tell it here to start from scratch.
- ThomasFriisPoulsenJul 08, 2019Iron Contributor
Just upgraded, waiting... ... ... ... :)