1 of 1 people found this helpful
1 - BSA will automate all of this, so it will handle copying the patches to the targets and running the patch. this can happen at different times if you want.
2 - it really depends what you want to do. you can run the deploy and push the patch at the same time, you can stage the patch files before the deploy, you can mount a file share during the deploy and pull patches from there. blade will automate all of that for you.
3 - yes, you can automate this.
4 - yes
5 - yes.
Thanks for the reply Bill
1. Point Clear to me.
2. Point Clear to me.
3. Where are those option , could you please give me some clues on that ? Is it in pre / post task of patch remediation ?
4. Same to the third point.
5. How to do this suppress option ? Is it via pre / post tasks ?
3 - you can create a nsh script job that does a reboot, and waits for the box to come online - you can add that to the batch job that's created for patch deploys. there are a few of those scripts on the communities here. i would also submit a rfe for a pre- deploy reboot option in jobs. for the post- part you can use the reboot options on the job and say 'reboot at end of job'
4 - in the pre/post of the job you can run any command you want, so 'net stop <service>' or 'sc <whatever>'
5 - you can control the reboot options during deploy so no reboot is initiated until the end of the job, or ever, but it sounds like you want to get run of some warning message? if it's a command line thing, put it in the post- command of the job.
Thanks Bill for your help.