what happens when you click on one of the radio buttons next to 'daily' or 'weekly' ? my gui looks the same, and i'm able to select any of the items on that list.
The deploy jobs is suppose to execute only once as it changes the state of the system which will occur only once. Such as application deployment or changing a registry settings or adding a user . However it totally depends upon use cases that needs to be automated . There's a workaround that you probably would like to use is to include the deploy job as part of batch job and then schedule it daily, weekly or monthly.
It's gray-out and I can't select it, with both ways (also with the workaround)
One more update, if we select a file deploy job than the daily/weekly etc .. schedule is OK, but with blpackage or software deploy job, than the daily/weekly/monthly/interval schedule is gray-out
1 of 1 people found this helpful
1) If you include the bldeploy job as a part of batch job then you should be able to schedule the batch job .
Please check the screen.
2) The file deploy job can be executed multiple times which does not necessarily changes the state of the system.
OK it's works, But the truth is I really want to understand why it is not working properly, because in the end I should explain it to the customer...
The reason is that blpackages and custom software packages have been create to execute only once but not daily/weekly/monthly . For example, you would be creating a custom software package consisting of McAfee AV v9.0 and you would be executing it only once as it will install the AV successully . You would not re-run or schedule it cause the custom software package is suppose to execute only once .
However I agree that it should not happen in case of blpackages as the use case that you are trying to automate could be different which requires blpackage to be scheduled. There's an RFE files for this one and it will be available in next releases .