Please note that I am not a lawyer and all of the following is a rough interpretation of what I see from product use and available documentation I have perused. As always, liability issues and EULA interpretation requires qualified legal advice for your best protection.
Adobe appears to be fairly good about dealing with Terminal Services as a potential distribution platform. There are various reasons for this, I suspect. Adobe is a company which is traditionally a standard-setter in several fields, and the mind-set that produces this tends to spill over into other areas even if an organization is not incredibly familiar with a technology.
A classic example of this is their EULA for Adobe Acrobat Reader 5 and related products. Even though the Reader is freely downloadable, Adobe tends to be protective of their rights to it, and several of the normal subjects of discussion there seem to imply that you could be infringing use when installing on a Terminal Server. Fortunately, Adobe explicitly allows installation a Terminal Server to clear up that question. Section 2.2.1 of the EULA specifically allows installation of the Reader on a Terminal Server.
I would like more, of course, but if the average product had the amount of TS support that Adobe Acrobat Reader does, administrative installation would be a non-issue.
The following were primarily drawn from
Adobe Solutions Network: Technical Notes - Acrobat/PDF
Extending The Adobe Acrobat Installer On The Windows Platform
Deploying Adobe Acrobat Installer using WTS
Although there is no Terminal-Server specific support which I have seen for Adobe products, they do provide a set of forums for ad hoc free user-to-user support, and Adobe internal staff also participate. If you register for access to their forums, you can then directly log in to their news server for newsreader access. Look on the Adobe site for details; they don't hide this information, it is just inaccessible enough to make spamming a difficult proposition.