![]() ![]() Using Add-WindowsDriver didn't work as it only allows drivers to be installed into offline images, not into the currently running system. Using Add-PrinterDriver didn't work as it should for a majority of our printers as their drivers are not available in the Windows driver store by default. ![]() I was rather happy to see that new Cmdlets were introduced with Server 2012 which seemed to be pointed exactly at what I wanted to achieve. I tried to create a PowerShell script to migrate all the printers from the appliances to the Windows server, which checks for published queues in the AD, installs the needed drivers on the Windows server and installs the printers as a last step. Problems we regularly encounter with the current solution. Sometime this year those printserver appliances will have to be replaced by a Windows printserver, because of ongoing ![]() We're currently using 10 printserver appliances for publishing about 1k printer queues to the AD and making them available to the users. Here's what I'm currently trying to achieve: This question is in addition to the following thread which already was marked as answered: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |