Package Permissions In Sql Server

Hi, first post here. Sorry, I know there are a million threads on this kind of topic, but none of them have helped me (nor anything else on the Internet).

Here's my situation (trying to give as much detail as possible):

I have a package that I made on one computer. The package opens an ODBC connection that requires a password, runs a query, does a few quick transformations, and then finishes with a script task destination.

First off, the package runs fine in BIDS. Then, I recently moved all my development stuff to a new server. Package still runs from from within BIDS.

I'm logged on as Administrator, which is the same user SQL Server, and all its parts are running as (including the Agent, and SSIS).

Now, I want to schedule the package to run in a job (which I already have set up with other steps by the way) in Sql Server. I have tried all of the following, and none work:

1) Set the package to encrypt sensitive with password. Then loaded the package into the job step from the file system, went to the command line tab and was prompted for, and entered the password. Didn't work.

2) Set the package to don't save sensitive, and created a configuration file with the password (also tried it with the entire connection string) saved. Created a job step for the package and added the configuration file. Didn't work.

3) With the package changed back to encrypt sensitive with password (and the config file removed), I imported the package into the SSIS Store from the file system. Then I had it set the imported package's security to encrypt with user key. Right clicked the package in the store, and did "Run Package." It runs perfectly, without prompting me for the password. Then I set up a job step, and point it to the package in the SSIS Store. Doesn't work.

4) Set up the package to create a deployment utility. Deployed the package to the SQL Server, using the option to "rely on server storage for encryption" and entering the password for the package. In SQL Server, I see it (under MSDB), I right click, "Run Package", and it runs perfectly without asking for the password. I set up a job step and point it to that package. Doesn't work.

Currently, I'm running the package by creating a simple batch file which calls dtexec for the package (with /DECRYPT mypasswordhere). Then I have this batch file being run under the windows scheduler. This works fine.

So then I tried using this command in a job step with cmdexec, instead of an SSIS step. This fails as well.

The only thing I have not tried yet is setting up a proxy account, but I don't really want to do that, and I don't see how it could help, considering everything is using the same user.

I know I'm not really being specific here with error messages and logs when I say the steps fail, but that's mostly because I'm not sure how to get good error reporting out of this. Any help with that would also be appreciated.

Please help, this is driving me up a wall.