<div>
Thanks for the feedback, this is the only way I could come up with as well. So far a few peculiar bugs bugs in the RemoteApp technology....but still very cool stuff.
</div>


Thanks for the feedback, this is the only way I could come up with as well. So far a few peculiar bugs bugs in the RemoteApp technology....but still very cool stuff.

<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
I would like multipe users to open an Access Front End file on their profile desktop, and allow this to happen by publishing one RemoteApp. Is there a way of doing this that will direct each user to a file on their own desktop? <br />
<br />
I've tried the following arguement but the RemoteApp load fails with an invalid path:<br />
%USERPROFILE%\Desktop\Acce<wbr />ss_FE.mdb<br />
<br />
The filename will be the same on everyone's desktop.<br />
<br />
I realize I could create 40 different TS RemoteApp .RDP files, but I'm looking for a better way.<br />
<br />
I can get this to work as Short Cut but when I try and set it up as a RemoteApp it won't work.<br />
<br />
Thanks,<br />
Ken
</div>
</div>


Hello,

I would like multipe users to open an Access Front End file on their profile desktop, and allow this to happen by publishing one RemoteApp. Is there a way of doing this that will direct each user to a file on their own desktop? 

I've tried the following arguement but the RemoteApp load fails with an invalid path:
%USERPROFILE%\Desktop\Access_FE.mdb

The filename will be the same on everyone's desktop.

I realize I could create 40 different TS RemoteApp .RDP files, but I'm looking for a better way.

I can get this to work as Short Cut but when I try and set it up as a RemoteApp it won't work.

Thanks,
Ken

Using the %USERPROFILE% variable in Terminal Server 2008 RemoteApps

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.