Steps to move GroupWise 6.5 mail and DMS from NetWare 6.5 to Windows 2003?
We currently run GroupWise 6.5 on NetWare 6.5 and will be moving our network to Windows 2003 Server with AD. We are using GroupWise for both email and DMS and would like to move it over.
What are the steps we need to take to move GW and get the email and DMS over to W2K3?
What are the steps we need to take to move GW and get the email and DMS over to W2K3?
ASKER
Thank you for your reply, but that's not what I meant. What I'm looking for is a way to keep GroupWise running in an AD environment without NW servers. I understand eDirectory can be installed on AD to facilitate this, but then I need to migrate GW over.
Also, our GroupWise is not just email, we are also using it as a DMS. I have not been able to find much documentation on a move like this, especially pertaining to the DMS.
Also, our GroupWise is not just email, we are also using it as a DMS. I have not been able to find much documentation on a move like this, especially pertaining to the DMS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
One other thing I didn't mention, is that you will need to install eDirectory onto a Windows server and put that Windows server into your eDirectory tree BEFORE you remove your NetWare servers. All GroupWise schema information will be automatically transferred to your new eDirectory/Windows server.
You can run eDirectory on the same server as you are running an AD domain controller but you'll have to change the LDAP ports from 389 to 390 and 636 to 637 (something different) when installing eDirectory otherwise LDAP won't work and you'll have a variety of problems. It is best, if you can to run eDirectory/GroupWise on a member server instead of a DC if you can.
Scott Kunau
You can run eDirectory on the same server as you are running an AD domain controller but you'll have to change the LDAP ports from 389 to 390 and 636 to 637 (something different) when installing eDirectory otherwise LDAP won't work and you'll have a variety of problems. It is best, if you can to run eDirectory/GroupWise on a member server instead of a DC if you can.
Scott Kunau
Have you considered migrating Groupwise and eDirectory to Linux? Novell's OES2 is SuSE Enterprise 10 with all the traditional Netware services ported over.
It would save you the requirement to run a legacy directory service like Active Directory on a legacy OS like Windows.
It would save you the requirement to run a legacy directory service like Active Directory on a legacy OS like Windows.
ASKER
alextoft: Yes, Linux has been considered but is not possible due to constraints we're under.
ZENandEmailguy: You solution looks like what we need, it will take a few days to set up and do a dry run - will post how it goes.
ZENandEmailguy: You solution looks like what we need, it will take a few days to set up and do a dry run - will post how it goes.
Alextoft: I would agree as I've moved several NetWare-based GroupWise systems over to OES2-Linux. eDirectory is in place and NSS volumes (suggested for GroupWise) make management no different than if the GW system is on NetWare. Novell Cluster Services on either NetWare or OES2-Linux work the same too.
Paulsolov: I'd be happy to help via remote control if you'd like...
Paulsolov: I'd be happy to help via remote control if you'd like...
ASKER
This does the migration nicely. We'll be testing for the next while and if any specific troubleshooting is necessary we'll post under a new question. Thanks again!
http://www.msexchange.org/articles-tutorials/exchange-server-2007/migration-deployment/groupwise-exchange-2007-interoperability-migration-part9.html