docs/htmldocs/printer_driver2.html

   1 <HTML
   2 ><HEAD
   3 ><TITLE
   4 >Printing Support in Samba 2.2.x</TITLE
   5 ><META
   6 NAME="GENERATOR"
   7 CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
   8 ><BODY
   9 CLASS="ARTICLE"
  10 BGCOLOR="#FFFFFF"
  11 TEXT="#000000"
  12 LINK="#0000FF"
  13 VLINK="#840084"
  14 ALINK="#0000FF"
  15 ><DIV
  16 CLASS="ARTICLE"
  17 ><DIV
  18 CLASS="TITLEPAGE"
  19 ><H1
  20 CLASS="TITLE"
  21 ><A
  22 NAME="PRINTING"
  23 >Printing Support in Samba 2.2.x</A
  24 ></H1
  25 ><HR></DIV
  26 ><DIV
  27 CLASS="SECT1"
  28 ><H1
  29 CLASS="SECT1"
  30 ><A
  31 NAME="AEN3"
  32 >Introduction</A
  33 ></H1
  34 ><P
  35 >Beginning with the 2.2.0 release, Samba supports
  36 the native Windows NT printing mechanisms implemented via
  37 MS-RPC (i.e. the SPOOLSS named pipe).  Previous versions of
  38 Samba only supported LanMan printing calls.</P
  39 ><P
  40 >The additional functionality provided by the new
  41 SPOOLSS support includes:</P
  42 ><P
  43 ></P
  44 ><UL
  45 ><LI
  46 ><P
  47 >Support for downloading printer driver
  48         files to Windows 95/98/NT/2000 clients upon demand.
  49         </P
  50 ></LI
  51 ><LI
  52 ><P
  53 >Uploading of printer drivers via the
  54         Windows NT Add Printer Wizard (APW) or the
  55         Imprints tool set (refer to <A
  56 HREF="http://imprints.sourceforge.net"
  57 TARGET="_top"
  58 >http://imprints.sourceforge.net</A
  59 >).
  60         </P
  61 ></LI
  62 ><LI
  63 ><P
  64 >Support for the native MS-RPC printing
  65         calls such as StartDocPrinter, EnumJobs(), etc...  (See
  66         the MSDN documentation at <A
  67 HREF="http://msdn.microsoft.com/"
  68 TARGET="_top"
  69 >http://msdn.microsoft.com/</A
  70 >
  71         for more information on the Win32 printing API)
  72         </P
  73 ></LI
  74 ><LI
  75 ><P
  76 >Support for NT Access Control Lists (ACL)
  77         on printer objects</P
  78 ></LI
  79 ><LI
  80 ><P
  81 >Improved support for printer queue manipulation
  82         through the use of an internal databases for spooled job
  83         information</P
  84 ></LI
  85 ></UL
  86 ><P
  87 >There has been some initial confusion about what all this means
  88 and whether or not it is a requirement for printer drivers to be
  89 installed on a Samba host in order to support printing from Windows
  90 clients.  A bug existed in Samba 2.2.0 which made Windows NT/2000 clients
  91 require that the Samba server possess a valid driver for the printer.
  92 This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients
  93 can use the local APW for installing drivers to be used with a Samba
  94 served printer.  This is the same behavior exhibited by Windows 9x clients.
  95 As a side note, Samba does not use these drivers in any way to process
  96 spooled files.  They are utilized entirely by the clients.</P
  97 ><P
  98 >The following MS KB article, may be of some help if you are dealing with
  99 Windows 2000 clients:  <I
 100 CLASS="EMPHASIS"
 101 >How to Add Printers with No User
 102 Interaction in Windows 2000</I
 103 ></P
 104 ><P
 105 ><A
 106 HREF="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP"
 107 TARGET="_top"
 108 >http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</A
 109 ></P
 110 ></DIV
 111 ><DIV
 112 CLASS="SECT1"
 113 ><HR><H1
 114 CLASS="SECT1"
 115 ><A
 116 NAME="AEN25"
 117 >Configuration</A
 118 ></H1
 119 ><DIV
 120 CLASS="WARNING"
 121 ><P
 122 ></P
 123 ><TABLE
 124 CLASS="WARNING"
 125 BORDER="1"
 126 WIDTH="100%"
 127 ><TR
 128 ><TD
 129 ALIGN="CENTER"
 130 ><B
 131 >[print$] vs. [printer$]</B
 132 ></TD
 133 ></TR
 134 ><TR
 135 ><TD
 136 ALIGN="LEFT"
 137 ><P
 138 >Previous versions of Samba recommended using a share named [printer$].
 139 This name was taken from the printer$ service created by Windows 9x
 140 clients when a printer was shared.  Windows 9x printer servers always have
 141 a printer$ service which provides read-only access via no
 142 password in order to support printer driver downloads.</P
 143 ><P
 144 >However, the initial implementation allowed for a
 145 parameter named <TT
 146 CLASS="PARAMETER"
 147 ><I
 148 >printer driver location</I
 149 ></TT
 150 >
 151 to be used on a per share basis to specify the location of
 152 the driver files associated with that printer.  Another
 153 parameter named <TT
 154 CLASS="PARAMETER"
 155 ><I
 156 >printer driver</I
 157 ></TT
 158 > provided
 159 a means of defining the printer driver name to be sent to
 160 the client.</P
 161 ><P
 162 >These parameters, including <TT
 163 CLASS="PARAMETER"
 164 ><I
 165 >printer driver
 166 file</I
 167 ></TT
 168 > parameter, are being depreciated and should not
 169 be used in new installations.  For more information on this change,
 170 you should refer to the <A
 171 HREF="#MIGRATION"
 172 >Migration section</A
 173 >
 174 of this document.</P
 175 ></TD
 176 ></TR
 177 ></TABLE
 178 ></DIV
 179 ><DIV
 180 CLASS="SECT2"
 181 ><HR><H2
 182 CLASS="SECT2"
 183 ><A
 184 NAME="AEN36"
 185 >Creating [print$]</A
 186 ></H2
 187 ><P
 188 >In order to support the uploading of printer driver
 189 files, you must first configure a file share named [print$].
 190 The name of this share is hard coded in Samba's internals so
 191 the name is very important (print$ is the service used by
 192 Windows NT print servers to provide support for printer driver
 193 download).</P
 194 ><P
 195 >You should modify the server's smb.conf file to add the global
 196 parameters and to create the
 197 following file share (of course, some of the parameter values,
 198 such as 'path' are arbitrary and should be replaced with
 199 appropriate values for your site):</P
 200 ><P
 201 ><PRE
 202 CLASS="PROGRAMLISTING"
 203 >[global]
 204     ; members of the ntadmin group should be able
 205     ; to add drivers and set printer properties
 206     ; root is implicitly a 'printer admin'
 207     printer admin = @ntadmin
 208
 209 [print$]
 210     path = /usr/local/samba/printers
 211     guest ok = yes
 212     browseable = yes
 213     read only = yes
 214     ; since this share is configured as read only, then we need
 215     ; a 'write list'.  Check the file system permissions to make
 216     ; sure this account can copy files to the share.  If this
 217     ; is setup to a non-root account, then it should also exist
 218     ; as a 'printer admin'
 219     write list = @ntadmin,root</PRE
 220 ></P
 221 ><P
 222 >The <A
 223 HREF="smb.conf.5.html#WRITELIST"
 224 TARGET="_top"
 225 ><TT
 226 CLASS="PARAMETER"
 227 ><I
 228 >write list</I
 229 ></TT
 230 ></A
 231 > is used to allow administrative
 232 level user accounts to have write access in order to update files
 233 on the share.  See the <A
 234 HREF="smb.conf.5.html"
 235 TARGET="_top"
 236 >smb.conf(5)
 237 man page</A
 238 > for more information on configuring file shares.</P
 239 ><P
 240 >The requirement for <A
 241 HREF="smb.conf.5.html#GUESTOK"
 242 TARGET="_top"
 243 ><B
 244 CLASS="COMMAND"
 245 >guest
 246 ok = yes</B
 247 ></A
 248 > depends upon how your
 249 site is configured.  If users will be guaranteed to have
 250 an account on the Samba host, then this is a non-issue.</P
 251 ><DIV
 252 CLASS="NOTE"
 253 ><BLOCKQUOTE
 254 CLASS="NOTE"
 255 ><P
 256 ><B
 257 >Author's Note: </B
 258 >The non-issue is that if all your Windows NT users are guaranteed to be
 259 authenticated by the Samba server (such as a domain member server and the NT
 260 user has already been validated by the Domain Controller in
 261 order to logon to the Windows NT console), then guest access
 262 is not necessary.  Of course, in a workgroup environment where
 263 you just want to be able to print without worrying about
 264 silly accounts and security, then configure the share for
 265 guest access.  You'll probably want to add <A
 266 HREF="smb.conf.5.html#MAPTOGUEST"
 267 TARGET="_top"
 268 ><B
 269 CLASS="COMMAND"
 270 >map to guest = Bad User</B
 271 ></A
 272 > in the [global] section as well.  Make sure
 273 you understand what this parameter does before using it
 274 though. --jerry</P
 275 ></BLOCKQUOTE
 276 ></DIV
 277 ><P
 278 >In order for a Windows NT print server to support
 279 the downloading of driver files by multiple client architectures,
 280 it must create subdirectories within the [print$] service
 281 which correspond to each of the supported client architectures.
 282 Samba follows this model as well.</P
 283 ><P
 284 >Next create the directory tree below the [print$] share
 285 for each architecture you wish to support.</P
 286 ><P
 287 ><PRE
 288 CLASS="PROGRAMLISTING"
 289 >[print$]-----
 290         |-W32X86           ; "Windows NT x86"
 291         |-WIN40            ; "Windows 95/98"
 292         |-W32ALPHA         ; "Windows NT Alpha_AXP"
 293         |-W32MIPS          ; "Windows NT R4000"
 294         |-W32PPC           ; "Windows NT PowerPC"</PRE
 295 ></P
 296 ><DIV
 297 CLASS="WARNING"
 298 ><P
 299 ></P
 300 ><TABLE
 301 CLASS="WARNING"
 302 BORDER="1"
 303 WIDTH="100%"
 304 ><TR
 305 ><TD
 306 ALIGN="CENTER"
 307 ><B
 308 >ATTENTION!  REQUIRED PERMISSIONS</B
 309 ></TD
 310 ></TR
 311 ><TR
 312 ><TD
 313 ALIGN="LEFT"
 314 ><P
 315 >In order to currently add a new driver to you Samba host,
 316 one of two conditions must hold true:</P
 317 ><P
 318 ></P
 319 ><UL
 320 ><LI
 321 ><P
 322 >The account used to connect to the Samba host
 323         must have a uid of 0 (i.e. a root account)</P
 324 ></LI
 325 ><LI
 326 ><P
 327 >The account used to connect to the Samba host
 328         must be a member of the <A
 329 HREF="smb.conf.5.html#PRINTERADMIN"
 330 TARGET="_top"
 331 ><TT
 332 CLASS="PARAMETER"
 333 ><I
 334 >printer
 335         admin</I
 336 ></TT
 337 ></A
 338 > list.</P
 339 ></LI
 340 ></UL
 341 ><P
 342 >Of course, the connected account must still possess access
 343 to add files to the subdirectories beneath [print$]. Remember
 344 that all file shares are set to 'read only' by default.</P
 345 ></TD
 346 ></TR
 347 ></TABLE
 348 ></DIV
 349 ><P
 350 >Once you have created the required [print$] service and
 351 associated subdirectories, simply log onto the Samba server using
 352 a root (or <TT
 353 CLASS="PARAMETER"
 354 ><I
 355 >printer admin</I
 356 ></TT
 357 >) account
 358 from a Windows NT 4.0 client.  Navigate to the "Printers" folder
 359 on the Samba server.  You should see an initial listing of printers
 360 that matches the printer shares defined on your Samba host.</P
 361 ></DIV
 362 ><DIV
 363 CLASS="SECT2"
 364 ><HR><H2
 365 CLASS="SECT2"
 366 ><A
 367 NAME="AEN71"
 368 >Setting Drivers for Existing Printers</A
 369 ></H2
 370 ><P
 371 >The initial listing of printers in the Samba host's
 372 Printers folder will have no real printer driver assigned
 373 to them.  By default, in Samba 2.2.0 this driver name was set to
 374 <I
 375 CLASS="EMPHASIS"
 376 >NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</I
 377 >.
 378 Later versions changed this to a NULL string to allow the use
 379 tof the local Add Printer Wizard on NT/2000 clients.
 380 Attempting to view the printer properties for a printer
 381 which has this default driver assigned will result in
 382 the error message:</P
 383 ><P
 384 ><I
 385 CLASS="EMPHASIS"
 386 >Device settings cannot be displayed.  The driver
 387 for the specified printer is not installed, only spooler
 388 properties will be displayed.  Do you want to install the
 389 driver now?</I
 390 ></P
 391 ><P
 392 >Click "No" in the error dialog and you will be presented with
 393 the printer properties window.  The way assign a driver to a
 394 printer is to either</P
 395 ><P
 396 ></P
 397 ><UL
 398 ><LI
 399 ><P
 400 >Use the "New Driver..." button to install
 401         a new printer driver, or</P
 402 ></LI
 403 ><LI
 404 ><P
 405 >Select a driver from the popup list of
 406         installed drivers.  Initially this list will be empty.</P
 407 ></LI
 408 ></UL
 409 ><P
 410 >If you wish to install printer drivers for client
 411 operating systems other than "Windows NT x86", you will need
 412 to use the "Sharing" tab of the printer properties dialog.</P
 413 ><P
 414 >Assuming you have connected with a root account, you
 415 will also be able modify other printer properties such as
 416 ACLs and device settings using this dialog box.</P
 417 ><P
 418 >A few closing comments for this section, it is possible
 419 on a Windows NT print server to have printers
 420 listed in the Printers folder which are not shared.  Samba does
 421 not make this distinction.  By definition, the only printers of
 422 which Samba is aware are those which are specified as shares in
 423 <TT
 424 CLASS="FILENAME"
 425 >smb.conf</TT
 426 >.</P
 427 ><P
 428 >Another interesting side note is that Windows NT clients do
 429 not use the SMB printer share, but rather can print directly
 430 to any printer on another Windows NT host using MS-RPC.  This
 431 of course assumes that the printing client has the necessary
 432 privileges on the remote host serving the printer.  The default
 433 permissions assigned by Windows NT to a printer gives the "Print"
 434 permissions to the "Everyone" well-known group.</P
 435 ></DIV
 436 ><DIV
 437 CLASS="SECT2"
 438 ><HR><H2
 439 CLASS="SECT2"
 440 ><A
 441 NAME="AEN88"
 442 >Support a large number of printers</A
 443 ></H2
 444 ><P
 445 >One issue that has arisen during the development
 446 phase of Samba 2.2 is the need to support driver downloads for
 447 100's of printers.  Using the Windows NT APW is somewhat
 448 awkward to say the list.  If more than one printer are using the
 449 same driver, the <A
 450 HREF="rpcclient.1.html"
 451 TARGET="_top"
 452 ><B
 453 CLASS="COMMAND"
 454 >rpcclient's
 455 setdriver command</B
 456 ></A
 457 > can be used to set the driver
 458 associated with an installed driver.  The following is example
 459 of how this could be accomplished:</P
 460 ><P
 461 ><PRE
 462 CLASS="PROGRAMLISTING"
 463 >
 464 <TT
 465 CLASS="PROMPT"
 466 >$ </TT
 467 >rpcclient pogo -U root%secret -c "enumdrivers"
 468 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
 469
 470 [Windows NT x86]
 471 Printer Driver Info 1:
 472      Driver Name: [HP LaserJet 4000 Series PS]
 473
 474 Printer Driver Info 1:
 475      Driver Name: [HP LaserJet 2100 Series PS]
 476
 477 Printer Driver Info 1:
 478      Driver Name: [HP LaserJet 4Si/4SiMX PS]
 479
 480 <TT
 481 CLASS="PROMPT"
 482 >$ </TT
 483 >rpcclient pogo -U root%secret -c "enumprinters"
 484 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
 485      flags:[0x800000]
 486      name:[\\POGO\hp-print]
 487      description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
 488      comment:[]
 489
 490 <TT
 491 CLASS="PROMPT"
 492 >$ </TT
 493 >rpcclient pogo -U root%secret \
 494 <TT
 495 CLASS="PROMPT"
 496 >&gt; </TT
 497 > -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""
 498 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
 499 Successfully set hp-print to driver HP LaserJet 4000 Series PS.</PRE
 500 ></P
 501 ></DIV
 502 ><DIV
 503 CLASS="SECT2"
 504 ><HR><H2
 505 CLASS="SECT2"
 506 ><A
 507 NAME="AEN99"
 508 >Adding New Printers via the Windows NT APW</A
 509 ></H2
 510 ><P
 511 >By default, Samba offers all printer shares defined in <TT
 512 CLASS="FILENAME"
 513 >smb.conf</TT
 514 >
 515 in the "Printers..." folder.  Also existing in this folder is the Windows NT
 516 Add Printer Wizard icon.  The APW will be show only if</P
 517 ><P
 518 ></P
 519 ><UL
 520 ><LI
 521 ><P
 522 >The connected user is able to successfully
 523         execute an OpenPrinterEx(\\server) with administrative
 524         privileges (i.e. root or <TT
 525 CLASS="PARAMETER"
 526 ><I
 527 >printer admin</I
 528 ></TT
 529 >).
 530         </P
 531 ></LI
 532 ><LI
 533 ><P
 534 ><A
 535 HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD"
 536 TARGET="_top"
 537 ><TT
 538 CLASS="PARAMETER"
 539 ><I
 540 >show
 541         add printer wizard = yes</I
 542 ></TT
 543 ></A
 544 > (the default).
 545         </P
 546 ></LI
 547 ></UL
 548 ><P
 549 >In order to be able to use the APW to successfully add a printer to a Samba
 550 server, the <A
 551 HREF="smb.conf.5.html#ADDPRINTERCOMMAND"
 552 TARGET="_top"
 553 ><TT
 554 CLASS="PARAMETER"
 555 ><I
 556 >add
 557 printer command</I
 558 ></TT
 559 ></A
 560 > must have a defined value.  The program
 561 hook must successfully add the printer to the system (i.e.
 562 <TT
 563 CLASS="FILENAME"
 564 >/etc/printcap</TT
 565 > or appropriate files) and
 566 <TT
 567 CLASS="FILENAME"
 568 >smb.conf</TT
 569 > if necessary.</P
 570 ><P
 571 >When using the APW from a client, if the named printer share does
 572 not exist, <B
 573 CLASS="COMMAND"
 574 >smbd</B
 575 > will execute the <TT
 576 CLASS="PARAMETER"
 577 ><I
 578 >add printer
 579 command</I
 580 ></TT
 581 > and reparse to the <TT
 582 CLASS="FILENAME"
 583 >smb.conf</TT
 584 >
 585 to attempt to locate the new printer share.  If the share is still not defined,
 586 an error of "Access Denied" is returned to the client.  Note that the
 587 <TT
 588 CLASS="PARAMETER"
 589 ><I
 590 >add printer program</I
 591 ></TT
 592 > is executed under the context
 593 of the connected user, not necessarily a root account.</P
 594 ><P
 595 >There is a complementing <A
 596 HREF="smb.conf.5.html#DELETEPRINTERCOMMAND"
 597 TARGET="_top"
 598 ><TT
 599 CLASS="PARAMETER"
 600 ><I
 601 >delete
 602 printer command</I
 603 ></TT
 604 ></A
 605 > for removing entries from the "Printers..."
 606 folder.</P
 607 ></DIV
 608 ><DIV
 609 CLASS="SECT2"
 610 ><HR><H2
 611 CLASS="SECT2"
 612 ><A
 613 NAME="AEN124"
 614 >Samba and Printer Ports</A
 615 ></H2
 616 ><P
 617 >Windows NT/2000 print servers associate a port with each printer.  These normally
 618 take the form of LPT1:, COM1:, FILE:, etc...  Samba must also support the
 619 concept of ports associated with a printer.  By default, only one printer port,
 620 named "Samba Printer Port", exists on a system.  Samba does not really a port in
 621 order to print, rather it is a requirement of Windows clients.  </P
 622 ><P
 623 >Note that Samba does not support the concept of "Printer Pooling" internally
 624 either.  This is when a logical printer is assigned to multiple ports as
 625 a form of load balancing or fail over.</P
 626 ><P
 627 >If you require that multiple ports be defined for some reason,
 628 <TT
 629 CLASS="FILENAME"
 630 >smb.conf</TT
 631 > possesses a <A
 632 HREF="smb.conf.5.html#ENUMPORTSCOMMAND"
 633 TARGET="_top"
 634 ><TT
 635 CLASS="PARAMETER"
 636 ><I
 637 >enumports
 638 command</I
 639 ></TT
 640 ></A
 641 > which can be used to define an external program
 642 that generates a listing of ports on a system.</P
 643 ></DIV
 644 ></DIV
 645 ><DIV
 646 CLASS="SECT1"
 647 ><HR><H1
 648 CLASS="SECT1"
 649 ><A
 650 NAME="AEN132"
 651 >The Imprints Toolset</A
 652 ></H1
 653 ><P
 654 >The Imprints tool set provides a UNIX equivalent of the
 655         Windows NT Add Printer Wizard.  For complete information, please
 656         refer to the Imprints web site at <A
 657 HREF="http://imprints.sourceforge.net/"
 658 TARGET="_top"
 659 >       http://imprints.sourceforge.net/</A
 660 > as well as the documentation
 661         included with the imprints source distribution.  This section will
 662         only provide a brief introduction to the features of Imprints.</P
 663 ><DIV
 664 CLASS="SECT2"
 665 ><HR><H2
 666 CLASS="SECT2"
 667 ><A
 668 NAME="AEN136"
 669 >What is Imprints?</A
 670 ></H2
 671 ><P
 672 >Imprints is a collection of tools for supporting the goals
 673                 of</P
 674 ><P
 675 ></P
 676 ><UL
 677 ><LI
 678 ><P
 679 >Providing a central repository information
 680                         regarding Windows NT and 95/98 printer driver packages</P
 681 ></LI
 682 ><LI
 683 ><P
 684 >Providing the tools necessary for creating
 685                         the Imprints printer driver packages.</P
 686 ></LI
 687 ><LI
 688 ><P
 689 >Providing an installation client which
 690                         will obtain and install printer drivers on remote Samba
 691                         and Windows NT 4 print servers.</P
 692 ></LI
 693 ></UL
 694 ></DIV
 695 ><DIV
 696 CLASS="SECT2"
 697 ><HR><H2
 698 CLASS="SECT2"
 699 ><A
 700 NAME="AEN146"
 701 >Creating Printer Driver Packages</A
 702 ></H2
 703 ><P
 704 >The process of creating printer driver packages is beyond
 705                 the scope of this document (refer to Imprints.txt also included
 706                 with the Samba distribution for more information).  In short,
 707                 an Imprints driver package is a gzipped tarball containing the
 708                 driver files, related INF files, and a control file needed by the
 709                 installation client.</P
 710 ></DIV
 711 ><DIV
 712 CLASS="SECT2"
 713 ><HR><H2
 714 CLASS="SECT2"
 715 ><A
 716 NAME="AEN149"
 717 >The Imprints server</A
 718 ></H2
 719 ><P
 720 >The Imprints server is really a database server that
 721                 may be queried via standard HTTP mechanisms.  Each printer
 722                 entry in the database has an associated URL for the actual
 723                 downloading of the package.  Each package is digitally signed
 724                 via GnuPG which can be used to verify that package downloaded
 725                 is actually the one referred in the Imprints database.  It is
 726                 <I
 727 CLASS="EMPHASIS"
 728 >not</I
 729 > recommended that this security check
 730                 be disabled.</P
 731 ></DIV
 732 ><DIV
 733 CLASS="SECT2"
 734 ><HR><H2
 735 CLASS="SECT2"
 736 ><A
 737 NAME="AEN153"
 738 >The Installation Client</A
 739 ></H2
 740 ><P
 741 >More information regarding the Imprints installation client
 742                 is available in the <TT
 743 CLASS="FILENAME"
 744 >Imprints-Client-HOWTO.ps</TT
 745 >
 746                 file included with the imprints source package.</P
 747 ><P
 748 >The Imprints installation client comes in two forms.</P
 749 ><P
 750 ></P
 751 ><UL
 752 ><LI
 753 ><P
 754 >a set of command line Perl scripts</P
 755 ></LI
 756 ><LI
 757 ><P
 758 >a GTK+ based graphical interface to
 759                         the command line perl scripts</P
 760 ></LI
 761 ></UL
 762 ><P
 763 >The installation client (in both forms) provides a means
 764                 of querying the Imprints database server for a matching
 765                 list of known printer model names as well as a means to
 766                 download and install the drivers on remote Samba and Windows
 767                 NT print servers.</P
 768 ><P
 769 >The basic installation process is in four steps and
 770                 perl code is wrapped around <B
 771 CLASS="COMMAND"
 772 >smbclient</B
 773 >
 774                 and <B
 775 CLASS="COMMAND"
 776 >rpcclient</B
 777 >.</P
 778 ><P
 779 ><PRE
 780 CLASS="PROGRAMLISTING"
 781 >
 782 foreach (supported architecture for a given driver)
 783 {
 784      1.  rpcclient: Get the appropriate upload directory
 785          on the remote server
 786      2.  smbclient: Upload the driver files
 787      3.  rpcclient: Issues an AddPrinterDriver() MS-RPC
 788 }
 789
 790 4.  rpcclient: Issue an AddPrinterEx() MS-RPC to actually
 791     create the printer</PRE
 792 ></P
 793 ><P
 794 >One of the problems encountered when implementing
 795                 the Imprints tool set was the name space issues between
 796                 various supported client architectures.  For example, Windows
 797                 NT includes a driver named "Apple LaserWriter II NTX v51.8"
 798                 and Windows 95 calls its version of this driver "Apple
 799                 LaserWriter II NTX"</P
 800 ><P
 801 >The problem is how to know what client drivers have
 802                 been uploaded for a printer.  As astute reader will remember
 803                 that the Windows NT Printer Properties dialog only includes
 804                 space for one printer driver name.  A quick look in the
 805                 Windows NT 4.0 system registry at</P
 806 ><P
 807 ><TT
 808 CLASS="FILENAME"
 809 >HKLM\System\CurrentControlSet\Control\Print\Environment
 810                 </TT
 811 ></P
 812 ><P
 813 >will reveal that Windows NT always uses the NT driver
 814                 name.  This is ok as Windows NT always requires that at least
 815                 the Windows NT version of the printer driver is present.
 816                 However, Samba does not have the requirement internally.
 817                 Therefore, how can you use the NT driver name if is has not
 818                 already been installed?</P
 819 ><P
 820 >The way of sidestepping this limitation is to require
 821                 that all Imprints printer driver packages include both the Intel
 822                 Windows NT and 95/98 printer drivers and that NT driver is
 823                 installed first.</P
 824 ></DIV
 825 ></DIV
 826 ><DIV
 827 CLASS="SECT1"
 828 ><HR><H1
 829 CLASS="SECT1"
 830 ><A
 831 NAME="AEN175"
 832 ><A
 833 NAME="MIGRATION"
 834 ></A
 835 >Migration to from Samba 2.0.x to 2.2.x</A
 836 ></H1
 837 ><P
 838 >Given that printer driver management has changed (we hope improved) in
 839 2.2 over prior releases, migration from an existing setup to 2.2 can
 840 follow several paths. Here are the possible scenarios for
 841 migration:</P
 842 ><P
 843 ></P
 844 ><UL
 845 ><LI
 846 ><P
 847 >If you do not desire the new Windows NT
 848         print driver support, nothing needs to be done.
 849         All existing parameters work the same.</P
 850 ></LI
 851 ><LI
 852 ><P
 853 >If you want to take advantage of NT printer
 854         driver support but do not want to migrate the
 855         9x drivers to the new setup, the leave the existing
 856         <TT
 857 CLASS="FILENAME"
 858 >printers.def</TT
 859 > file.  When smbd attempts
 860         to locate a
 861         9x driver for the printer in the TDB and fails it
 862         will drop down to using the printers.def (and all
 863         associated parameters).  The <B
 864 CLASS="COMMAND"
 865 >make_printerdef</B
 866 >
 867         tool will also remain for backwards compatibility but will
 868         be removed in the next major release.</P
 869 ></LI
 870 ><LI
 871 ><P
 872 >If you install a Windows 9x driver for a printer
 873         on your Samba host (in the printing TDB), this information will
 874         take precedence and the three old printing parameters
 875         will be ignored (including print driver location).</P
 876 ></LI
 877 ><LI
 878 ><P
 879 >If you want to migrate an existing <TT
 880 CLASS="FILENAME"
 881 >printers.def</TT
 882 >
 883         file into the new setup, the current only solution is to use the Windows
 884         NT APW to install the NT drivers and the 9x  drivers.  This can be scripted
 885         using <B
 886 CLASS="COMMAND"
 887 >smbclient</B
 888 > and <B
 889 CLASS="COMMAND"
 890 >rpcclient</B
 891 >.  See the
 892         Imprints installation client at <A
 893 HREF="http://imprints.sourceforge.net/"
 894 TARGET="_top"
 895 >http://imprints.sourceforge.net/</A
 896 >
 897         for an example.
 898         </P
 899 ></LI
 900 ></UL
 901 ><DIV
 902 CLASS="WARNING"
 903 ><P
 904 ></P
 905 ><TABLE
 906 CLASS="WARNING"
 907 BORDER="1"
 908 WIDTH="100%"
 909 ><TR
 910 ><TD
 911 ALIGN="CENTER"
 912 ><B
 913 >Achtung!</B
 914 ></TD
 915 ></TR
 916 ><TR
 917 ><TD
 918 ALIGN="LEFT"
 919 ><P
 920 >The following <TT
 921 CLASS="FILENAME"
 922 >smb.conf</TT
 923 > parameters are considered to
 924 be deprecated and will be removed soon.  Do not use them in new
 925 installations</P
 926 ><P
 927 ></P
 928 ><UL
 929 ><LI
 930 ><P
 931 ><TT
 932 CLASS="PARAMETER"
 933 ><I
 934 >printer driver file (G)</I
 935 ></TT
 936 >
 937         </P
 938 ></LI
 939 ><LI
 940 ><P
 941 ><TT
 942 CLASS="PARAMETER"
 943 ><I
 944 >printer driver (S)</I
 945 ></TT
 946 >
 947         </P
 948 ></LI
 949 ><LI
 950 ><P
 951 ><TT
 952 CLASS="PARAMETER"
 953 ><I
 954 >printer driver location (S)</I
 955 ></TT
 956 >
 957         </P
 958 ></LI
 959 ></UL
 960 ></TD
 961 ></TR
 962 ></TABLE
 963 ></DIV
 964 ><P
 965 >The have been two new parameters add in Samba 2.2.2 to for
 966 better support of Samba 2.0.x backwards capability (<TT
 967 CLASS="PARAMETER"
 968 ><I
 969 >disable
 970 spoolss</I
 971 ></TT
 972 >) and for using local printers drivers on Windows
 973 NT/2000 clients (<TT
 974 CLASS="PARAMETER"
 975 ><I
 976 >use client driver</I
 977 ></TT
 978 >). Both of
 979 these options are described in the smb.coinf(5) man page and are
 980 disabled by default.</P
 981 ></DIV
 982 ></DIV
 983 ></BODY
 984 ></HTML
 985 >