On Apr 28, 2012, at 3:02 PM, Arno Hautala wrote: > On Sat, Apr 28, 2012 at 12:47, objectwerks inc <[email protected]> wrote: >> >> On Apr 28, 2012, at 10:33 AM, Dinse, Gregg (NIH/NIEHS) [E] wrote: >>> >>> Also, even if I should not care about it, I do not know how to stop it >>> from running. Mainly I am concerned because it dominates my Console logs. >>> These same 15 lines of "error messages" are repeating every 5 or 10 >>> seconds, so it is difficult to see any other messages because they are >>> buried in millions of lines of centrify/McAfee messages. >> >> why bother? My point is: if this is a centrally managed machine, >> supposedly, and they don't support Lion, but you installed Lion, why rock >> the boat? I don't know how your IT dept is but I would not want to involve >> IT in anything I did not have to. > > If it's anything like my experience with Centrify, it's down to trying > to audit / push out unsupported hardware. The Windows machines are > handled by external IT and Centrify compatible hardware must have that > installed. IT then uses Centrify to log in and inspect the installed > software, looking for security flaws (without checking for backports). > As soon as a few flaws are identified, the hardware is kicked off the > network until justification is supplied. Maintaining the OS and > packages is up to the user. > > I don't know if it's the same in this case, but Centrify may be > required for the machine to stay on the network.
He does not seem to be off the network now, so I would continue to ignore Centrify and let the errors go to the console. If it becomes a concern, worry about it then. _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
