I have been using screen connect for a while now and am very impressed.

I have been trying to expand it use into my new Xenn Destop environment, unfortunately when the unattended client is installed no matter how many desktops are running screen connect see it as the same machine.

As such you can see in the console one machine that keeps changing its name. Hope this makes sense and was just wondering if anyone else has experienced these issues or deployed the agent to citrix.

It sounds like you are using an installer that uses the a PREDEFINED name instead of using the machine name. Create a new installer that will use the machine name. This way if you install it on multiple machines it will bring up a different machine name on each install.

For anyone else that may want to use ScreenConnect on XennDesktop I have managed to solve the problem.

It seems when ScreenConnect calls back to the server it uses a predefined string attached to the service, this is fine in most uses as each install is different and generates its own connection.

The problem with XennDesktop is the client is installed on the base image then duplicated on all child machines.

Using the dynamic name changes it in the portal but because the string is the same it will report as the same machine but with a different name. Therefore if you power on 5 child machines you will only see one in the portal as all 5 clients are essentially identical.

To solve this issue I changed the connection string on machine start up to include a unique value from the child machine.I gathered the machine name and with a little conversion edited the connection string to include this.

This now reports each child machine as unique in the portal.

I have attached my script for others use, my naming convention for this script was VPCTEST#### so you will need to alter the mystring section of the script to match yours.

i have a different question about xenDesktop all my users are logging using citrix which is fine i can support them to see there screen but the chat option is not usable and screen sharing is not usable since screen connect is installed on the local machine and they dont see it and i share my screen it pops up on the local machine not on the citrix desktop

Hmm, that's potentially a XenDesktop issue rather than a ScreenConnect one; have you tried contacting Citrix about it?Or does anyone else who uses XenDesktop have ideas on how to do this? We admittedly aren't all that familiar with it.

So far if you want to use the chat tool in a XenApp environment ScreenConnect agent needs to be installed on the XenApp server. You can then change the session you are looking at and message the currently accessed user. Unfortunately, there is no way to specify which session through the web console.

Are there any current XenApp users using ScreenConnect in their environments? I'm taking a second look at ScreenConnect cloud next month and I have to be able to connect to XenApp sessions. How does this work now? Have there been any improvements?

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.