I've tried the IP Virtualization but it didn't make any difference. My question is does anyone know of a way to get Remote Desktop Server to provide a unique computer name for each session? i.e. I've tried the "FLAGS" registry fix I've used before but can't get any It's a D/B application written in OpenEdge Progress so I guess does need to have the ability for a unique connection.
MOCHA RDP LITE CANNOT CONNECT WINDOWS 7 SOFTWARE
the applications client software is installed on the Remote Desktop server and works fine for User A, when User B logs in they get an error from this application along the lines of "There is already a computer with this All well and good except one of their business applications requires a unique computer name for eachĬonnection. We're looking at replacing the traditional client\server network at a clients site with a Remote Desktop based network and are running some tests. I have also Added the GPO from the MS article below but the logoff script and the folder are still not deleted. We also get in the servers Application logĮvent 1530 from User Profile Service - Saying Outlook 2010 still has registry handles openĮvent 1533 from User Profile Service - Saying it can't delete the users profile folder. I have tried installing the following hotfixes but nothing seem to resolve the removal of the profiles. This causes issue because we need to manually remove these old folder from the servers weekly. Script do not run and were are left with Stale user profile folders. We are experiencing an issue where when a user’s session is disconnected the Logout We are using a mandatory profile with folder redirection and login and logout script. We have windows 2008R2 SP1 server with RDS installed that is running Citrix Xenapp 6.5. Has anyone else had the same issue? Any ideas on resolving this? To use the main IP of the server and that RDS is preventing it from doing so (or something like that). I suspect that the security sandboxing that Java Web Start does is causing it to attempt I have turned off virtual IP on a test server and this allows things to work as expected, so it is definitely the interaction with virtual IP that is causing the problem. This is in comparison to running from my PC, where javaws downloads the individual files referenced in the JNLP file and
MOCHA RDP LITE CANNOT CONNECT WINDOWS 7 DOWNLOAD
I have run Wireshark to see what is happening from a network point of view and there is no traffic after the download of the JNLP file. The process just drops to about 200K of memory and stays inactive. The JNLP file downloads and javaws.exe launches to run this, but never gets any further. We are running RDS on 2008 R2, using per session virtual IP, and we are unable to run any applications that use Java Web Start (we've tried 3 so far).