I'm trying to set up a proof of concept app server for a low cost solution and so far it was easy installing the App Server and I thought I configured it ok but things just are not working quite right. Currently, I have the AppServer running on a Window 7 Ultimate machine with 4g ram. I have 2 apps published, one being Adobe Reader for a test. I can launch the app on my Xoom running Jelly Bean and the 2x Android Client (sort of) but instead of launching the app It launches the desktop (and I can then launch the app, but want JUST the app to launch). On two other Windows 7 Ultimate PC's (1 64 bit, the other 32 bit) using the client to try and launch the apps, I get the standard windows Remote Desktop blue bar at the top like it's remotely connecting but it goes away after a few seconds (and it shows the ip address of the client vs the server which is odd). I've tried connecting using an internal IP of 192.168.0.xxx and via an external ip and hostname, all results the same. I've logged out of the App Server machine so no ID's where logged in at the time. This is what I see in the logs: [T 05/00000018] Sat Aug 11 13:33:45 2012 - Failed to get MAC Address (The network name cannot be found. [0x00000043]) [I 0E/00000000] Sat Aug 11 13:33:45 2012 - Session login for user: user@domain.net/server-name, from IP: 192.168.0.110:56913 was successful. [I 03/00000005] Sat Aug 11 13:33:45 2012 - Domain in FQDN is not supported [I 06/00000034] Sat Aug 11 13:33:45 2012 - Resource LB User 'user' Server 'SERVER-NAME' Session state: 0 - New Session [I 06/0000000A] Sat Aug 11 13:33:45 2012 - User user@domain.net/server-name, Client CLIENT-NAME, Address xx.xx.xx.xx:56913 wants to open "#1" Application, Server SERVER-NAME:3389 is available [I 05/0000000B] Sat Aug 11 13:33:45 2012 - Client connection from Address xx.xx.xx.xx:56913 is tunneled to SERVER-NAME (192.168.0.115):3389 [I 06/00000015] Sat Aug 11 13:33:47 2012 - Session 2 User USER Address 192.168.0.110 Protocol RDP State Active Type Desktop SERVER-NAME
Windows 7 cannot act as a terminal server, so it will only allow publishing of desktops to work correctly. publish apps off a terminal server instead of the Windows 7 and you won't see a full desktop. through some quick tests, on android clients it will show the server wallpaper however no start bar will be available for the user, but on windows clients the app will launch by its own off a TS
