Re: Linux Files Server with Netware 5 Directory Service
Edward van der Maas
>
> Hello All,
>
> I am virtually new to Novell products and ask for your knowledge and
> wisdom.
> Currently, I have Netware 5 server serving directory and file server
> services.
>
> I am looking for your advices on setting up linux file server but
> keeping this Netware for directory service.
>
> Does this mean, I have to use SLES or could I use RHEL?
If you want to use a File server on Linux the same was as NetWare
operates you want to use Open Enterprise Server on Linux. Open
Enterprsie Server is a set a services that run on top of SuSE Linux.
(RHEL is not supported).
OES will provide NSS, eDir, iPrint etc.
--
Cheers,
Edward
Edward van der Maas
>
> I see. Thank you for that.
>
> So it looks like I just need to purchase SUSE Linux Enterprise Server
> and renew subscription for updates and support.
>
> And for Netware compatibility I would run Open Enterprise Server on
> SUSE. With that I would be done with running file server separately
> from Netware.
>
> I do see that I can download Novell Open Enterprise Server with 60-day
> trial but I cannot seems to find any kind of pricing info. Do I just
> purchase a server-license??
I'd say so. I'm not very good with the whole license stuff. I generally
leave that to sales people :) Most likely someone else can answer this
question :)
> Next step would naturally be getting rid of Netware server since it is
> basically obsolete. At this point, I would have to decide on :
>
> 1) a new OES for eDir service
> 2) extend the SUSE OES file server to run eDir service (dont know if
> this is a good idea?)
> 3) migrate Netware to SUSE file server. I would need to setup SUSE
> with XEN (this case would be if i really need to keep Netware eDir.
> is this correct??)
When you build your new SLES server and then install OES you can add it
to the tree you already have in place. That way users will keep their
password, username etc. When you configure OES use two disks (or
logical arrays if you have a raid controllor). One is for the base OS
and one for the NSS volumes you'd like to host. Thats a lot easier then
having to configure EVMS when you only have one disk.
> I know in Windows environment, running DC/AD and file server would be
> a no-no. I have about 100 users on LAN and few lightly used appd
> would be on this server. For sure, it seems like eDir would be alot
> less than AD, and from what I'm reading OES2 sounds like a very good
> product.
If you purchase OES you are entitled to Novell Identity Manager I
believe. Novell IDM allows you to synchronise user accounts (and other
objects) between Active Directory and eDirectory. So even if you would
like to use AD you can do this quite easily without having the headache
of having to create users in two places. The user can then authenticate
to both AD and eDir using the same username and password.
--
Cheers,
Edward
David Gersic
> I know in Windows environment, running DC/AD and file server would be a
> no-no. I have about 100 users on LAN and few lightly used appd would be
> on this server. For sure, it seems like eDir would be alot less than
> AD, and from what I'm reading OES2 sounds like a very good product.
A single OES server can handle this load.
The reason you shouldn't mix Active Directory DC duties with file serving
is because when configured to be a DC, the Windows box disables file
caching, so its file system performance "inhales strongly".
--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com
Please post questions in the newsgroups. No support provided via email.