Outlook - For those of you folding on this all I have to say is that you are not evangelizing GroupWise. Outlook completely subverts a system being auditable and discoverable with local files on the workstation. I don't know how many times things have gone sideways because a PST file was corrupted.
You have to be a true believers and you have to show why in no uncertain terms that GroupWise is the superior product and you have to sell sell sell!!!
Having said that the Developers have to give us a GW client that is re-factored, bloat removed and can out outlook, Outlook AND is truly X-Plat, but until then we have to fight the good fight.
Unified Messaging - About 1 in 10000 people use all of that cruft at once. Make phone calls through and e-mail client? Really? I don't think the vast majority of customers do that.
Customers that switch to Windows for file and print are already MS centric clients and they WILL go with OL/E and very few will continue with GW.
"No More NetWare Client for single sign-on..." I don't even know what that means. GroupWise can take its credentials from the network connection. If in a windows environment then the security token a network connection is in memory and GW can access that.
Those of you advocating the elimination of ConsoleOne as the administration utility are correct, but if you think that having you GW configuration based upon the Apache/Tomcat stack are very much asking for trouble since you obviously have very short memories. The entire house of cards can come crashing down far to easily. Even MS does not do that with critical systems. A VERY thin client akin the to MMC needs to be developed and built that is completely X-Plat for administration of the GW system. This must be a completely self contained executable that does not require a privileged account to run and no installation is required. You simply pull it down, start it up and point at the GW system you need to administer. Failing that, then a single agent that is a self contained Micro-HTML stack needs to be built that does not require anything else. If the Apache/Tomcat stack is broken for ANY reasons and GW depends on it of administration then you have a running GW system that you cannot configure and that is a deal breaker.
You really want to harp on something? How about getting ALL GW settings OUT of the registry. Whomever did that stupidity needs some serious re-education. EVERY setting for the client should be stored in the GW user database That way when you run, "Reset Client Options" they actually all RESET so that after a user has completely trashed their GW client configuration it is a simple fix.