Local printers are created when a user logs in to the computer running the ezeep Blue Print App. Should that not be the case, please check the following:
- ezeep Blue Print App is installed and running on the machine where the printers are expected to be created.
- Look in Apps&Features for ezeep Blue Print App
- Verify that the service TPAutoconnect is running
- Open a command prompt and run this command and provide the output to our service team for further diagnosis:c:\program files\common files\thinprint\tpautoconnect.exe -v -a wss://ezprint.ezeep.com -p 443 -t -1
- ezeep Blue Connector is installed, running and connected on the machine where the physical printers are configured
- Look for the ezeep Blue Connector icon in the taskbar.
- If there is no icon, the ezeep Blue Connector is not running. If it is installed, you can start it by typing ezeep Blue Connector in the Windows search bar.
- If the icon looks like this , the ezeep Blue Connector is running but not connected to the ezeep Blue Cloud. Right Click on the Icon and select Log In to provide user credentials.
- If the icon looks like this , hover over it. It should show the client name, followed by a web address and an ID
- The same user credentials are being used for the ezeep Blue Print App and the ezeep Blue Connector.
- If in doubt, use the How-To articles Change user account credentials on the ezeep Blue App and Change user account credentials on the ezeep Blue Connector to re-enter credentials
- Local Printer support is not disabled for everyone
- Log in to the ezeep Blue admin portal, click on Local Printer Support and make sure that the checkbox Disable Local Printer Support for everyone is unchecked.
- At least one group to which the user belongs is listed on the Local Printer Support page.
- Log in to the ezeep Blue admin portal, click on Local Printer Support and make sure that the list of groups contains all required groups.