Rather old post and I've been away for a few days so sorry for delay in
reply, but..

Home Folders have absolutely nothing to do with local userprofiles, in fact
we used to allocate home folders on Netware 3.x servers for DOS clients, in
the dim and distant past. All you need to achieve this is some variable such
as %username% which can be included in a NET USE command (Or MAP for Netware)
so that the mapping is user-dependent.

The only client this won't work for is a laptop user - and they always are
the most difficult to cater-for satisfactorily. Point of fact, roaming
profiles don't work too well for laptop users either, since they will rarely
be in-sync with the local copy.

"Tim Meddick" wrote:

I'm talking about his [own] files on a shared [public] network drive.

If no profiles existed the user would have to keep any personal files on his own hd.

Any files he saved to a public drive would be visible to all!

WITH profiles - a user can store files on a networked public drive with his profile's
security credentials and access them from any console on the network providing he
logs in to his profile.

For example - I log in to any PC as %user% and get access to a "My Documents" folder
on the public drive.

Any files saved to this folder can be accessed again by logging into any other PC on
the network as %user% again.

No-one else but %admin% can "see" the files in "My Documents" even though they are on
the "public" drive.

==

Cheers, Tim Meddick, Peckham, London. :-)