Automatic Update of Outlook Connector

[davidfy]

Would it be possible to develop some way of automatically updating the Outlook connector from a Scalix server (via ftp) rather than visiting each Outlook client individually?

This would help in keeping clients up-to-date with releases.

Thanks.

[ScalixSupport]

Hi!

Of course this could be done, do refer to the section "Automating Scalix Connect Installation"
at page # 29 in the Client Deployment guide at http://www.scalix.com/documents/Scalix_ ... 11.0.1.pdf

Thanks,
Subir

[swordfish]

The guide refers to automatically deploying the connector. However the biggest problem is that you have always in the release notes for every new connector - "delete the old user profile and create a new one". Deleting the profile and all old connector files can not be achived with the instruction in this guide.

[racmar]

swordfish,

I am also VERY curious about this one little sentence. I do NOT want to have to go to all of my 100 clients and recreate all their message stores. We have approx 50 offsite outlook users /w 1GB and 2GB mail stores. This would take us forever to upgrade them all.

Any word from the scalix gurus????

[ScalixSupport]

What is the current version of Scalix Outlook connect version which you all are trying to
upgrade?

If the old Outlook Connector is any of the Scalix 11.0.1 or above, you all may avoid to create
a new profile but if you have the connector installed for Scalix 11.0.0 or below, profile
deletion and creation of new and unique becomes essential. Yes there have been some
big improvements, one should take advantage of these.

Hope the confusion is gone now.

Thanks!
Subir

[swordfish]

What is the current version of Scalix Outlook connect version which you all are trying to
upgrade?

If the old Outlook Connector is any of the Scalix 11 one, you need not create a new profile
but if you have the connector installed for Scalix 10, profile deletion and creation of new and
unique becomes essential.

Hope the confusion is gone now.

Thanks!
Subir

The confusion is not really gone because your release notes say that we should create a new profile with previous 11.x.x version of the connector. It's not clear why "should" and in which cases.

[ScalixSupport]

Hi!

Sorry for the last post, just before you replied, I edited my response.

See if that clarifies.

Regards,
Subir

[swordfish]

It makes much more sense during install of a new version of the connector, the install to check for existing Scalix MAPI profile on the machine and prompt for deleting automatically such profile. Also to give capability during automated deployment via msi to be able to specify option "force delete old profile". This way much of the hasles will be avoided and you can still cater for clients with large profiles logging over slow links. I don't think this will be a big programing change but will help a lot.