Thanks @CMonty, in our case it's a bunch of Sharp network printers.... Although I found that their printer server wasn't configured optimally (using standard IP ports, instead of the Sharp Printer ports). I swapped them over last night so I'm hoping that this fixes it (it looks like there was a delay, possibly from the Sharp proprietary printer driver stuff not being able to communicate over the standard IP ports, I'm hoping). Just so crazy that in all the deployments I've ever worked on, I've never seen this happen, lol.

what are Sharp Printer ports?

When you have a printer configured that uses TCP/IP, you need to either configure an "IP Port" that attaches the driver to a printer via that means, or, some printer manufacturers have proprietary communication methods, that install special networking ports. So with Sharp printers, you have to use the SC port, and point it at the IP addy of the printer, so it communicates uses Sharps IP communication standard.

I had to do the same than CMonty, creates a vbs until I start mapping them via GPO + make it the default here.