How to turn the installation of a network printer into an adventure

We need the print server's IP, the printer's model, and, in this case, Murphy as a consultant.

On Linux:

1) Go to http://localhost:631 , or to System Settings - Printers
2) Select "add a printer"
3) Select "network printer"
4) Enter print server's IP
5) Enter printer model
Done. Fortunately, everything is left to the OS.

On Windows, running on VirtualBox on the Linux host:

1) Google and download print server drivers
2) Google and download printer drivers
3) Run the print server installer
4) Exit the installer, because it needs the drivers to be there
5) Run the printer installer
6) Exit the installer, because it looks for the printer locally
7) Repeat steps 3 to 6 a few times
8) Run the printer installer
9) Select "Advanced install"
10) Install the drivers together with a non-existent local printer
11) Run the print server installer
12) Exit the installer, because it cannot auto-detect the printer and does not let you enter the IP manually
13) Shutdown VirtualBox
14) Switch Linux to the same wireless network as the print server, which fortunately happens to be within range
15) Set VirtualBox to bridged networking rather than NAT
16) Turn on VirtualBox again
17) Run the print server installer
18) Select print server
19) Select printer
20) Print test page
21) Shutdown VirtualBox
22) Switch back to the secondary (bridged) wireless network
23) Put back NAT on VirtualBox
24) Turn VirtualBox back on
25) Realize that the test page fails even though you can ping the print server
26) Install a PDF printer and print from the host OS
The OS does have a nice and pretty printer installer, as well as a nice and pretty hardware installer, but noooo, everything has to be overridden by things that don't take all use case scenarios in mind...