Moving a file fails after copy to share with ABE Enabled

Question

We have a 2019 Windows Server with an application that will copy files to a location and then immediately move it. The share has ABE enabled on the file server (also 2019). If the file is copied to a location in a share and moved within a second after it will say the file is missing/can't be found. One server is in azure and the other server in our datacenter with SDWAN tunnel. If I perform the same action on a server local to the file server there are no issues. If I disable ABE on the file server I can copy and move the file immediately without issue.

Is this a problem with Latency (30ms), ABE, or can something else be causing a delay. If we wait 3 seconds it works just fine with ABE enabled. I have tried messing with firewall, smb, nic types and it doesn't seem to matter.

Any help would be appreciated.

Answer 1

Hello @derek deckert

You are right, this is an observe behavior from Access Based Enumeration implementation. There is even a full reproduction investigation on this phenomena:

https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/access-based-enumeration-abe-concepts-part-1-of-2/ba-p/400435

Hope this helps with your query,

--
--If the reply is helpful, please Upvote and Accept as answer--