GroupWise: Sick and tired of negative GroupWise press?
By Kari Woolf, GroupWise Product Marketing Manager
As most of you know, we just launched GroupWise 2012 this week, and there’s a lot to celebrate. We not only have a great product today (one that includes many customer-requested enhancements focused on hot topics like mobility, social collaboration, and end-user productivity); we have a robust roadmap to carry us far into the future. So what’s the rub? The fact that media coverage about GroupWise is anything but fair and unbiased.
To begin with, you may have seen this article, offering the sweeping conclusion that “no one cares about GroupWise.” Some of you have weighed in to rebut this claim, and we thank you for that! If you haven’t seen the article until now, consider it a rallying cry to stand up against this kind of false perpetuation of the “old Novell” story. And in case you’re tempted to believe such fatalistic predictions about the demise of GroupWise, consider my response to this article:
First, the points on which we agree. Yes, it’s been awhile since our last release. Yes, Novell’s past focus on GroupWise has wavered. And yes, like all on-premise email vendors, we face competition from Google and the cloud.
But if you’d like to know the noteworthy facts (versus the tired refrain) of the contemporary Novell GroupWise story, consider this:
These are the facts of the GroupWise story. We invite Mr. Strom to speak with us about any of these developments–or to talk with GroupWise customers and partners who care deeply about this product and its future. Let’s stop belaboring the past. It’s a new day for GroupWise, and the future is bright.
But is that the only press-related injustice we need to address? Definitely not. There’s also the slew of articles on the City of Los Angeles’s high-visibility migration from GroupWise to Gmail. Is anyone else growing weary of these unoriginal variations on the same tired theme? I definitely am. And while we certainly don’t speak for our customers—or publicly second-guess the wisdom of their decisions—we DO find fault with the media for continually portraying GroupWise as the goat in this story.
The truth is that the City of LA was running an older version of our product—a fact that any amount of due diligence on the part of the press could have uncovered. And what about the age and configuration of the hardware it was running on? Ever seen a single one of these articles dig into THAT extremely relevant fact? Nope. Some of the basic tenets of “investigative reporting” seem to have been missed. The bottom line is that reporting on GroupWise based on its 2003 merits is patently unfair, and we’re crying foul. Since when did the press ever write about Windows 95 or Exchange 2003 with such contemporary zeal and vigor? Never. That’s when.
And let’s not forget that even this older version of GroupWise meets fundamental needs that Google currently can’t, which is why it remains in use in certain pockets of the municipality. So, again, why the flat and utterly unimaginative quest to find new ways to portray Novell as old? How about reporting on the facts as they stand TODAY? Better yet, why not report on who Novell IS today, and what that signals for TOMORROW?
These kinds of articles not only do a tremendous disservice to the companies they cover, but to the readers who rely on them for perspective and information-gathering. If you’re tired of this kind of GroupWise coverage from the mainstream IT media, pass this post along. Reblog it, tweet it, and share it with others who want the REAL story—the story of Novell’s recommitment to its customers, the story of GroupWise’s return, and—as time will undoubtedly tell—the story of a company that found its place serving customers again. You don’t have to believe me until the proof points are in. But please don’t believe what the press feeds you in the meantime.
How to Map to a Microsoft Windows Share via Novell/Netware Login Script
By Skip Thompson
I recently had a K12 customer call with the following problem:
We bought some curriculum that had to install on a Windows server, and the user would need a mapped drive connection to it. So, I needed to map a drive letter to the Windows server during my user’s regular login script so that they did not need to log in twice.
We attempted several things without success including:
1. calling a DOS batch located on sys:public
2. putting the Net Use commands directly into the login script (#net use x: \\server\share)
Ultimately, we determined the following syntax would do what we wanted:
#COMMAND /C NET USE X: \\SERVER\SHARE
The actual command includes “password /user:domain\user” which passes the user and password along at mapping time. It’s a generic user on the windows share, but we wanted a password to stop runaway viruses from exploiting a read-write share with no password.
For more on syntax, visit ComputerHope.com.
How to find the most recently installed packages with RPM
By Chris Clark
Did the new package you just installed leave you less than excited and now you want to remove it? That is usually no big deal by itself, but what about all of those dependencies that got installed along with it? You probably want to uninstall them, too but can’t remember all of those arbitrary names. Plus, your graphical tool may not allow you to filter by install date, so what can you do?
One simple way is to use the command line tool, rpm. From a terminal, type:
rpm -qa - -last
The newest packages will be at the top. Since it will most likely be a long list, you may wish to pipe the output to less:
rpm -qa - -last | less
Type q to exit less. You could also pipe the output to grep to search for a specific day or date like this:
rpm -qa - -last | grep Jun
Of course, you can also use the “- -queryformat” option and impress your friends at parties:
rpm -qa - -queryformat ‘%{installtime} %{name}-%{version}-%{release} %{installtime:date}\n’
Basically, what the command is doing is querying the rpm database and with the “- -queryformat” option, you are specifying which “fields” in the database you want to see. The “%{installtime:date}” is a query option that tells the command that you want the date formated as a date string instead of the system time format. The “\n” means “new line” so that each package is listed on its own, individual line.
You could then pipe the whole thing to grep or use sort to find exactly the packages you want:
rpm -qa - -queryformat ‘%{installtime} %{name}-%{version}-%{release} %{installtime:date}\n’ | sort -n +3
Updating HPLIP in Suse Linux Enterprise Desktop 10 SP2
By Chris Clark
(Please be aware that this is not a supported solution)
Unable to create print queue, please restart cups and try again