Has anyone ever seen, or does anyone have a reason that would explain why when I install (either a push from ePO or manual install) the Agent on a computer that has a Canon printer driver installed the agent gets installed into "C:\Program Files\Canon\Easy-WebPrint EX"?
The agent operates fine, and can be updated without issue. I am seeing it on a handful (10 out of 8000 endpoints) so I don't believe it is a issue with permissions, or group policies getting in the way.
Recently I had to repair an agent, so I ran frminst /forceuninstall from the McAfee\Agent folder under Program Files and deleted the Agent folder prior to reinstall; upon reinstall (since the Canon driver was now installed) it reinstalled to the Canon folder.
This issue has existing since at least 126.96.36.1993 and we are currently running 188.8.131.528 so it doesn't seem to be version specific either.
Thanks for the suggestion Dutchman39, I should have checked that first. Alas, the variable is pointing to Program Files as expected.
Sorry, let me clarify. (the downfall of talking in shorthand)
Does teh Cannon software perhaps change the NTFS Permissions on \Program Files?
LOL. I kinda wondered what path you were going down with that last question. But to answer your question, no, permissions on the Program Files folder look the same as they always did.
Having said that, I suppose the Canon installer could change the perms on the folder during install, but I'd be surprised if that was the case.
I am going to grab a spare machine and install the Canon driver and play around, I'll watch the folder permissions during install.
I'm grasping at straws a bit, but, if you switch into the SYSTEM account using psexec, is the Program Files variable still correct?
If you push an Agent package that explicitly sets the install directory instead of using the Program Files variable, does that go to the right directory?
A good questions tkinkead, I've actually be using psexec interactively to access a users machine remotely to check settings. Alas, the Program Files variable is the same for both the user and System.
I've never actually tried running the installer with the install directory set, I will give that a go and see what happens.