Link to home
Start Free TrialLog in
Avatar of dennmaine
dennmaine

asked on

Netware - Groupwise Migration

Hello EE
  I have reached a sad day in my career,  I've been tasked to plan the migration from Netware 6/5.1 Edirectory 8 to Microsoft Windows 2003 server utilizing AD.   Here is my question:  I have 3 Netware servers one running NDPS for printing,  the second is a primary File server (part of a SAN),  the third is our GroupWise Email server,  in this scenerio what is the best way to remove Netware as an OS?   The constraints are:  We are keeping GroupWise and running it from a Windows platform.  Our users currently obtain access to network resources via login script delivered mapped drives.  Is it possible to remove Netware completely and run Edirectory from a Windows server for GroupWise administration purposes?  

The literature I get from Microsoft focuses on a GroupWise to Exchage migration (out of scope).   the literature from Novell seems to focus on a migration from Netware to Linux (an avenue I'd rather avoid).  Any information,  white papers or advice would be greatly appreciated.

-Dennis


 
SOLUTION
Avatar of PsiCop
PsiCop
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hmmm....allow me to clarify. GroupWise doesn't need your users to be managed in the same directory service as the application runs. I was offerring that as a contrast to how AD/W2K3/Exchange operates. But I was unclear.
Avatar of dennmaine
dennmaine

ASKER

Thank you ShineOn & PsiCop for your responses.  I currently run GroupWise 6.5 SP 2 and will remain on this version when moving over to Windows.  I did find some documentation on LDAP authentication (we are set this way currently).

-Dennis


 

At any rate, ignore the documentation you see from the Microsoft site re: GroupWise.  They don't want you to know how to manage any email/collaboration system that isn't Exchange/Outlook based.

You should look into ways to synch your AD users with eDirectory and vice-versa, to simplify administration.  

You mention using LDAP authentication.  That's too bad - Windows 2003 LDAP services is not fully LDAPv3 compliant.  There are lots of "not fun"  (aka "horror") stories out there of folx trying to get LDAP working properly on Windoze/AD.  You may want to consider an open-source LDAP server to provide LDAP authentication services.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
"for migration of edirectory I would get a product from Microsoft called services for netware...can also sync between the two such as password"

I wouldn't. I've used it and its garbage. I'd get DirXML and use the AD connector to sync the passwords and file permissions between the environments.
If the only function being synchronized is the GroupWise/NDS passwords I would think the LDAP implementation would be the cleanest.   ShineOn do you have any recommendations for open source LDAP solutions?  Thank you qjohnson99 for the feedback it's definitely helpful in planning  the actual cutover to a Windows implementation of GroupWise.


-Dennis
"Is it possible to remove Netware completely and run Edirectory from a Windows server for GroupWise administration purposes?"

Yes.

Oh - another note on the LDAP thing - eDirectory is fully LDAPv3 compliant (to my knowledge) and will act as your LDAP server after it's installed on Windoze.  I forgot about that.

Just make sure you set it up to use eDirectory for LDAP authentication services and not the crap LDAP service that comes with AD...  You shouldn't need OpenLDAP.
The Windows LDAP Work fine and has good support.
Windows LDAP is not worthy of use.  Since they will have eDirectory, which has excellent support, it makes no sense to use a half-baked LDAP.
I agree with ShineOn - Microsoft's implementation of LDAP in AD is pathetic at best.  It's not even LDAPv3 compliant.