<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A18IqTCQUOkta Classic EngineIntegrationsAnswered2024-02-22T16:22:32.000Z2024-02-21T21:49:15.000Z2024-02-22T16:22:32.000Z
  • IanM.34980 (Farmers Insurance Group)

    During an AD integration setup, you choose which OUs to include.

  • BrianT.01893 (Customer)

    Thanks for the tip. To check this, I went and removed the agent from one of the servers. I deleted the agent folder, rebooted and re-installed the agent. I did get prompted during the setup to select any OU's to import. This is agent v3.16.1 on Windows server. My guess is the agent is ignoring some Object Classes. It seems to only import Class: Container and Class: Organizational Unit. The Builtin has it's own class builtinDomain. Other missing OU's have thier own class as well like, lostAndFound. Is there a way to added the builtinDomain class to the import list or do I need to migrate these groups to another OU? The builtin seems to be a legacy from older AD.

    Expand Post
This question is closed.
Loading
AD Integration - Builtin OU missing