repent34

I have tried to implement the MS article called, "Appendix B, Configuration
Proceedures for Migrating from Novell Groupwise Messaging Functionality".


Groupwise6 uses Console1, and not NWADMN32, there are several key steps that
I cannot replicate under Console1. MS states in this paper that nothing has
changed in Groupwise 6 so these proceedures will work. Say waht?

I cannot find an updated MS paper that addresses this issue. I would think
that if MS wants us to migrate that badly to them that it shouldn't be this
difficult.

Anybody tackled this yet??

c

in disguise

Any good business or technical reason to switch? What stopped you from
upgrading to GroupWise 6.5?

repent34

Not sure what that has to do with my question. IMHO Netware/Groupwise
****s. Novell is headed in the wrong direction and I doubt they will be in
business much longer. Groupwise is ugly and my users hate it. I do to. You
asked.

c

in disguise

It has this to do with it:

1. Moving from one email system to another is done for a few reasons -
political, technological, lack of admin skills, to solve a particular
problem, and so on.

2. If the reason for the switch is to solve a particular problem, then
you may already have the solution within your current email system, but
lack the knowledge / skills to implement it, or the particular problem
may require a change. If you already have the solution in front of you,
it may be a whole lot easier / cheaper to solve that problem with what
yo have than to rip and replace an entire system.

Regarding the "ugly" comment - God knows where that comes from, as you
can use Outlook to access the GroupWise system, as well as the web
browser of your choice.

How do you quantify, "ugly"?

How do you come to the conclusion that "NetWare/GroupWise ****s!"? If
it's because you don't understand it, then ignorance is to blame - not
the technology.

Why do "the users hate it"? Properly configured and administrated,
GroupWise (like any other email system, operating system, application,
et al) should be relatively problem-free. If you have a mis-configured
or under-powered server, then you can hardly blame anyone but those
administering / supporting the system for the problems you've run into.

FWIW, I give the same argument for those wanting to move from Exchange
to GW - do what you can to get what you have working properly first,
then if you absolutely cannot get it to work the way you want, then
consider changing.

Changing because of some blind loyalty to a particular company is stupid
at best, asinine at worst. As a CEO, I have fired employees who can't
see past their own "religious war" of technology.

repent34

You asked and I gave my 2 cents worth. All I can say to answer all of your
questions is look at the market share. Ask anyone on the street about
Novell, and they will say, Novell Who? The only reason Microsoft doesn't
buy out Novell and dig a big hole and dump it in there is because of the
DOJ. $80 billion vs $5 billion speaks for itself.

Again, I am asking a technical question, nowhere did I state that I wanted
to enter into a discussion with anyone as to why I'm doing what I'm doing.
The fact is, I'm doing it. If you don't have an answer to my question,
that's fine. Please drive through.

PS, using Quest now anyway so this thread is mute.

bob christian

Quest does have some good products.
CompuSven has a good mail shuttle that will aid in the migration.

tony

We are currently deciding between Groupwise 6.5 and Exchange 2003.

We didnt like Groupwise 6.0 as we couldnt get the Outlook 2003 connector
to work correctly with it.
Apparently thats now been fixed, and GW 6.5 goes beta soon ?

Whats the actual technical problem ? I use both Console1 and NWadmin so
know some of the differences.
Also could you use Imanager for any of these tasks ?

in disguise

Tony,

How about GroupWise 7? http://www.iwantgroupwise.com/

tony

Sorry my fault, thought GW6.5 was seqoiua. 7 is the new version , with
apparently (not tried beta yet) outlook connectors.I dislike the GW
client itself, and even strong supporters of it admit that for "basic
users" it doesnt have the look and feel of Outlook.

My only worry with Novell is they are moving very Linux based, and
whilst they state they are keeping the netware core and running it
alongside I wonder how long it will be before a big re-training exercise
may be needed. At that point I could see some companies retraining
people in MS rather than Linux.

Also if deciding check out the costs. Novell usually charge more per
client access, but less for the actual product. MS are usually more for
the product but less on client license. Therefore if you have a lot of
users it may make more fiscal sense to go Outlook

Additionally I dont know how well Groupwise would plug into say a Live
Comms Server, Project Server , Shaepoint server which can help end users
keep lots of information in one central location.

in disguise

Tony,

You may change your mind after reading a review on it.

http://www.eweek.com/article2/0,1759,1832958,00.asp