Re: Using rdesktop on single Windows applications via SeamlessRDP
Dotan Cohen <[email protected]> Tue, 19 Jul 2011 20:52:08 +0300
| Newsgroups | gmane.network.rdesktop.user |
|---|---|
| Message-ID | <CAKDXFkP3zSx9-YcA=KKJ0LuhiZjEsGtgsYQyehD6=Nh8R4en1Q@mail.gmail.com> |
On Tue, Jul 19, 2011 at 19:20, Christopher Roberts <[email protected]> wrote: > Well you have really provided us with all the information you require ;) - > from that page it states: > Quite so, but I thought that I might have been in error so I didn't bother mentioning what didn't work for me. >> Then run rdesktop with: > >> rdesktop -A -s "c:\seamlessrdp\seamlessrdpshell.exe notepad" > Of course, as there is no connection info there it fails. My Windows install is in a VirtualBox VM, so I'm not sure which server address to use. The obvious 127.0.0.1 didn't work! >> Please note that under Windows Server 2008, both seamlessrdpshell.exe >> and the program on its command line must be published Terminal >> Services applications. Also, seamlessrdpshell.exe must have >> command line parameters enabled. This is accomplished through >> the Windows Server 2008 "TS RemoteApp Manager's" >> "Add RemoteAppProgram" dialog (remoteprograms.msc). > > I assume this would not be the case with Windows7, but I have never run > Windows 7. > I don't know if this will be an issue, but in Windows 7 "Terminal Services Manager" is called "Remote Desktop Services Manager" and I don't seem to have it in this Home version of Windows 7 (google makes me understand that Ultimate has it, at least). Thanks! -- Dotan Cohen http://gibberish.co.il http://what-is-what.com ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/