From the other thread, it doesn't look like this is a TFS issue. Or a CA issue. It's really just related to what Steve started explaining about package protection and then other general security related issues you can run into with packages. The gist of it is in the following article - really the same issues:
SSIS package does not run when called from a SQL Server Agent job step
You'll need to understand security context and permissions for all processes, connections, file system or database access used in the package.