Search through the registry on the client machine - make any instance of
"c:\my documents" point to "h:\"
You could create a .reg file to make these changes, then apply them to
each machine.
Then you need to train the users to save their personal
shit^H^H^H^Hstuff on H drive (Home drive) and stuff that is shared on S
drive (shared drive)
Tell them that anything they choose to save on their C drive is not
backed up and dire things will happen if they don't use H and S drives.
Here's my home /netlogon/logon.bat
--------------------------
@echo off
net use h: /h
net use s: \\caffeine\shared
net use t: \\caffeine\tmp
net time \\caffeine /set /y
net use lpt2 \\caffeine\lp
\\caffeine\netlogon\rwhodwin.exe
exit
rem this script requires control M chars at the end of each line
rem that is - it must be a DOS batch file.
-----------------------------
This line might do better for use as the H: mapping
net use h: \\caffeine\homes
On Sat, 2002-11-30 at 10:33, Andrew J Sands wrote:
>
> I'm back.....
>
> For the "professional" site admins on the list, would it be possible for you
> to share thoughts or ideas on SAMBA client logon scripts...what you use?
> Helpful hints? Pitfalls...etc
>
> My site has sub-15 clients BUT reassigns workstations on an as available
> fashion. They're mostly Windows98SE and I'm wanting to find a way to
> centralise the document storage with the least amount of client confusion
> cause most of my present problems are "PEBKAC" related!!
>
> Alternatively how dangerous is it to smbfs mount the drive in the client and
> maybe rsync the contents. Thoughts, pitfalls, fables, religious quotes are
> all welcome.
