Is there a way to monitor RDP connections to servers? For instance I can’t connect TS (RDP) to server however the server is up, due to which we wont get any SCOM alerts. On researching on this I found there is a Remote Desktop Management Pack for SCOM and Terminal Services MP as well, would this be helpful in my case? http://www.microsoft.com/downloads/en/details.aspx?FamilyID=bd5710af-7218-4162-9b94-23396625e3b3&displaylang=en http://www.microsoft.com/downloads/en/details.aspx?FamilyId=1428ECFD-8C3E-4779-A383-4C491D2684F3&displaylang=en Thanks all for your assist. xs

Hi, I guess that depends on what exactly you want to monitor. Most management packs monitor from the server itself. So they check if required services are up and no specific errors occur. What I think that you are asking is to actually connect from another machine to this machine. So some kind of an outside test, a perspective, a watcher, synthetic transaction. The management packs you mention are very helpful for checking the server itself. So if services are running, no strange errors, performance counters and those kind of things. These mps do not do a test from another machine back to your machine. I would definately first look into those two management packs and see what they come up with before going further into synthetic transactions. If you are looking for that it is a bit more complicated. Of course you can check if the port is up by doing a port check to start with. Bob Cornelissen - BICTT (My BICTT Blog)

Hi, As Bob mentioned, these MPs will monitor the server status. To monitor connection, you may need to setup rule/monitor to check event log regarding the connection failures.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.

I'd second the comment to monitor port 3389. I've even seen where that port is monitored not just to tell if Terminal Services is listening, but also as a backup to the heartbeat and not reachable monitors. Sometimes when 3389 stops, so does a lot of other RPC and SMB functions, so checking this port can be an indicator of other problems as well.Layne, 2011 Microsoft Community Contributor Recipient

Thanks all for your insight I will create a port 3389 check and explore other possibilities. Your insights are really appreciated. xs

Create group based service monitor for Terminal Services service that targets your custom group. Example... In the SCOM console, go to the Authoring pane and select Attributes | Create new attributeEnter the name, next Discovery Method Discovery Type: Registry Target: Windows Operating System_Extended To get this, browse to the Windows Operating System, the wizard then creates the extended version because it is a sealed MP. Management Pack: Your New MP Registry Probe Configuration Key or Value type: KeyPath: SYSTEM\CurrentControlSet\Services\TSM Server1Attribute Type: Check if existsFrequency: 3600 seconds There are likely some improvements I could do here, but at this time I am only looking for the existence of the key (assuming the existence means its installed and running). The next step is to create a group based on this new attribute. In the SCOM console, go to the Authoring pane and select Groups | Create a new group Name your group appropriately (TSM Servers) and select your MP Ensure you select the same MP the attribute is stored in, otherwise the extended class may not be available Skip the Explicit Members screen the goal is to have 100% dynamic membership On Dynamic Members, click Create/Edit rules Select the Windows Operating System_Extended class and click AddProperty: TSM ServerOperator: EqualsValue: True Finish out the wizard and your new group will appear.