:?: I just installed 2X AppServer 4.3 (build 199) using the single server scenario on Windows Server 2003 with TS activated. I'm testing the waters right now. I created a desktop object, but don't find a way to define apps for that desktop. Also, don't see where do I configure the users who will use that desktop (assign the desktop to them so that this it what they see). I'm not using the 2X Client, just the MS RDP client.[/url]
Hi there, If you publish a whole desktop, all the applications on the server's desktop can be used. If you need to publish applications you need to make use of the 2x Client Application. Nixu
I need to use this with CE thin clients, for which there is no 2X App server client. Isn't any way to redirect RDP clients to the 2X App server? Maybe changing the default TS server port?
Win CE Clients can only make use of loadbalanced full rdp desktops. I suguest you give a look at the 2X thin clients. This might solve your problem. 1) boot client with 2X OS, 2) publish apps from Application Server. 3) Launch apps from the 2X OS Nixu
I upgraded from 4.3 to 5.0 to test the new features. Since I needed thin client support, I installed ThinClientServer 4.1 on another server. The client PC running ThinClientOS would not connect (message said that there were no published apps for me). I rembered that in the ThinClientServer 4.1 setup screens, there was support for App server 3.x and 4.x, but not for version 5. I went and completely uninstalled App server 5, removed references to the registry, restarted the server, and installed App server 4.3, then published an app. I'm still getting an error message even from the Windows 2X client (Failed to get application information, 2X Application Server might not be running or you don't have permissions to run the application.). Please help.
Hello, please do the following steps and post the results here: - go to the Application Server - open the 2X Console then you got the Console Window and Terminal Servers should be marked. - select the first entry(there should only be one in your constalation) - klick on "Check Agent" is the Agent up and running? Are you running Appserv in direct or Gateway mode? Is your Server firewalled(e.g. Windows Firewall)? This could be an issue, too. Regards, Alex
The agent verified ok and was correct version (4.3 build 199). I'm using Direct Mode with no firewall. However, your suggestion gave me an idea. From the Check Agent screen, I uninstalled the agent and then installed it again. Then, I tried launching the applications from the 2X client and all went OK!!! Still need to try from the 2X ThinClientOS, but I guess it will be all right.
Well, from the 2X ThinClientOS I get the published application icons but they don't execute. I'll post a question on the 2X ThinClientServer forum. But regarding 2X AppServer, I would suggest two ways of enhancing this product that can increase its applicability to thin clients without having to use 2X ThinClientOS for those of us that would like to avoid using two products to get apps into a thin client: First method- Provide a 2X Client that can be installed in the Terminal Server. This client would not start an RDP session when launching an app since it's already running in an RDP session. This client would just connect to 2X AppServer, list the applications, and launch them directly from the current RDP session. Another way can be using the same existing client but having 2X AppServer recognize that the client is running from the Terminal Server and provide the apps directly and not through another RDP session. It all depends on which component (2X Client or 2X AppServer) is the one that establishes the RDP session when apps are launched. I tried this installing 2X Client in a different Terminal Server than the one that has 2X AppServer and it works fine except that if you minimize the 2X Client screen, you can't make it come back and switching between apps inside the RDP session is cumbersome. This would have to be fixed. Then, you can configure a thin client with a regular RDP connection to autostart the 2X Client installed at the Terminal Server and will get just the published apps. Second method - Leverage on the fact that Citrix client is available for thin clients and that 2X AppServer can respond to Citrix client requests. Provide capability to 2X AppServer to answer requests from Citrix clients (either thin clients or PCs) but provide the apps from regular Terminal Servers. 2X AppServer would be a gateway between Citrix clients and applications in Terminal Servers. When I think about this approach, a 2X Client is not needed at all, just an enhanced 2X AppServer. Saul Rodriguez
