Netware 4.11 Groupwise 5.5 Netware 6.5 Groupwise 7 migration

Question

The setup is as follows:
Server 1 - NW4.11 SP9 (DS611) and Groupwise 5.5
Server 2 - NW5.1 SP6 (DS7.61) and Groupwise 5.5 POA
Server 3 - NW4.11 SP9 (DS611) and Groupwise 5.5 POA
Server 4 - NW4.11 SP9 (DS611) and Groupwise 5.5 POA.
We are to replace all 4 servers with OES Netware 6.5 and Groupwise 7.
Ideally a new tree would be benefical in order to have a fresh new
structure.
I am looking for the best migration path between the above current setup
and the new:
Server 1 - NW6.5 and Groupwise 7
Server 2 - NW6.5 and Groupwise 7 POA
Server 3 - NW6.5 and Groupwise 7 POA
Server 4 - NW6.5 and Groupwise 7 POA
Regards

Answer 1

Scott,
Thanks for your response, I will digest the information given.
Could you please send me your email address in case I require further
info or your kind offer of remote support.
Many thanks
Tas
[email protected]
> Here is how I would do the project:
>
> Update your NW 4.11 servers to DS 6.21c (the last rev and one required
on
> all NW 4.11 servers in order to put an eDirectory-based server (NW 6.5)
into
> your existing tree. Also you need to update your DS 7.61 server to DS
> 7.62c.
>
> If you use the Deployment Manager (NWDEPLOY.EXE) on the NW6.5 SP6
overlay OS
> CD, you can check the tree for versions of DS that will work with
eDirectory
> 8.7.3.x.
>
> Next, I would install NW 6.5 SP6 and put it into your existing tree. I
> would check schema synchronization (set dstrace=nodebug; set
> dstrace=+schema; and set dstrace=+ss) on each server to make sure there
are
> no errors and the major schema update that occurs with the introduction
of
> eDirectory.
>
> I would add each of the other NW 6.5 servers before I do anything with
> GroupWise.
>
> When all NW 6.5 servers are in and your tree is happy, per a health
check
> you will be ready to copy with the TOOLBOX.NLM all of your GroupWise
> components over to the various new NetWare 6.5 servers. Obviously,
you'll
> have all of GroupWise shutdown during this process. TOOLBOX.NLM is very
> fast and easy to copy GW data to a different NW server. The Server
> Consolidation/Migration utility works well too but I prefer Toolbox.
>
> Once the various pieces of the GW system are copied, it is time to
install
> the GW 7.01 agents to make the upgrade to GW 7.x occur.
>
> 1) Build a software distribution directory on one of the NW 6.5 servers
with
> 7.0.0 code; update it to SP1 and then put the IR1 code over the top of
that
> BEFORE you run the install to put the POA/MTA agents in place.
>
> 2) Make a copy of the primary domain database.
>
> 3) Using the 7.0.1 (IR1) agent software, install the agent software to
the
> Primary domain server and load just the MTA. Let the Primary Domain
update
> to 7. If there is a PO on that same server, load the POA and let the PO
> update to version 7.
>
> 4) Do the previous step on each server that holds a GW component until
all
> domains and pos are at 7.
>
> 5) Verify the database paths and IP addresses on each domain and po and
then
> rebuild each database.
>
> 6) Install a new GWIA and a new WebAccess.
>
> 7) Rename all of the directories that held GroupWise components on your
OLD
> servers so that there is no chance to successfully load the old NLMs.
>
> Contact me via email if you'd like further help. I believe I could
help you
> via remote control.
>
>
>
> Scott Kunau, CDE, MCNI
> eDirectory/GroupWise Consultant
> Innovative Global Technology Group
> Cincinnati, Ohio
>
>
> >>> On 2/26/2007 at 7:35 AM, in message
> <[email protected]>, <[email protected]>
> wrote:
> > I have seen that document, the thing that worries me is that Netware
4.11
>
> >
> > is not covered.
> >
> > How about if I wanted to keep the same tree, install the new NW6.5
> > servers within it and then migrate the Groupwise 5.5 system (running
on
> > NW4.11) onto a new NW6.5 server running Groupwise 7?
> >
> > Thanks in advance
> >
> >
> >
> >
> >
> >> Try TID10007622
> >>
> >> --
> >> Timothy Leerhoff
> >> Novell Support Forum Sysop