I'm running 8.5 RU2 with persistent connection, and I love how real time many things are.
I have noticed, though, if I'm deploying an image with many software installs that install as post image tasks, often patch will begin installing titles and this creates a conflict causing my software installs to fail.
For example, we have a technology lab with several adobe titles, several autocad titles, etc. It can take these image jobs 80+ minutes to complete.
The agent should somehow be smart enough to not allow these install conflicts to happen. Please don't suggest I start building fat images building the titles into the image, that's just bad practice. If I need to update Photoshop on 3 labs, I don't want to rebuild 3 images, I just want to update 1 post image task used in the 3 lab imaging jobs.
For now, I'm just disabling all my patch policies when we image those lab machines, but that's not ideal and a little bit of a security risk as someone needs to re-enable them.
I don't want to not put the patch plugin on the base image because as soon as it attempts to install, it kills the agent mid whatever it's doing. I thought about having a dummy file placed at end of image time and then scope the patch plugin to only install on computers with that dummy file, but again I think this would also a timing issue because existing machines in the console being reimaged would fall into the filter and attempt to install the agent as soon as they come up.
Thoughts? I am sure I posted this issue before, and I looked through my post history, but couldn't find it, so I apologize if I'm repeating myself to some.
I'll put a ticket in as well.