none
Distributing PrinterExtension in v4 printer driver RRS feed

  • Question

  • Hi,

    In a point and print scenario , say where a V4 driver is shared on a Windows Server 2012 and a downlevel client(like Windows 7) accesses it through enhanced point and print driver. The documentation says the printer extension can be shared through Url or through media.

    But I did not find any documentation on how this is done.

    Is there a way the V3 printer extension can be delivered to the clients during point and print scenario? If so how can it be done for Downlevel client and windows 8(v4 printer extension). Also which location should the printer extension be installed for it to work. The point and print pulls only config files and not printer extension

    Thursday, June 13, 2013 6:19 PM

Answers

  • Vinod,

    You are correct that enhanced point and print only pulls the configuration files necessary to build a connection. This is the intended behavior. We expect that printer extensions are distributed using normal software distribution tools as described here: http://msdn.microsoft.com/en-us/library/windows/hardware/jj659902(v=vs.85).aspx.

    Otherwise, you can specify which URL users should go to in order to download and install the app on their own. This is used to populate an additional tab in the desktop print preferences UI which tells users how to get additional features for their connection. In the manifest, this is set by the PrinterExtensionUrl directive http://msdn.microsoft.com/en-us/library/windows/hardware/jj218737(v=vs.85).aspx. IT administrators may override this by setting this registry key on the server: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\<print queue name>\PrinterDriverData\PrinterExtensionUrl.

    Thanks

    Justin

    Thursday, June 13, 2013 8:15 PM

All replies

  • Vinod,

    You are correct that enhanced point and print only pulls the configuration files necessary to build a connection. This is the intended behavior. We expect that printer extensions are distributed using normal software distribution tools as described here: http://msdn.microsoft.com/en-us/library/windows/hardware/jj659902(v=vs.85).aspx.

    Otherwise, you can specify which URL users should go to in order to download and install the app on their own. This is used to populate an additional tab in the desktop print preferences UI which tells users how to get additional features for their connection. In the manifest, this is set by the PrinterExtensionUrl directive http://msdn.microsoft.com/en-us/library/windows/hardware/jj218737(v=vs.85).aspx. IT administrators may override this by setting this registry key on the server: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\<print queue name>\PrinterDriverData\PrinterExtensionUrl.

    Thanks

    Justin

    Thursday, June 13, 2013 8:15 PM
  • Hi Justin,

    From the link:

    http://msdn.microsoft.com/en-us/library/windows/hardware/jj659902(v=vs.85).aspx.

    I was able to find only the below details regarding distribution:

    " it could be distributed in a setup.exe or an MSI package, and advertised in the printer's Device Stage experience by using the PrinterExtensionUrl directive specified in the v4 manifest. When a printer extension app is distributed via an MSI package, you have the option of adding the print driver to the package or leaving it out and distributing the driver separately. The PrinterExtensionUrl is shown on the printer preferences experience."

    Some questions that I have are:

    1. For a Windows 7 OS which connects to a V4 driver, how should this MSI be designed, where should the printerextension.exe(desktop) should be copied to? to the spool folder?

    2. If I provide the line in the addtional tab, it will point to a setup.exe,what is this setup.exe supposed to do?

    Thanks

    Vinod

    Thursday, June 13, 2013 8:44 PM