Browse to the Platform page for the Windows machine on which you are wanting to configure the Terminal Services monitoring. On the right, toward the top of this page, click on "New Server". Give it a name, say, "HOSTNAME Terminal Services". In the "Server Type" drop-down, select the new Terminal Services type, which should be there if the plug-in is doing its thing. The required "Install Path" field baffled me for a sec, but it should not really matter what you put in here. I just put "C:\WINDOWS\System32\svchost" in there. Click OK.
You will be told you have to go into "Configuration Properties" to finalize the configuration. I set my "Auto-Discovery for Sessions" to On, and clicked OK. A few minutes later, the Availability and Active Sessions showed up as indicators under Monitor. You can add "Inactive Sessions" and "Total Sessions" as well through the Metric Data tab (click on "Show All Metrics", and set collection intervals to begin collecting).
When you browse the Platform, you will now see your Terminal Services Server listed as a Deployed Server.