See above. I'm seeing (a LOT) of reports on my McAfee ePolicy server that C:\Program Files\LANDesk\LDClient\startasuser.exe is trying to terminate various McAfee processes, including C:\Program Files\McAfee\Common Framework\naPrdMgr.exe, C:\Program Files\McAfee\VirusScan Enterprise\EngineServer.exe, etc. In some instances, I'm seeing this from the inventory scanner, of all things!
I'm sure it's some kind of package I built, but I think I've only used the Run as Currently Logged in User setting on one package--and that one was never assigned to the machines that I'm getting the McAfee alerts on.
Any idea where to start on troubleshooting this? I can (probably) exclude the Landesk processes from the McAfee scans, but I don't know that that will help, since it's actually the McAfee self protection that's knocking it down.
On the flip side, it doesn't seem to be affecting either product, just completely cluttering my ePolicy logs.