locked
Core OS MP / Terminal Services 2008 - Bug in the discovery ? RRS feed

  • Question

  • Hi Everyone,


    One of my customer has exactly the same problem that we have heure : http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/d82ffbdf-f861-462a-a5a8-765d0178401d

    Impossible to monitor Terminal Services on Windows Server 2008 R2.


    So, when we look at the terminal services discovery, it's targeted to the Windows Server 2008 Full Computer. -> OK
    Now, you take a look the group, you could see that the Windows Server 2008 Full Computer Group must normally include R2, but this is not the case -> Problem :s

    A group containing all computers that are running a Windows Server 2008 Full (including R2) version of the Windows operating system

    when you open the group, you could see that there is only windows server 2008 and not any R2. So for me there is a mistake in the description of the group or a bug in the core os mp.


    Thank you

    Bests Regards

    Christopher

     


    Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be
    Thursday, May 5, 2011 1:21 PM

Answers

  • THe MP you need is called remote desktop services.  This was the name of what previously was called Terminal Services.  This MP is specific to Server 2008 R2.  The older Terminal Services management pack is the wrong one in this case.

     

    You can access the RDS management pack here http://www.microsoft.com/downloads/en/details.aspx?FamilyID=bd5710af-7218-4162-9b94-23396625e3b3&displaylang=en



    Microsoft Corporation

    Thursday, May 5, 2011 8:30 PM
  • TS monitoring is targetted to "Windows Server 2008 Full Computer" class, not the group. You can check the group because the class criteria is the only criteria for the group...

    The criteria for the group is only Windows Server 2008 Full Computer and i can confirm the group doesn't contain r2 machines. But to say it's a bug would require to figure out the discovery (discover windows 2008 servers), for now i'll just keep it as a incorrect copy of the group description (from windows server 2008 computer group, which is the only 2008 server group that doesn't have a r2 counterpart and corresponding class).  


    Rob Korving
    http://jama00.wordpress.com/
    Friday, May 6, 2011 12:31 PM

All replies

  • Did you install the latest server base operating system management pack?
    Regards,
    Marc Klaver
    http://jama00.wordpress.com/
    Thursday, May 5, 2011 4:08 PM
  • yes, I've got the last version. I same the same behavior in my three environments. When I check the Windows Server 2008 Full Computer Group, it contains only Windows server 2008 and not any R2. (or regarding the group description, it must also contains R2).

    Could you confirm that you have the same ?


    Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be
    Thursday, May 5, 2011 8:23 PM
  • THe MP you need is called remote desktop services.  This was the name of what previously was called Terminal Services.  This MP is specific to Server 2008 R2.  The older Terminal Services management pack is the wrong one in this case.

     

    You can access the RDS management pack here http://www.microsoft.com/downloads/en/details.aspx?FamilyID=bd5710af-7218-4162-9b94-23396625e3b3&displaylang=en



    Microsoft Corporation

    Thursday, May 5, 2011 8:30 PM
  •  

    I also imported it, but after 24h, I noticed that none of my R2 servers have been discovered. So I found that the Windows Server 2008 R2 Full Computer Group population is disabled by default, and the RDP mp is targeted on it, so it couldn't work like this, I had to create a override. Why ? Nothing is the mp release notes about that, I didn't find the reason.

    From what I could I see, Terminal Services 2008 mp seems to be more complete than the RDP mp, and excepted from the group discovery issue, I don't see why it couldn't work with windows server 2008 R2.

    So, do you confirm that there is a bug with the population of the group Windows Server 2008 Full Computer Group which must also contains the R2 servers ?

     


    Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be

    Thursday, May 5, 2011 8:40 PM
  • That would do it.
    Microsoft Corporation
    Thursday, May 5, 2011 8:44 PM
  • TS monitoring is targetted to "Windows Server 2008 Full Computer" class, not the group. You can check the group because the class criteria is the only criteria for the group...

    The criteria for the group is only Windows Server 2008 Full Computer and i can confirm the group doesn't contain r2 machines. But to say it's a bug would require to figure out the discovery (discover windows 2008 servers), for now i'll just keep it as a incorrect copy of the group description (from windows server 2008 computer group, which is the only 2008 server group that doesn't have a r2 counterpart and corresponding class).  


    Rob Korving
    http://jama00.wordpress.com/
    Friday, May 6, 2011 12:31 PM
  •  

    Hi,

     

    In the following document, we can see “Not all the objects are automatically discovered. To discover those that are not automatically discovered, you must use overrides.”

     

    Remote Desktop Services Management Pack Guide for Operations Manager 2007 - Understanding Management Pack Operations

    http://technet.microsoft.com/en-us/library/ff723845.aspx

     

    Meanwhile, regarding the object discovery issue, please also refer to:

     

    Remote Desktop Services Management Pack Guide for Operations Manager 2007 - Troubleshooting

    http://technet.microsoft.com/en-us/library/ff723844.aspx

     

    The management pack discovers no objects.

    Make sure that your RD Session Host servers are using application mode, not Remote Administration mode.

    Discovery of RD Session Host servers running in Remote Administration mode is disabled by default.

     

    Hope this helps.

     

    Thanks.

    Nicholas Li - MSFT
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, May 9, 2011 2:58 AM
  • Thanks all for your replies ;-)

    I prefere the Terminal Sercices mp as there is more views, graphs, .... but as you said, for win2k8 R2, no other choice than using the remote desktop services.

     

     


    Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be
    Wednesday, May 11, 2011 6:42 AM