We're just getting into migrating (actually in the process of going through
Novell's On-Demand courses) from NetWare to OES2.

Unfortunately (because we're not yet "experts" in Linux), I have a request
to provide Linux to two of our researchers and the proposed solution is to
give them access to a SLES or OES2 server using Cygwin from their Windows XP

Without yet having even installed OES2, I have a few questions:

1) Is it resonable to propose this solution of using Cygwin to X-Windows
into SLES or OES2 for these two users? We would install the applications
they require like SAS and a few other applications and give them limited

2) If this is a resonable solution, is it considered safe to give users this
type of access to our OES2 server? I'm a NetWare guy and remote access to a
NetWare server is inconceivable to me, except for administrators that need
to reach the console screens. Otherwise, its iManager, ConsoleOne to manage
services and users reach NetWare services by logging into eDirectory and
reaching NSS, iPrint, ZENworks, etc...
I'm just concerned that if these users would have too many privileges, they
could mess around with eDirectory by adding replicas etc... ?

3) The reason we think that it would be better to give them access to Linux
via an OES2 server is to possibly simplify authentication. From what I
understand, login to this Linux server can then be done using their
eDirectory account. I'd rather avoid having to administer new accounts on
this OES2 server in case access requests to this server grow.

4) If OES2 X-Windows access is not a good idea for end users, should we then
provide this using just SLES? With just SLES, any possibility to benefit
from authentication against our eDirectory or AD (which are in synch using
IDM) ?

5) If all of the above are a bad idea, I imagine you'd suggest just given
them SLED on a local workstation. Correct?

Thanks for any help and sorry if questions are very newby.