Pharos API Restricted Server setting

  • Updated on Jan 6, 2026
  • Published on Jan 6, 2026
  • 2 minute(s) read
Prev Next

Question:

How can I restrict Print Jobs to Specific Uniprint Print Servers or Blueprint Collectors when users upload or email documents into the system?


Resolution:

A new feature has been added to the Pharos API to allow restricting which Print Servers are used to process and store the jobs submitted via MP email or Print Center upload.

This requires an update to the Print Center (API/Web) and editing of the configuration file on the API server.  MobilePrint uses the API server to process emailed jobs, as does the Print Center web for uploading jobs, so both uploaded and emailed jobs will be sent to the restricted server(s) defined.

Note: Requires Print Center version greater than 1.7.6.

  1. On the API server, in the \Inetpub\wwwroot\PharosAPI folder:
    1. take a copy of the PharosSystems.API.config  file
    2. store a copy of this config file somewhere safe.
  2. On the API server, in the \Inetpub\wwwroot\PharosAPI folder.
  3. Open the PharosSystems.API.config file in notepad with Admin privileges.
  4. Locate the following tag at the bottom of the config file:  <RestrictedServerConfiguration/>
  5. REPLACE this tag with one of the following xml blocks (copy and paste exactly as shown below or the config file will be overwritten *See Note below).

For a Single central Print Server for email/upload jobs:

  <RestrictedServerConfiguration>
<RestrictedServers json:Array="true" xmlns:json="http://james.newtonking.com/projects/json">
       <Host>KB-2K12-R2-A90</Host>
     </RestrictedServers>
  </RestrictedServerConfiguration>

Or, if there are multiple central servers to hold the email/upload jobs, use the following instead:

  <RestrictedServerConfiguration>
    <RestrictedServers>
       <Host>KB-2K12-R2-A90</Host>
     </RestrictedServers>
     <RestrictedServers>
       <Host>KB-2K12-R2-B90</Host>
     </RestrictedServers>
 </RestrictedServerConfiguration>

Please Note: To use just a single server, you must use the single server config described above, do NOT just use the multiple server xml block and delete one of the server entries as this will cause the config file to be overwritten.

  1. Edit the server name(s) to reflect the central Print Server(s) or Collectors to which the email/upload jobs should be sent.
  2. Save the config file.

No restart of any service is required. The change to the config file will be detected by the API service on the fly. 

  • To revert the change

If you want to return it back to not using a central server, replace the added xml block with:

  <RestrictedServerConfiguration/>

  • Additional Servers

Repeat the application instructions on any additional instances of the API (if there are any, as is the case for an ARR server farm).

Ensure the PPC Web component also has the 1.7.6 or later patch applied if it is installed on a server separate to the API.

Important Note:
If a mistake is made in the xml formatting of the RestrictedServerConfiguration section, the API will turn the config file into a backup file (will append the date to the file name, saved in the same folder)  and it will create a whole new config file.  This new config file is NOT a useful one.  It will be obviously different from the original (ie it will be shorter with different tags).