Best practive for number of queues to create in a 2012 Hyper-V print spooler

we planning deploy 2 node 2012 cluster host hyper-v session running print spooler. there a best practive or white paper guide on optimal number of queues should create on spooler?

this depend on number of clients have , volume of printing occurring.

having more 2 thousand shares gets hard manage.  i've had 5000 on clustered vm.

there several factors consider , not white paper hard numbers.

if looking limiting factors, try keep under 20,000 active print client connections.  encounter resource constraints in services other spooler using non-page pool memory.

---

alan morris formerly windows printing team

Windows Server  >  Print/Fax