-
Title
How to verify if Printer issue is related to environment -
Description
When user logs on or runs slogic.bat, there are issues with the Printer Elements and it appears that Desktop Authority does not map printers. -
Cause
There could be many reasons; validation logic misconfiguration, printer drivers, Active Directory, Network Connectivity or OS issues contributing to this problem. Typically it is related to network access/connectivity issues, or element configuration issues. -
Resolution
First, review a copy of the SLTrace.htm file to confirm that upon login the user was configured to run and map the specified printer.
After confirmation that the printer is validated, highlight and copy the printerserver\printer path from the SLTrace.htm file, and on the computer exhibiting the issue, go to START | RUN and paste the path. Click OK or ENTER and confirm whether you can manually access and map this printer manually.
If the printer populates successfully, then there is most likely a configuration issue with and it is recommended to contact Quest Software Support for immediate assistance.
If printer does not populate successfully, you should see the reason why Desktop Authority has not been able to map this printer. Reasons are usually print driver, OS, or “access denied” issue to this printer or network resource.
Additional Information