If you're used to administering your SQL Servers using Windows Authentication, one side effect is that you'll end up owning a lot of databases, jobs, plans and packages. Sometime this has undesirable effects such as a job or package not working properly. But it's not always obvious how you can change the owner of a package once it's created. Note that it is slightly different for each version of SQL Server. Before I learned this trick, I would literally delete and recreate the package when logged in as SA just to get the package under the proper owner. Otherwise, every time you edit the plan, the job owner will change to match the plan owner which could cause the job to fail.
SQL Server 2008 Maintenance Plan or SSIS Package
--change the owner of a SQL Server 2008 Maintenance Plan or SSIS Package
UPDATE [msdb].[dbo].[sysssispackages]
SET [ownersid] = 0x01 --sa user
WHERE [name] = 'YOUR_MAINT_PLAN_OR_PACKAGE'
SQL Server 2005 Maintenance Plan or SSIS Package
--change the owner of a SQL Server 2005 Maintenance Plan or SSIS Package
UPDATE [msdb].[dbo].[sysdtspackages90]
SET [ownersid] = 0x01 --sa user
WHERE [name] = 'YOUR_MAINT_PLAN_OR_PACKAGE'
SQL Server 2000 Maintenance Plan
--change the owner of a SQL Server 2000 Maintenance Plan
UPDATE [msdb].[dbo].[sysdbmaintplans]
SET [owner] = 'sa'
WHERE [plan_name] = 'YOUR_MAINT_PLAN'
SQL Server 2000 DTS package
--change the owner of a SQL Server 2000 DTS package
--note you need to update the owner column as well
UPDATE [msdb].[dbo].[sysdtspackages]
SET [owner] = 'sa',
[owner_sid] = 0x01 --sa user
WHERE [name] = 'YOUR_DTS_PACKAGE'
