• 0 Posts
  • 51 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle


  • Yep, instant sync is never a guarantee. There still has to be a queue for command messages along with authentication plus authorization of said commands. And just like you said, you must be connected to a network that then can reach their cloud to even receive the command queue.

    I run a sync service between multiple Active Directory domains as a result of a merger and the directories haven’t been cutover yet. Along with this sync is a password sync that is normally instant. Most of the times (> 90%), less than a second. Sometimes 3 seconds. Other times? 2 minutes. Even when things are within the same LAN, there’s the possibility of a backed up queue.

    So yeah, this is purely on him trusting the sync implicitly and not verifying. In my case, I trust it too but will on occasion have to assist users because it’s not infallible. Karma got him and I have zero sympathy.















  • Hilariously, I bet it’s because their Active Directory domain is the same as their public domain, and it becomes a massive pain in the ass to hostname the root domain. Yes, externally you can do it just fine, but then it’s not consistent internally on their private network.

    One solution is you run IIS (or any other web server) purely as a permanent redirect for the internal host, but it would then need to run on each domain controller which brings its own set of issues.