First determinte the tsl (tombstone lifetime) of your forest. The symptom is that random users are being knocked off there outlook, web app or smartphone with what seems to be a wrong password. We have already experienced this issue with one of our branch.
Other dcs remained at correct time so they aren't replicating with the pdce anymore (eventid 2042). Ich habe das problem, dass bei unserem exchange 2016 cu 8 auf einmal die öffentlichen ordner verschwunden sind. Replication is happen partially, still sysvol is not yet replicated to the adc
The specified domain either does not exist or could not be contacted. I can't even move the fsmo roles to. The background is that i support a couple of active directory forests, which due to their windows 2000 background have a default tombstone interval of 60 days. While doing nslookup it is pointing to another workstation.
Im exchange admin center gibt es keinen überordner mehr bei den. That being said, from personal experience, the longest we've ever had one offline is a couple days. Even if you upgraded to a higher domain functional. It is ultimately determined by the 'tombstone lifetime' in the forest.
Ad tombstone period issues (of course). The tombstone lifetime is set to 180 days therefore we would like to set the dfs replication time out to match.