Danita,
Thanks for your reply and for the most part, I figured as much but wanted to know just what I needed.
We are going to migrate NetWare 6.0 with G/W to OES2/SLES and of course I am looking for the best way to keep G/W working, and I gather it should stay on the same server since using ID-transfer in Migration changes that.
Given what you presented I will perhaps rename the source N/W server, making the appropriate UNC mappings at the G/W primary domain, and with client server IP addresses being modified thus not employing ID-transfer.
And if you and others have suggestions I shall be indebted to all
Originally Posted by dzanre
|
MeekTJ wrote:
>
> At the moment I have G/W 6 running a NetWare 6.0.5 server. I will be
> migrating the file system to a OES2 SP1 Linux server. We are running
> eDirectory 8.7.3 for the time being.
Well, you do not say what version of GroupWise you plan to put on your OES2
SP1 Linux server - because GroupWise 6.0 will not work! In fact, of course,
there is no GW6.0 for Linux. You will need to go at least with GW7, but GW8
is your best bet.
And yes, you technically CAN leave the data on the current NSS volumes and
migrate it over, but it isn't the best possibility because there are many
NSS settings from your NetWare volume that aren't as efficient on Linux.
While you might very well want an NSS volume on Linux for GW, we really
recommend that you create a brand new NSS volume, using settings that are
more appropriate for the Linux NSS and move the data over.
--
Danita
Novell Knowledge Partner
Moving GroupWise to Linux?
Moving GroupWise
|