I'll sum up this post in the shortest amount of words possible: the DST 2007 update from Microsoft breaks Intellisync for SalesLogix.
I've had an experience with Intellisync outlined here here and considering it's Google's 4th site when searching for "SalesLogix Intellisync" (no quotes), I figured perhaps the "juice" could help me come up with something I can tell the people I work for.
During the preparation for DST changes this year, I did as much research as possible on the impact with regards to SalesLogix. I don't know the exact specifics but SalesLogix would not login after the DST patch from MS was applied. The initial response was a registry hack, which basically reverted the registry to pre-patch conditions and that is never a good sign. 6.2 Service Pack 6 and 7.0 Service Pack 1 were Sage's answer to the DST problem for good so I opted to go the path of least resistance and potential headache, which is to say I went with the service pack.
The problem with this approach is outlined in this ITToolbox posting: http://crm.ittoolbox.com/groups/technical-functional/saleslogix-l/62-sp6-bug-1355381
To sum up a lot of responses, the basic problem is that Intellisync is reporting an error during login, coincidentally the same location the SalesLogix client itself had a problem. Had Intellisync not start up or at least initialize it's sync process I might not think anything of the coincidence but it seems really suspicious. In my response (and my 2004 post), I reported that I believe Intellisync is an engine and ultimately it's the makers of the conduit that are responsible for it's behavior. Since my 2004 post both the engine and conduit updates have been given by Sage so my assessment seems pretty fair.
I didn't write this post to point fingers or play the blame game. As of this point, almost a month after the upgrade, I no longer care. I simply want this answered: Will it be fixed? If so, when?
If the problem can't be fixed, documentation should be updated to report the fact that someone who buys SalesLogix after 3/11/2007 most likely will not have a working Intellisync. It's misleading at best, false advertising at worst. The only 2 entities with the keys to fixing the problem are Sage and Nokia (previously Pumatech). I've heard nothing through official channels to suggest there is even an issue from either party. According to this link, Novell was quick to supply an Intellisync update to deal with the DST issue (scroll down to GroupWiseMobileServerDST.exe or do a search). It's not technically the same as the engine SalesLogix uses but it does suggest that the ball is silently in Sage's court, if a match is even being played (to overuse the metaphor).