Can you check the apm.xml on the client machine and see if it is empty? If it is then the client isn't getting the information from the core that it has an optional policy to install.
Any luck on this? We are seeing the same behavior, the apm.xml file has a cached portal task in it, and shows a recent time stamp but is not updating the contents accurately.
we are seeing issues with the portal due to the client not flipping automatically to/from direct and gateway mode. setting this to one or the other manually fixes it for us.
I would also add that Mac software tasks delivered via the portal that contain multiple (main and final) distribution packages seem to crash the task permanently on the server when run. We are just seeing this in the last few days so just an initial observation. Moving this one to the software distribution forum.