OSX Lion + LiveMeeting

Today marked the first time that I had to attend a live meeting after I recently upgraded my primary workstation to OSX Lion. Unfortunately, it wasn’t the smoothest experience.

Typically, Safari renders these meetings the best so it is my go to browser for meetings. Unfortunately, I would get the prompt for trusting the java app and a window would load with nothing happening. Same with Chrome. Firefox actually rendered the window with a Java loading icon spinning for all its worth, but never actually loading the meeting.

So, bail and go to my VDI. Now, I use my VDI for 2 things, powerCLI and VMware access. Its pretty bare bones. I found out that it didn’t even have java to join the web meeting that way. Live Meeting actually told me my version of Internet Explorer was not compatible even after installing java. Seriously Microsoft? I ended up installing the live meeting client and was into the meeting 15 minutes after the start. Yeah for productivity.

So surely I wasn’t the first one to trek down this path of Live Meeting plus OS X right? Correct! This post outlines the issue fully AND the solution. Here it is if you want to avoid a click:

All I did was go to Java Preferences (under Utilities) and on the Advanced Tab, ensure that the last option on the list “Verify mixed security code (sandbox vs. trusted)” is set to “Enable – run with protections, no warnings”. This is probably what was causing Java to hang before opening the session.

So there it is. I figured I ran into it, others surely would as well.

3 thoughts on “OSX Lion + LiveMeeting

  1. Unfortunately, this only works for attendees. Apparently, the fix doesn’t work when presenting a Live Meeting. This appears to be because PowerPC code is used in Live Meeting presentations and Apple decided it was time to drop Rosetta from Lion.

  2. Livemeeting already worked horrendously with the Mac. The optimistic part of me thinks perhaps this is the excuse MSFT needs to come up with a real Mac client. The realist part of me thinks this is the excuse MSFT needs to not develop it any further.

Comments are closed.