First MCX/AD attempts- policies not applied to machines

[elvisizer]

Hello AFP world. I’m making my first attempts at managing macs using MCX delivered through AD. My AD admin has just finished extending the AD schema on our development domain for MCX. I can bind to that domain from my mac, and I can see users and groups from AD in workgroup manager. I can even authenticate and create policies in WM without errors.
The problem is, none of my MCX policies are being reflected on client machines at all. I’ve applied policies to both single machines and computer groups. Running mcxquery -computer gives me a listing of all the policies I’ve created for the machine specified, but the MCX area in system profiler is blank, and like I said, none of the policies are actually getting applied.
Any tips for things I should look at first?

edit: hmmmmm . . . . computer accounts created by binding are not populating the ethernet ID on the network tab. I know that was required to get MCX working with a local directory– does the Ethernet ID need to be populated in AD as well?
I did try to just add it manually, and got a “Error of type eDSNoStdMappingAvailable (-14140) on line 331 of /SourceCache/WorkgroupManager/WorkgroupManager-361.3.1/Plugins/ComputerAccounts/ComputerNetworkPluginView” error.

[elvisizer]

so, the macAddress attribute was missing from that AD environment- I had the AD admin add it (he was surprised it was missing since it is in our production schema) and new machine accounts are populating it and applying policies successfully.

[Author]

Posts