EAS 6.3.1 Client and Outlook Add-in

[djthriller]

The 6.3.1 client and Outlook add-in are available from Autonomy as of
yesterday.

Haven't done much testing, but it appears the certificate is no longer
required during installation of the Outlook Add-in. I'll be working on
creating a package for deployment via SCCM today. I'll post results.

[joyrex]

Hello,
Have you been able to get the 6.3.1 client to work with Outlook 2010 ?
Not having any luck here..

[normansoth]

Hi,

what is the issue you are getting?

[Kenny Yuen]

I downloaded the 6.3.1 EAS client and tested on my machine with
Outlook 2010 32 bit. Here is what I did,

1. Install the setup.exe
2. Installed the easext2007setup.msi

When I open Outlook, I can see the stubbed messages with the icon.
However, when I open them, it only brings up the stub and not any
attachments. It’s as if the client was disabled.

I checked the disabled items and don’t see anything there. I also
checked the add-in’s for Outlook 2010 and do not see the add-in.

Does this work for Outlook 2010? Or has anyone seen similar issues?

On Wed, Feb 23, 2011 at 7:36 AM, normansoth <lim...@hotmail.com> wrote:
> Hi,
>
> what is the issue you are getting?
>

> --
> You received this message because you are subscribed to the Google Groups "Autonomy/Zantaz EAS Archive Forum" group.
> To post to this group, send email to zantaz-eas-a...@googlegroups.com.
> To unsubscribe from this group, send email to zantaz-eas-archive...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/zantaz-eas-archive-forum?hl=en.
>
>

[PerArdua]

Hi Kenny

All you should need to do is run the setup.exe with elevated rights.

I tend to run it from an elevated command prompt.

Regards

PA

[Kenny Yuen]

Thanks PA,

I just tried it with elevated rights and got the same thing. Are you
running it on Outlook 2010 32 bit? I'm still waiting for our vendor
to get the 2010 add-in for EAS 6.3.1, I was told the EAS 6.3.1 Client
was only for Outlook 2003/2007.

thanks again

[normansoth]

Hi,

Now there are two EAS client:

- one for Outlook 2003/2007 which size is around 30 mb.
- one for Outlook2007/20010 which size is around 350 mb.

Maybe you don't have the correct client for Outlook 2k10

[joyrex]

I was able to get mine to work by downloading the seperate
outlookplugin install for 6.3.0, installing it and then running the
setup.exe from the 6.3.1 EAS client install. Stubs retrive, but still
very buggy and locks up when trying to search by folder.

where did you get this 350mb installer for Outlook 2010 ? I did not
see anything on automater

[Kenny Yuen]

I'm using the EAS Add-in (350meg install) and the stubs will not work.
I see the add-in tab in Outlook 2010 32 bit, but the stubs do not
work. If anyone has the EAS 6.3.1 add-in for Outlook 2010 working,
please let me know how you did it. I haven't had any luck.

Thanks!

[normansoth]

Hi,

I have been able to make it work the only issue I got was with offline
synch where the retrieval was not working. These has been partially
fixed with version 6.3.1

[Kenny Yuen]

Thanks for the update, are you running your EAS IIS in 6.3.1 also?

[normansoth]

Hi,

Can you try the following test:

From outlook 2k10, go to the EAS Addin en click on the EAS web client
icon

1. It should open the EAS Web client interface with all the mailbox's
folders and subfolders. Is that working?
2. If the interface is displayed, click on a message and see if it
well open. Only the .eas should be retrieve.

This is to test the connectivity with the EAS IIS and see if the
retrieve function is working outside Outlook 2K10.

[PerArdua]

I did an install of 6.3.1 last week.

6.3.1 client for Outlook 2003/2007 silent install tested fine, using
the clientconfig.exe to generate this as with the previous client
process.

6.3.1 addin using a customised transform, geenrated by Orca worked
fine on a windows 7 x86 with outlook 2010 x86 and windows 7 x64 and
Outlook 2010 x64.

Using the x86 addin when you have Outlook 2010 x86 and the x64 addin
when you ahve Outlook 2010 x64.

The transform can be pushed using the quiet mode or passive mode.

Tested using an elavated command prompt running the setup.exe.

Regards

PA

[Jbutler]

I was able to successfully install after manually installing the
Visual Studio Tools and Microsoft Office 2010 primary interop
assemblies.

When a new user logs, they receive the EAS Com Add-in dialogue box and
have to click install before using the client. Can we prevent this?

[Kenny Yuen]

Hello,

Can you let me know the version/order you did the install?  We can't
seem to get it to work here.   We have 64bit win7 machine with office
2010 32 bit.

Thanks!

On Mon, Mar 21, 2011 at 12:02 PM, Kenny Yuen <kenny...@gmail.com> wrote:

[djthriller]

Sorry for opening this post and abandoning it. As is the usual, I hit
another road block trying to deploy an EAS feature and had to shelve
it for higher priority items.

At this point, the EAS Outlook Addin 6.3.1 dated 2/22/11 is installed
and functioning well on our Win7 32bit with Office 2010 32bit
workstations. The installation was completed manually following
instructions on pg 92 of the EAS for Exchange Installation Guide for
EAS 6.3, 2/15/11, Revision 1. I took the liberty to adjust the
instructions.

- Microsoft .Net Framework 3.5 SP1 (went with already installed
Microsoft .NET Framework 4)
- MSXML 6.0 SP1
- Windows Installer 3.1 (went w/ 5.0 that comes w/ Windows 7)
- Visual Studio Tools for the Office System 3.0 Runtime (went w/
Microsoft Visual Studio 2010 Tools for Office Runtime (x86))
- Office 2007 Primary Interop Assemblies (went w/ Microsoft Office
2010 Primary Interop Assemblies)

I've kicked off an attempt at deploying via SCCM on a XenApp 5 for
Windows 2008 32bit server. I'll update with status tomorrow. The SCCM
push is completing the following:

- MSIEXEC /I MSXML6_x86.MSI ALLUSERS=TRUE REBOOT=SUPPRESS /QB
- vstor40_x86.exe /q /norestart
- MSIEXEC /I o2010pia.msi ALLUSERS=TRUE REBOOT=SUPPRESS /QB
- msiexec /i "EAS Outlook Addin Installer.msi" /qn ALLUSERS=1

An AppSense Environment Manager configuration will be used to apply
proper registry settings at server startup.

[djthriller]

No luck with the first attempt at deploying via SCCM using the
Autonomy provided instructions. The prerequisites installed without
issue.

I was able to manually install the EAS Outlook Addin after the SCCM
XenApp image deployed using the SCCM installation package. However,
the EAS addin did not function until I also manually the following
registry keys and values copied from a functioning Windows 7
workstation.

- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\User Settings
\Autonomy.EASOutlookAddin
- HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\AddIns
\Autonomy.EASOutlookAddin
- HKEY_LOCAL_MACHINE\SOFTWARE\EDUCOM TS\EASEXT

Also, each user is prompted with the Microsoft Office Customization
Installer requiring them to Install the Autonomy.EASOutlookAddin.

Not exactly what I would call a ready for primetime installation
process. I will be contacting our EAS support vendor to determine
whether instructions for deploying to a terminal services environment.

[djthriller]

Almost there. The SCCM deployment is working.

- MSIEXEC /I MSXML6_x86.MSI ALLUSERS=TRUE REBOOT=SUPPRESS /QB
- vstor40_x86.exe /q /norestart
- MSIEXEC /I o2010pia.msi ALLUSERS=TRUE REBOOT=SUPPRESS /QB

- msiexec /i "EAS Outlook Addin Installer.msi" ALLUSERS=TRUE
REBOOT=SUPPRESS /qn

I'm not sure that all of my AppSense EM applied registry settings are
still necessary. I'll review that this week.

The final piece to correct is the MS Office Customization Installer
prompt each user receives requiring them to Install the
Autonomy.EASOutlookAddin.vsto. The command below installs the .vsto
silently, but only for the current user.

- "C:\Program Files\Common Files\microsoft shared\VSTO
\10.0\vstoinstaller.exe" /s /i "c:\program files\zantaz\eas outlook
addin\autonomy.easoutlookaddin.vsto"

[Jbutler]

I was able to suppress that final add-in message via GPO turning off
macro checks in the security settings of Outlook.