Under Scheduled Task Properties | Select scheduled task | Select Start Later | Use Appropriate Date and Time.
Isn't that to initiate the task to download and then run? It's been a while since I've tried using this method, so bear with me (or beer with me)... I need it to download all the installer files to the local drive before log off on Friday, set to launch the install Monday morning at login... If that's the correct method, great, I just need to confirm it all before I start deploying. I do plan on testing it on a VM or two, but it will help the process along to have confirmation...
Using a prestaging method
That is why we have the ability to "Pre-stage" software. But the problem is that files are only cached for 48 hours by default and so you would have to change that in the delivery method.
There are two ways to pre-stage software.
Create Scheduled Task #1
Use a Multicast-cache only task.
Create a batch file task pointing to a blank batch file and add all the files as additional files.
Either of those methods will cache the files.
Create Scheduled Task #2 to start monday morning as Zman recommended. If
There is a lot we don't know.
Do you machines check for policies every time they login?
Will anyone login on saturday/sunday?
Are the computers on Saturday/Sunday? If not, then you can start the 2nd task as early as Friday night and use a policy.
Single batch file task
You could also deploy as a batch file task. But the problem is that without doing Multicast, you cannot change the 48 hour cache time, so you have to use multicast or change the registry key and restart the targetted multicast service on the clients before hand.
Create a batch file with a command like this. (As an administrator run localsch.exe /? for more information on local scheduler commands.
REM My Batch File localsch.exe /exe="%programfiles%\LANDesk\LDClient\SDMCache\share\folder\someinstaller.exe" /cmd="/quiet /some /other /switches" /start="25 February 2008 05:00:00"
So now you will deploy the batch file, the additional files will be included.
So you want to pre-stage the installation file first then run the task at a specifc date - is that correct? If so create a job that target multicasts the installation out to the targets first (use a Multicast delivery Method). Then create a Policy Supported Push at the given date and time.