The permanent fix was to rebuild the Appstacks with a AppVolumes template that was created fresh from 2.14.2.
Support said there wasn't going to be an issue having the 2.13.2 agent on the provisioning VM.
We are on 2.14.2 on both agent and manager sides. Only the provisioning VM is on 2.13.2 to workaround this issue.
Ahh, OK. I am doing the same thing now, too, and so far so good as I'm now able to update each AppStack and in each one, I'm enabling Windows Search again. Unfortunately that means we are going to have to go through all of our AppStacks and do this. Ugghh.
So far I have not had any luck using a capturing/provisioning VM with the older 2.13 agent and fixing our AppStacks. I've re-enabled the Windows Search service in it, but somehow the service is still being disabled on the VMs that we push the AppStacks to.
I did another test by using the new template and that does fix the issue like you said. I'm not sure how we are going to proceed here, as we have a ton of AppStacks that would be great if we could fix, but so far no luck
