I have built the manifest file which works just fine when you deploy it. I want to be able to include the run schedule in the deployment package too. I want the Database Admin to be able to just double click the manifest file and him set a location and the schedule will already be there. (Schedule as in, the dts package runs every night) I don't want the DBA to have to go out and manually schedule it, he screws up enough stuff. I'm using SQL Server 2008 r2. Thanks, Rob

As far as I know deployment manifest file is just to deploy the package and not to schedule it. So I don't thik it is possible. You can create a sql agent job for the package, schedule it, script it out and give the .sql to your DBA to execute the same on other server by changing certain parameters( like server name, command).Nitesh Rai- Please mark the post as answered if it answers your question

You can execute the manifest using a batch as the first step and then schedule it to run as a second. Nitesh gave you a good idea by the way and if you want the package to run off the file system then you can use script below to schedule a Windows Task Scheduler job. strComputer = "." Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set objNewJob = objWMIService.Get("Win32_ScheduledJob") errJobCreated = objNewJob.Create _ ("Notepad.exe", "********123000.000000-420", _ True , 1 OR 4 OR 16, , , JobID) Wscript.Echo errJobCreated Arthur My Blog

Great idea. I will try that. Thanks!