>>However, the best approach in this scenarioo is to put your COM component into MTS/COM+. There you can set the executiion context of the package by assigning a speicific user to it. But it'll run slower in MTS and there's more admin overhead in getting components installed and updated on the server (and debugged on the local machine).
>>
>>
>>+++ Rick ---
>>
>
>Also remember, if you set the identity of your packages, the components will run without someone being signed on the web server. Could you explain in more detail your last sentence? I have not found that this causes any extra admin or debug overhead.

You ahve to install the component in MTS. It's an extra step in the development and deployment process. And it's considerably slower running the component in MTS.