I've been testing the new Citrix Profile templates. So far in testing the WI 5.1 template is working with both Mac Safari and Mac Firefox with Xen Desktop 5.1. I'm going to try to test Citrix client delivery. Not sure if it works with Mac or not.
One issue that has always occurred. We use Network Connect with a ACL that limits it to the ICA ports instead of JSAM since is seems more robust. For Xen Desktop role, we point the "Home Page" to the Citrix Xen Desktop web server to start this immediately. However, the home page tries to load before the NC client is finished connecting, giving some error messages while trying to connect to Xen, and requiring you to click a link to manually connect to Xen. It works but is not seamless. There should be an option for the Home Page to wait until NC connects.
Finally, after NC connects on the Mac, the window stays open on top the the browser window. You have to hit the "-" button to minimize it. I'd sure like NC to automatically minimize after connecting the way it does in Windows.
-- Next... Testing full VPN NC on Mac using user certificates, and Windows Xen 5.1 testing, and Citrix WI 4.6 testing under windows.
The response from juniper support concerning the RDP Launcher was this:
The RDP launcher is a new feature introduced in 6.5R1 release code. It is enabled when you check the option to allow user to use Windows Terminal Service. If you are not using Windows Terminal Service feature under user role >> general, then please uncheck it and RDP launcher will be removed from user's bookmark page. If you are using Windows terminal Service feature, at present release it is not possible to remove it. I am working with development team if we can add a new option to allow admin to disable the RDP launcher at moment as I have seen several customer requsting the same.
Removal isn't an option if you want to use the windows terminal service feature...
i have been running it since it came out both on our test box and in production about a week after, it works perfectly in 64bit mode which is the reason we deploed it, i have tested it up to windows 7X64.
a few things i did notice when switching from NC to WSAM
We had a small group of users test Network Connect 6.5 and 2 people said they were prompted to reboot their PC after NC installed. Then were asked to reboot again after rebooting the 1st time. I have never seen any reboot requirements before with NC. Has anyone else? We do not have GINA or TOS Bit enabled.
Also there is a new prompt that comes up asking you if you want to run the file neoNCSetup.exe. You can choose Always, Yes, or No. Not sure why Juniper added this. Seems to just confuse the end user even more.
We had a similar issue regarding some machines needing a reboot after installing the 6.5R1 Network Connect client. It appeared that if the machine had a previous of Network Connect, a reboot wasn't required.
This was a big enough issue for our area that was rolling out the client that I opened a case with Juniper. For our specific case, it appeared to be related to leaving on our current/old IPSEC client. If we removed the old IPSEC client and did a fresh install (no previous versions) of Network Connect, then it wouldn't request the reboot.
We've been running 6.5R1 for the past two weeks on a cluster of SA4000s and we've had quite a few client issues;
Norton 360 + WSAM = BSOD
Symantec Antivirus + WSAM = intermitent local DNS/WINS/NetBIOS name resoultion issues
ZoneAlarm + WSAM = No worky
Supposedly these issues are being addressed in 6.5R2 which is scheduled for release in November 2009. A workaround to these problems is to use JSAM or NC which appear to work fine in all of the above scenarios.