Blog Entry

Submitted by sjt4423 on 17 June 2010 - 9:41am.

Not to sound negative, but I suspected that this would happen. I sympathize with those who want it "yesterday" (as I am also working hard to come up with reasons why there is no replacement mobility solution for the aging Intellisync). But when my clients ask me about this, I tell them that we are still a good 3 or 4 months out (even if the product is released next month), which allows for more "bake" time in my own environment.

I've been playing with the tech preview since it was released during the US Brainshare conference. It has gone through some very significant changes and improvements. My hat's off to the developers and project managers of the datasync crew. However, there are two very real issues that I would really like to see resolved BEFORE the release (as it will directly affect how well received the product is in our environment):
1) HTML Email compatibility: I understand that you can flip-the-switch on hidden attachments in the connector settings... However, this only allows the html attachment to come down and you need to select it (on iPhones, anyway) to view the email in HTML. Unfortunately, the Droid does not even allow you to open attachments with the .htm extension, so this work around does not, well, work.
2) Not enough information when querying the company address book: So far, Droids do not even have access to the system address bood (sigh)... but for the iPhones, there is a query screen - but the problem is that you only get their email in the query! It would be nice if it included phone numbers and physical addresses.

Anyway, for the most part, I like the steady improvements. Keep it up, Dean - and if at all possible, please consider my 2 main issues mentioned above. :-)

-thanks

Submitted by tmstone835 on 17 June 2010 - 11:59am.

The good news is that you are still moving forward and that you have released another update. The bad news of course is that it isn't ready yet but you already told us that would be the case.

It sounds as though you are 80 to 90 percent along. That last 10 or 20 percent is the hardest sometimes so keep plugging away. My compliments to the team.

Tom S.

Submitted by bigdog on 17 June 2010 - 1:17pm.

That many admins are rolling the tech preview out into production just so that they can offer their mobile users with something other than vaporware?

While I speak for my users, I believe the majority would agree, the installed GroupWise base doesn't really care about that Novell wishs to "demonstrate the central role Novell Data Synchronizer" but rather would like a the bugs that were carried over from GroupWise 7 to 8 fixed, they would like a mobile solution for their email.

Why does it seem that Novell is not helping with the basic needs of it's users? Yes Microsoft SharePoint, SugarCRM and salesforce.com might be wonderful useful products but they don't have anything to do with a GroupWise mobile solution other than the fact that Novell made the choice to include them.

What good are the chrome wheels and spinners if you have no car to put them on?

Come on Novell, get back to the basics and forget the fluff.

Submitted by aaronm04 on 18 June 2010 - 12:03pm.

I very much appreciate the updates and honesty about the progress of this. That said, another push makes for further frustration for both my users (who have to deal with IMAP as the only mobile solution for their new smartphones) and me (who has to deal with more months of questions about iPhone/Android/webOS sync solutions). It would have been easier to accept a Fall 2010 release announcement last Fall (2009) rather than a series of release date pushes which is what we got. Maybe certain progress indicators showed the timeline that was announced. Whatever the reason, it makes it no less frustrating.

With this latest delay, I've considered deploying a pre-release version of the server. However, because there is no upgrade path from the pre-release to the full release, I'd rather not install and configure the services twice, much less ask all the users who installed it on their phones to have to reinstall it for the production release.

Aaron

Submitted by joe_mr on 21 June 2010 - 3:14am.

F... off connecting Microsoft SharePoint, SugarCRM, salesforce. This is !not! the central role of the Novell Data Synchronizer. We need this product SO LONG time ago. Laughable news.....
Sorry for my ostentation, but..... ahh forget it!

Submitted by jchamp on 21 June 2010 - 12:06pm.

Doesn't the mobility pack team talk to the GroupWise team working on SP2? Shouldn't they be testing their work against the Beta as a matter of course?

I agree with those who say why wait for Sharepoint, etc. Take care of the core user base, then roll out additional connectors as they become available. Email and calendar are key for many users.

-Jerry

Submitted by emerson on 21 June 2010 - 1:37pm.

The first beeing....with Novell acting like this...again and again, it's not the competition you need to worry about. Loosing existing customers and keeping possible new one's away can be achieved without any help from MS and others..

Second, the focus on what type of SW and what type of development is beeing done gives the impression that the customerbase is NOT that intresting. Instead, it starts to look as if the main goal is to be "any other player" in the field for add-ons to Microsoft Networks, which in turn might highten Novell's value for a take-over.

Submitted by ketter on 23 June 2010 - 6:43am.

It is important to have a solid release. But when you realize how long customers have been asking for the Mobility Pack, it should be released first. People may be asking for Sharepoint, SugarCRM, etc... connectors, but I'm not hearing it. You need to get a solid Mobility Pack out the door ASAP and then worry about the other connectors.

Submitted by okuepfer on 23 June 2010 - 7:35am.

Sorry to add this here - but Replacing the Mobile stuff (Nokia) is urgent case in at least on of our projects.

Urgent means - after this blog started, which made clear it will be not vavailble latest by begin of August, they launched now Exchange Migration Project, where it is evaluated, how long this will take - and they are extreamly pushy on this, as they wait now since early spring for a solution.

So please please please - tell us a RELIABLE Release Date - and make shure this is in near future. I beleive October will be not what the customers are willing to wait for.

I am so sorry to write this here - but we NEED this product working for GROUPWISE.
Other features sounds great, but do NOT have this need, like GROUPWISE does.

Oli

Submitted by jmarton on 23 June 2010 - 11:56am.

"Spending money [...] will not be acceptable in this case"

Sorry, but migrating to Exchange does in fact involve spending money.

It's unfortunate that installing something temporary isn't acceptable. Many people are successfully using the technology preview with various mobile platforms. NotifyLink is an alternative to those who don't want to put beta (or alpha) software into production.

Yes, it stinks that there isn't a production release available now, but that doesn't mean there isn't a way for GroupWise customers to successfully sync mobile devices. In fact, not only are customers able to do this today, but there are a couple of ways of doing this even if neither is the "perfect" solution.

Joe

Submitted by dlythgoe on 30 June 2010 - 4:27pm.

I wanted to provide another update on our plans and timetable for Novell Data Synchronizer. The timing of the Mobility Pack is just as we communicated it in our previous update: September. But we'll be releasing the engine, the GroupWise connector and the initial set of third-party connectors in July. As I've stated many times previously, the development schedule and process for these components have been completely independent of those for the Mobility Pack. And the Mobility Pack release schedule has in no way been adversely affected by releasing these other components earlier than expected. Details on our plans are provided below. As always, I welcome your thoughts and comments.

Availability Details

We have decided to ship Novell Data Synchronizer in two phases. First, we will release the Novell Data Synchronizer engine, the GroupWise connector and connectors for SharePoint, SugarCRM and salesforce.com. These components will be available in late July. Please note that these connectors are being developed by a separate team and have IN NO WAY delayed the release of the Novell Data Synchronizer Mobility Pack.

As we communicated earlier, the Novell Data Synchronizer Mobility Pack will ship in the September timeframe, with a public beta available in July. Customers who want to test-drive the product can access the open technology preview here until the public beta is released.

Purchasing Details

As a reminder, Novell Data Synchronizer is not supported on GroupWise 7, and GroupWise 8.0.2 will be required to enable its full functionality. Customers current on GroupWise, Novell Open Workgroup Suite or Novell Open Workgroup Suite Small Business Edition maintenance will be entitled to GroupWise 8.0.2, as well as the Novell Data Synchronizer engine and the GroupWise connector. Customers current on Novell Teaming maintenance will be entitled to the Novell Data Synchronizer engine and the GroupWise connector. Connectors for third-party applications must be purchased.

Platform Requirements

Remember that the initial release of Novell Data Synchronizer will only run on the 64-bit SUSE Linux Enterprise Server (SLES) 11 platform. While the SLES entitlement provided with GroupWise cannot be used to meet this requirement, the shipping version of Novell Data Synchronizer will include its own SLES entitlement. More details will be available in the product's end-user license agreement.

Dean

Submitted by emerson on 7 July 2010 - 2:26am.

but hopefully a giant leap for Novell..

You know, Joe M and Dean, I think at least for myself, I'd like to make one thing clear.
We are NOT the one's trying to be negative or anti-novell in any way.
I think it's quite the opposite. We, the one's complaining, are out here trying to defend the installed base of Novell solutions either at our own sites or, in our case, at the customer's sites. The truth today IS that it's easier for the customer to go away from Novell than to defend the installed base.
Once, with Zen or Netware as the base for the customer, it was easier to defend issues or delays.
Today, with the issues around with Zen and OES, the message we receive from the customer is more like "why ?"...... MS is easier.

And, to be honest, even though Im the first to loose due to my focus and history with Novell's products, Netware, Zen, etc..,, I to have to confess that while MS's solutions are getting more stable and easier to use...YES; even from my perspective, the Novell alternative's today have lost quality. Probably in my p.o.v, due to the ever expanding Linux and Identity product focus at Novell.

It comes down to the basic's,
Make the essential products stable and keep them current, then we'd have a MUCH easier task selling Teaming, IDM or whatever......

Submitted by rmyers1968 on 21 July 2010 - 12:19pm.

Hi, I am wondering if you guys are considering making a VM appliance of the GW mobility. I figure if more than 50% of sites chose to roll out a VM appliance that requires only minor configuration changes to get up and running with their GW system, it would be great for those sites. But more importantly for BUG catching and Support.

If over 50% of sites are using the same VM, it makes BUG catching so much easier for you (since you have a copy of the exact VM that is deployed). You could set it up on OpenSUSE and even publish on VMWARE's site... (VMware Server and ESXi are both free, for those whom have yet to adopt visualization). You could even set up VMs for Oracle's, XEN and Microsoft, but given VMWARE still has most of the market share (particularly with people still with Novell) and ESXi installs and runs on a modified Linux (so no extra OS licensing required).

I figure when the product is released, and there are issues, you can either easily reproduce and fix (if the problem is in GW mobility) or locate more easily the source of the problem...

I sort of assume your lab is most likely already using virtualization for testing purposes, so this would not involve mush extra work.

Just trying to suggest ways to make a roll out a little easier for everyone (also reduces amount of time spent on testing install procedures...)

Ray

Submitted by stanleytee on 26 October 2010 - 3:29am.

I am aware this thread is a little dated now so am unlikely to get a reply but, I have tried several times to find the SugarCRM connector mentioned above but to no avail, does anyone know where to actually download this from?

Regards and thanks

Oliver