Your Android powered device is now setup to synchronize data using Exchange Activesync
Exchange ActiveSync is a synchronization method that uses direct push technology to ensure changes in Email, Contacts, Calendars, Tasks and Notes are automatically recorded in both the WebMail Service and the mobile device in real time.Įxchange ActiveSync is supported on most mobile devices on the market, including Apple iPhone and iPad, BlackBerry, Google Android, Motorola, Nokia, HP WebOS and Windows Phones. I am going CRAZY WITH 4 SETS OF DATABASES.Īpple does live sync with Outlook, Google does live sycn with apple Nobody live synces with anybody.Ĭan anyone recommend any VOIP platform that actually LIVE syncs databases?Ĭall comes in and directly goes into databases with a single click?Īm I dreaming or are we in a 4-5 way fight of contact management with us guys on the losing side.Web Wiz Mail Servers support Microsoft Exchange ActiveSync. Google contacts, or apple contacts on iPad, Outlook contacts or even heaven forbid Facebook contacts. Now please tell me can RON LIVE syc its db with another database like So a new call is a new contact added to db and progress / tasks are made on this contact. New client calls the 1 office number and if I can take the call I do or I let it go to my assistant. My assistant and I both need to monitor all calls coming in ( ONE SINGLE CONTACT LIST.Ĭan RON actually synchronize with any other contact databases. Im Road warrior and I count on my virtual staff to help me manage my contacts. The other more disturbing possibility is that microsoft is trying to force users over to Outlook, I do hope that is not the case.
The main possible reason I can see for microsoft to discontinue Gmail EAS support in this update is that the update with calDAV and carDAV support may have been delayed beyond July when google will disable EAS support on their end, and microsoft dont want errors occuring when users try to sync gmail on their phones between then and the update to support the new protocols.
Essentially what they have done is transitioned from EAS to their own proprietary protocol, but they went via an open protocol so as not to cause user revolt, and so they can claim to be all supportive of everything open. Google is now trying to push developers to its own proprietary syncing protocol. These are two open protocols for calendar and contact syncing respectively which google is also trying to make more closed by restricting access to a whitelist of developers (thankfully including microsoft).
However Gmail support for contact and calendar syncing will be continued in WP through CalDAV and CarDAV in a future update. Google's support for EAS is not ending til July, so I'm not quite sure why Microsoft has chosen to end it earlier.