AFP548 Changing the world one server at a time.

One client bound to OD won’t eat mcx/settings

Home › Forums › OS X Server and Client Discussion › Open Directory › One client bound to OD won’t eat mcx/settings

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #380924
    p0ddie
    Participant

    Hi there,

    I have a problem that weirds me out.

    I have an OD (10.6.6 OD server and replica) managed network with several clients (10.5/10.6), computer groups with settings and so on. Everything works flawlessly with the other Macs.

    This particular 20″ C2D 2.4GHz iMac was restored from a DeployStudio image with 10.6.6 and automatic binding to the OD (this image works flawlessly on at least 10 other Macs – older and newer ones, e.g. a 2008 Mac Pro or an i3 iMac). This guy however, when bound to OD, does enable me to login users from the OD, but it won’t display e.g. the customized login window, in fact, System Profiler -> managed preferences shows “no data found”.

    Things I have done so far:

    – triple checked the computer account has the right MAC associated and is in the right computer group
    – deleted and re-entered the MAC of the iMac
    – tried with the hardware UUID (although the first characters are zeros, so this Mac is managed by his MAC address)
    – unbound and rebound the machine to OD
    – unbound and rebound the machine to OD with trusted binding, creating a computer account in the process and adding that account to the computer group
    – re-imaged the whole thing again
    – switched from dhcp to a static IP
    – used dscl to query the directory (everything shows, the computer record also contains all the correct infos from what I can judge)
    – zapped the pram of the iMac (weird thing: after zapping and rebooting, OS X told me there was a new network adapter and found the Ethernet adapter again, same MAC tho)
    – updated with Apple software update server to 10.6.8

    I seem to be missing something that prevents this machine from respecting its OD settings… but what? This is quite annoying since I need the machine to be in the right computer group to install tons of software with munki.

    I could try completely formatting the drive again and installing from an OS X disk, but that defeats the purpose of the nice DeployStudio/OD/munki thing I have going on here…

    Does anyone have a good idea what is happening and more importantly, how to fix it?

    TL;DR: An iMac is freshly imaged with an image that works with other iMacs and does not respect his MCX settings although it is in the right computer group.

    Thanks!

    #380940
    p0ddie
    Participant

    solved… sort of. I used a retail 10.6.3 installer, erased the disk and rebound to OD, now it accepts the mcx settings. Strange as we have the same instadmg base image on roughly 100 machines, all of them work.

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