John Rowan (9/29/2016)
The solution files are only needed for development. Once you've built the package into it's .dtsx file, the solution is really not needed. Your job is not calling the solution, it's referencing the .dstx file. So just move the .dtsx file over to the new location and make sure the job step references it there. I'm assuming from your post that your jobs are referencing file system packages and not packages in the catalog.
Hi John, I think your right, I was expecting it to copy the whole lot, but it didn't. So I ended up using File Explorer, and copied the whole project folder to the share drive. then I opened VS, nav to the share, opened the main file, all was there. So I went through turning off the encryption on each of the .dstx packages. All was going well, until, I renamed the package name, then, every single package became "lost" as now there is no content.
So clearly, it's not so easy to copy an existing solution lock stock and barrel, remain intact, rename it, and plunk it into another location. I want to make a renamed copy of an existing solution over to another share drive, so I can make mod's to it, and not loose paths, pointers, etc... is there a step-by-step for this task?