[captainulf]

I’ve tried one way by using the Applications preferences in Workgroup Manager and denying launch of the Lion Installer by way of its bundle identifier. It seems to work for network accounts even when they’re admins on the machine. Locally defined users that are admins appear to have the option of overriding the denial by providing their password so if your users are local on the machines it may not be ideal.

Also apparently denial by bundle id is a deprecated Tiger feature although it seems to work in SnowLeopard. I’ve append the MCX settings I manually injected into the appropriate directory service object. You’ll have to substitute “com.apple.Chess” for the appropriate bundle id of the Lion installer.

[code]


mcx_application_data

com.apple.applicationaccess

Forced


mcx_preference_settings

AllowUnbundledApps

ApprovedAppLaunchesOthers

DenyList-Raw

com.apple.Chess

editable


com.apple.mcx.using.disallow.list


OpenItemsInternalDrive

SystemLaunchers-Raw

com.apple.dock

com.apple.finder

mcx_union_policy_keys


mcx_input_key_names

DenyList-Raw

mcx_output_key_name
DenyList
mcx_remove_duplicates
mcx_union_as_dictionary


mcx_input_key_names

SystemLaunchers-Raw

mcx_output_key_name
SystemLaunchers
mcx_remove_duplicates
mcx_union_as_dictionary

[/code]

[captainulf]

You’d be right. That’s what one gets for not know exactly how things interrelate. Thanks for the heads up.

I have a question though. I ps’ed for mountd and noticed that several mountd processes seemed to be running

server:/ admin$ ps -ax | grep mountd
209 ?? Ss 0:00.19 mountd
27416 ?? Ss 0:00.03 /usr/sbin/mountd
27474 ?? Ss 0:00.02 /usr/sbin/mountd
27521 ?? Ss 0:00.06 /usr/sbin/mountd
27766 ?? Ss 0:00.04 /usr/sbin/mountd
27847 ?? Ss 0:00.04 /usr/sbin/mountd
27923 ?? Ss 0:00.08 /usr/sbin/mountd
28051 ?? Ss 0:00.06 /usr/sbin/mountd
28151 ?? Ss 0:00.04 /usr/sbin/mountd
2040 p1 S+ 0:00.01 grep mountd

Is that normal?

Also, has the grey bubble been adressed in another thread/article and did I just not see it? I’ve found plenty of equally frustrated posts though. You’d think there’d be an Apple KB article or a fix by now.

[Author]

Posts