Microsoft The Windows Server Print Server role team is looking for your input - Windows Printing Team Blog - Site Home - TechNet Blogs

Windows Printing Team Blog

Setup, connect, and print with confidence

The Windows Server Print Server role team is looking for your input

The Windows Server Print Server role team is looking for your input

  • Comments 7
  • Likes

Do you use the Windows Server Print Server role in your environment?  Are you using the either of the print server management packs for OpsMgr 2007?  Do you use the print management console?  If you answered yes to any of these questions then we would greatly appreciate your input to help form the future manageability plans for the print server role.  Head over to the OpsMgr public Connect site and fill out the "Print Server Management Survey".

Registration to the Connect program only requires a Windows Live ID.  The survey is anonymous and should take about 5 minutes to fill out the 11 questions.

Thank you in advance for your time and your feedback.
-Cory Delamarter
Program Manager
System Center Operations Manager

Comments
  • how to install a printer in 2008 R2 by command line?

  • Hi eh1000,

    Please consider reading this article http://blogs.technet.com/print/archive/2009/10/16/printer-management-using-powershell.aspx and using a script similar to:

    [void][reflection.assembly]::LoadWithPartialName("System.Printing")

    $server = new-object system.Printing.PrintServer

    $server.InstallPrintQueue("QueueName1","Microsoft XPS Document Writer",@("FILE:"),"winprint", @([System.Printing.PrintQueueAttributes]::EnableBidi))

    Alternatively, you can use the inbox VB script ‘prnmngr.vbs’ to install printers as needed.  This script is located with the other print scripts in “C:\Windows\System32\Printing_Admin_Scripts\en-US” and the syntax is as specified in the file:

    ' Abstract:

    ' prnmngr.vbs - printer script for WMI on Windows

    '     used to add, delete, and list printers and connections

    '     also for getting and setting the default printer

    '

    ' Usage:

    ' prnmngr [-adxgtl?][co] [-s server][-p printer][-m driver model][-r port][-u user name][-w password]

    Examples:

    prnmngr -a -p "printer" -m "driver" -r "lpt1:"

    Thanks!

    Microsoft Printing and Imaging Team

  • How do i migrate a windows 2000 print server to windows 2008(not R2), I have version 2 drivers also installed in the windows 2000 server.

  • Hi Guys,

    what do you think to Post some Tipps and Tricks, HowTo's or more Powershell Scripts?

    For example:

    Powershell Script - How to install Driver with some special default settings...

    Printing Problems, howto analyse...

    If I update the Driver on the Server is the driver also updated on each client?

    I have added this Blog to my favorites but since many month there has nothing changed.

    If you would add some tips and HotTos then many more people would read this Blog :-)

    Just an Idea....

    And Maybe many other Peoples would discuss more Topics...

    What do you think?

    regards

    Kai

  • Dear Team,

    First off, I should say that in the main I've used the 2000/XP/2003 printing system for the past few years across WANs and LANs and servers and clients, and I think that printing system was overall a big improvment on what went before. But..

    I'm fighting with introducing 2008 R2 and 7 into the networks, and I probably won't be able to express my feelings on this. I don't fully know how far back you guys reach in terms of legacy, sometime I think you only seem to test against current family versions.

    In terms of Print Servers, and Terminal servers, I've never had such a miserable time as I am having now in terms of printing. And I mean ever. Windows XP through Terminal servers bombs with endless failure, windows presentation foundation crashes, and with complete failure in terms of 'easy print'. Loading drivers fails endlessly - in particular in the area of X86 legacy drivers.

    Windows XP clients can't use the old connect method if the user is none admin. Its failing on the same drivers as they had on 2003 - where as they could install from the older server - now they cannot.

    And a ton more, but the biggest thing is the sheer level of driver failure, broken printing, problems because the x64 and x86 drivers versions are not matching.

    I have to install drivers on a local 32 bit machine and export it back onto a server.

    I honestly don't know how this got past any form of user testing, or customer testing. I have no idea how this made it through any Q and A at all. The whole thing as far as Legacy goes is distressingly broken to the point of being sub Beta level acceptability.

    I know that probably, its a case of reading and re-learning how to deploy the printing side of things, and there are always things that have to be changed - and I realise that in the main the system may well work great in a Win 7/ X64 senario, but 2008 r2 as a print server facing legacy clients - is grim indeed.

    I also know you'll blame drivers and 3rd parties. But they did not change the printing subsystem - MS did.

    darren.stewart(AT)stagetech.com

  • i like your website blog article it look great to me!

    From: http://www.dowprinting.com/

  • Windows XP through Terminal servers bombs with endless failure, windows presentation foundation crashes. sometime I think you only seem to test against current family versions. kyocers copiers in gold coast

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment