App Volumes Agent causes Network Printers to fail to install

[taopiglet]

We have recently setup an App Volumes 2.7 Server/environment utilizing AppStacks ONLY (NO Writable Volumes).  The AppStacks are working fine on Linked Clone Virtual Desktops.

We normally deploy our network printers via Group Policy using pushprinterconnections.exe (part of Windows 2008 R2).  This has worked fine for years until we installed the App Volumes Agent on the Virtual Desktops.  Now, the Network Printers will not install on the Virtual Desktops.  The only errors we see are in Event Viewer (Applications and Services Logs/Microsoft/Windows/Print Services/Admin).  The below are the errors we see:

Error 601:  Client Side Rendering

The print spooler failed to download and import the printer driver from \\SERVERNAME into the driver store for driver HP Laserjet xxxx

Error 215:  Installing a Print Driver

Installing printer driver HP Laserjet xxxx failed, error code 0x3, HRESULT 0x80070057

We also cannot manually install printers with the App Volumes Agent installed once we have received the above errors...we get the message "Printer cannot be found". 

NOTE:  We are using the same exact Master Image to create Windows 7 (SP1) Linked Clone Virtual Desktops.  This image has 2 Snapshots...one without App Volumes Agent and one with App Volumes Agent.  This is the only difference between the two snapshots.  Linked clones created without the App Volumes Agent can install/receive Group Policy Network Printers without any issues.  Linked clones created with the App Volumes Agent installed fail to install the Network Printers.

[Ray_handels]

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.

[Sravan_k]

I was still using this as workaround!!