Download software and drivers for DYMO ® label makers and printers.
If you are running a Samba print server for Windows clients, you can upload drivers and preconfigure printers. If a user connects to a printer on the Samba server, Windows automatically downloads the driver and installs it locally. The user does not require local administrator permissions for the installation. Additionally, Windows applies preconfigured driver settings, such as paper sizes and the number of trays.
Before you can set up automatic printer driver download, configure Samba as a print server and share a printer. For details, see Setting up Samba as a Print Server. |
Many driver are provided in a way that enables you to upload them to your Samba print server:
Ask your printer vendor, if the driver supports uploading to a print server for automatic download by Windows operating systems.
Samba only supports the printer driver model version 3 that is supported in Windows 2000 to 10 and Windows Server 2000 to 2016.
To use package-aware drivers:
spoolssd
service. For details, see Enabling the spoolssd Service.The driver model version 4, introduced in Windows 8 and Windows Server 2012, is not supported in Samba. Use version 3 drivers instead.
Printer drivers for the 64-bit Windows architecture, you can only upload from a Windows 64-bit operating system. 32-bit drivers you can upload from both 32-bit and 64-bit Windows operating systems.
To provide driver for both architectures, you must upload 32-bit and 64-bit drivers that uses exactly the same name for both architectures. For example, if you are uploading the 32-bit HP Universal Printing PS
driver and the 64-bit HP Universal Printing PS (v5.5.0)
driver for Windows, the driver names are different and cannot be used and preconfigured for the same printer.
Using the default setting, Samba reports itself as Windows NT x86
architecture. Thus, 64-bit drivers stored on this print server can only be assigned to a printer if additionally a 32-bit driver with exactly the same name is uploaded. Otherwise, Windows does not display the driver in the list displayed in the printer's properties when assigning the driver.
To provide only 64-bit driver on the Samba print server:
[global]
section in your smb.conf
file:Only users and groups having the SePrintOperatorPrivilege
privilege granted can upload and preconfigure printer drivers. You can grant this privilege to any user or group.
For example, to grant the privilege to the Domain Admins
group, enter:
It is recommended to grant the privilege to a group instead of individual accounts. This enables you to add and revoke the privilege by updating the group membership. |
To list all users and groups having the SePrintOperatorPrivilege
privilege granted, enter:
Windows downloads printer drivers from the print$
share of a print server. This share name is hard-coded in Windows and cannot be changed.
To share the /srv/samba/printer_drivers/
folder using the print$
share name:
smb.conf
file:SePrintOperatorPrivilege
privilege granted must be able to to write to the share. For example, to set write access for the Domain Admins
group and read permissions for other users to be able to download the drivers:When setting up a Samba print server on an Active Directory (AD) domain controller (DC), you cannot use POSIX access control lists (ACL). Use the Windows utilities to set extended ACLs. For details, see Enable Extended ACL Support in the smb.conf File. |
Principal | Access | Apply to |
---|---|---|
Creator Owner | Full control | Subfolders and files only |
Authenticated Users | Read & execute, List folder contents, Read | This folder, subfolders and files |
Domain Admins | Full control | This folder, subfolders and files |
Samba automatically creates the architecture subdirectories on the print$
share when uploading a driver.
In July 2016, Microsoft released an update to fix security issues in the Windows print spooler. This update changes the behaviour and limited support for non-package-aware printer drivers. In October 2016, Microsoft published an update to mitigate these problems in an Active Directory (AD). For further details, see MS16-087. This section describes the procedure to work around the problems in an AD. |
To avoid installing malicious drivers from untrusted sources, Windows asks you if you trust the print server when you preconfigure a printer or when a user installs a printer. Create a group policy object (GPO) to trust the Samba print server and work around the known issues introduced by the Windows print spooler security update:
Administrator
account.Group Policy Management Console
. If you are not having the Remote Server Administration Tools (RSAT) installed on this computer, see Installing RSAT.Create a GPO in this domain, and Link it here
.Legacy Printer Driver Policy
. The new GPO is shown below the domain entry.Edit
to open the Group Policy Management Editor
.Computer Configuration
→ Policies
→ Administrative Templates
→ Printers
entry.Point and Print Restriction
policy to edit the policy:Users can only point and print to these servers
and enter the fully-qualified domain name (FQDN) to the field.Do not show warning or elevation prompt
in both the When installing drivers for a new connection
and When updating drivers for an existing connection
list.OK
.Package Point and Print - Approved servers
policy to edit the policy:Show
button.OK
.Group Policy Management Editor
. The GPOs are automatically saved on the Sysvol
share on the domain controller (DC).Group Policy Management Console
.Wait until the Windows domain members applied the group policy automatically. To apply the policy manually:
To connect to the Samba print server:
SeDiskOperatorPrivilege
privilege granted and write permissions on the print$
share.Start
, enter Print Management
, and start the application.Print Servers
entry and select Add/Remove Servers
.Add servers
field, and click Add to List
.OK
.When you are connected to the print server, you can perform certain tasks, such as uploading drivers and preconfiguring printers.
To upload a printer driver:
Print Servers
entry, double-click your print server, and right-click to the Drivers
entry.Add Driver
.Next
.Have Disk
and navigate to the folder containing the printer driver for the selected architecture.When you upload 32-bit and 64-bit drivers for the same printer, both drivers must have exactly the same driver name. For details, see 32-bit and 64-bit Drivers. |
Finish
to start uploading the driver to the print$
share.Drivers
menu.Optionally, upload drivers for additional architectures.
Print Management
ConsoleTo assign a driver to a printer using the Windows Print Management
console:
Print Servers
entry, double-click your print server, and select the Printers
entry.Properties
.No
. The driver is selected in a later step from the list of uploaded drivers.Advanced
tab and select the driver from the list. For example:OK
to set the driver for the printer.smb.conf
file:Rename
.smb.conf
file, and press Enter
.[F5]
key.rpcclient
UtilityTo assign a driver to a printer locally on a Samba print server using the rpcclient
utility:
print$
share:HP Universal Printing PS
driver to the DemoPrinter
printer, enter:If the administrator preconfigured the driver on the print server, users connecting to the printer getting automatically the settings applied as default. Preconfigured settings are applied automatically to all driver platforms for the printer, if drivers for multiple architectures are installed on the server. For details, see 32-bit and 64-bit Drivers.
To preconfigure a printer:
Print Servers
entry, double-click your print server, and select the Printers
entry.Properties
.Device Settings
, is provided that enables you to set general settings, such as installed paper trays.Advanced
tab and click Printing Defaults
.OK
.