I now have complete feature parity with a 64-bit OS (Windows 7) running
64-bit Office 2010 with LiveMeeting and Office Communicator, that I had
with 32-bit Office 2007 not too long ago.
You can read about the changes for LiveMeeting here and the changes for the Conferencing Add-in here.
You can download the updated LiveMeeting client here and the updated Conferencing Add-in here.
For the add-in, you will have to choose 32-bit or 64-bit which depends
on which flavor (32-bit or 64-bit) of Office you are using. The only
64-bit version of Office to date is the Office 2010 Technical
Preview/Beta. Any version before that is 32-bit.
Anyone running a 32-bit OS is going to use 32-bit Office and will want the 32-bit version.
You can certainly run 32-bit Office on a 64-bit OS, and in this case,
you would want the 32-bit Conferencing Add-in. One reason I can think
of is if you want to keep using Xobni until a new version of that
application comes out, or you have other 32-bit Office plugins that you
use.
I am using 64-bit Office primarily for a relatively strange reason.
Sure, running native applications is a good thing, but I am mainly
interested in applications not "mucking around" with my Office
configuration by adding in things covertly.
The biggest offender I can rattle off the top of my head is the plugin
that iTunes installs into Outlook without asking. It has a notorious
history of causing problems with delaying Outlook to shut down. I'm not
picking on Apple, I just wish it was an optional component of iTunes.
Plus, I'm just a fan of 64-bit applications in general.
Note: One limitation of using Live Meeting on a 64-bit
OS still remains - uploading Office documents other than PowerPoint to
LiveMeeting and having LiveMeeting dynamically convert/scale the
documents to each client's workspace. I generally don't use this
feature so it is a non-issue for me.
The technical reason - a 64-bit Microsoft Office Document Imaging (MODI) print driver does not exist.
