Re-reading many message threads in this and other forums, I'm
confused. For SLED, LUM creates users accounts on-the-fly after eDir
login (like DLU on ZEN on Windows), the Novell client reads login
scripts and maps drives (like on Windows) but integration with LUM is
less than transparent, and there may or may not be plans to support
roaming profies, without which settings and user document folders are
stuck on each machine the account was created on, making it very
difficult to support without mass confusion.

I run a college network. If we are to have a chance to make people
interested in an alternative to Windows, all those functions must be
transparent to users (as it is with the Windows client and ZEN) --
they authenticate to the directory, their local account is created,
they get their network resources, and their roaming profile settings
and locations are as expected. They logout, their info is safe on the
network, their account is deleted. They go to the next class in a
different lab and repeat. This happens thousands of times per day in
30 different labs with students of wildly different capabilities and
expectations. But it just works.

This has been the Novell experience since the beginning (16 years for
us). It is still valid. Anything less than this makes SLED an
unworkable alternative. I'm looking for a way to make it workable. By
summer we'll have 1200 XP/SLED dual boot machines in labs and offices.
To make SLED a viable alternative we need those other features.
Otherwise, it's just a toy for the curious. Unfortunate.

So, here are my end of year questions:

Which of these fundamental functions are working with which others?

Which ones are in the SP beta plans?

Which ones are not being planned?

What is the process for helping the planners understand the needs of
the users out here?