How to Monitor Print Services on Server 2008 R2





Many people have commented that there is no Print Server Management Pack for Server 2008 R2.


As of this writing – the current Print MP is 6.0.6392.0 which supports monitoring Print Services on Windows 2000, Windows 2003, and Windows Server 2008.  However – when the Print Services Role is added to Windows 2008 R2, there is no monitoring.


Until there is an official management pack to handle Windows 2008 R2, I offer this addendum MP.


What I found, is that the Print Services Role in Server 2008 R2 is very similar to the Print Service Role in Server 2008.  The key difference on the surface – is that the role has been renamed:


On Server 2008 it is “Print Services”:



On Server 2008 R2, it has been renamed to “Print and Document Services”:



I noticed that the discovery for Server 2008 Print Server Role is not discovering Server 2008 R2 print servers, and quickly see why.  The Microsoft.Windows.Server.2008.PrintServerRole.Discovery uses a WMI query to discover this role.  The query they used was:

SELECT Name FROM Win32_ServerFeature WHERE Name = "Print Services"

This is the primary issue.  Since it was renamed – it was also renamed in WMI on Server 2008 R2.  If we modify that query to:

SELECT Name FROM Win32_ServerFeature WHERE Name = "Print Services" OR Name = "Print and Document Services"

This will discover the print services on Server 2008 or Server 2008 R2.  The Performance counters are the same between versions, and the service monitors work the same on either version.


I have created an addendum MP that will do a few things:

  1. Contains an override to disable the Microsoft.Windows.Server.2008.PrintServerRole.Discovery discovery in the 2008 Print MP.
  2. Contains a modified discovery which will discover print services on 2008 or 2008R2.
  3. Contains an override to disable the Printer Object discovery.
  4. Contains an override to change Printer Object discovery from 900 seconds to 14335 seconds.

After making these changes – my Server 2008 R2 print servers are discovered, and monitored.  I tested stopping the spooler service, and it worked as designed.  The performance views also started populating with data.


The primary reason I disabled the Printer Object discovery – is that these increase the instance space for no reason.  There are no monitors or rules which target these discovered printer objects.  They are simply discovered and not used.  My recommendation is to leave this disabled, unless you have a very specific monitoring requirement to create monitors for these as individual objects, and show individual health state for printers.  This does not exist out of the box.  If you have any large print servers with hundreds of printers, this can be a lot of discovery data.


I still strongly recommend that you consider disabling the performance collection that is enabled for the Print Queue objects out of the box.  This can be a VERY large amount of performance data that provides very little value.  I discussed disabling these in a previous post – here:


The addendum MP is attached below:

Comments (19)

  1. Anonymous says:

    Hy there

    I got the same problem like Aleksey described. Does anyone have some suggestions?


  2. Anonymous says:

    Hy there

    I got the same problem like Aleksey described. Does anyone have some suggestions?


  3. Anonymous says:

    Thanks Kevin.  This was just what I was looking for.  

  4. Kevin Holman says:

    Hi Steve –

    After I wrote this, I saw Rob Ryan's article with a similar solution.  I wish I would have seen that a month ago!

  5. Kevin Holman says:

    @Hector –

    Create a Group of windows computer objects, based on a dynamic expression where name matches wildcard PS*.  Then create two overrides on the main print server role discovery – one that disabled it for all objects, then one that enables it for a group – using your custom group.  Then run remove-disabledmonitoringobject to clean up the old systems.

  6. Anonymous says:


    Thanks for the addendum, it really helps!

    I do have a request you might be able to help me with.  On our environment Print Servers are named with "PS" as the first two letters of their name. Those are the only Windows Based computers with print services I care to see under the Print Server Management Pack views.

    How can I change/update the discovery so it works only for those systems? I'm new to authoring MP's; I know those discoveries start from Windows Computers group, I'm thinking I can create a 'PS Group' and have the discoveries started there.  Is that an option?

    I'll keep researching this; any help will be greatly appreciated.

    Thanks again.

  7. Anonymous says:


    The View under Microsoft Windows Server 2008 print services/Print Server State now populates!! Thx for that

    But it is still empty for the State view under 2003 Print Services.

    I gather this will not be fixed as 2003 server is too old now.

    But thx again for fixing the 2008 print server part.

    John Bradshaw

  8. Kevin Holman says:

    @Aleksey –

    I dunno…..  I'd guess that something is sick with WMI on those machines.  Can you try and run them manually via WBEMTEST?

  9. K Engelhardt says:

    New version:



    Date Published:


  10. Rob Ryan over on his blog has also posted a simlar work around:…/workaround-management-pack-for.html

    My question is, if this is so easy to do, why haven't Microsoft released this officially yet?!?!?!?

  11. Aleksey says:

    Thank you, Kevin

  12. Aleksey says:

    There are new Alerts after install Addendum MP from my servers with Windows Serever 2008 R2 Standard Edition:

    Alert: Workflow Runtime: Failed to run a WMI query



    Alert description: Object enumeration failed

    Query: 'SELECT Name FROM Win32_ServerFeature WHERE Name = "Print Services" OR Name = "Print and Document Services"'

    HRESULT: 0x80041013

    Details: Provider load failure

    One or more workflows were affected by this.

    Workflow name: Microsoft.Windows.Server.PrintServer.2008.R2.Addendum.PrintServerRoleDiscovery

    Instance name:

    Instance ID: {1DD220AE-7D05-8A37-F45B-6003F52EBF98}

    Management group: MY-SCOM

    Do you have any thoughts on this?

  13. Erling Brandt Kjeldsen says:

    Any chance that you can provide us with a monitor and a view (fx. a small MP) to monitor and alert on "toner low / Paper Jam / Tray open and stuff like this ?   from our discovered Printers..  I have installet the 2008 portion of the Print Server MP and Rob's add-on MP to get my win 2008 R2 print servers. So i have the list of printers if i look at members of the "Print Services Instance Group"  – but all the printers are listed as "Not Monitored" 🙁  

    Yours Erling B. Kjeldsen

    University of Southern Denmark

  14. John Bradshaw says:

    Also Erling, U may want to check out the following which I'm sure Kevin would commend:…/focusing-on-the-printer-printer-monitoring-mp-supplement.aspx



  15. Steve says:

    You should really use the feature ID and not the display name – would avoid issues in future as well since the ID wont change.  This is a property on the WMI class

  16. momadmin says:

    Hi Kevin,

    Firsty Thanks for posting all such very essential and useful posts which really help us to fix day-to-day and unusual issues in SCOM 🙂

    I need to ask that Can we monitor a situation: if someone changes a print driver from the set one for a print queue.

    Can we monitor this that who made changes and receievd info as alert using SCOM.



  17. Nathan Campbell says:

    Take your time Microsoft on fixing this 🙁

Skip to main content