Client setup per-profile?

[biggertigger]

I have the latest server build (6.2.512) and have installed the Client on a Terminal Server. I am having to set up the Client connections, etc. for each user profile that I log on with. Shouldn't this be totally seamless to the user who logs on, so they don't go thru this setup process to get their apps published to their profile? I feel like i missed something...

Thanks for any advice you can give!
- Jeff

 

[nixu]

Hi there,

The client should be installed on the Client Machine (eg. on a Win XP machine) not on the Terminal Server.

Nixu

 

[biggertigger]

Thanks for your reply. What I am wanting to do is have my users RDP into a Terminal Server (let's callit TS1) and then be able to run a published app that is actually hosted on another server (let's call it TS2), running the 2X Application Server. If I don't install the Client software on the server my users are connecting to (TS1), how will they see the published apps?

Again, maybe I am missing something. Thanks for any insight you may have!

- Jeff

 

[nixu]

Hi there,

It is still possible to use the 2X Client in that manner..

So basically your issue is that users need to set up the client the first time they connect to TS1.

This can be solved by setting the default settings in the Client MSI before installing it on TS1. See the Documentation on how to do this. It should be quite strait forward to modify the MSI using Orca.

Nixu

 

[biggertigger]

Thank you again for your help. The MSI modification sounds like what I need to do, so I will take a look at that.

I appreciate your time helping me with this - Thanks!

Jeff

 

[zippo]

Thank you again for your help. The MSI modification sounds like what I need to do, so I will take a look at that.

I appreciate your time helping me with this - Thanks!

Jeff

more to this if you connect an rdp session from within another rdp session you get performance degradation. always connect from the client and do not tunnel rdp over rdp.