I've searched and read the forum looking for an answer to why Win9x clients refuse to bind the fileserver homedir+userid to a logical drive (H:\)... I thought I found the answer in the topic "Sharing", but that did not work either... :(

The problem:
Win9x clients bind H:\ to the the fileserver "Users" directory, when I want it to be fileserver+Users+userid (in my case \\xntsrv1\users\@userid).

The WinNT 4 sp5 fileserver has D:\User as the shared dir \\xntsrv1\Users.

How should I configure User manager for domains to get KIX working for binding the correct path to H:\ ? I've tried \\xntsrv1\Users\%username% together with the following KIX scripts:

#1:
$Home = "\\xntsrv1\users\" + @USERID
USE H: /DEL /PERSISTENT
USE H: "$Home"

#2:
$Home1 = "\\xntsrv1\users\"
$Home2 = @USERID
$Home = $Home1 + $Home2
USE H: /DEL /PERSISTENT
USE H: "$Home"

Neither of 'em works... i'm getting gray hairs here... help!

none of the shares on the fileserver is hidden, do I have to hide the perhaps?

Dammit, there MUST be a solution for this common problem?

Discussing Deep root mapping, i have resently posted a script to create a hidden share for each user
If you can live with all these shares it it a possible solution for Win9x clients.

Erik

; IF <> NT MAP HOMEDRIVE THIS WAY
IF @INWIN<>1
USE F: $FS+@USERID+"$"
ENDIF

; WinNT
IF @INWIN=1
USE F: @HOMESHR
ENDIF

?

The common practice is to name the directory @userid$ and share it as the same.

Then map to it with use X: \\server\@userid$

------------------

"He was a good little monkey and always very curious..."

(darn i'm stupid sometimes, but have mercy, i'm a newbie :)

hmmm... what's missing now is an automated way for making the @USERID$ directory if it's missing... (eg, a new user is logging on, and I haven't made his/her share dir on the server).

Erik had some idea's on this...

Thanks every1

PS. This is not uniquely a Win9x problem rather it is an NT problem. NT can not do "map rooting" or "deep mapping" either. Rather, NT has a trick feature built-in so when NT-workstation talks to NT-server it can connect to special pseudo-share created by NT-server. This special user directory is not a true share & thus not hidable. These special shares are useless with any client other than WinNT or Win2000 clients.

[This message has been edited by JackLothian (edited 08 December 2000).]

echo Creating a new personal folder for %1 on fileserver %fs%
echo If you don't want to do this, press CTRL-C now!
echo Otherwise, press any other key.
pause

net use x: /delete

net use x: %fs%\SYS1\HOME

REM Create new directory
md x:\%1

REM Allow user access to their own directory (in addition to Domain Admins)
cacls x:\%1 /e /g "domainName\%1":f
rem cacls x:\%1 /g "domainName\'domain admins'":f

REM Deny "Everyone" access
cacls x:\%1 /e /r everyone

net use x: /del

REM Create a share for the new directory
rmtshare %fs%\%1$=D:\SYS1\Home\%1
rmtshare %fs%\%1$ /g everyone
rmtshare %fs%\%1$ /g "domainName\%1":f
rmtshare %fs%\%1$ /g "domainName\Domain Admins":f
rmtshare %fs%\%1$ /remark:"%1's Personal Files"

These utilities will not run properly from a Win9x machine so Win9x clients can not automatically create home shares.

Here is a possible template for a bat file creating a new user. Using the FOR command you can adapt it so it reads a text file containing the appropriate user info for any number of accounts. I recommend running it from the server.

NET USER %USERID% %password% /add
NET USER %USERID% /scriptpath:LOGON.BAT /passwordchg:no /passwordreq:yes
NET USER %USERID% /times:M-F,7AM-6PM
NET USER %USERID% /fullname:%fname% /comment:%comment% /expires:%edate%
NET GROUP STUDENT %USERID% /ADD

MD d:\USERS\Z%USERID%
XCACLS.EXE D:\USERS\Z%USERID% /t /c /g administrator:fo;fo webmaster:f;f %USERID%:f;f /y
NET USER %USERID% /homedir :\USERS\Z%USERID%
RMTSHARE \\server\%USERID%$=D:\USERS\Z%USERID% /grant %USERID%:f users:2 /remark:%FNAME%
RMTSHARE \\server\%USERID%$ /grant administrators:f
RMTSHARE \\server\%USERID%$ /grant %USERID%:f