We are making great progress on the Gradenko and ActiveSync Connector technology. This last week we released BETA2 of Gradenko and expect to release BETA3 next week. We also expect to release an Alpha/BETA of ActiveSync before the December Holiday break. In our testing, we have successfully synchronized on all major mobile device platforms. Note: ActiveSync is an 'over-the-air' solution. Not a desktop sync solution.
So - Will your device be supported? We hope to provide you enough information to answer that question! Including a 'known' device support list and a known 'unsupported' list.
So let's walk through some of the logic....
Do you have a BlackBerry device? Then your device is supported using the BES solution from RIM. These devices are NOT a target for the ActiveSync solution.
Now onto ActiveSync....
The first question to ask is: Does your mobile device state that it 'supports connecting to Microsoft Exchange 2003 SP2 or later?'
If your answer is YES, then your device is supported and will work with the new ActiveSync connector technology.
The more common answer will probably be "I DON'T KNOW"....
If this is your answer, then the next question will be: "Does your phone/device run on one of these mobile operating systems?"
- Apple OS 2.0, 3.0, 3.1 or later - Symbian Series 60 3rd-5th Edition or later - Windows Mobile 5.0, 6.0, 6.1, 6.5 or later - Palm OS with VersaMail or Exchange ActiveSync Update software - Palm webOS - Android 1.5 and 1.6 with additional software OR 2.0 - Maemo Internet Tablet OS 5.0
If the answer is YES, then your device is most likely supported.
We will 'certify' several devices including:
- Apple iTouch and iPhone - Nokia e62, e71, N97 - MotoQ - Samsung Intrepid - HTC Pure - Palm Centro and Pre - T-Mobile G1 - Motorola Droid
These devices represent a cross-section of mobile device operating systems. We also have a list of 12 other devices that we also intend to 'certify', but the list above is the initial pass.
We believe that our testing and certification will validate the initial supportability of roughly 250 unique smart phones.
We will publish a Device Support Matrix and Flow Chart so that our customers will be able to easily tell if their device is supportable.
Even if your device is not supported using BES or ActiveSync, we will provide other email synchronization options that include POP/IMAP and WAP access to your GroupWise mail through your mobile device.
This information will also be available in a WIKI format that will allow easy updates and contributions from partners, customers and end-users to help communicate the best ways to get GroupWise email, calendar and contact data from GroupWise to your mobile device - no matter which device you currently own or which device you purchase.
We expect to publish all of this information when the ActiveSync solution goes to Public BETA or at least by the time we release the technology.
I hope this information is useful and look forward to your feedback and questions.
We are not prepared to publicly announce a BETA date or release data yet for the Mobility Pack.
We do expect to be in Alpha by the end of this month and we believe it will take us 3-4 weeks to get to BETA. So generally speaking, we estimate that Authorized BETA will be late February or early March.
This week has seen some significant break throughs on the Mobility Connector side and so there is encouraging progress.
I am dying to get my hands on the Mobility Connector. I have seen one client move to Google Apps and one move to Exchange in the last 3 months. Their reasons haven't completely relied on mobile connectivity but it gave them yet another excuse to justify their actions.
We applied for the authorized beta - and apparently did not make the cut. We have been waiting for this functionality for about 1 year. All of our senior management have iPhones and currently are not able to sync their calendars. They are pushing us to switch to Google Apps. I have been holding them off with the hopes of having at least something they can test. But it looks like this functionality is too little too late. And once we swtich away from GroupWise it will only be a matter of time before we switch away from OES as well. I love Novell products but if they cannot offer these basic services that others can then it makes it hard to continue to use them.
We have had several users try different applications (paid and unpaid) to try to sync - including companionlink (which is supposed to be one of the best). None of them worked correctly. The best solution so far is to start using a gmail calendar and delegate appointments to gmail and then sync with the iphone. But of course this provides only one-way synchronization - so some users have stopped using the Groupwise calendar altogether and are only using gmail.
I am currently an user for Notifylink, and it works flawlessly with the iPhone. But I do have to admit the whole process has it's drawbacks: 1.- Slow Push response You have to sync the message to a server somewhere, then that server has to locate your device, which in turn has to download the message. It usually takes about 5-10 mins... Not much, but a heck of a lot slower than Blackberry. 2.- Service Cost If you just have 1 or 2 users, it's fine. But when you want to have 10+ users, it'll almost cost u as much as the Novell license in the first place!!!, that is just not fair... 3.- Administration I now have a separate control panel to monitor, administer, and configure, FOR EACH USER. It's jut to painful
This is why I can tell you guys from Novell one thing: This implementation is sure to be VERY widely accepted.
Since I am a current user on another solution, I would like to enroll on the testing for this. Where can I signup?
We have not started BETA yet for the Mobility Pack. We will notify those who were selected as soon as we are ready. Please see Alex Evan's blog for more details on the selection process and where things are at.
I know why you had such a hard time finding it....it was posted in NGWList, not on his blog - it was only referred to in his blog.
Here is what he said:
We have hit a number of issues delivering beta, and I am not comfortable delivering something that is unstable. Until those issues are resolved we will not be releasing the product. Our first goal is to give a pre-beta to our current Gradenko beta customers, followed by rolling out to a broader closed beta group. I expect that to happen in the next few weeks. That will help us assess gaps and quality and give us a better idea of release dates for public beta and FCS. I anticipate that to be at least 3 months out.
A number of our customers are using NotifyLink, Toffa and Companion Link, or rolling out Blackberries in the interim.
I can assure you that this is a top priority for us right now and everyone who can is assisting in getting this shipped. I wish I had better news and I am sorry.
Unfortunately we are in the same boat. The delay in getting this mobility solution implemented has caused the higher ups to force us to Exchange. And to make things "easier" for me, we are moving from OES to AD. Shame that it has come to this, but maybe its for the best. It will make Novell stay on top of technology instead of following......