Is "msdb/" part of the package name or are you indicating that it's stored in msdb? If it's the latter, you don't have to specify that.

If you would rather store the package in the files system, as I do, set the pacakge protectionlevel to "EncryptAllWithPassword".

See this thread: http://www.sqlservercentral.com/Forums/Topic619676-148-1.aspx

Open the diagram in SSMS, right-click in open space of the diagram, select "Copy Diagram to Clipboard", open something you can print from e.g. ms Paint or Word and paste.

My mistake. I should have said, "whichever admin login you want to run the job. When I've created a credential, I've used the login which runs SQL Server...

It will be whichever non-admin login you want to run the job. If you click on the "Add.." button you'll see your choices are logins, server roles, or msdb...

Whether the databases are critical or not, I think restoring backups would be the best way to recover.

No. They'll be able to start the job but it will still fail on the package step. You need a proxy that has been configured to use the...

The db_dtsadmin role is not applicable to DTS packages. Regardless of whether the job runs a DTS package or an SSIS package, you must create a security credential and...

Good advice. Since the Transfer Objects Task is no longer available in the Import/Export Wizard, scripting is the easiest way to copy views.

I'm interested in this subject because we're preparing to move a server into a DMZ also. My understanding is that the server in the DMZ shouldn't be able to...

Use the Transfer SQL Server Objects task to copy views.

Check the permission properties of db_dtsadmin and verify that it has execute permission for sp_dts_listfolders. It does in all my SQL instances and I think that's the default. ...

Mh,

The script will work for copying logins to SQL 2008 because logins are essentially unchanged between 2005 and 2008.

Although I haven't had a problem editing a standalone package, maybe your problem is the one in this kb article. It might be worth trying the workaround?

http://support.microsoft.com/kb/920298

I'm able to edit the packages after moving them to the server select "Package Configurations" from the BIDS menu, and edit the configuration file path.