# Creating Mobility Print Queues on Reference Computer

Install published Mobility Print queues and printer-specific drivers on a clean reference computer before cloning them into Print Deploy.

!!!warning Source-derived reference
These notes were recovered from OneNote. Configuration, permissions and operating results have not been freshly verified. Confirm the applicable authority and environment before acting.
!!!

Once the mobility print queues are published from the Mobility Printer server they are ready to install on a reference computer.

Installing on a reference computer enables installation of specific drivers AND applying desired configuration to the print queues. Both drivers and configuration is then included when they are cloned to PaperCut and installed on clients via Print Deploy.

## Installing Mobility Print Queues on Reference Computer

Use a clean (freshly imaged) PC as the reference computer. A virtual machine is most suitable.

- Open a browser and go to [http://\<Mobility Print Server IP\>:9163/setup](http://172.16.20.42:9163/setup). e.g.  <http://172.16.20.42:9163/setup>
- Download the Mobility Print package to the reference computer.
- Run the Mobility Print package to install the mobility print printers that you want to roll out to clients. You must authenticate with the server to complete the installation, but this can be any valid administrator. This has no bearing on print cloning or print deploy.
- Mobility Print queues are installed with the Papercut Global Postscript driver by default.
- Open Print Management Console and add printer drivers.
- Install the printer drivers required for each printer, including the latest Papercut Global Postscript driver if required.
- Open each printer and change the printer driver to the driver required to support the options included on the printer.
- NOTE: There is a bug with the Papercut Global PostScript driver in that it is supposed to support staple features across multiple brands of copiers. However it doesn't work with Fujifilm copiers. The source records switching to the vendor's driver to support all required features in that environment.

## Related guidance

- [Topic overview](Introduction.md)
- [Source review status](../../review/Review-status.md)
