Here’s one more new KB article we published this morning. This one talks about how to allow App-V clients to print to HP UPD printers:
When using the Hewlett-Packard Universal Printer Drivers (HP UPD) with the Microsoft Application Virtualization (App-V) client and trying to configure a printer through the Enter a Printer Address... dialog box, you receive the following error:
--------------------------- Error: HP Universal Printing --------------------------- Invalid Address.
Verify and re-enter the address, or use a different address. --------------------------- OK ---------------------------
This behavior is by design. By default, App-V does not allow access to global objects such as semiphores and mutexes from within App-V. These objects must be explicitly excluded.
To allow App-V clients to print to HP UPD printers use the following steps:
On 64-bit machines, this will be located at:
For example, add values 94 and 95 where the highest ObjExclusions value is 93:
Windows Registry Editor Version 5.00
Note that this solution assumes that the printer is otherwise accessible and that other, identical clients are able to connect to the printer.
For the most current version of this article please see the following:
2626751: Error: HP Universal Printing | Invalid Address when using the Hewlett-Packard Universal Printer Drivers with Microsoft Application Virtualization
J.C. Hornbeck | System Center Knowledge Engineer
App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
So does this apply both for 4.5 and 4.6 RTM?
Is this from within an App-V application or is this if you using the universal drivers for your printers and then trying to print from an App-V application. A little more detail would help. We use the universal drivers and have never seen this issue.