Rather than doing a batch-based install (since batch can be - let's face it - 'a bit special' at times) ... have you considered doing it as a provisioning job?
Provisioning is perfect for things that need to run sequentially & go through reboots. Yes, it's "named" for deploying OS'es, but folks have been using to distribute complicated packages for as long as it's existed .
That way you can do individual install steps / call individual scripts / batches as needed, do your reboot, and then continue post the reboot?
That was the second resort we thought of but the issue was like we need user to have deferral options available. Which was not there for provisioning job..
You can make provisioning jobs now be regular policies (assuming you're on LD 2016 ?) -- so you can just send a message out to your users - "here's the icon I want you to click in the portal when you're OK with the machine rebooting / needing 30 minutes to install the new AV" - or something to that effect.
Comms is half the battle (won) .
Wouldn't that sort your problem out ...? (Unless you're not on 2016 of course).
Holding my horses on this one ... need to confirm this (might have been dreaming things up). Pretty sure we can do provisioning tasks through the portal now, will try to confirm later in the day when I get some time today to play with this.
Yep - it's all good. You *CAN* make provisioning packages appear as regular packages ... we've introduced that in early 9.6 in fact:
... so if you're on 2016, the provisioning package is hiding as a "Universal Package".
... so you can treat it as a regular package there (rather than straight-up scheduling the provisioning template).
So - that should sort you out .
Did Phoffman manage to get you a satisfactory answer here? If so, please mark his answer as correct.
If you are still needing further assistance please let us know that as well.