The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Advanced Outlook Integration/Intellisync and 7.2
Posted: 17 Oct 07 6:48 AM
|
Have any improvement been made in these features in 7.2? I tend to stay away from both as I have had extensive problems with duplicate meetings/contacts, meetings disappearing and a host of other 'outlook' upsetting issues in the past. Have others had the same experience? Is it any better in 7.2? Thanks |
|
|
|
Re: Advanced Outlook Integration/Intellisync and 7.2
Posted: 18 Oct 07 2:32 AM
|
I would say no. Others may disagree. I now use Exchange Link instead which, whilst it isn't perfect, is a whole lot better in my opinion and very stable. It's also setup on the server so you don't have to visit each PC. |
|
|
| |
|
Re: Advanced Outlook Integration/Intellisync and 7.2
Posted: 19 Oct 07 7:35 AM
|
Like Mike I too use EL in our production environment and Intellisync is NOT installed on anything.
Yes, it has a few issues but there is an SP in the works (for EL). The specific date has not been publicly announced but I'm sure you will hear from Mike (or me when it happens.. probably Mike first... -- rjl |
|
|
|
Re: Advanced Outlook Integration/Intellisync and 7.2
Posted: 21 Oct 07 4:05 AM
|
Please advise - what is Exchange Link? (We run Exchange in house)
Will this fix the integration problems we are experiencing when using running SLX 6.2 in Terminal Services? And, we use a remote mail program to send email from mobiles via Exchange - will Exchange Link automatically log these to SLX history?
And ... Is there a product which can take an inbound email and automatically log to history and create a ticket? and is there a method of handling user not found?
|
|
|
|
Re: Advanced Outlook Integration/Intellisync and 7.2
Posted: 21 Oct 07 6:05 AM
|
Exchange Link is a separate product (developed entirely by SalesLogix) and is a server based model for linking with Exchange in order to sync data to/from SLX. It has many advantages over i/sync in that it only requires setting up on the server (no client pieces). It's entirely suited to TermServer as there's nothing on the TS to be done. Everything traverses via SLX direct to Exchange from a nominated server. Ideally, the link sits on the Exchange Server - but you can put it anywhere (i.e.SLX server) *BUT* it has very specific requirements if you do (hence, best to put on Exchange Server itself) - and only then needs the SLX OLE DB Client to work. You can get further details and pricing from your BP.
|
|
|
|