I have developed an SSIS package which uses an XML configuration file for connection information. It runs fine both from Visual Studio and from an Agent job after I specify the location of the XML configuration file in the Agent job definition. My question is regarding the target location of the XML configuration file after deployment. Ido my SSIS development on a local workstation with SQL Server 2005 DE and Visual Studio 2005 installed on it.I deploy my SSIS packages to a remote SQL Server 2005 SEserver. Both machines are running SP1.I double-click the package manifest from my local workstation and specifiy the remote server in the deployment utility. The package gets deployed to the remote server just fine but the XML configuration file ends up on my local workstations C:\Program Files\Microsoft SQL Server\90\DTS\Packagespath. I would have expected that the XML configuration file would have gone to the same path on the remote server, where the package itself was deployed. Obviously, when I run the deployment utility from the remote server, it stores the XML configuration file in the same path on the remote server. But this is not a workable production solution.

There is now an utility available in CodePlex which can be used to batch update SSIS Package Configuration File paths without using BIDS: http://ssisconfigeditor.codeplex.com/