Why don't packages build on remote Print Servers?

Why don't packages build on remote Print Servers?

Packages can be built on all Print Servers as long as the build machine has read and write access to the Package Build Location and Shared Directory. The machine will also require access to the printer information on other Print Servers.

For example:

The Print Server on the Principal Server machine is able to create packages (with spool queues on other print servers) as long as it has access to the printer info for each Spool Queue

The Print Server on a machine in another domain will not be able to create packages if it cannot access the Shared Directory and Build Location (specified in Pharos Administrator at File menu > System Property > Packages ). The Package Builder will check whether it has access to this location. Once a connection is established, it will build packages as normal.