1. Home
  2. FAQ's
  3. PrintAgent Support for DFE’s

PrintAgent Support for DFE’s

The PrintAgent is a Windows service that can be installed on the DFE of the printer and acts as a local application. It enables remote RIPs to query local files at the printer DFE and to spool files to the local harddisk without having to set-up sharing and access rights.

The PrintAgent advertises its services at port 9100. The installer of the PrintAgent will automatically open this port on the Windows fire-wall, but is not able to do this for 3rd party fire-walls.
Installation
During the installation the Installation Wizard will ask for the location of the hotfolder. This location is the hotfolder that is used by the printer DFE and all output of the RIP will be stored at that location.
After the installation is finalized the PrintAgent is already running, no restart is required.
To change the location of the output folder just uninstall and install again the PrintAgent.
Note: The registry location of the path is [HKEY_LOCAL_MACHINE]/SOFTWARE/Wow6432Node/PrintAgent/PrintAgentPath
Problem solving
PrintAgent automatically creates a log file at C:\PrintAgentLog.txt. This log file contains by default the critical messages and errors. Sometimes it can be needed to have a more detailed log. The increase the logging level add the following line as first line to the PrintAgentLog.txt:
Level=3
After modifying the PrintAgentLog.txt go to the Service Manager and restart the Aurelon PrintAgent service.

Accessing remote shares

PrintAgent is designed to work with the local volums of the DFE. As PrintAgent runs as a service it does not have access to any of the mapped drives and can’t access log-in information. The following hack allows you to go around this limitation, however it is not supported by either us or Microsoft. Use this at your own risk. (I have tested it on Windows 7 x64)
For this hack you will need SysinternalsSuite by Mark Russinovich:
  1. Open an elevated cmd.exe prompt (Go to Start -> Type cmd -> Right click -> Run as administrator)
  2. Navigate to the folder containing SysinternalsSuite using the cd command (e.g: “cd C:\User\Desktop\SysinternalsSuite”) -> Enter
  3. Execute the following command: “psexec -i -s cmd.exe” -> Enter
    Note: You are now inside of a prompt that is nt authority\system and you can prove this by typing “whoami”. The -i is needed because drive mappings need to interact with the user.
  4. Create the persistent mapped drive as the SYSTEM account with the following command: “net use z: \\servername\sharedfolder /persistent:yes”
    Note: This command will map the folder from the command (“sharedfolder”) to a network location (z in this case).
WARNING: You can only remove this mapping the same way you created it, from the SYSTEM account. If you need to remove it, follow steps 1 and 2 but change the command on step 3 tonet use z: /delete.
NOTE: The newly created mapped drive will now appear for ALL users of this system but they will see it displayed as “Disconnected Network Drive (Z:)”. Do not let the name fool you. It may claim to be disconnected but it will work for everyone.
Updated on February 23, 2019

Was this article helpful?

Related Articles