Richard writes:

We had problems with .ini file.  It wouldn't show all parameters in the .ini file, only top 15.

That's good to know.  We have a VB script that uses an INI file that is assumed to be the same name as the package.  For deployment, we set only a gINIpath variable (UNC path) to tell it where to find the INI.  All settings are then in the INI, with no parameters.  Typical variables at the moment are source/target UDL path, production source, production server, test/prod folder paths, start/end date.  The packages all determine whether the source UDL connection is "production" and will export to production folders if it is.  We store the package and INI in VSS as it should look in production so we don't have to change anything for a production deployment.  It works pretty well.  Dynamic properties make me

We don't have more than 15 parameters in the INI, but I'll bring it up as a potential risk.

One would do well to realize that DTS doesn't need to "run on a server".  I'll be making a push soon to store them as .DTS and run them from a production folder path.  That comes right after obliterating our dependency on our Exchange server.