RemoteApps won't open outside of TS session (what's the point, then?)

Question

Hi guys, 
Not exactly new here, but it's been a while! I have a question regarding the deployment of RemoteApps to PCs on an enterprise network with
Windows Server 2008 (32-bit): I've created the necessary .rdp files, set the apps not to require a TSGateway authentication for now, because we're not in a production environment yet, disabled network authentication
for the same reason (test users are on an intranet). 
After creating the .rdp files for, say, Adobe Reader or MS Word in the Packaged Programs in Program Files at the root of the server, I copy-paste the whole folder to a network location, so that they are shared with test users. (I tried to just place a shortcut
to this folder in the network drive, didn't work) 
That's when the problem starts: double-click on the .rdp files brings up the logon window, and when users click on Connect, they get an error message saying the remote computer couldn't be found and please contact the System Administrator (yours truly). 
If we are to assess the pros and cons of RemoteApps vs full TS session logon, we first need to be able to launch them... I must have overlooked something, probably something real basic, but I can't for the life of me find what! 

Answer 1

Hi,
In TS RemoteApp Manager, under Terminal Server Settings, did you specify the correct FQDN for server name?  This should be done before creating .rdp files and/or windows installer packages.
-TP