I need to get going on this again, I had most things set up but was having trouble installing some applications.
What I was doing was building a "large" number of installs into a policy and running that after joining the domain and name change and inventory. But some of the apps were erroring, didn't matter if I uploaded the installer or if it was winget. My theory is that the system needed a reboot, but previous policies should have taken care of that. Also getting in the way was the fact that if the first install failed, it would skip all the other items in that policy, even when I set it to continue. This was all on v1.5.8 but I don't think there were too many changes in 1.6.0 aside from some security/bug related changes.
So now I'm wondering if I should build a single policy for each application and set it to reboot after each install? or figure out where a balance point might be for reboots and set the reboot as a separate policy in the chain of events?
Having 20 reboots is not something I look forward to seeing, but it might be the only way.