Blog Entry

dlythgoe's picture
blog
Reads:

4179

Score:
4.666665
4.7
3
 
Comments:

7

GroupWise: Building and Charging ahead with new Energy!

Author Info

2 August 2010 - 8:34am
Submitted by: dlythgoe

(View Disclaimer)

In the last few years, collaboration at Novell has changed dramatically. It used to be that it meant just one thing: GroupWise! Now it is obvious that it is much much more than just GroupWise or just email/calendaring. Events in the last few weeks have caused me to reflect on that change and the positive energy that is flowing through the engineering halls recently.

The energy comes from several different perspectives and is contagious for different reasons. First of all, in a meeting with the entire Collaboration Business Unit, our CEO announced that we would be expanding the GroupWise engineering team in Provo - effective immediately. New engineering/management/human factors and QA positions were added to the http://www.novell.com/company/careers/ site on Friday.

This is a big boost to the team and our ability to execute on our customer's objectives. The team continues to be a model of delivery. Just this year, the team has delivered several public releases including

GroupWise
- GroupWise 7.0.4
- GroupWise 8.0.1 HP1
- GroupWise 8.0.2

Teaming
- Novell Teaming 2.1
- Durango authorized betas

Novell Data Synchronizer
- Novell Data Synchronizer - 3 Connectors (Sugar, SharePoint, SalesForce.com)
- Mobility Pack Tech preview, alpha and public beta.

Novell Conferencing
- Novell Conferencing 2.0
- next update due at the end of August

Pulse
- update 1 and update 2 - over 7000 users already!
- update 3 is due in August

In addition, we have shared our progress about Ascot - the next major release of GroupWise. Ascot internal demo 3 is scheduled for September. The designs, implementations and progress is signifcant and encouraging. QA is already running 64-bit Ascot agents in our lab. Ascot has shifted gears and is gaining momentum daily. We are definitely keeping Tom Sanders - our project manager - very busy!

Mobility is obviously still our highest priority. We continue to work non-stop on the quality and availability of this technology. Public beta was a major step forward and indication of the project status. We plan to refresh that public beta this week and we continue to feel confidence in our September release date. We have several customers working with us by rolling out this technology into their production environments with GroupWise 8.0.2. They also have been giving us positive feedback and constructive evaluations.

Pulse is a great new addition to our Collaboration family. I spend a great deal of time using the technology and exploring ways that this real-time environment can help me do my work. I currently have over 350 people following me on Pulse - I am following over 1200. I have had several technical swarming sessions around topics I need input and feedback on. I actively use several social technologies in my professional and personal life including this blog, GroupWise, Teaming, Messenger, Conferencing, FaceBook, Twitter, Linked-In and now Pulse.

I continue to find new ways to use each of these mediums to accomplish my objectives. I am interested how many of you are using these technologies as well...come join me and let's innovate together the collaboration space!

Novell Teaming will release the next major version of this product line later this year. Durango is currently in authorized beta. Our User Interaction specialists have been working overtime getting this release just right! Check it out!

Novell Conferencing is also progressing well. The next release of this product is scheduled for the end of August. It has a number of great new features and we will be expanding the hosting centers. The European center will be online soon. We will keep you updated as we progress to release.

The Product Management team has also been very busy on several fronts. Last week, the entire team was meeting in Provo for their regular Summit. I do not know all of the details yet, but I do know that the objective of these meetings is to come together around the current status of things and chart a path forward. This is a challenging and rewarding activity. I do know that they are a very opinionated group and getting consensus can be illusive. However, they are also professionals and expect to meet customer, market and company objectives in the most effective ways. I applaud their efforts and look forward to helping them find success.

Ok - I admit that upon re-reading all of these paragraphs and thoughts - I am not sure that I was just rambling...but its a blog...that's ok isn't it?

Sounds good for a Monday at least....

Dean


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

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, test, test before you do anything drastic with it.




User Comments

tmstone835's picture

I sense your excitement

Submitted by tmstone835 on 2 August 2010 - 7:50pm.

This sounds like great news for us GroupWise die hards. You have needed this boost for a long time and I am glad to see it happening. When you look at your accomplishments over the past year it does show a lot that has been done. It is important to keep up the momentum but you don't want to burn them out either.

I wish I had some decent programming skills so I could apply for one of the jobs.

Tom S.

ssinghose's picture

This is good news

Submitted by ssinghose on 6 August 2010 - 12:08pm.

Dean:

First - congratulations on all the updated releases from the team.

Second - The expansion of the staff is the best news I've heard in a long time. Especially after a visit from the CEO. Seems like the news from all industries these days is cut, cut, cut. The collaboration team must be doing something right to get approval from the top to expand. Public commitment from upper management - GroupWise is alive and well.

Keep up the good work

de's picture

Yeahbut ...

Submitted by de on 20 September 2010 - 5:23pm.

Groupwise has become such a hard sell for me, even though I still believe it is a superior product. The three biggest impediments that I now deal with are:

1) Broken MS Office & Acrobat integration. For some reason, even though Novell developers know that they chose to make a change in the integration, they can't seem to understand the importance of the issue. Users are -very- put out that they can't open any Acrobat or Word files if they are in the process of attaching one to a Groupwise email that hasn't yet been sent, and 8.0.2 not only doesn't fix the issue, it gives a new error whether or not the message is sent.

It's hard for me to understand, no less explain, why your engineers made this choice to change the behavior and force something so contrary to how people use the program. NOBODY expects to be creating an email with an attachment, and have the attachment "parent" program unusable until the email is sent.

And it means I have to craft my Acrobat deployment to completely remove the ability to email out of the program, which makes the issue even more apparent.

I'd have to ask why such a major issue wasn't fixed in SP2 along with the hundreds of other fixes, not to mention why developers chose to make such a radical app-breaking change in the first place.

2) Cost: The per-user cost of upgrading from Groupwise 7 to Groupwise 8 is frankly ludicrous. I can't possibly convince anyone to spend $129 per user to do this relatively minor upgrade, rather than spend those $$ on migrating to Exchange. Once-upon-a-time, Groupwise upgrades were $39 per seat; I believe that's what the upgrade to version 7 cost. Novell has now priced itself out of the market.

3) None of my clients trust Novell anymore, because not only did you choose to drop development of Netware, but you completely dropped the product, REMOVED critical support articles, and forced a migration that users didn't want. My remaining Novell clients have loved the stability of Netware, it is a full-featured product and does more than even Windows Server 2008, but you're forcing them to migrate to another platform rather than stay with what they want and has proven to work for them.

It's beyond comprehension that Novell made a decision to cut Netware users off at the knees. It would've been simple enough to keep the existing articles and patches available, but instead even that baseline was abruptly taken away, and even Novell's own current products don't even come with the ability to install on it's long-time server OS Netware!

Mark my word: when you FORCE users to migrate to another server OS from one they love and which is stable and mature and full-featured, they're going to mostly migrate to Windows. They won't migrate to Linux not only because of the scarcity of support staff, but also because some of their apps won't run on a Linux server, and they simply don't trust Novell anymore to live up to its word.

Please give me one answer I can provide to clients that addresses the way Novell not only dropped Netware, but removed the existing support pages and patches so that literally hundreds-of-thousands of web cites are broken ... Tell me how I am supposed to get them to stay with Novell, when they've had a product they love which has been stable and provides so much functionality ... but over which you so thoroughly shafted them?

This was the wrong thing to do, period. In consideration of all the existing links on the web and given the stability and maturity of the product, Novell could have simply stopped developing Netware but left the resources intact.

Just how do I tell these clients that they should migrate to Novell's Linux, instead of to Windows Server, when the Linux migration will cost them just as much and they feel they can't rely on Novell to play it straight?

My bottom line is that Novell has continued to kill its own devoted market. The company seems to continue to be managed by people who actually hate the products and want everything Microsoft-like, and who feel no regret about destroying customer loyalty. We know that the company took WordPerfect when it had an 85% marketshare, and managed to destroy it so completely (including making it so hard to buy) that under Novell's management the marketshare dropped below 10% and never recovered. Now you take those same customer-offensive actions with Groupwise and Netware, and yet you still expect people to stay around even after needlessly shafting them time & again, after making it clear yet again that Novell management doesn't want to support products that just plain WORK.

You owe us better.

http://iwantnetware.com/ (no affiliation)

It's been a few years - how has your NetWare plans changed?
Still using NetWare.
54.65% 229 of 419
Replaced NetWare with Windows.
22.20% 93 of 419
Replaced NetWare with Linux.
10.50% 44 of 419
Added more Windows servers.
4.53% 19 of 419
Added more Linux servers.
3.34% 14 of 419
Added both Linux and Windows to replace NetWare.
4.77% 20 of 419

-- DE

tmstone835's picture

I feel your pain

Submitted by tmstone835 on 21 September 2010 - 9:30am.

DE -

I feel your pain regarding Novell in general. Their shrinking revenue base along with the rumors of splitting up the company or selling it outright does not help the situation. They have tried to keep too many different fringe products alive and have spread the R&D money too thin because of that. Taking on the burden of an open source community has also made it difficult for Novell's financial health.

GroupWise is a superior product compared to Exchange but the reasons for staying and upgrading don't seem to matter to management when simple things become difficult because of GroupWise. GroupWise is certainly not the first product tested if at all when companies like Microsoft and Adobe introduce new versions or upgrades.

I agree that Novell should not have dropped the Outlook connectivity. It is always going to be a moving target because Microsoft will keep changing Outlook but it is a crucial element. Coincidentally, many third-party applications that rely on Outlook become broken as soon as a new version is released so it isn't just Novell that runs into that problem. Many Exchange upgrades are indefinitely delayed until the application dependencies are resolved with companies' CRM or internally developed programs. Sometimes that delay is measured in years.

Eric2001's picture

GroupWise Cost and Outlook Integration with Data Sync

Submitted by Eric2001 on 14 October 2010 - 11:24am.

You both make good, painful, but valid points. I recently saw the paper on the cost of GroupWise versus Exchange, and while there are many good reasons that GroupWise is a better busines decision, the paper focuses on cost, but includes the cost of Outlook as if most businesses are not purchasing MS Office suite. Pull out the cost of Outlook, because businesses see that as part of their MLA for Office, and GW looks much less attractive. Throw in Google apps into the equation, as the City of Los Angeles did, and it seems clear that the current GW per user costs are not part of the argument to stay with GW. Reliability, dependability, ease and lower cost of administration, efficiencies and productivity of the GW client, lower cost archive and failover applications, are all good arguments to select or stay with GroupWise. Licensing costs, not so good.

Integration is still a huge issue and becoming bigger. Some of this is what integrates with Exchange Server, but a lot is still on the client side. I noticed in setting up a phone on the new Data Synchronizer that you start out by selecting that the set up is for an Exchange server. The fields that follow appear to be the same as when you set up an Exchange server connection in Outlook. Any chance Data Sync can be used to connect Outlook to a GroupWise server? Has anyone tried this?

The potential sale and fragmentation of products is very worrisome. We use GW, OES, Teaming, iFolder, SecureLogin, ZEN, and more. The idea of these being split up and possibly discontinued, having support fragmented, licensing costs changing, doesn't help me sleep well.

Eric

blntskul's picture

Data Sync Not For That Purpose

Submitted by blntskul on 14 October 2010 - 1:16pm.

Data Sync is essentially an engine that presents PIM/email type data to its connectors. When you connect a mobile phone to an Exchange server, it's using Active Sync Protocol, which is designed specifically for mobile devices. Data Sync has an Active Sync connector, which looks like Exchange to a mobile device basically. You can't connect Outlook through a Mobility connector. You might be able to build a connector that connects Outlook clients to Groupwise through NDS, but I don't know that it's a good idea.

The good thing about Novell's current direction is they're breaking the inter-dependencies of their products to eDirectory and running on multiple platforms with multiple directory support. I wish it had been done 5 years ago. You should (and will at some point) be able to take Groupwise into an all Active Directory and Windows environment on its own. ZCM is already there.

I also don't care to speculate about the possible acquisition of Novell. Even if they're purchased and split up, it won't happen over night. Everyone needs to chill out on that subject.

Eric2001's picture

Data Sync and Outlook

Submitted by Eric2001 on 18 October 2010 - 4:17pm.

Thanks for the information. I thought the Data Sync was for more than just mobile devices and would actually be used to connect data between applications. Other parties somehow get their applications to communicate with Outlook. I thought that maybe Data Synchronizer could do that for GroupWise.

The comment about the potential sale was in the context of the discussion about the broader issues regarding future GroupWise sales and retention of existing clients. Certainly from my perspective (end user), as a company that relies on using Novell's products to, I believe, give us an edge in performance, reliability, administration costs, compared to our peers, the future of Novell and it's products is a serious issue. Uncertainty can't be ignored. Options must be considered in advance.

© 2013 Novell