We experienced this same behavior with our 4.1.2.0 testing last week with the OSX agent. I was going to open up another case for it but I guess I don't have to.
We were able to get it to auto-start on startup by installing the agent a 2nd time overtop of itself. Seems it puts the correct permissions on the Agent in the postupgrade script in the package -- but not in the postinstall script in the package. I was going to just try swapping names of the files around in the package and try it, but not sure if CCA does any CRC checking on the file and then dump it back up to where the agent file is stored on the CAM. --greg
