MCX System-Wide items won't take

[Sandy]

Hi!
I am stumped. I have a lab that is re-imaged and added to an MCX
profile in Casper, but will not take the startup/system wide prefs. My
test machine in my office works perfectly, imaged w/ the same config.
I've re-imaged a couple times and every time, my test machine works
and the lab fails. Local user MCX settings ARE working on the lab. I
initially had the lab in the MCX profile as a smart group, but have
now tried a static group, no difference.

I have wracked my brain for why my test machine works and lab doesn't.
Same imaging config (10.5.8), all same policies apply, no ip
restrictions on any applicable policies. Different Subnet, different
imac model (slightly) and different records in the JSS of course.

When I look at the /Computers/localhost file, the login screen message
and other system wide settings are there, but the Managed Preferences
Folder never gets populated with these settings. I compared this file
on the non-working and working, and it is same.

I started out w/ MCX framework being applied only to these computers
using scripts, but now have enabled MCX in my framework, since I'm
headed that direction. This is the only profile right now in my JSS.

I have lost my O.D./WGM. We're ramping up AD as fast as possible with
no schema-edit and only XtremeZ-IP for mac clients, (no admitMac or
Centrify, etc) . All my computers are currently unbound, roaming the
prairie freely ...
Anybody have suggestions on how to fix or what else to try?

This issue was happening in JSS 7.3.1, and still now is 8.0. though
everything else is working great... :)
Thanks!
Sandy

[tlarkin]

I have seen this happen when OD and Casper conflict with each other. Delete the com.jamfsoftware.mcx file under Managed Preferences in /Library and then reapply them.

[Sandy]

Hi,
I have finally figured out why my 10.5.8 Casper MCX system-wide settings are
not working... but how to fix?
In the file:
/private/var/db/dslocal/nodes/default/computers/localhost.plist
it shows the Airport MAC address, instead of the built-in. If I edit it to
the built-in, System-wide settings take effect.
How can I fix this the Casper way?
Thanks!
Sandy

On Mon, Dec 20, 2010 at 10:38 AM, Thomas Larkin <tlarki at kckps.org> wrote: I have seen this happen when OD and Casper conflict with each other. Delete the com.jamfsoftware.mcx file under Managed Preferences in

/Library

[#4]

Sandy,

were you ever able to fix this issue? I'm seeing it now on 10.5.8 clients
using Casper 8.22.

Cheers,
Clinton Blackmore

[nessts]

dscl . -delete /Computers/localhost ENetAddress
dscl . -create /Computers/localhost ENetAddress $MACaddr
assuming you set the proper MAC address prior to that command in a script it should be the ticket for you.

--
Todd Ness
Technology Consultant/Non-Windows Services
Americas Regional Delivery Engineering
HP Enterprise Services

[#6]

Thank you, Todd! That's great.

I've turned off the "Apply Computer Level Enforced Managed Preferences"
setting, and created the following script, based on your reply:

-------------
# ApplySystemLevelMCXSettings.sh

# Work around that ensures MCX settings are applied from Casper
# using the proper MAC address.

if [[ $EUID -ne 0 ]]; then echo "This script must be run as root" 1>&2 exit 1
fi

jamf mcx
dscl . -delete /Computers/localhost ENetAddress
dscl . -create /Computers/localhost ENetAddress `ifconfig en0 | grep eth |
cut -c 8-`
---------------

I put in a policy to run this at startup, ongoing, and to run it on our
every30 trigger, once a day.

It appears to be working.

Thank you so much for that prompt reply. I have submitted a bug report to
JAMF.

Cheers,
Clinton Blackmore