Active Directory plug-in default mcx settings

[kennyj]

Hello,

I’m trying to deploy Symantec Antivirus with the Symantec Administration Client to about 150 machines. Right now I have my server up and running, and am testing the client’s functionality.

I have run into an interesting problem that I hope someone here can possibly point me in a different direction. I can do everything except to push a virus scan down to a client. Digging around on Symantec’s enterprise support knowledge base I found that this can happen if you are using MCX. Here’s the knowledge base article on that: [url]http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/0a6bec82ff10be118825748e0079841d?OpenDocument[/url]

My first thought was… hey, I’m not using MCX. However, it turns out that once a client computer is bound to Active Directory, there are some default mcx settings that get pushed to any network accounts. I have mobile accounts turned on as it is the best solution for our needs here. The accounts show as managed, mobile.

“OK,” I thought, “I’ll try ripping out the mcx pref files from /Library/Managed\ Preferences/username and everything will be fine.” This did not work as the settings are applied again after you log back in as that user. Right now the only thing I can think of to fix this is to push mcx settings to all my machines. Does anyone have any suggestions on how to disable the default mcx settings being pushed by the AD bind plugin?

Thank you,
Ken

[kennyj]

Argh, I need to do some more testing. It seems that Symantec is wrong in their knowledgebase article. The services they refer to not being able to run under a managed user is incorrect. I do see them running when use ps and grep for them. Some run as the logged in user, one runs as root.

[Author]

Posts