Univention Bugzilla – Bug 34903
Unable to upload multi-arch driver
Last modified: 2015-07-29 12:57:00 CEST
Created attachment 5920 [details] Mulit-Arch(?) Driver A customer reported that he isn't able to upload multi-arch printer drivers. See ticket #2014051221006942 for further reference. It seems that you immediatly receive an error message in windows ("The folder you specified doesn't contain a compatible software driver for your device"), if uploading this driver (see attatched). I didn't reproduce it. As I didn't reproduce it I am not so sure if it's ucs-related.
The attached zip contains the version for x64 only. It corresponds to this download: http://support.ricoh.com/bb/html/dr_ut_e/re/model/mp23/mp23en.htm#Microsoft%20Windows%207%20%28x64%29 When I strictly follow the upload procedure as described here: http://docs.univention.de/manual.html#print-services:winclients and try to upload this x64 driver from an x64 Windows7 to a server side printer share, I receive the slightly misleading Windows error message The specified location does not contain a compatible software driver for your device. If the location contains a driver, make sure it is designed to work with the Windows x64 Edition operating system. It's misleading because you actually first need to upload the x86 version of the driver, which can be found here: http://support.ricoh.com/bb/html/dr_ut_e/re/model/mp23/mp23en.htm#Microsoft%20Windows%207 But generally this works as described in detail in the manual. As a first step (before digging into code for differences between Samba and native Windows behaviour) we could improve three things about the documentation: 1. Add some pictures to make things more clear: https://hutten.knut.univention.de/mediawiki/index.php/Arvid_memo/Windows_Printer_Driver_Upload 2. Point out more clearly the "wrong ways" - i.e. 1) Don't pick the wrong way through the Windows tools and dialogs, which does not offer the chance to upload a driver for both architectures. 3. Additionally document the "Print Management" MMC snap-in for the printer driver upload/management. This is included in Windows 7 (and apparently 2012? For W2k8R2 it's available via the RSAT tools): * http://technet.microsoft.com/de-de/library/print-scan-and-fax-server-installation-guide%28v=ws.10%29.aspx#BKMK_Add_printer_drivers * http://msdn.microsoft.com/en-us/library/cc753109%28v=ws.10%29.aspx#BKMK_UpdateDrivers
> When I strictly follow the upload procedure as described here: > http://docs.univention.de/manual.html#print-services:winclients > and try to upload this x64 driver from an x64 Windows7 to a server side printer > share, I receive the slightly misleading Windows error message Actually this message is also shown when uploading drivers cross-archicecture to a native Windows 2krR2 server. My impression is, that the message refers to the architecture of the server. Anymay it's misleading and we can do nothing about that. But from working with it, the usage of the Administrative Tools > Print Management or Verwaltung > Druckerverwaltung MMC snapin is much more transparent than the arcane GUI twists currently described in the documentation. It allows to upload and manage the printer drivers for the different architectures directly, on any print server.
OK, I'll close this issue as duplicate of Bug #38136 because both bugs describe to document the MMC snapin. *** This bug has been marked as a duplicate of bug 38136 ***
Ok, I did some adjustments in svn r62168, mostly for Bug 33000, Bug 35846, Bug 34903 and Bug 37148.