Problem: Our webex client would install on the xenapp image ok for any user, webex would connect and work ok first time, subsequent attempts to connect to a test meeting would crash the webex client.
Solution – Create a SYMLINK
Ensure that Appsense AM Agent is STOPPED before beginning the install. It was preventing the installation from completing 100% (even though you get no feedback that the install has failed)
Run the cisco webex client offline installation from the cisco website
Start the Appsense AM Agent
Create a (symlink) as WEBEX is stupid enough to install itself into c:\programdata\webex
to ensure all users had their own webex installation be sure to run the following command to creation a directory junction point.
h=userhomedrive or other personal drive they have full access to
mklink /D c:\programdata\webex\webex1124 h:\webex
Open Internet explorer and connect to www.webex.com/test-meeting.html and test the login – the client should open fine and connect
Solution – Already installed but broken:
Stop Appsense AM Agent
Run the webex offline installer and remove all components
Browse to c:\programdata and DELETE the webex folder
Now follow the ‘Solution – Fresh Install’ above.
Thanks for the write-up…do you have a link to the WebEx client that you used?
Try this: http://kb.webex.com/WBX68743
Having setup Meeting Manager 108 error when utilizing symbolic links to my homedrive. Not sure if AppSense AM has difficulties interpreting symbolic links when performing rights elevation. Did you run into any AM issues?
AM was a bitch. Had to add each and every file under the redirected path (not the path, just the name of each dll as the symbolic kink that am logs were blocking was the full servername and path to the user’s home drive) and ensure trusted owner was unticked.. also added programdatawebex as an allow … 🙂
Did you use audio and video for Meetings via XA6.5 or was it just chat?
It was the webex ‘presentation panel’ / login page. So they could watch the presentation and hear the presenters audio and that was about all we tested.
The wyse terminals weren’t tested to pass thru audio etc.. though I see no reason why it wouldnt work?
Be careful about deleting the C:ProgramDataWebEx folder. WebEx Network Recording Player puts it’s application in that folder as well. There should be a C:ProgramDataWebExWebEx1524 (not sure if the ‘1524’ is consistent across major releases) that you can delete that will fix the 99% problem, but it sometimes comes back.
http://discussions.citrix.com/topic/339242-running-webex-on-2008-r2/ (References this blog post)
Basically, symlink to the C:ProgramDataWebExWebEX folder to the user’s profile.
Wow nice feedback Tony – thanks!
Per http://www.experts-exchange.com/Software/System_Utilities/Remote_Access/Citrix/Q_28639784.html, a user with a very similar issue said that this issue was fixed in PVS 7.6. Does anyone have any further information? I have done a precursory review of the 7.6 release notes and don’t see this issue referenced. (http://support.citrix.com/article/CTX138199#7.6). We are seeing this issue in our environment with XenApp 6.5.