Running Sharepoint on a Novell Network

[swertel]

Is it possible to run sharepoint on a novell network. The isntructions say that it should be loaded on a Win2K Server or Advanced Server.

That may be feasible, but what about all the clients? Has anyone set up a functioning sharepoint system on a Novell server that could give us some extra hints?

I read that the client side has to map to the network "m" drive in order to move files around. How do the users like this? Do they get confused?

Basically, I'm looking for all the problems we may encounter when we implement sharepoint and tip-and-tricks to make the implementation smoother.

Thanks for your comments.

--Scott

 

[robsond]

Scott,
how did you get on with resolving your question? I am interested in Novell authentication. Got any tips?

Thanks

Dean

 

[swertel]

We bought a new server and loaded Win2K Advanced Server on it. We set up Sharepoint on this server and are migrating data we want to manage in little bits at a time. (Alas, I fear some day Novell may not be needed.)

As far as the client side, things are a pain. Everything functions well, but the clients don't have all the useful Novell utilities when dealing with the Win2K Server.

Basically, I still have all the same mapped drives. Some point to the Novell server, others to the Win2K server. My login script takes care of what I'm mapped to and the script is controlled by our IT department. The server OS is completely transparent to the client, except when I accidently delete something and need to salvage it, which I can't from the Win2K server. (Call help desk... please restore from backup! When will M$ make a useful server-side recylce bin?)

In order to actually utilize the Sharepoint Workspace, we just had to load the Sharepoint client on the machine and create a "Network Place" to point to the managed workspace. (We can also use the dashboard.) Problem is now I have a mapped drive and a network place that point to the same location. Using the network place utilizes sharepoint and all its useful tools, the mapped drive does not, resulting in broken links and non-maintained revisions. This is where I thought the "m" drive I mentioned in my original post came into play.

Still more testing.