(or, The Design of Exchange Direct Push in Exchange 2003 SP2)
Background
I bought my first cell phone in the summer of 2000 – the venerable Nokia 5160. With the attendant giddy excitement of a...
Updated Jul 01, 2019
Version 2.0
Blog Post
1. As was already mentioned here it does not look really as 'push' technology - it is 'pull' technology, as all the syncs are initiated by the device (here is why we need INCOMING http ports opened, right?). So why call it 'push'? Competing GoodLink is true 'push' technology as device only accepts updates directly from the corporate server (apparently saving air charges).
2. It is not clear what exactly is new - SP0 and SP1 have the same technology. Actually, at first I thought the mechanism described is ExchangeActiveSync for 2003 sp0sp1. So what do I miss? Seems like my hopes to get 'true push technology' with SP2 is a mirage.
3. It is not clear why to stick to this somewhat awkward mechanism with device requests loops (every request will cost you even if you are on unlimited data plan). At least in curent sp1 implementation the Exchange itself has to send SMS to device when changes occured, only then device open connection to the server to pull data. Is it different now in sp2? Or it is the same in sp1 (that is device periodically requests updates from the server) and we (O'K, I) just did not know it?
3. Whatever it is the simplicity mentioned (in the comments, at least) is first glance impression. That is it would be simple if it worked. Unfortunately, it is not really. It is buggy. I tested GoodLink technology and it IS simple - it took about three hrs to set up a pilot and make it work with Treo650. And it works flawlessly so far, setup was very well documented and easy to understand. And it is already four days as I am trying to make AUTD ActiveSync work on Exchange2003 with Motorola 220. Everything is set up according to all the docs I was able to get my hands on but it just does not work (to make sure it seems it WAS working for a while and then just stopped, with no apparent reasons). Since we can save some money using ActiveSync instead of GoodLink I'm still trying to get it working but...
Documentation is sparse, difficult to get and rather superficial. Software is definitely buggy and troubleshooting info is virtually non-existant. So what does anybody mean it is a 'simple' solution???
May be somebody can tell me how to make AUTD work or where to find troublshooting info?
2. It is not clear what exactly is new - SP0 and SP1 have the same technology. Actually, at first I thought the mechanism described is ExchangeActiveSync for 2003 sp0sp1. So what do I miss? Seems like my hopes to get 'true push technology' with SP2 is a mirage.
3. It is not clear why to stick to this somewhat awkward mechanism with device requests loops (every request will cost you even if you are on unlimited data plan). At least in curent sp1 implementation the Exchange itself has to send SMS to device when changes occured, only then device open connection to the server to pull data. Is it different now in sp2? Or it is the same in sp1 (that is device periodically requests updates from the server) and we (O'K, I) just did not know it?
3. Whatever it is the simplicity mentioned (in the comments, at least) is first glance impression. That is it would be simple if it worked. Unfortunately, it is not really. It is buggy. I tested GoodLink technology and it IS simple - it took about three hrs to set up a pilot and make it work with Treo650. And it works flawlessly so far, setup was very well documented and easy to understand. And it is already four days as I am trying to make AUTD ActiveSync work on Exchange2003 with Motorola 220. Everything is set up according to all the docs I was able to get my hands on but it just does not work (to make sure it seems it WAS working for a while and then just stopped, with no apparent reasons). Since we can save some money using ActiveSync instead of GoodLink I'm still trying to get it working but...
Documentation is sparse, difficult to get and rather superficial. Software is definitely buggy and troubleshooting info is virtually non-existant. So what does anybody mean it is a 'simple' solution???
May be somebody can tell me how to make AUTD work or where to find troublshooting info?