Get-Printer issue

Tagged: 

This topic contains 1 reply, has 2 voices, and was last updated by Profile photo of Don Jones Don Jones 3 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #44548
    Profile photo of Wes Stahler
    Wes Stahler
    Participant

    Working with a customer on a Printing related issue. Here is the initial description.
    "When I try to query a remote Windows 2012R2 print server via Get-Printer, the console hangs."

    My steps:
    Confirmed that Get-Printer -ComputerName PrintServer sits and spins...

    Works: Get-CimInstance -ClassName win32_printer -ComputerName PrintServer
    Works: Invoke-Command -ComputerName PrintServer -ScriptBlock {Get-Printer}
    Works: Enter-PSSession -ComputerName PrintServer .....
    Works: RDP and run Get-Printer

    So while we have alternative solutions, I am curious as to why on this specific Print Server only Get-Printer isn't performing as expected.

    Any ideas?

    #44715
    Profile photo of Don Jones
    Don Jones
    Keymaster

    So, WS-MAN and RDP work. I'm not sure what protocol Get-Printer uses natively, but I bet it's RPC, and I bet that's being blocked. It could also be WMI (DCOM, e.g., RPC), since 2012R2 disables old WMI by default.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.