The print spooler restart is indeed the problem.
Do you know where to remove the print spooler restart?
I don't believe you can actually remove it because it is being triggered by the client itself. But maybe someone from VMWare can tell you that (or just create an SR).
What we eventually did (because we did need the restart of the spooler service) is create a script that installs the printer and set a wait command in it. This way the printers are being configured correctly.
For now the only workaround provided by support is to add a scheduled task with delayed start and a repeat after 2 minutes (depending on your appstacks) which starts a uemrefresh.
I don't really like these kinds of workarounds, but for now it will do. (It is this or no appvolumes)
i have the same issue with appstack and network printers installation. My workaround is to create an appstack with all printers drivers.
Are there some updates on this AppVol - Printers - Spooler Issue? We have a simular issue and I am searching for input on this matter - thanks!
For as far as Appvolumes goes I don't think there will ever be because Appvolumes needs to restart the print spooler, otherwise printers added in an appstack won't be there. These printers are mostly PDF Printers (like Adobe PDF printer).
The only thing I can see happening is that Appvolumes sends a trigger to UEM (it will be intergated more and more) to attach the printers after print spooler restart but that's just my 2 cents.. We use a different tool and I would like to see an "open" trigger or maybe even an event so that "the other application" knows that Appvolumes is done and the print spooler service has been restarted. Maybe even add an option to start another service or application after the print spooler restart.
I was still using this as workaround!!