Sigh - Well - there's the problem. - well likely anyway.

I've never used Branch Office Direct Printing, frankly I'm not sure what the gain is over what I'm doing today?

@DustinB3403 said in Print Services - Migrate from one server to another: @IRJ people have a hard time reading labels that could save their life, I don't expect my users to read any announcements coming from IT. Edit: mostly because I know they don't care, they just need it to work. ^ this, so much this! My users only read my email today because they already knew the phones were having issues, and now they knew that I also knew. But a future notice, they won't remember for the most part 20 mins from now it's all good, again, mostly just flipping shit.

You /could/ turn on Operational Event logs for PrintService in Windows Server, then make an xml collector that adds up Param 8 from Event ID 307 in that log over a given time. Or get software where someone has already done that. (papercut prob does this).

And... you'd need a database to track the databases! Actually, as I think about it, separating databases really just becomes semantics. As long as it is a single application, separating the databases adds overhead (mostly for the developers) but in reality, it is always still all one datastore. One way or another, the application has to behave essentially the same no matter which way you do it. The one advantage to having them separate is that you can have different "versions" for different customers. But I'm not sure that that is a good thing.