Groupwise 5.5 to Groupwise 6.5 server clients

I have a bit of problem and not sure which way I should tackle this one.

I have 2 x Netware 4.11 servers, which will be upgraded to Netware 6.5 and
one of these servers have Groupwise 5.5 which will be upgraded to Groupwise
6.5.

The one server is being used for Groupwise archiving and currently setup for
UNC for archiving, i.e. p:\ab_hp, on this server I was planning on using
the migration wizard as this server also holds the user data. On the 2nd
server which Groupwise is running and the clients are configured for tcp/ip
connectivity to the groupwise system. This server only holds the Groupwise
database and no user data files.

Because this server is running Netware 4.11 the consolidation utility does
not support Netware 4.11.

As you see, the 2nd server holding Groupwise is the problem, as the clients
are configured for ip address connectivity and going to 200 workstations to
change the ip address is not suiteable.

Does the Groupwise 5.5 client search the NDS tree and find the post office 
and change the ip address automatically or do you have to change the 
groupwise clients to point to the new Groupwise server POA ip address?

Thanks

John 9/9/2005 12:20:00 AM

Create a DNS entry in your system (or update the workstations host
file if you have no DNS)   This entry should be called NGWNAMESERVER
If you create that now and point that at the existing GW system it
will work.To prove that, open a GW client on a brand new workstation
that has never connected and leave the IP address blank, it will find
your PO.

When you change the IP address of the PO, update the DNS and the
clients will follow when you next connect.



On Fri, 09 Sep 2005 00:20:00 GMT, "John"  wrote:

>I have a bit of problem and not sure which way I should tackle this one.
>
>I have 2 x Netware 4.11 servers, which will be upgraded to Netware 6.5 and
>one of these servers have Groupwise 5.5 which will be upgraded to Groupwise
>6.5.
>
>The one server is being used for Groupwise archiving and currently setup for
>UNC for archiving, i.e. p:\ab_hp, on this server I was planning on using
>the migration wizard as this server also holds the user data. On the 2nd
>server which Groupwise is running and the clients are configured for tcp/ip
>connectivity to the groupwise system. This server only holds the Groupwise
>database and no user data files.
>
>Because this server is running Netware 4.11 the consolidation utility does
>not support Netware 4.11.
>
>As you see, the 2nd server holding Groupwise is the problem, as the clients
>are configured for ip address connectivity and going to 200 workstations to
>change the ip address is not suiteable.
>
>Does the Groupwise 5.5 client search the NDS tree and find the post office 
>and change the ip address automatically or do you have to change the 
>groupwise clients to point to the new Groupwise server POA ip address?
>
>Thanks
>
>

Tim
___________________
Tim Heywood (SYSOP)
NDS8
Scotland
(God's Country)
www.nds8.co.uk
___________________

http://support.novell.com/forums/

In theory, practice and theory are the same
In Practice, they are different

Tim 9/10/2005 8:08:50 PM

Reply:

(Thread closed)