08-26-2009 07:23 AM
I was wondering if anyone had the 6.5R1 code running in production yet. If so, how is this code? Is it running well or are you seeing issues with it? 6.5R1 seems to have a number of fixes I need, but I am leary of putting an R1 version of code on our production units.
09-01-2009 10:28 AM
09-01-2009 06:49 PM
I have a few days' experience with 6.5r1. I cannot help you with 64bit questions as I only run XP/Vista32. Tthe only issue I have seen is rewrite differences (the app is Splunk) between 6.4r2 and 6.5r1. Network Connect works fine (32bit), and they didn't break AD/LDAP/DHCP integration either....
I'm not ready to upgrade my customers beyond 6.4 yet.
09-03-2009 08:48 AM
I've been having users testing it and first thing I ran into is users attempting to type in terminal server addresses in the Terminal Service launch bar that's just been added.
Have you found a way to remove it?
I am waiting on my Windows 7 and Vista 64 users to get back to me on their experience.
09-03-2009 08:51 AM
Oh and the release notes for 6.5r1 states that WSAM can be launced from 64 bit browsers on a 64 bit machine only through Java Applet with 64 bit JRE installed....
09-03-2009 09:42 AM
No, i haven't. I think i know where the radio-button is to dis/enable it... but i haven't checked all of my roles to see if i inadvertently enabed it...else it doesnt obey the button???? I have downloaded the config XML, but havent found it there either.
I'm also getting the following error upon reaching max-session-timeout:
Application popup: HttpNAR: dsHostChecker.exe - Application Error : The exception unknown software exception (0x40000015) occurred in the application at location 0x6aba1a36.
along with a C runtime error.... But this may be due to having a 4.x Cisco VPN client installed as well. Also, I use the NC launcher, not a browswer connection. so your mileage may vary.
09-03-2009 10:16 AM
I have looked everywhere for an option to disable it. Guess I will have to be more thorough while reading the manual.
Sorry to hear about your other issue. Thankfully we have license for 250 users and only an average of 100 users.
09-03-2009 01:06 PM
I loaded it to test the Exchange Activesync "Authorize Only" access. This works great, and does header checking so that only Activesync traffic comes through.
I'm testing XenApp 5.0 and 5.1 next.