Turns out there was a dependancy that we didn't know about that was mucking up the works. Part of the printing sub-system was (surprise!) residing on a volume we weren't expecting. So once we migrated that volume to the server running print-services, things started working great. Now we're trying to get rid of the dependancy.