How to present RDP client or browser URLs

[norrcomm]

First, I don't know what happened but my original post in this forum disappeared, like someone deleted it. In any event how can I do the following:

1- I want to present mstsc.exe /v:192.168.1.x /f for a connection to rdp clients
2- how can I present http://www.google.com for browsers.

I have tried both and cannot present them in 2x.

 

[gs]

Hi there,

I use win2008 r2 as TS with 2xVDS and have published mstsc (parameters /v:[IP] /f) as well as IE6 (internet options -> home page set to google.com). I use 2xClient and no issues.

Please provide a few more details about your environment?

Kind regards,

 

[kalel76]

First, I don't know what happened but my original post in this forum disappeared, like someone deleted it. In any event how can I do the following:

1- I want to present mstsc.exe /v:192.168.1.x /f for a connection to rdp clients
2- how can I present http://www.google.com for browsers.

I have tried both and cannot present them in 2x.

Not sure about mstsc.exe. I just tried doing what you were doing and I found that 2X was filtering out the mstsc.exe application from the terminal server. When you publish a single application and search for the mstsc.exe file, it mysteriously does not show up, though I have verified on the source terminal server that it is there. I think this is because there is now a feature to publish "Remote PC Desktops" though I am sure you need to pay for this feature.

About presenting a particular web browser page (like google), I have an open ticket with 2X on this. I have browser redirection turned on the client because dynamic web sites just don't display well in terminal services. However, there are times that I need to display websites in terminal services (such as internal sharepoint sites). What I do is publish iexplore.exe and pass the URL as a parameter. You would think that this would just launch an instance of IE on the terminal server. However, if the client has URL redirection enabled, whenever someone launches the published IE app, the client will redirect the URL to the local PC instead of opening IE on the TS session.

Any one else experience these quirks?