DanVM99's Posts

I can confirm that I've tested putting these registry keys in our AppStack template and any new stacks are problem free as a result. I did also find that you can go and manually edit the snapvol.cfg file when updating an existing AppStack by unhiding system files and going into C:\snapvolumestemp\MountPoints\sid during the provisioning process. In there you can add those two exclusions into the snapvols.cfg file before sealing up the updated stack. The resulting updated stack contained a working CutePDF printer for me. One other thing I have noticed is that the printers shown in Windows 'Devices and Printers' appear to differ from those shown when attempting to print using any captured applications delivered with AppVols. I seem to only have CutePDF and one other network printer in Windows but when printing from a virtual app like Adobe Reader or Word I have additional network printers that appear to have been brought through from my host PC.. There's probably a simple explaination for this but I can't work it out. I thought Thinprint would bring these network printers through into the Windows 7 VM being served up from View and not AppVols presenting them exclusively through the virtualised apps..

That's useful to know thank you. Just hope VMware get this issue patched asap. It's a real pain having to go through the full back, uninstall, reinstall plus agent updates x2 environments each time they change something though.. Really need a separate patch mechanism.

I've come across this issue despite upgrading to the very latest v2.12 121516 version  of AppVols. Though we're attempting to install CutePDF within an AppStack with a group of other "Standard Applications" like Office, 7-Zip etc. Does anyone know if AppVols captures printers successfully, or do they need to be installed in the Gold image? Thanks