MAPUSERPRINTERS

The right printers for every user, at every logon.

One text file decides which printers each user gets. At every logon, MapUserPrinters maps what applies, removes what no longer does, and sets the default printer — without admin rights.

  • No admin rights
  • x64 · x86 · ARM64
  • Signed configurations
NETWORK PRINTERS

Overview

Describe in one text file which printers go to which AD groups, OUs, AD attributes, locations, networks, computers, or tags. At logon, MapUserPrinters reads the file, maps what applies, removes what no longer applies, sets the default printer, and writes a log. It is built for logon scripts and Group Policy, and also works where Intune or another management tool handles deployment.

  • No runtime, no administrator rights, no internet access
  • No service and no installation on the clients
  • Single executables for x64, x86, and ARM64
  • User interface and log in English and German
ProgramForPurpose
MapUserPrinters.exeEvery user, at logonMaps and removes printers and sets the default printer. Runs silently and never shows a window.
MapUserPrintersConfig.exeAdministratorsEdits the configuration, previews the result, reads logs, and signs configurations.

Plan your rollout

Assign printers by rule

Use AD groups, sites, networks, computers, or policy tags. Set a default printer and remove outdated connections with cleanup rules.

Deploy on Windows

Deploy the executable, configuration, and license at user logon through Group Policy, Intune, or an existing script. Builds are available for x64, x86, and ARM64.

Keep using covered versions

The license is checked offline. Versions released during your maintenance term keep working. Renew maintenance for newer versions.

Request a trialRequest pricing

Check changes before rollout

Run WhatIf in the configuration editor to preview printer assignments for the current user and flag missing drivers without changing any connections.

Read about the configuration editor
Example WhatIf result for a user on Floor 1
  • PRT_01Connect and set as default
  • PRT_02Connect once
  • PRT_OLDRemove old connection
PERFORMANCE

How a logon run works

Every run checks the license and, when required, the configuration’s signature before it touches a single printer. It stays fast by avoiding the slow parts of typical scripts:

  1. Group membership from the logon tokenWindows has already resolved all nested groups at logon, so no LDAP queries are needed — even with thousands of configured printers.
  2. Local factsIP addresses, AD site, and session details come from local Windows caches and are read only when a line needs them.
  3. Parallel connectionsSeveral printers connect at once (4 by default). A print server that does not answer is skipped for its remaining printers instead of waiting for each timeout.
  4. Only changesExisting connections are read once; printers that are already mapped are left alone.
CONFIGURATION

The configuration file

One readable text file, MapUserPrinters.ini (or .txt), holds all printers and settings — one line per printer, with groups and options after a |.

[Printers]
\\PRINT1SV\PRT_01     | G_PRT_PRT_01; G_Floor1 | default
\\PRINT1SV\PRT_02     | *                      | once, ip=10.20.0.0/16
DEL \\PRTSV\*          | *

Groups

A line applies when the user is a member of any listed group, nested groups included. * means everybody.

default

Makes the printer the default printer; the first matching line wins.

mandatory / once

Mandatory printers are restored at every logon if the user removed them. Once printers are mapped the first time only; afterwards the user may remove them.

DEL rules

Delete printer connections, with wildcards — for example to retire an old print server. A printer the user is still assigned to is never deleted.

Comments

Lines starting with #. Prefix a printer line with # to disable it without losing it.

The file can be UTF-8, UTF-16, or ANSI, so group names with umlauts work.

SettingDefaultMeaning
ModemandatoryDefault for lines without once or mandatory.
RemoveUnassignednoRemove listed printers the user is no longer entitled to.
DisableWindowsManagedDefaultnoTurn off “Let Windows manage my default printer”.
Attempts, RetryDelay3, 2 sConnection attempts per printer.
Parallel4Printers connected at the same time.
ValidateGroupsnoAlso look up every configured group and log groups that do not exist.
LogFile, LogMaxSizeKB%APPDATA%\MapUserPrinters, 1024Log location and rotation size.
LanguageautoLanguage of the log: auto, en, or de.
TARGETING

Conditions: where and for whom

Besides groups, a line can require conditions on location, network, computer, session, tags, OU, or any AD attribute. Groups and all conditions must match. Within a condition, ; means or and ! means not — for example computer=LAB-*;!LAB-KIOSK*.

ConditionMatchesExample
ip= (subnet=)Any IP address of the computer10.20.0.0/16, 10.1.3.10-10.1.3.50, IPv6
network=A connected network: domain, private, public, or its namedomain, CorpWiFi
computer=Computer name, with wildcardsPC-BER-*
site=The computer’s AD siteBerlin
client=RDS/Citrix: the device the user sits atTHIN-BER-*
clientip=RDS/Citrix: that device’s address10.1.2.0/24
session=Kind of sessionconsole, remote, rdp, citrix
tag=Tags set by policy for the computer or userFinance; !Kiosk
userou=, computerou=OU of the user or computer object, sub-OUs includedSites/Berlin
user.<attribute>=, computer.<attribute>=Any AD attribute of the user or computer objectuser.department=Finance

Tags let Group Policy, Intune, or any other tool decide who gets a printer without AD groups: write tags such as Berlin or Floor 3 to the Tags policy value and target tag=Berlin in the configuration. Users cannot change them.

OU and attribute conditions read the user and computer objects once per logon with one signed and encrypted LDAP query each. Without a domain controller — on a laptop at home, for example — they don’t match and the log says why; network=domain makes such lines explicit.

Safe by default. Each fact is read once per logon and only when a line needs it. An invalid condition stops the run instead of silently widening who gets a printer, and /verbose logs which condition excluded a line.
ADMIN TOOL

The configuration editor

MapUserPrintersConfig.exe lets you build and check the configuration without editing text by hand. The file stays readable and can still be edited in Notepad.

Printer list

With check boxes to enable or disable lines, columns for action, groups, options, conditions, and comments, plus reordering.

Add from print server

Lists all shared printers of a server, derives group names from a template such as G_PRT_{share} or uses fixed groups, and adds conditions to all selected printers at once.

Printer dialog

Map or DEL rule, AD group picker, once or mandatory, default printer, one field per condition, AD attributes, and a comment.

Check groups

Looks up every configured group in AD and selects the printers whose groups do not exist.

Preview (WhatIf)

Runs the mapper for the current user without changing anything and shows what would be mapped, removed, or set as default — including missing drivers.

Log viewer

Opens your own log or a user’s log on another computer through the admin share, filters by run, level, and text, and refreshes automatically.

Signing and licensing

Sign configurations and install license files from the editor; /sign and /verify do the same from a script.

Convenience

Drag and drop of configuration files, light and dark mode that follows Windows, English and German switchable while running, and keyboard shortcuts for every command.

SECURITY

Security and central control

A changed configuration cannot send users to a foreign print server, and users never see or influence the configuration.

Signed configurations

The editor signs the configuration with your own key (ECDSA P-256, SHA-256) as a comment block at the end of the file. With the Require signed configurations policy, the mapper refuses unsigned, changed, or untrusted configurations and changes nothing. Re-saving in Notepad keeps the signature valid; any real change breaks it.

Allowed print servers

Limit mapping to listed servers by name, full name, or wildcard. Deleting old connections still works for every server.

Policies instead of files

All central settings live in HKLM or HKCU\Software\Policies\MapUserPrinters, which users cannot change.

Runs as the user

No elevation, no service, no installation on the clients.

Never shows anything

No message box or window, even for errors — everything goes to the log.

PolicyScopeEffect
Require signed configurationsComputerRun only configurations signed with a trusted key.
Trusted configuration signing keysComputerPublic keys whose signatures are accepted.
Allowed print serversComputerServers printers may be mapped from.
Tags for printer conditionsComputer and userTags for the tag= condition.
License fileComputerPath of the license file.

ADMX templates in English and German cover all five policies, for the Group Policy central store or Intune’s ADMX import. Any other tool can set the registry values directly.

LICENSING

Licensing

MapUserPrinters uses a signed license file that is checked offline. Without a valid license it logs the reason and changes nothing.

License file

MapUserPrinters.lic is readable text with licensee, edition, users, scope, and maintenance date. It is digitally signed, so any change invalidates it.

Scope

Bound to your Active Directory domain (including child domains) or your Microsoft Entra tenant, read locally from the computer — no internet access or online activation.

Maintenance

A license covers every version released up to its maintenance date and never stops working for those versions. Newer versions need a renewal. Only trial licenses expire.

Where it is found

The /license: parameter, the License file policy, next to the configuration, or next to the executable. The editor shows the status under Help › License.

Want to try it first? Request a time-limited trial license for your own environment. Request a trial →
ROLLOUT

Deployment and operation

Deployment is three files on a share and one line in a logon script or GPO: MapUserPrinters.exe, the configuration, and the license — for example in \\<domain>\NETLOGON\MapUserPrinters.

Logon

Add the executable as a GPO logon script or call it from an existing batch file. Parameters are optional.

Log

%APPDATA%\MapUserPrinters\MapUserPrinters.log in UTF-8, rotated at 1 MB, one marked block per run, readable with the editor’s log viewer.

Missing drivers

A failed mapping names the driver that is not installed, and /whatif checks drivers in advance.

Command line

/config:<file>Use a specific configuration file.
/log:<file>Write the log to a specific location.
/whatifDry run: show what would change, including missing drivers.
/verboseLog details, including which condition excluded a line.
/resetonceReset once printers so they are mapped again.
/lang:<en|de>Language of the log.
/license:<file>Use a specific license file.

Exit codes

0Everything done.
1At least one printer could not be mapped or removed.
2Configuration or setup error.
3No valid license.
4Signed configuration required, but missing or not accepted.