AFP548 Changing the world one server at a time.

Binding to a nested container?

Home › Forums › OS X Server and Client Discussion › Active Directory › Binding to a nested container?

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #367928
    bentoms
    Participant

    Hi guys got a l’il problem I need some advice on.

    I am currently going through the process of binding several Macs to a Test AD environment but have run into an annoying issue.

    We don’t use the AD Container “Computers” for binding machines to the domain. Instead we have a Container called “Test Computers” within which is 3 folders: Desktops, Laptops & Macs.

    No I can get the Macs to bind to the domain & create themselves in Test Computers, but not Test Computers\Macs…

    Any ideas?

    #367938
    bentoms
    Participant

    You don’t have rights to that then.

    I have full admin rights to the AD Domain. So I should have rights.

    The AD Plugin just advises that it cannot find the container.

    The AD plugin shouldn’t have any issues with putting accounts way deep into other places.

    So for CN= should I just put in the container name? i.e. Macs & not something like CN=Test Computers/Macs?

    #367948
    bentoms
    Participant

    what’s the CN that you’re using?

    The CN that works is the defualt one, CN=Computers.

    Which is fine for the test rig, but when this goes live it needs to be in LBTH Computers\Macs, (\ is used to illustrate folder location).

    Any ideas how I can create them in LBTH Computers\Macs via the AD Plugin?

    #367958
    bentoms
    Participant

    Right so, the domain is mycompany.com.

    The container ‘LBTH Computers’ is directly below this with three further containers within: Laptops, Desktops & Macs.

    It’s the Macs CN that I won’t to create in.

    So i guess the FQCN is something like \\mycompany.com\LBTH Computers\Macs.

    #367961
    bentoms
    Participant

    Yep that was it.

    Thanks very much.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.