Where Does PrinterLogic Store Client Configs and Logs?
Where PrinterLogic clients keep configs and logs on Windows and macOS, and what lives in the cloud portal.
Last updated
PrinterLogic pushes printers from cloud policy. The admin portal holds printers, drivers, and deployments. Each workstation runs a client that caches policy and logs activity. That cache is disposable.
Paths follow standard app data roots with PrinterLogic in the name. Exact subfolders shift with client releases, so check the versioned folder rather than memorizing depth. When printers vanish, restart the client service and force a policy refresh. Reinstalling the client is safe, since printers redeploy from the portal on next check in.
Where PrinterLogic stores this, by platform
%programdata%\PrinterLogic
Client cache and logs live here. Portal holds printers and drivers. Refresh policy after reinstall. Exact subfolders shift with client releases.
~/Library/Application Support/PrinterLogic
Client cache sits under Application Support with PrinterLogic in the name. Portal redeploys printers on sign in. Logs beside the cache help trace failed installs.
Frequently asked questions
How do I move PrinterLogic printers to a new PC?
Printers, drivers, and deployments live in the PrinterLogic cloud portal. Workstations hold client cache and logs only. Sign in on the new PC and let policies deploy printers. Copying client folders between machines usually carries stale tokens that fail.
Where is PrinterLogic print history?
In the admin portal reports plus client logs beside the cache for troubleshooting. Workstation history is thin by design. Export usage from the portal for audits. Client logs help support trace a failed deployment without guessing.
Notice an outdated path? Let us know.