Looking for some advice if possible about deploying packages that have dependencies, and need reboots?
I'm deploying .NET Framework 4.6.2, Microsoft Management Framework 5.1 and finally the Microsoft UEV Agent.
I created packages for all three, that work in isolation if I manually install them from DSM, reboot, then install the next, however as part of a software set they fail. I believe the issue is that they need a reboot from the previous step before the next package can install.
I thought there might be a way to get DSM to retry a package if it failed after the next reboot, but I can't seem to find it if it exists.
I don't mind if they are part of a set, or how I deploy them, I'd just like to try and find a way to handle this if possible?