Novell Cool Solutions

GroupWise Mobility Update



By:

January 14, 2010 2:35 pm

Reads:15,446

Comments:51

Score:Unrated

Print/PDF

As you can imagine I am getting daily emails about the status of our GMS replacement. In my last blog on the subject I stated that we would probably be shipping that product this month. Since that time and, as is often the case with software projects, things have not run entirely to plan. We had already put the product through our superlab for scalability testing, and refactored some of the code in response. We also had some additional work to do to change the underlying database that we using. So far everything looked good in our lab – we were getting good throughput (1000 users/devices in the test environment) and stability was good.

Then we got to the internal rollout. This is where we hit some problems – lab data and real life data are two very different things. Some users would sync with no issue at all, and some users could not get even the first item to sync. Product stability took a hammering too. Our engineering teams have been working through the issues and are making good progress, to the point where we are now syncing what seemed to be our most problematic mailboxes. In that process we have seemingly hit the item limit of an iPhone (9,999 emails), and we have Palm, Windows Mobile, Nokia and Android devices working against the server too.

In response to some of the early testing that we, and others have done, we have made a fairly major product change. We have consolidated our platform support matrix down to a single configuration. That supported configuration is 64bit SLES 11, using the PostgreSQL database. There are a few reasons that we did this, but the one that will help our customers the most is that we are delivering it as an Add-on CD for SLES. This means that you install it much like OES, and the wizard should take care of most of the configuration for you. This should allow you to get it up and running more quickly and reliably, and will cut down on the install types of questions that our support team gets.

We also looked at delivering the product as an appliance for XEN and VMWare, however, we chose to push that deliverable off until after we ship this first version. A question to you is how many of you are ready for a virtualized appliance, what kind would you want – and just as importantly, how many of you are not ready?

After all of the work that we did over the last 2 months we put the product through our superlab again, and results are very encouraging (caveat – test environment/data only). We seemed to comfortably scale to well over 1000 users on the configuration mentioned above. We also benchmarked it against GMS on the same hardware, and performed much better, both under normal load and very heavy load. On our test harness we had 1500 users configured and syncing with no real issue (CPU util, memory consumption, Disk I/O and response times were all within acceptable limits). We will get more real world data as we roll out more broadly internally, which is the real litmus test.

Our next milestone is to deliver the connector to our current set of Gradenko customers and let them validate it. After that we will go to closed beta, and then public beta. As I mentioned on NGWList yesterday I am expecting to get to public beta or FCS within the next 3 months or so, depending on closed beta experiences.

Dean recently blogged on the devices that will be supported here.

I am sorry that we are still not able to deliver the product, but I would rather we lived through this initial pain and get it fixed, rather than deliver something of low quality to our customers

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

51

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

51 Comments

  1. By:warper2

    Thanks for the update. I wanted to say that I am looking forward to the new product. GMS has been good but have customers that it would not work for. It will be nice with additional device support. I for one am ready for virtualizing it now and have been doing so with GMS for my company as well as for clients under Xen and VMware. I have had no real issues with doing so. I have only been supporting it on Sles for stability reasons. Never had it is as stable on windows. Surprise :-)

    Hope get to see it soon. Have customers who are really excited and waiting.

  2. By:jamesr9

    Great.

    So in Novell speak sometime in 2011 it should be ready.
    At this rate we’ll be on Exchange by then.

  3. By:rreurink

    Hi Alex,

    thnx for the update, but this is a real -groupwise killer- message. A > 3 months delay is just unacceptable for our site. There are issues with mobile devices every day, and because they are not supported, we can’t do anything more than swap the device, re-install the latest available Intellisync client and start over. We need a stable and supported solution for the Nokia E71/E72/E75 and we need it now. We are waiting too long now (no GW updates for a mobile platform over almost a year!)
    And support for a single configuration (SLES) is also a real killer, what happened with the Windows component? Just wiped out?

    As you can read, this is not the message I was waiting for. Good luck with your work, but this is so disappointing…

  4. By:dominicus

    And to answer your question.
    Yes we are virtualizing (only a small company with 7 users, but still) using vmware on MAC os X.
    We use mainly MACs and recently moved from SLES/OES2 to MAC server
    but Groupwise is too good to be rid of ;-)
    So have to have it running and on one server, so virtualisation is my only option.
    Have run GMS virtually on SLES/OES with vmware for 2 years before this and was working good.

    My two cents,

    DB

  5. By:jmarton

    I’m moving towards virtualizing my entire environment, so anytime I hear of an applianced-based solution I normally ignore it as you can’t virtualize a piece of hardware. But if we’re talking about a soft appliance, that is great. I’m already using one soft appliance in our ESX environment: M+Guardian. In addition, the supported configuration at that point pretty much becomes irrelevant.

    However, if delivering the software as regular software, it’s difficult to state only the most recent Linux version is supported for this product when Novell’s product lifecycle support page clearly states that the previous version is supported until 31 July 2016. That’s over six years away!

    Joe

  6. By:soundsolutionsinc

    I fully understand that during a major upgrade like this, that sometimes you don’t have much to report on. WE STILL NEED TO HEAR FROM YOU. We have folks very tightly wound here, waiting to get the next new device sync’d up to GroupWise. Being left in the dark versus being kept in the dark, amounts to the same info.

    We have a large mandate here that all new technology must be on VM, unless otherwise proven not to perform well in that environment. Should the decision internally here be made that we can’t afford to go to Exchange in 2011, we will likely migrate our NetWare 6.5 servers running GroupWise 7.03 to SLES on VMs and them upgrade them to 8.01 HP1.

    I do fully empathize with you and your testing efforts and wanting to be sure the product is rock solid before deployment. Maybe the question is how much of an upgrade did you try to do, with the staff that you have. Yes, making a major jump forward is crucial to staying in the game, give the faithful extra jimmies for their everyday applications. Reading the Novell Connection Magazine article about Novell Pulse (https://www.novell.com/connectionmagazine/2010/01/feel_the_pulse_part_one.html?sourceid=NCM_0110_tt1) and the interaction with Active Sync and all of the other major apps, such as GroupWise, Exchange, SharePoint and others, this sounds like a great leap forward for messaging. Hopefully this will be a large enough upgrade to get attention of some of the Microsofties, with a solid deployment.

    Good luck!

  7. By:elogjngf

    64bit SLES with PostgreSQL is fine. Who needs/wants something else? :-)

    FYI, we are ready for a virtualized appliance. We will actually run it on vSphere 4 anyhow.

    Side note: Performance is not our primary concern. We can quite easily provide more ‘juice’, but we can never fix missing/broken features/functionality.

  8. By:WalterH

    Hi,

    I am expecting to get to public beta or FCS within the next 3 months or so,

    Most of my customers will not wait so long, here in Austria, last year the Novell guys told all customers: at November 2009 we have a working preview!
    Customer paid maintenance to get the product but Novell did not made it in time.

    So most customer decided: Q1/2010 to use the Active Sync Connector or migrate to Exchange!

    Btw. GMS is a pain and we have a many iPhones here!

    Walter

  9. By:bigdog

    We have consolidated our platform support matrix down to a single configuration. That supported configuration is 64bit SLES 11, using the PostgreSQL database”

    That is unexpected and such will have role in decision of keeping GroupWise in our organization as many things are up in the air right now quesitoning the idea of retaining GroupWise as our email service.

    As an organization that has will be shedding NetWare and moving file services to Microsoft servers, this makes a very uncomfortable situation to implement SLES since the intention was move GroupWise to Windows servers and perhaps naieve assumption that we had that the ActiveSync solution could be implemented on a windows server plateform.

  10. By:bbecken

    So is the new Mobility version going to come with an entitlement for SLES 11 64bit well?

    I’m sure I’m not the only one that’s getting SLES under the OES2 entitlement.

    Three months is a long time to wait as well. For us, stability/integration and device support are more important than scalability.

  11. By:bluebeagle

    Thanks for the update. It’s disappointing to hear that in your best case scenario Novell is going to be a full year behind all major competitors in offering ActiveSync support. You’ve got to know that in the tech industry you can’t ignore a game-changing technology like ActiveSync that long without taking a hit. I know of no one who would buy a collaboration product today – or for that matter at any point last year – that can’t support the iPhone.

    Your ActiveSync strategy focused entirely on preserving existing customers. It amounted to telling them that they could get support from third parties while you took your time to develop a bloated, multi-purpose, synchronization gateway. Who thought this was a good idea for wooing new customers to GroupWise? You should have had programmers working around the clock as soon as it was apparent that the iPhone was going to be a runaway success. Your competitors did. They even managed to implement it without Novell’s much-touted Microsoft partnership. (Yes, we all know about Nokia. That excuse buys you 6 months, not enough time to debunk the claims of the global warming extremists.)

    Novell should stop worrying so much about preserving its existing customer base and look for ways to offer things your competitors aren’t. You can start by eliminating the need and COST for third party solutions for fundamental features like anti-SPAM and anti-virus scanning. Take that consideration out of the equation like the online providers have done.

    Don’t sit still. If you keep going like this you won’t have to worry about hearing from disgruntled customers.

    • By:sveld

      “Novell should stop worrying so much about preserving its existing customer base and look for ways to offer things your competitors aren’t. ”

      That’s what they are doing with the new Datasynchroniser product.

      Agree with you that GroupWise should have a at least more basic spam/av gate.

  12. By:WalterH

    Alex,

    limiting this product to X64 and distribute it as Add-on CD is a very very bad idea!

    Most of my customer uses a XEN environment but there is no unpartitioned storage space! So it is impossible to install another virtual server only for AS! My idea was to install AS on the GMS or GW WA server – so the Add-on CD is also a problem. Installing the product on older hardware is impossible because most older hardware is only i386 capable.

    We need a product that works on SLES 10 SP3 (OES2 SP2) and newer, i386 and / or x64, with standard installation procedure (no Add-on CD) and works on a already installed GMS or GroupWise server.

    Walter

  13. By:bug2fix

    the new devices that won’t work with GMS are growing. The new windows mobile version 7 won’t help probably… (understatement) since today i’ve read old WM6 applications will not work on WM7… goodbye intellisync.
    This annoucement could be the killer for us using Novell solutions. Mobile phone usage and sync of PIM and Email are so common in our (or any modern) company, we need an regularly updated and stable solution, which GMS is not. If it IS released within 2 months, we probably will consider using it, if later (say >6 months) it will be hard to hold back Exchange demand from the VP’s… too bad.

  14. By:amarchetti

    This is so disappointing and is going to confirm Novell’s death in the market. I am a huge supporter of GroupWise and other Novell products, but in the last few years they have just lost so much market share and are dying a slow death because of decisions like these. They should have years ago moved all their products to Windows including Directory Services. Because of the delay on ActiveSync we have decided to move to Exchange and so have many of our Clients. I do not think Outlook or Exchange is better than GroupWise, but we have been forced into this decision.

  15. By:amarchetti

    This is going to be like the Sony BETA and VHS battle. The iPhone is going to force so many companies to move to Exchange because it has taken Novell far too long to bring out support for it. They should have just released the beta ActiveSync so that people could have held on just a bit longer. Now with no support, we have to go to Exchange. Beta is just that, people can live with the problems with beta software, because at least something is better than nothing.

  16. By:RENEK

    These are very bad news for all groupwise customers we have.
    What is running fail on novell?

  17. By:fcpeer

    Thank you for the update on this new solution.
    I guess I am like most others – waiting for the new active sync product and disappointed that it is still 3 months out. That being said however, I would much rather wait the 3 months and have a stable product that I can “set and forget” instead of having to deal with angry users who can’t get the thing to work properly and I have to keep applying patches (sounds like something we all know??)

  18. By:waly510

    Novell should stop worrying so much about preserving its existing customer base and look for ways to offer things your competitors aren’t. You can start by eliminating the need and COST for third party solutions for fundamental features like anti-SPAM and anti-virus scanning. Take that consideration out of the equation like the online providers have done

  19. By:sveld

    Hi Alex,

    Thanks for keeping us notified. Al tough disappointing to have a this delay, it’s understandable. As I expected the pretty optimistic release schedule might slip a bit (he, it’s a solution from scratch!), I decided in the meantime to use for smaller customers the Notifylink OnDemand service, which works great. We were pretty impressed by the hand’s-on we had with Gradenko and ActiveSync at the EMEA Summit, so it can only get better! I do believe releasing too early is not an option either (although we would love to see it yesterday), as major changes to the foundation after releasing is not something to get happy from, neither are bugs.

    We intend to run this solution 99 percent of the cases virtual on ESX. Guess a SLES11 lic is part of the deal for GW customers?

  20. By:grimlock

    I don’t see the big deal about providing an appliance. It’s the same code, you just pre-package a virtual machine for it. The only issue would be cpu/io bottlenecking, and that should not be an issue except for very large deployments, at which point it’s probably best not to virtualize it anyway, or only do so on a server with a low amount of hosts.

    I don’t see how providing an appliance that Novell pre-configures is more support work than letting the user load their own “appliance” by installing sled themselves and the product themselves. You have a lot of unknowns there to troubleshoot, but you know exactly how your appliance was installed because Novell created it.

    Support XEN/VMware out of the box. If the hypervisor supports the OS you are running it on (SLES 11 64bit) as a guest, then it should work just fine.

    • By:ecyoung

      With a SLES appliance, it’s installed and setup by someone else (i.e. Novell). If you’re a Windows-only shop, with no SLES admins, that’s a big deal. Or, you may have SLES admins, but none of them may have any experience/training with SLES11 yet, because they may be an OES shop, and Novell, in all their glory, still doesn’t support OES on SLES11 (it’s been 10 months since SLES 11 released!).

  21. By:anh2lua

    We are running VMware ESX so an appliance is good. However, I still like it to be supported on Windows OS as well, Server 2008 maybe?

  22. By:nanathlor

    Generally a good positive post, it’s sounds like you getting on top of things however it is a shame it’s been delayed and although I have no probs with SLES11 it’s a shame it’s not SLES10 as well for OES2 customers (unless your giving away free SLES11 standalone licenses for GW customers!)

    Our customers are all virtualised (VMware mainly some XENserver) and generally only have a few mobile “power users” that actively use email on their mobile devices so they won’t be forking out a small fortune to go to Exchange any time soon.

    For any Windows guys worried about installing SLES11 I would argue that if you can work out how to install Win2008 you can work out how to install SLES11, the installs pretty straightforward then once it’s installed the config interface will be web based anyway and let’s face it Novell are a Linux company after all.

    Looking forward to the betas.
    Dave

  23. By:jchamp

    The iPhone’s been out since June 2007. Nokia announces Intellisync to be discontinued in September 2008. So Novell says keep waiting while our staff becomes increasingly frustrated at the lack of an affordable solution. This appears to be the same old story at Novell. We’ve been a Novell stalwart, but non-responsiveness and product delays continue to make it increasingly difficult to stay with them.

  24. By:GiovanniCoa

    Hi Alex,

    It’s about two years that I’m challenging to maitain our customers on Novell platform, but 2009 is the year that I discovered that is definitively a “Mission Impossible”.

    The hope of a new Novell based on OES2 Linux was definitively destoyed at my customers eyes during the year 2009. Novell have killed the image of the most important products like ZENworks, GroupWise and NetWare respectively with ZCM, Mobile Suite and OES2.

    Serial killing consist i losting trust in ZENworks customers, loosing trust of GroupWise customers that have the sensation to have the same web interface of five years ago and OES2 without any significant improvement.

    GroupWise Mobile Server is the last broken hope.

    I only want to say you that I’m not happy of what Novell is doing now and also make you aware that you are loosing my customers.
    Good luck.
    Giovanni Coa

  25. By:jurev

    It is really not clever from Novell that you don’t support practically any new phone which came on the market in last year.
    I myself don’t care about server, because this is technical issue which we solve internally, but not supporting new phones is business problem and I can’t persuade my users not to buy new phones, because they will not be able to use corporate mail and calendar.

    • By:bigdog

      I’m not sure the nature of your comment but…

      I will go along with Novell in NOT supporting a mobile device that just released in the last year, hey it’s hard to keep up.

      But…

      The push for ActivSync solution was to support the iPhone. As it’s already been pointed out, those things have been out since 2007.

      2010 is here but no Novell-iPhone solution unless you have a budget to buy third party applications. Novell tell us they are going to support mobile devices but the haven’t been able to get anything to market.

      Seems odd that at least two other groups have a solution for what Novell cannot figure out???? That right there shows that there are some major problems at Novell.

      As a result, people are leaving GroupWise since the rule #1 in customer service is to keep the customer happy and Novell is not doing that. I miss the days along time ago when Novell rocked, GroupWise was the cat’s meow but that was then this is now.

      • By:blntskul

        Man, I feel like a broken record. Novell was first to market with a free sync solution. It was the best thing on the market at the time (Intellisync). Nokia bought Intellisync. Nokia scrapped Intellisync and didn’t bother to give Novell a heads up. Novell had to come up with a solution, which is what we’re talking about. Novell hasn’t been sitting on their hands for years, watching the mobile phones go by. From nothing to market in around a year for something this complex is a pretty good time frame.

        The competitors that have solutions for the iPhone merely added one more device to the list of products that they already support. It’s nothing like building an entirely new product. Be patient. The result will be worth the wait. If you need something now, pay for the third party app, like Notify. It works well enough, and you should realize that paying for Notify in addition to GroupWise is going to be cheaper than migrating to Exchange, by far.

        It should also be pointed out that Apple didn’t raise a finger to try to support GroupWise. They did provide Exchange support with Active Sync. Microsoft didn’t do a thing to support the iPhone – Apple did that work. Why didn’t Apple work to support GroupWise? For the same reason they’ve never lifted a finger to support Netware or OES. They’re elitist pigs who don’t care about the needs of a pretty large portion of their clients. How can they get away with it, you ask? Magic, I think. People go into the Apple store knowing they’re going to pay more, and they’ll have to trade out everything else they own to have the pretty shiny sparkly thing, and they do it anyway. It’s freaking amazing. I wish all of the disgruntled iPhone users would band together and kick Steve Jobs square in the ass for causing this discussion.

        If any of you drop GroupWise over the iPhone because your users demand it, it’s your fault. The fact is, there are options for iPhone support with GroupWise, and have been for a long time. You would sooner drop a superior product with long standing success in your organization than pay for a few licenses for Notify, or whatever else. You’re lying to your users when you say you can’t support them. The truth is that you CAN support them. You just can’t support them at no additional cost – for the time being. If your users are buying iPhones, they’re paying through the nose for the service plan anyway; or your company is. Since when did anyone who buys an Apple product give a rat’s ass about frugality?

      • By:RogerIThomas

        It’s odd just about all my past posts have supported Novell, but I have to reply back to your comments.

        You comment that Apple did all the work for supping Exchange, thats not correct. All that Apple did was code to an open, well documented and well tested API. GroupWise has never had such an API in place, instead it has been limited to a mix and match set of APIs. Novell has all ways defered the fixing of this issue and you can find posts going back 10+ years from people pleading for this to be resolved so that third parties can extend and expand Groupwise. Instead part solutions were delivered instead, such as the third party Nokia solution (which Apple was never going to support) or API retreads such as the web services layer that still can’t even compress its data stream so is unuseable on a mobile device.

        The greatest problem for GW is that it needs a gateway to convert it’s current APIs and data store into a communications process that can be used by phones. The new gateway may at last fix these issues but it’s way to late too market. face it for most GW sites it needs to be in place for the first shipment of the new ipad hit people’s desks not many months after.

        As for the rest of your post you are taking to point of view of an IT person, I have no idea where you work but most companies are run by CEOs, CTOs, CSO, CFOs who don’t care about IT. For the last 2 years all they seem to have cared about is their iPhone, iTouch, Windows Moble or Android device all of which need this gateway.

        I do agree that any company that still has GW in place at this time should wait as the Exchange roll out with be costly and take far longer, but all I have seen in the last 2 years is GW being dropped by company after company and the only companies I know who still have GW in place have it because they all cut their IT budgets to zero.

        Roger

      • By:chapindad

        Roger,

        I agree completely with you. The disappointment in the GW APIs has been going on since GW started and has only gotten worse since GW 5.5. Not being able to do a simple restore of a single message from tape is purely because of not having a communications server, GMS, to do that third party translation like exchange communications server. This should have been done back in GW 7 release and at least when GW 8 was released. And now a 3 month delay is going to put a lot of pressure on us to move to exchange. Right now we have blackberries but there is talk of moving to iphones because of the EULA from RIM. If this happens in the next few weeks then I may have no choice but to start down that path and once I go down that path I will not be coming back. If I am going to take the heat for email then I might as well use something that benefits my resume.

  26. By:blntskul

    You’re right about the API generally, but not about the mobility issue specifically. Let me rehash this some more. If you’ve kept up with the various blogs on this subject, you will have heard it before.

    Novell repackaged Intellisync before Nokia owned the product. When they made that decision, it was very logical. Take the best product on the market, rebrand it and give it to customers for free. And they did it before the other guys. Microsoft’s push technology with Exchange came along later. Active Sync as a protocol was not a standard, as you call it. It was a piece of junk that only Microsoft used and only Windows Mobile supported. It took some time before the major phone manufacturers gave in and included Active Sync support by default. You act as if it’s been a standard for 10 years or something. Up to this point, Novell had every expectation that Intellisync would continue to be a market leader in that space, and new phones would be supported.

    Enter Nokia. They bought Intellisync, picked out the pieces that they wanted, and scrapped the rest. This didn’t go one for 10 years either. By the time Novell, and the rest of the world outside of Nokia, knew that Intellisync was going to die, and that iPhone – or any other new phone – support wasn’t coming, it was time to make a fast change of course. So over the last year or so, they’ve built a solution from the ground up that works with the now prevalent Active Sync defacto standard. By the way, before Nokia changed direction and went with Active Sync, there were relatively few devices that supported it. Apple didn’t pick Active Sync support because it was some huge industry standard. They picked it because it was the Microsoft solution, and their business model is to support their own stuff first, Microsoft second, and that’s about it. Between Nokia and Apple, their decision to go with Active Sync is what turned it into a standard.

    Let me also repeat – there are options, and there have been options nearly since the iPhone was released. For many phones, GMS is still the free solution from Novell. For those newer phones not supported by GMS, you can buy Notify, or one of the other solutions. They offer a hosted model if you like, so you don’t even have to install it. So I’ll say it again – any company that drops GroupWise over the iPhone is making a poor decision. Not only because, for love of Pete, it’s a phone and there are tons of options, but also because you can absolutely support the iPhone with GroupWise.

    You’re right for the most part – CEOs, CTOs, CSOs and CFOs don’t think about IT as the focus – and they probably shouldn’t. Unless it’s a technology company, IT is like the plumbing. But guess what they do care about, almost unilaterally – MONEY. It’s the IT director or CIO’s job to help the people in command understand why things are the way they are, and to help guide them. And what I’m saying is if there’s an IT person, or director, or CIO out there that sits down with their CEO, CSO, CFO, etc. and tells them that they can’t have an iPhone because, gosh darnit, our email system just won’t work with it – it’s either a lie, most likely hiding an agenda, or it’s the mark of stupidity.

    If my CEO calls me over to show me his new iPhone – which, by the way won’t happen because I proactively offer other compelling solutions that make my users happy – but if he did, I would give him the 50 cent explanation about how we’re going to achieve his goal, and leave his office where I will immediately get on the phone with the Notify folks. It’s just not complicated.

    We have GroupWise in place because we’re not going to throw out a good solution for a phone, although, as I pointed out, we wouldn’t have to.

  27. By:grerikson

    You need to find another solution. As an end user for an organization that uses Novell Groupwise for its e-mail, I was informed by Novell in the fall, prior to my purchase of a Palm Pre, that I would have push e-mail within 30 days. Since then its been 30 more days, then 30 more days every time I checked back in. Now its 90 days, and my confidence in ever getting it on this phone in my lifetime is Zero. Of course, I’m also beyond my replacement period for the Pre as well. Welcome to the Bardo. Thanks, Novell.

    • By:blntskul

      Not trying to pick a fight, but if you’re an end user, why were you talking to Novell rather than to your internal folks? And why did you buy a phone that your company can’t support? And is this the first time you’ve ever had to wait longer for something than you anticipated? And who at Novell gave you a 30 day time frame? If that really happened, you should go ahead and let Alex know who he needs to fire. Oh, and I haven’t been keeping tabs lately – is the Pre currently synching with iTunes, or is it currently blocked? I bet Apple’s going to win that smack down. My sarcasm gets the best of me. It does sound like I’m picking a fight. Sorry.

  28. By:grimlock

    “If my CEO calls me over to show me his new iPhone – which, by the way won’t happen because I proactively offer other compelling solutions that make my users happy”

    I’m happy you have a work environment like that however most of us don’t. Let me give you an example of how it works in the rest of the world. I’m fairly certain that my situation is far more common than yours.

    CXO walks into your office on a Monday morning and says “I just bought this over the weekend. I need to get my e-mail and calendar on it. (Even better when I.T. is supposed to approve all computer related purchases, and this was bought and expensed, bypassing that procedure.) Better still is when the CEO’s administrative assistant walks into your office with their new phone and says, this needs to be set up on our system. I’ve actually not had that situation here but I’d bet we have some readers here that have.

    It’s exactly the same as upper management mandating a move to Exchange over the objections of I.T. It’s not because I.T. didn’t do it’s job, it’s that ultimately the upper management will consider it’s judgment superior simply because it is upper management, and not based on any technical knowledge of the situation. They want what they want and they pay you to make that happen. You not liking it is not a concern.

    Most of us don’t have a third party sync solution because we were using GMS. (Blackberry shops not included as you needed BES regardless) When I tell the CXO that unfortunately we can’t sync that device, but if you spend $XX,XXX on Notify we can have that up and going for you, he’s going to look at that as a failing of I.T. despite the fact that I.T. can’t get the purchase approved by management.

    Regardless of how the situation came to be, the expectation that someone above your head is never going to buy a phone without checking with you is going to get you disappointed in most shops. Many of the people I work with here will come and ask me my opinion about what a good phone to get would be and what will work with our systems. I also work with people above me that routinely show up with the latest toy they bought and expect us to make it work. I fully expect to see an ipad in here some time in the near future…

    “And what I’m saying is if there’s an IT person, or director, or CIO out there that sits down with their CEO, CSO, CFO, etc. and tells them that they can’t have an iPhone because, gosh darnit, our email system just won’t work with it – it’s either a lie, most likely hiding an agenda, or it’s the mark of stupidity.”

    That would depend entirely on the reason given. Right now, if you come to me with your droid phone or iPhone and want calendar sync, I’m going to tell you our system won’t work with it… BECAUSE… we don’t have a sync solution in place for that, and it’s not in the budget to put one in any time soon. So the reality is, our system won’t work with that. If however I just say GroupWise can’t work with that at all.. Then yes, I’d agree with you completely.

    We’re unfortunately in a bad situation of having to outlay money for a sync solution as a temporary holdover. Sure we could keep using it, but ultimately if the GMS replacement turns out to be good, you would much rather be supporting one platform for your sync needs and you would phase the temporary solutions out.

    The thing that’s saving a lot of companies Novell installations on a temporary basis is that they don’t have the money to rip and replace with an Exchange solution. Novell can only hope that what it ultimately releases makes the disgruntled shops happy enough to keep them from switching.

    • By:bluebeagle

      There are many lessons here for Novell, not the least of which is that those who live by the third-party solution die by the third-party solution. Intellisync was a good short-term strategy. In the long term the technology should have been bought or replicated in-house (as Microsoft would have done).

      blntskul said:
      “any company that drops GroupWise over the iPhone is making a poor decision.”

      Notify adds additional cost. So does GWAVA. And so does the anti-virus software. We actually pay more for GWAVA and anti-virus software than we do for GroupWise. Our administrative overhead is increasing, too. GWAVA, at best, requires a significant investment of time in self-study; at worst, it requires training (i.e. GWAVACON). Gradenko will exacerbate this problem. Now factor in the complexities of migrating from NetWare to Linux, especially if you aren’t already running Linux. Finally, add to this Novell’s recent decision to skip public betas and the instability and bugs that we have seen in the latest clients (crashing, phantom items in “Work in Progress”, etc). For many, the fact that another round of holiday-inspired iPhone acquisitions has come and gone and we STILL don’t have a good solution for it is merely “the straw that broke the camel’s back”.

      “If my CEO calls me over to show me his new iPhone….I would give him the 50 cent explanation about how we’re going to achieve his goal, and leave his office where I will immediately get on the phone with the Notify folks. It’s just not complicated.”

      NotifyLink is a nice product but those of us who have actually evaluated it know that it can be less reliable than both BES and GMS. You may find your CEO back in your office 3 months later demanding to know why he has to restart his mobile device all the time.

      Now I understand the desire to defend Novell. I’ve been a fan for over a decade. The problem is that they’re failing “The Dr. Phil test”. You may think their strategies were correct, that all of the decisions were the right ones at the time and that Novell is merely a victim of forces beyond their control. As Dr. Phil would say, “How’s that workin’ for ya?” Because from where I sit, the folks are headed for the exits.

  29. By:dali

    Normaly a struggle for keeping GroupWise for many of our customers (instead of Exchange) is painfull but we could win that part.
    Now all the management deciders does have an iPhone and they MUST sync it right NOW. None of all the other arguments does mather and only for that reason some of our customers already started a plan to migrate to Exchange. All thanks the syncing-problem!

  30. By:WalterH

    Hi,

    last year in Vienna the Novell guys told us: November 2009 (yes 2009) we have a preview – with some limitations.

    Walter

    • By:aldowner

      Hi, Walter, just curious to know, what kind of limitations? In what subjects or areas or anything? What is the limitations?

      • By:sveld

        Don’t worry it would just have been a beta/preview of the product with -limited- sync options, which I remember was only syncing calendar and contacts at the given point. It was meant to give a early look at the product, and noway was supposed to be useable it in production environment.

  31. By:mannisto

    This is bad.

    You can be arrogant and tell to use 3rd party …

    We must listen every day of new phones rollin’ into Customer-environments with questions about mobility. We gave a date of end of 2009 as you have instructed and it was JUST bareable.

    Now… three (3) months MORE !

    IT lives in it’s own bubble but Customers wanting to use and do business despite times are not very happy with this.

    AND you don’t have to listen to their complaints. You have to listen to US, who TRY to talk to you.

    Virtualization OK. What ever software packing OK. JUST DELIVER, Please.

    J

  32. By:WalterH

    Hi aldowner,

    the told as: not all features will work for the preview IIRR syncing emails will not work but calendar and contacts will work.
    But November 2009 is already over and most of my customer plans the migration to Exchange or Zarafa.

    Walter

  33. By:ekindsch

    Novell needs a clear, meaningful direction and products that offer the features its competitors have led our users to expect (at least). Assurances that Novell has money in the bank are worth little when no one there seems to know how to invest that nest egg. I fear the only thing keeping GroupWise in our environment is internal political momentum, which is rapidly eroding.

    My users have been waiting for the new mobility add-on for months. They are losing patience. They regularly point out how GroupWise lacks many of the features they use at home. GroupWise is competing for mind share with Gmail as well as Exchange; both support ActiveSync.

    Our trusted consultants shrug when we ask where GroupWise is going. They can’t explain how Novell’s expanding array of communications offerings complement one another or integrate into a cohesive strategy. None of their other customers have found Teaming worthwhile. Few see the point of Google Wave, let alone reason to consider a commercial implementation of it (i.e. Pulse).

    Our phone guys keep telling us about the integration we could implement if we “just” switch to Exchange. Their products don’t support GW, and they don’t plan to add such support since “everyone is running Exchange, or moving to it”.

    Whatever advantage Novell once had in our organization may already be gone. I’ll be happy to put a test VM on our VSphere servers, assuming you release something before May; by June we may be looking elsewhere.

    • By:sveld

      “Few see the point of Google Wave, let alone reason to consider a commercial implementation of it (i.e. Pulse)”

      I don’t think Pulse is a commercial implementation of Wave. Pulse can talk to Google’s Wave using WFP and I do see this as something that really may just make the difference for Pulse. First of all Pulse is a new way to communicate or interact as you like with other people using it’s own internal system. Hooking up Pulse to other systems, either using WFP to talk Google’s Wave server, or using Datasync to talk to or sync information from Teaming/GroupWise/other systems turns it into a dashboard (Pulse was called project ‘Cockpit’ before) for all your communication and allows you to see, follow and search all that’s important for ‘you’ making use of an universal inbox. Making use of Datasync connectors Pulse can be fed with streams out of other data silo’s from any social network as Facebook, Linkedin or Novell’s own product’s Teaming/GroupWise/Messager/File/iFolder; anything that could be important to you as a user.

      Could something like Pulse be done in GroupWise, instead of creating a new product,? Well probably, but GroupWise is about mail and calendar (personal), Teaming is about working together and adding something like Wave (live interact with the rest of the world) cannot be done without restucturing those products. What would my customer say if I told him he could now start a wave in GW instead of sending a mail message? Most probably they would think ‘ok, whatever’ and send a mail anyway, just cause they are used to do that in GroupWise. To change this we need something new, appealing to the user, easy and anywhere to use… as we are gotten used to do at home (gmail, hotmail, yahoo).

      I spend quite a time every day trying to remember where I left a file, a message, something someone send me using either IM, Linkedin, my private mail, then trying to contact someone using those same channels and keeping in sync data in those silo’s, that for me something like Pulse sounds verry welcome. Let Pulse decide for me how to contact someone. If it would do something live that could be using WFP and if a contact is offline and I only have an email address left of that contact it can let GroupWise drop a message.

  34. By:chapindad

    Groupwise as an Admin is a great product. As an Admin I have no doubt which email system I want to administer. Other than the lack of eDir integration in the last 15 years is perplexing, but I do like that my users can have these massive mailboxes and it is secure from end to end.

    But that has been that way since at least GW 5.5. The client interface was good at GW 7 and it is stable unlike the GW 8 client. I didn’t need a rewrite of the Client just to make things seem pretty. I need real world features that matter to the user such as GMS, QUICK message level restore, and simple, powerful and easy integration points for 3rd party vendors. Heck, copy the integration point of exchange so that 3rd party vendors can write one product that works with both systems. I know this means that you will have to work to keep your APIs in lock step with Exchange but you know the saying: “Lead, Follow, or Get out of the way”. You have lost almost all 3rd party support, it is time to get it back.

  35. By:skapanen

    One month gone..
    where are we now?

  36. By:loerincz

    Hi,

    I read this blog and any other blog’s to the gradenko but it is a big problem to get clear information when Novell give us a solution for the new devices are not supported by GMS. I am a long Novell customer and i have many discussion with my markers how we can not support the new devices. But i have no answer and the pressure is now very high for me to give them any answer.
    And I will not get other software from 3rd party to realize the way for the new Dev. like iPhone, Nokia and so on.

  37. By:sjalife

    Hi Alex,

    Thanx for the update…
    My company is a current user for another solution, (see my posts on Dean’s blog).
    I am very interested on joining the Beta for the Mobility Pack, where should I apply?

    thanx

  38. By:mannisto

    ALMOST three (3) months now. Could we get timeline for release, please.

    First Customers has allready used his feet on YOU (and Us).

    br

  39. By:rphrphrph

    What’s the latest word my friend. Any news on the schedule??

  40. By:rphrphrph

    Not much more to say than that. I absolutely love the idea.

Comment

GroupWise Mobility Update



By:

January 23, 2009 5:05 pm

Reads:19,546

Comments:40

Score:4.5

Print/PDF

There have, naturally, been lots of questions about our future mobility direction. Some of you will have already seen this mentioned in other places today but I am here to share a little direction with you. We decided some time ago that we would move our mobility story to ActiveSync which, for better or worse, is becoming the de facto standard mobility protocol, Blackberry aside. We will implement ActiveSync on the server, so that any ActiveSync enabled device will be able to talk natively to GroupWise. Of course, this includes iPhone support as well as Windows Mobile, Palm (new one included), Nokia Symbian OS (E and N series) in addition to many other devices.

We plan to deliver the solution to replace GMS this year. Right now I don’t have any more information that I can share, but rest assured that it is our #1 priority. Of course, you may have also seen that we released GroupWise Mobile Server 3.0.1 for Linux into public beta last week – look on http://download.novell.com for the download. Finally, we continue to have a great relationship with RIM that rounds out our mobility strategy.

I hope that clears up some uncertainty, and we are excited about this direction and the benefits that it will give you and your companies.

[edit]
I got a number of questions this week at GWAVACon so I felt I should update my blog. Many of you only support a few devices and want to know the best way to support them. Whether you support a few, or a lot of devices you should look at http://notifycorp.com/
They offer a hosted mobility solution that is a excellent choice for small business customers, or customers wanting to consolidate all of their mobility support

2 votes, average: 4.50 out of 52 votes, average: 4.50 out of 52 votes, average: 4.50 out of 52 votes, average: 4.50 out of 52 votes, average: 4.50 out of 5 (2 votes, average: 4.50 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

40

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

40 Comments

  1. By:redds

    Will this new solution include OTA and push technology or will it have to be tethered to a PC/laptop?

    • By:aevans

      It will be an OTA solution. ActiveSync is a protocol not a program, so it will allow any ActiveSync enabled device to talk to an ActiveSync enabled GW server

  2. By:redds

    Does this mean that this new solution will only run on Windows servers? How will OTA syncing work?

  3. By:WGamradt

    “Novell will support GroupWise Mobile Server through
    October 31st, 2009,”

    Tell me that is a typo. Novell has stated that they and Nokia would support Mobile Server for the next two years. Now all of a sudden support is ending in a few months and the product to replace it has not even hit beta?! Is that right?!

    It is stuff like this that continues to make Novell solutions increasingly difficult to recommend and sell.

    Great.

    • By:aevans

      Nokia is supporting Intellisync Mobile Suite for 2 years – we will continue to monitor our support date as we work on the replacement technology. Rest assured, we will not leave you in the lurch

  4. By:FlyingGuy

    Alex, this is getting to be a habit with you and one that I am really begging to dislike. This is also leading to me and a few others I would imagine to start to wonder if we should continue to trust you.

    So how about some details like:

    1. Will this be a Linux Implementation?
    2. Will it require a Windows Server and all the expense and hassle that comes with that?
    3. This year, uhmmmm care to be just a BIT more specific?

    While we were all *** begging *** for info and making lots of suggestions, had you already made this decision to lock your GW user base into a MicroSoft product?

    You need to stop playing coy with us and either be informative so we can make plans or you can just keep losing more and more customers.

    We have to sell this! When a customer hears, “Well the Novell mobility solution is really a Microsoft product how much longer before they say to themselves, “Hell I should just shift to Microsoft because it is their software and they can integrate their software together better then these guys can.”

    And what about licensing cost, what about IP issues, what about a LOT of things like is this going to ge yet another JAVA/TOMCAT/Apache/ god alone knows what kind of fresh H*&L mashup that is going to yet again be dependent on 5 or more layers of software? Is it going to crammed full or Perl and python scripts that at best unfathomable except ( and possibly not even to them when it’s finished ) to those who wrote it?

    When it breaks are we going to be faced yet again with error messages that spew forth 50 lines of java classes that lead you to absolutely nowhere like the infamous “MainHallway” errors? Or will it be some Microsoft error codes that MS, even if you pay them, wont deal with?

    • By:blntskul

      I almost hate to reply to such a silly diatribe, but I must. Your first two questions about running on Linux or Windows – what do you think that the current solution runs on? Even if it did only run on one or the other, what’s the big deal? It’s a pretty specialized application, which probably warrants having it’s own server(s), just like Blackberry Enterprise, Notify and many others. Ridiculous questions.

      If he could be more specific about the time frame, he would have been. You have a free solution that’s working now, and will be supported well beyond the release of its replacement. Novell isn’t going to drop support for GroupWise Mobile a year ahead of its replacement.

      Novell is supporting the Activesync protocol – not the Activesync client that Microsoft provides with their Windows Mobile devices. It’s the same thing that Nokia and Apple use to sync to compatible services now. It’s the smart way to go. It doesn’t mean, by any stretch, that Novell is repackaging a Microsoft solution.

      I mean seriously . . .

  5. By:redds

    Why another Microsoft solution? Isn’t Novell a Linux company. Again start acting like it. As a customer I have moved to OES2 Linux and getting rid of many of my Windows boxes. I don’t want to add another one.

    • By:aevans

      ActiveSync is a protocol, so we can implement it in any fashion we chose. We will be implementing it on Linux and Windows so that you have the choice on how to deploy. This is a benefit of our relationship with Microsoft, where we are able to offer support for what is becoming the de facto mobility protocol, aside from the BES. Most of the new devices on the market, and many of the older devices out there have an ActiveSync client on them – which means that they will be able to sync with GW with no modifications

  6. By:tmstone835

    I don’t think that you have much choice other than to have an ActiveSync enabled GroupWise. All of the smart phone vendors are supporting it and it is too big of a market to ignore. If GroupWise wants to be a player, it has to come out as soon as possible. I would like to see early-summer as the target rather than the end of the year.

    I believe the APIs are published for ActiveSync so move forward now instead of later.

    It has to be a Linux solution and not reliant on a Windows server. I agree with the previous comment about that. We are trying to eliminate Windows servers rather than adding them.

  7. By:Magic31

    WGamradt : Not seeing where you are reading GMS support will be dropped this year? I’m reading they are pushing to get out the new solution for Groupwise Mobility to ease the current uncertainty for a Groupwise solution.
    They way I interpret the news (as also other postings/blogs), is that the 3.0 GMS series will be maintained but not developed any further. In that sense the support can still be given while a new product is pushed out.

    I’d rather have seen Novell buying the GMS solution from Nokia.. but then Novell would also have to keep developing all the clients and other extra aspects. Following where others seem to be headed (even Nokia) might be wiser in this case.

    I do share the concerns others here have posted :
    +1 to maintain a Linux version of your solution!! Many customers are VERY happy with the fact GMS is running on their SLES boxes. I do hope (strongly) the next solution will offer the same platform choices.

    Keeping an eye on your developments!

    Cheers,
    Wj

  8. By:DaveHowe

    ActiveSync is the defacto standard for phone syncing – not supporting it will hurt more, and lead to customers going to microsoft to give them systems with the functionality they need.

    It would be nice if there was a rfc standard for this which all phones supported, but we have to live in the real world here.

  9. By:ackitsme

    I’m hoping that this will follow a similar format to the existing GWMS in that I can have a server on the outside of our network that does all of the customer interfacing so that I don’t have to open up direct access to my post offices.

    We’re an extremely security conscious company and, aside from the GWMS and BES, we do not allow ANY access to e-mail without a VPN client.

  10. By:gurneetech

    I realize its still early in the process and details that can be released publicly are sparse, but I have to thank you for the news. Once released, no longer will we have to worry about 3rd party support for a sync client. While Activesync isn’t perfect, it does do a good job.

    This is exactly the kind of integration that I’ve been hoping to see come from Novell. If the MS agreement had a hand in it, then excellent. At the end of the day this will benefit everyone.

  11. By:foccer

    Good news that you have a direction but please consider the fact that SyncML is also a standard supported on many phones.
    In fact quite a few phones that do not support Activesync support SyncML just fine.

    hoping the next server will at least attempt to support more than the one protocol

    • By:DaveHowe

      I agree. if you *only* support activesync, where’s the value added in not just going the whole hog and switching to exchange (which our customers are apparently doing at an alarming rate)

      However, if you support ActiveSync AND SyncML AND other protocols, you have a product that is more flexible and supports a wider range of devices – microsoft can afford to say “do it our way and buy products that support doing it our way” but novell cannot.

  12. By:glofish

    Novell does some great things sometimes that just make sense. Looking forward to seeing this one play out.

  13. By:stideswe

    Much as I hate MS, ActiveSync is widely adopted and works very well (even behind a reverse proxy for instance). As such, Novell making a native ActiveSync gateway for GroupWise is bloody excellent news. Thank God you finally decided!

    I concur with foccer who requested SyncML support: I’d imagine ActiveSync and SyncML are not hugely different and providing protocol level support for both would make good business sense for Novell and help to support a truly open standard.

    You might consider MS to be buddies now but we all know what a total bunch of *****s (think of your own expletive here) they are and you shouldn’t just fall in line to support their protocol without supporting the open standard which they don’t own and which is also widely used. Try not to kick Open Source/Open Standards in the teeth as you are reliant to some extent on differentiating yourself from the Redmond beast. When it has ceased to be convenient for MS to be mates with you they will try and screw you over without even blinking an eye – and that day will come pretty soon.

    Isn’t is odd how people are so focussed (including me) on supporting the bloody iPhone. Now that people have them they realise how power hungry and overrated they are and the whole furore about how crap GroupWise is because it doesn’t support iPhone has died down. In the long term though Novell cannot ignore this sort of thing because eventually the iPhone and others will improve and actually be worth owning. Also Novell should not ignore RIM/BES whose product is way superior to any other option and who did the right thing by providing support for GroupWise way back. If we didn’t buy a BES server some years ago we would have ditched GroupWise a long way back. We only still use GroupWise now because BES was there and ready to use and works so bloody well.

    Simon

  14. By:stideswe

    You’ll produce a solution faster if you just concentrate on one platform. And the platform you should choose is Linux of course. It makes sense for Novell customers to have a Linux solution that doesn’t require them to purchase or manage a crappy Windows box.

    You’ll also keep your internal costs (of coding and testing) the product down if you only provide it on one platform – Linux of course.

    ps. Testing – do I need to explain what that means, as I sometimes wonder where Novell is concerned? My relationship to Novell is as a paying customer which means I should be treated differently and have different functions to perform than the people who work in QA at Novell. I’m paid by my company to perform IT support/projects – I’m not paid by Novell to spend countless hours helping them debug their lousy code.

    pps. Do I need to explain QA? It is the department at Novell where there is one old man asleep in a darkened room. A word of advice get more staff in there and/or train them better, and/or inversely relate their pay to the number of bugs that leak out, as that lone man is doing a pretty poor job of late and he seriously needs some help.

    Simon

    • By:blntskul

      Not very constructive man. Novell’s initial releases tend to be better than most. GroupWise in particular is a very solid product. Even at that, if you install .0 releases of anyone’s products, you’re going to find the problems. That’s not just a Novell thing. If you’re implying that their subsequent releases are overly buggy, I have to disagree.

      As far as concentrating on one platform goes, it may turn around quicker and cost less, but they’ll also hit a smaller audience and sell less of their product. One of the worst things about Microsoft’s products is that each one of them locks you into one or more of their other ones. One of the worst things about avid Linux supporters is that they think you’re a traitor if you support anything else – because why would you, right? Novell’s approach is a smart one.

      • By:stideswe

        On the first point, yes the backend is extremely reliable (at least since we’ve been running it on Linux). The Win32 client has been fairly unreliable (until GW7 SP2 when it finally settled down) with crashes and other aberrant behaviour. The iCAL implementation was a total debacle and wasn’t properly fixed until GW7 SP3. There is a serious bug in GW7 SP3 HP1 that totally corrupts some outbound emails – making them twice the expected size and with all messed up MIME boundaries. Novell are, in my opinion, particularly adept at releasing bugs, GroupWise isn’t their worse product in that respect but it has had a fair few serious defects in recent times.

        On the second point, I’m sure it makes sense to develop to both Linux and Windows but they should concentrate on the Linux port first as I believe that’s what customers would expect/want and it would prove more cost-effective for the customers too.

      • By:blntskul

        I guess we can agree to disagree. Everything’s relative. Support Microsoft Exchange for a while and you’ll appreciate the reliability and efficiency of GroupWise. As for releasing on Linux first, it’s just not smart to ignore Windows users. I think Linux is a better server platform, but if a great percentage of their customers run Windows, they should attend to them just as quickly. It’s key to breaking into that huge segment. They would have no success selling solutions to primarily Windows shops if their Windows development lags behind. I want Novell to do well overall, and Windows is (unfortunately) a big part of that.

  15. By:rovabu

    Hi Alex,

    If you say: “Finally, we continue to have a great relationship with RIM that rounds out our mobility strategy”, I have two questions:

    – when will BES 4.1 have SOAP/XML support for GroupWise 8? Both Novell and RIM seem to be a bit vague about why this doesn’t work and when BES 4.1 will be ‘certified’ and tested for GroupWise 8

    – will you Novell attend the WES in Orlando in May? Last year Novell’s complete absence was surprising for many.

    Roel

    • By:blntskul

      I’m running GroupWise 8 and BES 4.1.6 and they work just fine together. I asked RIM before I upgraded to GW8, and the guy I spoke to said that they haven’t officially announced anything, but it’s working with no problems in the labs. That may be of no comfort to you without their official stamp of approval, but it does work fine. In fact, I called RIM support today for something, and they were fine with my version of GroupWise.

      • By:rovabu

        Object API connection mode works, SOAP doesn’t. We’ve reported those issues to RIM and were told that this is not supported to begin with (GW8 and SOAP).

      • By:blntskul

        Well, don’t tell my BES. It might break. I didn’t do anything special. I was running BES 4.1.6 with the GroupWise hot patch with GroupWise 7.0.3 in SOAP mode, then we upgraded to GroupWise 8.0 HP1. It works just fine for me.

    • By:aevans

      The BES question is regarding RIM’s roadmap, so I can’t comment with any real authority. I know that BES engineers and our engineers are always talking, and that RIM are working on a 100% SOAP enabled BES, but I can’t comment on the specific version that it will show up in. BES 4.1 subscribes to SOAP events, for change notifications, but uses the Object API for the actual item sync – so it is, arguably, already supporting SOAP, just not 100%.

      BES 4.1 does support GroupWise 8 – Novell was an early adopter of the latest BES. If your question is “when can I install the GW8 client on my BES server, instead of the GW7 client”, my flippant answer is “hopefully never” – with the view that BES will become 100% SOAP enabled and the client is no longer needed on the BES server. The more complete answer is “When RIM complete testing with the GW8 client and certify it for use” – but right now there is no real push to do so – you gain nothing.

      Novell is planning on attending WES this year yes. I will probably not be part of the contingent, but then I have no direct Product Management need to be there. It is more of a sales and marketing function.

      • By:rovabu

        I’m talking about using SOAP against a GW8 POA as the preffered connection method, with a GroupWise 7 client installed on the BES. I don’t even want to consider upgrading the client to GW8 :-)

        After the release of GW8 and upgrading customers to it, we ran into SOAP issues. Basically nothing worked. RIM just stated it wasn’t tested and certified for GW8 to begin with, after its initial release, so we had to switch back to Object API connection mode which has stability performance issues and is not something which is preferred to begin with. After that we didn’t get any updates any more on this issue. I’m just curious in the light of Hot Patch 1 we should give it another try. Since switching connection methods means reinstalling the BES software itself, which is not an excercise without risk, I’m curious on the status from a product management perspective.

  16. By:pintoa2000

    We are a large customer of Novell products incuding Groupwise and have a growing iphone user base.. We recently approached Notifycorp for an eval since need to Sync groupwise email and contacts to our iphone users..

    The product installation took a while and we had a few configuration issues to resolve which took a couple of weeks.. Our 5 iphone users did not get sufficient time to evaluate the product and the eval period expired.. we approached notifycorp to extend our eval for another month so that we can have users test this properly .. but they refused.. they wanted us to pay for the extension which is absolutely ridiculous.. after trying to explain to this sales person that we are not satisfied with our eval and would like some more time.. he refused.. we cancelled the evaluation and are now looking at the only option of moving to exchange or waiting for Novell to provide the activesync for gwise functionality..

    absolutely frustrating.. and to think we were on the verge of buying this product but all we needed was a little more time to evaluate.

    • By:gathagan

      We had the exact opposite experience.
      Like you, we’ve had some problems with the iPhone integration.
      Like you, we asked NotifyLink to extend the test period.
      They committed to extending the test period. In fact I believe the test period for us begins when the bugs are ironed out.
      I agree with the frustration issue, since problems persist. At least in our case, however, NL has been very responsive.

  17. By:PN134

    Please advice the time lines set to enable iPhone integration with GroupWise? I see that the real development will be on ActiveSync so if this is the protocol to be used, when will it be available? Is there a an alpha or beta available to test this? A customer who has been using GroupWise for years are asking about this and due to the large volume of iPhone customers, they are being forced to move to Exchange. Thank you for your quick response.

  18. By:AngeloP

    Will the GroupWise 8 ActiveSync protocol work on NetWare OES1 servers also? Or do we have to upgrade servers and migrate them over to Linux OES2?

    Also, will the ActiveSync protocol be coming out at the same time for all the platforms? If not, which one is going to get it first?

    Thanks for helping me out with this needed information.

  19. By:mconradt

    Since we deployed Notify Link Server we sync all our iPhones and even iPod Touchs with GroupWise it works great and the email handling on these devices is pure luxury against all the other devices I’ve see and testet.
    It emporing against furstating, it’s easy and fun !
    Calendar works perfect with invitations, even that there still some little bugs inside. But from the past, I’m confident that they will be fixed !
    Go ahead and email Paul dePond and I’m sure he’ll extend your license !

  20. By:iphonebecky

    Aevans,

    Do you have a better sense of timing for the release for ActiveSync? I need to sync my iphone with Groupwise. I’m trying to decide if I can wait for your release, or if I should pay for a stopgap until it is released.

    Thanks!

  21. By:thsundel

    Any update on release date for Active Sync support?? The number is growing for devices that won’t work with GMS.. We really need your solution asap, and please do not release the Windows version of this product before the Linux version!! We really would like to have Linux servers instead of Windows servers… If you release the Windows version first them most of your customers will deploy that instead of running it on “your” operating system!!!

    • By:cris2per

      For example, they may be charged by a security company $22 for a security guard to protect an empty lot. Is it really worth it??? How in the world can these companies afford to pay so much for security guards??? Also, some companies use off-duty police officers and pay them $30 per hour… how can a place like a motel afford to pay someone that much money? And how is it worth it?

  22. By:cris2per

    I go to do AMD website and fill out the information for my notebook, Notebook Graphics – Mobility Radeon Series – Mobility Radeon HD 5xxx Series – Windows 7 64 Bit, and afterwards it sends me to the next page with a download for ATI Catalyst. I do not see any links to update my driver though? Am I doing something wrong? This is my first ATI graphics card so I am new to this process. Thanks in advanced.

Comment

RSS